@lomars You’re right, it does sound like a plugin and/or theme conflict. Please see Testing Comet Cache in a Clean WordPress Installation.
Hello Raam Dev
Finally i have find the guilty plugin:
WooCommerce EU VAT Assistant
This plugin works together only with a free plugin:
Aelia Foundation Classes for WooCommerce. If i disable this plugin, Comet Cache is working perfect again.
So i have post support thread in the wordpress plugin support section (in case you want to have a look):
After update 1.6.2.160315 Comet Cache plugin is not working anymore
I will tell you what is going on, but for the moment all wooCommerce websites using Aelia plugins, can’t run Comet Cache, because of Aelia Foundation Classes for WooCommerce.
Best regards and thanks.
I can confirm what lomars wrote. We inadvertently introduced a bug in yesterday’s release of the EU VAT Assistant, and that caused an issue with Comet Cache. The updated we released today (just a couple of minutes ago) should address it.
Clarification for other readers
The Aelia Foundation Classes for WooCommerce is very rarely the cause of conflicts. It’s a library on which other plugins are based, which doesn’t do anything by itself. Disabling that library means disabling all the plugins based on it (even though they appear as “active”, they are actually disabled).
If you left the AFC active and disabled the EU VAT Assistant, you would have noticed that the issue disappeared as well. Bottom line, the EUVA was the one with the bug, the AFC had nothing to do with it.
Since there is this common misconception that “disabling plugin X solves the issue, therefore plugin X is the cause“, which is as widespread as it is incorrect, I thought appropriate to clarify why that’s not always the case (especially with the AFC plugin). 🙂
And, as a further remark, I would strongly recommend lomars, and anyone else, to refrain from accusations of “sabotaging” other plugins, like you did on the other thread.
We don’t get paid by other teams to promote their products and, most importantly, we would never enter into an agreement geared towards the sabotage of other people’s work. Assuming that we do something like that simply based on an announcement on our site is as offensive as it is shortsighted.
We don’t take these accusations lightly, and we won’t tolerate them either.
For reference, the bug we found was caused by a JavaScript issue.
The bug did not prevent Comet Cache from working (the caching mechanism still worked perfectly), it simply threw an error in the admin pages, and prevented other scripts from running properly. As a result, the scripts on the Comet Cache page were not loaded, and clicking on the various elements didn’t have any affect.
Bottom line: it was a purely JS issue, with no tangible effect on Comet Cache caching logic, apart from the broken UI.
So this issue is completely solved… Thanks to the very reactive support of WooCommerce EU VAT Assistant plugin…
Thanks a lot Diego!!!
You’re welcome. It’s ironic that we released the buggy update yesterday, and received support requests in relation to it ten minutes before we released the fix (which was already in progress when the support requests were filed).
@diego
All my apologies again for my suspicious mind. This has began with some other free/commercial plugin’s worst practices. The last one, for me, was Yoast SEO…
advice to all readers:
WooCommerce EU VAT Assistant is a strongly recommended free plugin for wooCommerce that works perfect for EU VAT purpose in an harmonic integration within wooCommerce. I use this plugin in 2 wooCommerce webshops and it just do a perfect job…
This thread is just about a small javascript minor bug issue, that was interacting with comet Cache plugin, and solved with a really quick update du to the remarkable smart reactive support of WooCommerce EU VAT Assistant team.
Very sorry again Diego, and thank again.
Many thanks also to the very effective comet Cache support !
Best regards
@daigo75 Thank you very much for chiming in here and clarifying the issue and the fix. I’m glad to hear that the problem has been resolved. 🙂
