Combining CSS Issue With Noo Menu

[bigboytravelCustomer Topics: 3 Posts: 14]

I use WP Rocket to cache my site and have noticed an issue with NooMenu whenever I select "Combine CSS files" as it breaks NooMenus which are below the mobile/responsive breakpoint.  This issue either jumbles the dropdown mobile menu when the toggle is open or prevents the toggle from opening the menu at all depending on what type of phone you are on.

I have found that I can exclude the path /wp-content/plugins/noo-menu/(.*).css when combining the site's CSS which fixes the mobile NooMenu issues but creates weird issues with my website which has the Enfold theme and isn't a viable option.

I used to have the same problem with Noo Menu when combining JS but I was on version 1.3.2 and that was fixed by going to version 1.4.1 which is the newest but is still 2 years old.  Have had the same problem with Noo Menu with other caching/minifying plugins and WP Rocket is one of the top 3 on the market.

Any plans to update Noo Menu to be better compatible with minified/combined CSS & JS since a lot has changed since the last update 2 years ago?

Jon

Add New Note to this Reply

[bigboytravelCustomer Topics: 3 Posts: 14]

If you are doing an update to fix the Combine CSS issue it would also be great to have an option to select "Font Awesome" already loaded in theme, ect as the plug pulls resources and external requests to serve Font Awesome even when it's not needed. Could maybe even consider loading the base mobile toggles for NooMenu as icon/png instead the plugin instead of pulling external files.

Add New Note to this Reply

[JackieNooTheme Topics: 0 Posts: 3537]

Hi.

Thank you for contacting us.

We will check our plugin to fix the issue with Woo Rocket and minified/ combined CSS JS in next version.

Please wait for us.

Thank you.

Jackie.

Add New Note to this Reply

[bigboytravelCustomer Topics: 3 Posts: 14]

Jackie,

Thank you for the update.

In addition to the mobile toggle/menu issues with minified/ combined CSS, it also seems that WP Rocket has a hard time properly including NooMenu in it's auto-generated Critical path CSS when you select the option Optimize CSS delivery.  The issues are seen as won't carry over NooMenu text styling in Edge, and NooMenu disappears after a second in Safari & Firefox, but works okay sometimes in Chrome.  The Critical path CSS is an issue across the board below the mobile breakpoint however.

I'm using WP Rocket 2.11.7 but have noticed the same issue back to version 2.9 as well as with other major caching/minifying plugins.  I also have it set up in a staging environment.

Thanks again,
Jo

Add New Note to this Reply

[JackieNooTheme Topics: 0 Posts: 3537]

Yes. Thank you for noticed. We will check the issue with WP Rocket again.

Thanks.

Jackie.

Add New Note to this Reply

[Author]

Posts