Plugin Author
vark
(@vark)
Hi,
Thanks for using the plugin.
You’re the only user amongst thousands reporting an issue.
Suggest going back to the current version.
Then suggest a *full module conflict test*:
To track down a module conflict, please follow these steps ** PRECISELY **:
(1) Install and activate a maintenance mode plugin (if desired)
(2) Then, DO ALL (*at the same time*):
(-) do a full site backup!
(-) deactivate ***all*** plugins except Woo, my plugin (and maintenance mode plugin)
(-) ** switch to a clean default theme like “twentynineteen” **
— (This removes all other possible conflicts.)
(-) turn off all deals except the one we are examining.
(3) ** close your browser completely, retest in a fresh, clean browser session **
(4) if good, add 1 module back in. ** Retest **
(5) Repeat until conflict identified.
** This test depends on following the outlined steps fully. **
Best,
Vark
(PS – If you do have a module conflict, it will likely boil down to choosing between the 2 conflicting modules…)
Thank you for the quick response. But wouldn’t I only need to do that if it still wasn’t working? Its clearly something different in the update since its working with the previous version perfect but not the newest version. No?
Plugin Author
vark
(@vark)
Hi,
1. the fact that yours is the only report of this issue, and that I can’t replicate the issue, indicates that the issue is unique to your environment.
2. from what you’ve described, there’s no issue with keeping the older version for now. However, that means you’re frozen to this generation in perpetuity, unless you hunt for the issue in your environment.
Vark
