Viewing 16 posts - 1 through 16 (of 16 total)
  • Author
    Posts
  • #1012484

    Hi,

    I have a problem. My footer has a different display between the page N ° 1 and all the other pages of the web site.
    I use the back office enfold feature that allows me to use a page as a footer and socket, so I do not use widgets. And this system does not look good with woo-commerce. How can I do ?

    Thanks

    #1012674

    Hey pixeet2016,

    Try adding this css code in Quick CSS (located in Enfold > General Styling):

    .postid-736 .container_wrap_first.container_wrap.sidebar_right .container {
        max-width: 100%;
        width: 100%;
        padding: 0;
    }
    
    .postid-736 .container_wrap_first.container_wrap.sidebar_right .container .content.av-content-small {
        width: 100%;
    }
    
    .postid-736 .container_wrap_first.container_wrap.sidebar_right .container .content.av-content-small .entry-content-wrapper {
        padding-right: 0;
    }

    Let us know if this helps.

    Best regards,
    Nikko

    #1012701

    Hi,

    With your code the display is better but it still looks different from the other pages. The content area is 100% instead of 1310px, it should be limited and for the footer the blue zone should not be 100% either but the map must be 100%. How can I correct this?

    Thx for your help

    #1012930

    Hi,

    If you remove the .postid-736 it will show better for sure.

    Thank you :)

    Best regards,
    Basilis

    #1013665

    Hi,

    I think you did not understand. The correct display is the one present on all the pages of the site and the bad one is on the page postid-736. So I think I have to target css postid-736 not remove it.
    I would like that the footer is identical on all the pages. It is not normal that on postid-736 the display is different, and i don’t understand why. How can I fix this bug?
    I added the code of your first answer, but the display is still not correct, as you can see if you compare postid-736. at all other sites of the site.

    Thx !

    #1013733

    Hi pixeet2016,

    Please post us your login credentials (in the “private data” field), so we can take a look at your backend.

    1. Install and activate ” Temporary Login Without Password “.
    2. Go to ” Users > Temporary Logins ” on the left-side menu.
    3. Click ” Create New “.
    4. Add the email address for the account ( you can use (Email address hidden if logged out) ), as well as the ” Role ” making that the highest possible and the expiry about four days
      ( do be sure that we have enough time to debug ).
    5. Click ” Submit “.
    6. You’ll now have a temporary account. Please provide us here in the private section the URL, so we can login and help you out.

    When your issue is fixed, you can always remove the plugin!
    If you prefer to not use the plugin, you can manually create a admin user and post the login credentials in the “private data” field.

    Best regards,
    Nikko

    #1015221

    Hi,

    Did you had time to look at my problem?
    I gave you in private the access to my back office. Have you had them?

    Thx

    #1015352

    Hi pixeet2016,

    Best regards,
    Victoria

    #1015539

    In fact the problem is related to the enfold theme.

    I created a product with woo-commerce. And the display of the footer is problematic. The footer is not created with the widgets but with the new system implemented in enfold which gives the possibility to manage the footer as a page and to set this page as a footer in the enfold options. If the footer is created with widget it works but if it is created with the pages (and i want it like that) there is an incompatibility between the two.
    The bug is only visible on the page product test and the page gift card. To my mind the display problem of my footer come from an incompatibility between the footer and the publisher. And it is not normal that i can not use the woo-commerce with with the new footer system.
    Can you help me to solve this bug ?

    Thx

    #1016047

    Hi pixeet2016,

    I noticed that the bug only appears on product pages that aren’t using Avia Layout Builder.
    Can you try to switch those pages that has those issues.
    For the meantime, I have added this code to fix the product pages that has those issues.

    .single-product .container_wrap_first.container_wrap.sidebar_right .container {
        max-width: 100%;
        width: 100%;
        padding: 0;
    }
    
    .single-product .container_wrap_first.container_wrap.sidebar_right .container .content.av-content-small {
        width: 100%;
    }
    
    .single-product .container_wrap_first.container_wrap.sidebar_right .container .content.av-content-small .entry-content-wrapper {
        padding-right: 0;
    }
    
    .single-product .container_wrap_first.container_wrap.sidebar_right br {
        display: none;
    }
    
    .single-product .container_wrap_first.container_wrap.sidebar_right .av_iconlist_title br {
        display: block;
    }
    
    .single-product .container_wrap_first.container_wrap.sidebar_right .av_gmaps_main_wrap {
        padding-bottom: 50px;
    }
    
    .single-product .container_wrap_first.container_wrap.sidebar_right .flex_column_table,
    .single-product .container_wrap_first.container_wrap.sidebar_right 
     .av_textblock_section {
        max-width: 1210px;
        margin-left: auto;
        margin-right: auto;
    }
    

    Best regards,
    Nikko

    #1016151

    I’m sorry but there is still a problem.
    The first container (the product part) must not be 100% wide, but the card in the footer must be in 100%.
    How can I fix this problem ?

    #1016174

    Hi!
    I fixed it by adding this code to the child theme functions.php

    
    add_action('ava_before_footer', 'avia_footer_fix_products' );
    function avia_footer_fix_products()
    {
    	global $avia_config;
      
      	$the_id 				= avia_get_the_id(); //use avia get the id instead of default get id. prevents notice on 404 pages
    	$footer 				= get_post_meta( $the_id, 'footer', true );
    	$footer_options			= avia_get_option( 'display_widgets_socket', 'all' );
      
        if( false !== strpos( $footer_options, 'page' ) )
        {
          /**
          * User selected a page as footer in main options
          */
          if( ! in_array( $footer, array( 'page_in_footer_socket', 'page_in_footer', 'nofooterarea' ) ) ) 
          { 
            $avia_config['layout']['current'] = array('content' => 'av-content-full alpha', 
                                                      'sidebar' => 'hidden', 
                                                      'meta' => '', 
                                                      'entry' => '',
                                                      'main' => 'fullsize');    
            $avia_config['conditionals']['is_builder'] = true;
            $avia_config['conditionals']['is_builder_template'] = true;
          }
        }
    }
    

    The css code is not required. I’ll report it as a bug to our developers and ask them to include a fix with the next update.

    Best regards,
    Peter

    #1017445

    Hi,

    I’m really sorry but the bug is still not fixed.
    My gift card page is always 100% wide while the rest of the site is limited in width. The difficulty of the bug is to manage the fact that part of the footer is in 100%, the blue zone of the footer has a limited width and the content of the page also has a limited width (which is not currently the case) could you help me to fully resolve this bug?

    I added your code in my function.php file and commented the css.

    #1017573

    Hey!

    I added to Quick CSS:

    
    #main > div.sidebar_right:first-child{
    	max-width: 1310px;
    	margin: 0 auto;
    }
    

    This fixes the problem on the page in private content.

    Cheers!
    Günter

    #1017905

    Hi,

    It’s fixed.

    Thx

    #1017964

    Hi pixeet2016,

    Glad that we could help :)
    Feel free to comeback if you need further assistance.
    Thanks for using Enfold and have a great day!

    Best regards,
    Nikko

Viewing 16 posts - 1 through 16 (of 16 total)
  • The topic ‘Footer bug’ is closed to new replies.