Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
  • #244102

    When I change the regular menu item to mega menu the mega menu is cut to the size of the name of the menu item. The regular menu works fine. What do I do to fix the mega menu so it shows normally? Thank you for your help. A.



    Can you post the link to your website please? please activate the megamenu so we can take a look.



    I was working on fixing the WPML issue. Here is the link to the site: http://www.kfbl.edu.ba/wp/



    Thank you for using the support forum!

    I’m sorry but we’re not entirely sure what is causing this issue. If you don’t mind resetting the menu and logo position options on Enfold > Header > Header Layout that would be great. Change the settings to another option then change it back. Additionally, I noticed that your installation has a memory limit of 40M which might cause the Advance Layout Builder and the Layer Slider to hang on some circumstances. You might want to increase the wordpress php memory limit to at least 128M. The first thing you can do to remedy this is to enter the following lines in your wp-config.php file at the root of your installation:

    define( 'WP_MEMORY_LIMIT', '128M' );
    define( 'WP_MAX_MEMORY_LIMIT', '256M' );

    You can also contact your host if you’re not comfortable doing the adjustments yourself. Refer to this link for more info: http://dailyblogging.org/wordpress/increase-wordpress-memory-limit/



    Thank you. I’ve increased the memory in the wp-config.php. The mega/menu works fine in the logo left menu right position. It does not work well whenever the logo is above the menu.



    Thank you for the info. I can see the issue now.

    Please add this on Quick CSS or custom.css for a temporary fix:

    #header_main_alternate .avia_mega_div {
    left: -700px !important;

    Adjust the left position if necessary. Don’t remove the !important tag. We’ll investigate the issue further.

    Best regards,

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.