forge12marc
Forum Replies Created
-
Hi @100chi
Hotfix v2.2.56 is live. It addresses the issue you reported. Please confirm whether it’s resolved on your end.Hi @bonaldi ,
Hotfix v2.2.56 is live. It addresses the issue you reported. Please confirm whether it’s resolved on your end.Hi @bonaldi
Thanks for the additional details.
One more thing we need to clarify:
Could you please check whether the same issue also occurs with version 2.2.55?Regards.
Hello Gösta,
could you please confirm whether this issue still occurs with version 2.2.55?
Hi @monoloid
Thank you for the detailed description. We’ve already released a hotfix in version 2.2.55 that addresses this issue with variable WooCommerce products.
Could you confirm whether updating to 2.2.55 resolves the problem on your development site?hello @homepagehelden
Thank you for providing the clean test installation. We were able to reproduce the issue exactly as you described. The problem has been resolved in version 2.2.55, and the hotfix is already released.
The error does not occur on all Twenty-themes; our regression tests did not go as far back as Twenty Nineteen, which is why this slipped through.
We appreciate your assistance in isolating the root cause. If you have any further questions or notice anything else, feel free to reach out.hello @homepagehelden
Thank you for the additional details and for listing your environment.
We can confirm that the issue appears after updating our plugin from 2.2.53 to 2.2.54, but the JavaScript errors you shared are thrown inside WooCommerce core scripts (
wp-util.min.jsandadd-to-cart-variation.min.js). Our latest update mainly changes how JavaScript is loaded/optimized, so the most likely cause is a conflict between this new loading strategy and another component in your stack (theme or plugins).To properly identify the root cause, we need at least one of the following:
– access to a staging site where we are allowed to temporarily disable other plugins and caching, or
– confirmation from your side that the issue still occurs on a clone with only WordPress, Divi, WooCommerce and our plugin active (no other plugins, no caching/minification).
– a full copy of the site created with Duplicator (including the installer) sent via WeTransfer to info@forge12.comIf it’s not possible for you to provide a link or a controlled test environment, our options are unfortunately very limited, because we cannot safely reproduce and debug your exact configuration. In that case, the safest short-term workaround is to stay on version 2.2.53 while we try to reproduce a similar setup on our side.
If you can share a URL or a staging environment, we’ll be happy to investigate this further and adjust our script loading to avoid the conflict.
Thank you for your message. At the moment, none of the reported errors point to any of our scripts. To investigate this properly, we need a bit more information:
– a link to the affected page
– details about your environment (theme, active plugins, caching)
– and, if possible, steps to reproduce the issue.
Once we have this data, we’ll review the situation immediately.Hi Bonaldi,
We have tested version 2.2.54 extensively in our development environment and could not reproduce any login issues. Everything operates correctly on a clean setup.
This strongly suggests a plugin incompatibility on your installation.
Could you provide more details, or send us a full copy of the site using Duplicator via WeTransfer?
Alternatively, access to a staging environment would allow us to investigate directly.Regards.
Hi @pablodj
We’ve identified the issue, and the fix ships tomorrow.
The update resolves double submissions in Elementor forms and refreshes captchas automatically after validation errors.
Thanks for helping us refine the experience.Hi @ivowebflow
We’ve identified both issues, and the fix ships tomorrow.
The update resolves double submissions in Elementor forms and refreshes captchas automatically after validation errors.
Thanks for helping us refine the experience.Thanks for reaching out. You can enable the logs in the plugin settings to see which factors trigger the spam detection — that will help identify what’s being flagged.
You can then adjust the options in the Extended tab to better match your setup.
Additionally, the upcoming beta version of our SaaS service will let users define individual thresholds for detection intensity. The rollout is planned for November.hello @hephaistos,
Thank you for reporting this. We’ve reviewed the issue and confirmed it — the toggle appears even when WP Job Manager isn’t installed. This will be fixed in the next update.
@martinpelletier – Thank you for your feedback. We’ve tested the reported issue extensively but couldn’t reproduce it — when the login protection is disabled, no CAPTCHA is triggered, and login works as expected.
It’s possible that a local cache or a conflict with another plugin caused this behavior. If you can share some details about your setup, we’ll be glad to investigate and help resolve it quickly.@regruppe – Thanks. This will be fixed with the upcoming update.