My eroor in the console
Uncaught ReferenceError: woo_variation_swatches_options is not defined
at new e (frontend-pro.min.js?ver=1.0.40:1)
at HTMLFormElement.<anonymous> (frontend-pro.min.js?ver=1.0.40:1)
at Function.each (jquery.min.js:2)
at s.fn.init.each (jquery.min.js:2)
at s.fn.init.value [as WooVariationSwatchesPro] (frontend-pro.min.js?ver=1.0.40:1)
at HTMLFormElement.<anonymous> (frontend-pro.min.js?ver=1.0.40:1)
at HTMLDocument.dispatch (jquery.min.js:2)
at HTMLDocument.v.handle (jquery.min.js:2)
at Object.trigger (jquery.min.js:2)
at HTMLFormElement.<anonymous> (jquery.min.js:2)
Hi all,
Temporary you may rollback to 1.1.2, Hopefully your issue will resolve.
We are working on it to fix it with the next version as soon as possible.
Thanks
I’m having the same issue with 1.1.4 I had to rollback to 1.1.2 as well
Same problem here.
If i deactivate PRO Version 1.0.40 add on, and only activate the free version Version 1.1.5 it´s work.
Any fix for the PRO add on?
Same here, issue with v1.1.3 and v.1.1.4. Reverted to v 1.1.2 as suggested and issue was resolved.
I reverted to 1.1.2 but same issue…cleared cache too.
But seems to work for everyone else – will keep trying, perhaps a cache I havent cleared yet.
Had to clear cloudflare cache, all good now with 1.1.2
-
This reply was modified 3 months ago by
Encify.
Hi @damiafaw @dzined @topladyse @rayge @creditoinsieme @jerbnl @birkhoff20 @lunorag @seetiggergo @birkhoff20 @rishadan
We are sorry for your inconvenience. We have fixed the issue. Could you update to the latest version (1.1.5) of your swatches variation free version?
If you are also using the advance version of our swatches variation plugin, you are using the same version (1.1.5)
WooCommerce version should be the latest version 4.9.0
Kindly let us know your reported issue has been fixed or not in this latest update.
Thanks
hello, unfortunately for me the problem continues to arise even with the latest version 1.1.5
Problem persists also with 1.1.5
I’ll keep waiting until someone says it works
Same problem here. Had to rollback and that fixed it, but cripes…
It’s sad. It takes me 5 days to get the courage up to click the damn update button for any plugin I have (even after I have tested on staging). I know as soon as I open up that Pandora’s box I will be restoring backups and pulling cords.
OK I updated to 1.1.5 free then updated pro to 1.1.5 and it is working fine now.
The problem still persists, I did the update but the buttons still don’t work.
Furthermore, the pro version of the plug-in has no other updates to make. (the latest PRO version is 1.0.40)
