bobmorain

Having the same issue with mobile hamburgur menu. The dropdown menu is not opening with polylang V 3.0.6 activated.

Same error here, any solutions?

Hi,

I’m using Litespeed cache and Woocommerce 4.5.2. Cleaning the cache does not fix it. It seems the issue targets products randomly. For some products the variation label appears but for others its still undefined.

Hi,

Yes, the version is 1.1.0. I have found that each variation product must be updated in edit mode before the attribute name is displayed when selected. Somehow, the plugin only picks up attribute names for updated/newly-listed products.

Of course for a store with hundreds of variation products there must be a more practical way of doing this rather than updating them one by one.

Thank you.

Follow up, I found the error to be caused by 2 things, 1) the Remove Query Strings option in litespeed cache
page optimization setting and 2) Remove Query Strings From Static Resources plugin. Disabling 1 and 2 resolved the console error with wocommerce 4.3.3. Not planning to upgrade to 4.4 anytime soon.

Follow up, in my case Jquery migrate helper pluing did not resolve the issue. I found the error to be caused by 2 things, 1) the Remove Query Strings option in litespeed cache
page optimization setting and 2) Remove Query Strings From Static Resources plugin. Disabling 1 and 2 resolved the console error.

Follow up, in my case Jquery migrate helper pluing did not resolve the issue. I found the error to be caused by 2 things, 1) the Remove Query Strings option in litespeed cache
page optimization setting and 2) Remove Query Strings From Static Resources plugin. Disabling 1 and 2 resolved the console error.

@invokeeer still no luck for me with 4.3.3 :/

Same issue here, getting the exact same jquery error. Downgraded all the way to 4.2, error still there.

Same issue here with exact same error as @invokeeer. Really would like to know about a solution as downgrading woocom version did not work. Now the checkout page no longer updates the shipping rates when a new address is entered.

Thank you for your quick response @leap13support.

I turned off lazy load on Litespeed & Autoptimize. The issue seems to be resolved indeed!

Thank you for the solution.

By any chance, is there a way to exclude premium media grid from lazy load (by way of css or js) without having to turn lazy load off site-wide?

Have a great day,
Rob

PS. Just found Autoptimize does have such option! This post is resolved.

• This reply was modified 4 years, 4 months ago by bobmorain.

Thanks for your reply. I confirm that both issues are solved now.

Same issue here, @nocaredev, so replacing the code allows the EWWw plugin to be re-activated without crashing admin dashboard, but all features of the plugin besides its basic mode are still giving fatal errors.

• This reply was modified 4 years, 4 months ago by bobmorain.

Okay, will do. Thank you.

I added the path in Automatize and Litespeed exclusion but unfortunately no joy. In fact, now you can also see this error in console:

pum-site-scripts.js:7 Uncaught ReferenceError: jQuery is not defined
at pum-site-scripts.js:7