• Stefan Matei

    (@nonsalant)


    Since updating to 2.1.3 the Megamenu CSS only works on the home page, leaving the other pages with a broken menu. If I change “Output in <head>” the CSS is applied on all pages, but I’d rather keep this in a separate file (“Save to filesystem”).

    This is what I have in the source code of the home page (where the menu still works):
    <link rel='stylesheet' id='megamenu-css' href='http://www.eatingfromthegroundup.com/wp-content/uploads/maxmegamenu/style.css?ver=50ff6b' type='text/css' media='all' />

    And this is all the other pages, where the menu is broken:
    <link rel='stylesheet' id='megamenu-css' href='http://www.eatingfromthegroundup.com/wp-admin/admin-ajax.php?action=megamenu_css&ver=1.8.2' type='text/css' media='all' />

    Any advice?

    https://wordpress.org/plugins/megamenu/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author megamenu

    (@megamenu)

    Hi Stefan,

    The Output vias admin-ajax option was completely removed in the latest version (because it can be really slow), so I don’t understand why you’re still seeing traces of it on your site. Are you using any caching plugins or something like cloudflare?

    Please also check that the wp-content/uploads/maxmegamenu folder and the wp-content/uploads/maxmegamenu/style.css file are writable (if it is not then the CSS output option will automatically switch back to Output in head).

    Regards,
    Tom

    Thread Starter Stefan Matei

    (@nonsalant)

    Hi Tom,

    The stylesheet file and the maxmegamenu folder (from /uploads/) are both writable.

    I also don’t have any caching plugins active and we’re not using cloudflare or any other CDN.

    Thanks,
    Stefan

    Plugin Author megamenu

    (@megamenu)

    Hi Stefan,

    Please can you:

    1. go to Mega Menu > General Settings and change the CSS Output to “Save to filesystem”.
    2. go to Mega Menu > Menu Themes and save the theme.
    3. go back to Mega Menu > General Settings and check the CSS Output option.

    If the CSS Output option has changed back to “Output in <head>” then it means the plugin has been unable to write the new CSS to the filesystem.

    Regards,
    Tom

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘CSS Output to filesystem stopped working in the latest update’ is closed to new replies.