Conflict between Autoptimize and WooThumbs by Iconic

Resolved alec527
(@alec527)

7 months, 2 weeks ago

Hello,
I’m encountering a conflict between Autoptimize and WooThumbs by Iconic. When I disabled JS optimization, the page stopped loading (loaded completely blank). When I disable either Autoptimize or WooThumbs, the page works fine. When I add WooThumbs to the JS exclude list (“plugins/iconic-woothumbs”), there is no effect. Could you please help me figure out how to fix this conflict?

Thanks,
Alec

The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 18 total)

1 2 →

Plugin Author Optimizing Matters
(@optimizingmatters)

7 months, 2 weeks ago

you’ll probably have to add wp-includes/js/dist to the JS exclusion list Alec, can you give that a go?

frank

Thread Starter alec527
(@alec527)

7 months, 2 weeks ago

Hey Frank,
Thanks for your quick response! I actually am already seeing it in the JS exclusion list

Plugin Author Optimizing Matters
(@optimizingmatters)

7 months, 2 weeks ago

in that case I think you’re also using AsyncJS (an older plugin I also manage)? either simply disable that or in AsyncJS also exclude wp-includes/js/dist?

Thread Starter alec527
(@alec527)

7 months, 2 weeks ago

Disabling AsyncJS worked to fix the issue! Is that plugin entirely redundant if Autoptimize is also activated or is there a benefit to having both plugins activated?

Plugin Author Optimizing Matters
(@optimizingmatters)

7 months, 2 weeks ago

one can optimize a site entirely with just AO, no AsyncJS needed, but some prefer to combine as AsyncJS can be easier to configure 🙂

Thread Starter alec527
(@alec527)

7 months, 2 weeks ago

Ok, thanks again for all of your help!

Plugin Author Optimizing Matters
(@optimizingmatters)

7 months, 2 weeks ago

you’re welcome, feel free to leave a review of the plugin and support here! 🙂

Thread Starter alec527
(@alec527)

7 months, 2 weeks ago

Hey Frank,
I’ve got a follow up issue / question: I started noticing that my autoptimize cache size grew to many gigabytes. I went to the following guide:

https://blog.futtta.be/2014/03/19/how-to-keep-autoptimizes-cache-size-under-control-and-improve-visitor-experience/

And noticed that it’s recommended to turn off the “Also aggregate inline JS?” option. However, once I did that, the page became completely blank. If your recommendation is to turn it back on and follow the steps in the blog post, how do I view the source of the optimized JS (step 2)

Plugin Author Optimizing Matters
(@optimizingmatters)

7 months, 2 weeks ago

hmm, instead maybe try deactivating “aggregate JavaScript” and instead activate “don’t aggregate but defer” and “also defer inline JS”?

Thread Starter alec527
(@alec527)

7 months, 2 weeks ago

Just did that but am still getting the blank page

Plugin Author Optimizing Matters
(@optimizingmatters)

7 months, 2 weeks ago

I had a look and the amount of inline JS added by woothumbs is … staggering (the HTML is 1.55MB which in my opinion is way too much) and it seems the server can’t handle optimizing that. try adding iconic_woothumbs_variations_data to JS optimization exclusions and make sure “minify inline CSS/ JS” is off.

Thread Starter alec527
(@alec527)

7 months, 2 weeks ago

I’m encountering the blank page issue when I add iconic_woothumbs_variations_data to the exclusions – not sure what the mechanics of this plugin conflict are

Plugin Author Optimizing Matters
(@optimizingmatters)

7 months, 2 weeks ago

and is the “minify inline CSS/ JS” option off?

Thread Starter alec527
(@alec527)

7 months, 2 weeks ago

yes

Plugin Author Optimizing Matters
(@optimizingmatters)

7 months, 2 weeks ago

then I’m afraid I can only suggest to disable JS (or all) optimization entirely on that specific page (using the “autoptimize this page” metabox on the “edit” view of the page).

Viewing 15 replies - 1 through 15 (of 18 total)

1 2 →

The topic ‘Conflict between Autoptimize and WooThumbs by Iconic’ is closed to new replies.