Hi @tomangell,
Thank you for your feedback and suggestion.
Our development team has been actively testing this issue, including with the beta version, but so far we have not been able to consistently replicate the problem on our end in the same way some users are experiencing it.
Since the issue may be environment-specific or related to a particular setup/cache configuration, would it be possible for you to open a support ticket through our official support portal so we can connect you directly with our developer and resolve this issue more efficiently.
You can open a support ticket by clicking this link.
For other readers: we will update the resolution here once the client’s issue has been resolved.
Thanks & regards,
WPExperts Support Team
I’ll respectfully decline to take further steps on this end and will wait until you either fix the issue or, preferably, simply revert the plugin back to its prior, unbroken form for now. Please consider doing that. Clearly there are several of your users having an issue with your recent update.
Hi @tomangell,
We completely understand your concern and appreciate you taking the time to report the issue.
At the moment, our development team is still actively investigating this behavior. While a few users have reported similar problems after the recent update, we have unfortunately not yet been able to consistently reproduce the issue in our own testing environments, which is making it more difficult to isolate the exact cause.
That is why we requested additional debugging information through the support portal, as setup-specific factors such as caching, optimization layers, theme compatibility, or server configuration may be contributing to the issue.
If possible, please also share the complete scenario or exact steps that consistently trigger the problem on your end. A full workflow or screen recording may help our developers better identify the root cause.
We respect your decision not to proceed with further troubleshooting steps on your side. Please be assured that the issue remains under investigation by our team, and if we identify a confirmed root cause or release a fix/revert, we will update the community accordingly.
Thank you again for your patience and feedback.
Thank you
There are no steps that “trigger” the problem on my end except for your recent update to the plugin. Snippets that I had for years and was using without issue are now broken. I didn’t create any new snippets or change anything about my workflow. Your plugin update just made my existing snippets unusable. Please kindly revert the official version of the plugin back to its prior unbroken form while you continue to investigate this.
Hi @tomangell,
We appreciate your patience and the details you have shared so far.
Our development team is continuing to investigate the problem, and we will update you as soon as we have more information or a confirmed fix.
Thanks again for your feedback and support.
Thank you
Hi @tomangell,
Thank you for your time and patience.
We’re pleased to let you know that the reported issue has been fixed. Our team has prepared an updated build for your testing. This is not a beta version; it is a production-ready build. Once you have tested it and confirmed that everything is working correctly, we will proceed with releasing it to all users.
We have also prepared a guide that explains the required steps. The instructions are provided both in the video and in a text format.
To permanently resolve the issue, please update the plugin using the latest build provided below. After updating the plugin, open the Classic Editor block and update the snippet by removing the old rendering and then re-entering it, as demonstrated in our guide.
Updated plugin:
https://drive.google.com/file/d/1Bj9A1D7oMysu_rgXDsuf70DxO6VbAHQB/view?usp=sharing
Guide video:
https://www.awesomescreenshot.com/video/53284457?key=72e7cbd5098c978b79ef606644b7d6c7
We look forward to hearing your feedback.
Thank you.
Thanks for your work to get this right. Respectfully, however, I don’t intend to install anything but a proper plugin update pushed out through official channels. If the build is production-ready, as you say, please push the update through WordPress and I will install it then.
@tomangell
you couldn’t be less cooperative. these guys are bending over backwards for you. Perhaps you could share with the forum how much money you have donated to the development of this plugin.
