tumple
Forum Replies Created
-
Hello WPClever,
Another update.
On a staging site of the exact setup I updated to 4.0.1 of WooCommerce. All went fine as far as I could test but the problem still persists.
I’m not willing to update the production site as yet to be able to show you but I did some more digging and discovered the root of the problem.
In the new version of your plugin in the file assets/css/frontend.css you have some new additions at the start of the file to hide the default variations html.
Particularly this line prevents the Back In Stock Notifier section from ever being shown:
.woovr-active.woovr-show-availability .variations_form .single_variation .woocommerce-variation-availability { display: none !important; }If I comment out the new additions, down to line 16 everything works again.
For some reason on this setup the ‘display: none’ is not required to hide the default variations.
The default Variations table already has display: none as an inline style though I’m not sure if that’s coming from your plugin or somewhere else.
Hopefully that’s a clue towards being able to resolve this conflict of plugins.
Thanks.
Hello WPClever,
Thanks for your reply and insight.
Is there any chance you can make earlier versions available so people can rollback more easily if problems occur please?
I fear we could be waiting a little while longer to update Woo Commerce as our payment provider is a little delayed in announcing being compatible.
Thanks again.
Hello WPClever,
Thanks for your reply and apologies for lack of details.
I had updated to 5.4, WooCommerce still on 3.9.3 at the moment due to waiting for a couple of other plugins.
If I use plugin troubleshooting mode and disable WPC Variations Radio Buttons the Back In Stock Notifier works again.
Here’s a link to a page with the Back In Stock Notifier failing to work since upgrading Variations Radio Buttons:
https://www.bigplantnursery.co.uk/shop/plants/bamboo/fargesia-black-dragon/Many thanks for your time!
- This reply was modified 6 years, 1 month ago by tumple.
A follow-up from all of the above…
The 5.2.4 vs 5.3 aspect was a non-issue.
I’m still having problems with 1 setup with this plugin. I’ve updated the working setup and it’s all fine so it’s pointing to something else.
Here is an error I get in the console when the editor error occurs:
Uncaught TypeError: Cannot add property className, object is not extensible http://my-dev-url.com/wp-content/plugins/advanced-bootstrap-blocks/dist/blocks.build.js line 1If there’s any further de-bugging tips you can provide it’d be much appreciated.
Thanks!
Just to add to this, I was able to test almost my exact setup that led to the errors above with the only difference being WP 5.2.4 rather than 5.3 and it all worked fine.
So it looks as though something in 5.3 and your plugin dis-agree.
Thanks.