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

    (@futtta)

    Well, I’m not a WooCommerce or WC Products Customizer expert by any measure, so I’m just guessing, but maybe try adding “woocommerce-products-customizer/ressources/js/” to the comma-seperated exclusion-list and possibly “jquery.js” as well (or “force JS in head”)?

    hope this helps,
    frank

    Thread Starter confused

    (@nicole2010)

    Thanks for the quick response. Unfortunately it didnt work BUT I found a method that helped me discover what would work and I wanted to post it in case it helps anyone else in a similar situation.

    I copied the source of the page onto a Word document – once with the plugin activated and a second time without the plugin. I then compared the two versions using Word’s compare function. It showed me the difference between the two versions and I was surprised to see how many differences there were (i.e. how many plugins were not working with Autoptimize activated). I then copied all of the css and js files that were not apprearng in the version without Autoptimize activated to the list of exceptions (“Exclude scripts from Autoptimize”) and now all of the plugins are working.

    Hope this helps others too!

    Plugin Author Frank Goossens

    (@futtta)

    Thanks for the feedback Nicole, but I’m afraid your solution is not 100% OK; Autoptimize’s job is to remove all separate JS (and CSS) files and aggregate that into one big, optimized one. Most JS continues to work OK that way, except if it doesn’t (e.g. your WC Products Customizer), in which case you’ll have to dig a little to find exactly what JS-file to exclude.

    The solution you described means you are preventing Autoptimize form doing most of the JS or CSS optimizations, rendering AO rather … out of work, really ??

    So (as per the FAQ), best will be to either do some trial & error, looking at the “browser console”‘s output to see if a JS error is preventing your products from being customizable and try to find out what exactly to exclude. While doing that, do take into account that AO also aggregates (and minifies) inline JS, so excluding that could be a solution as well.

    frank

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Plugin clash’ is closed to new replies.