sergeyf1
Forum Replies Created
-
Hello Patrick,
Thank you very much for your reply.
I have updated the forum thread for the Simple Cloudflare Turnstile plugin and added more information, including my March 3 email (to Forminator) in which I described the scenarios causing the error, as well as your responses on the forum. Hopefully the plugin author can read everything and find a solution that fixes the problem.
Here is a link to my post on the Simple Cloudflare Turnstile plugin forum
https://ww.wp.xz.cn/support/topic/forminator-forms-submission-error-when-using-simple-cloudflare-turnstile-1-29-0/#post-18350487Hello,
Important update on this problem.
The problem described in the previous post depends on your plugin.
In order not to be unsubstantiated I am updating this forum thread with additional and important details that I hope will help you to fix the problem.
I contacted Forminator plugin support additionally via email (see screenshot) on March 3, 2025. In the email I provided details on how the error occurs and what causes the error. I outlined in the email detailed test scenarios where the error occurs.
A few days later, I received 2 responses from Forminator plugin support.
The links are as followsFirst response of March 5
https://ww.wp.xz.cn/support/topic/forminator-forms-submission-error-when-using-simple-cloudflare-turnstile-1-29-0-2/#post-18342717Second response, dated March 9 (with more details)
https://ww.wp.xz.cn/support/topic/forminator-forms-submission-error-when-using-simple-cloudflare-turnstile-1-29-0-2/page/2/#post-18350395Hello Amin,
Yes, I have seen the emails from Forminator support staff. I have corresponded with them several times already. We are in the process of solving the problem. All correspondence is done via email.
Thank you very much!
Hello Amin,
I answered you in an e-mail. I opened access to the test site for you 2 days ago.
You can do on the test site whatever you consider necessary to solve the problem.More details in email correspondence and also in this thread on the forum.
Hello Nebu John,
Thank you for your reply.
I wrote earlier that the problem is the same whether using the default theme (Twenty Twenty-One 2.4) or any other theme (Kadence, for example).
Yesterday I wrote to your email as requested by your support person (Kris). The email contains a link to this forum thread and also login credentials to the admin panel of the test site. In addition, the email contains some more details about the problem.
Hello Kris,
I sent an email to the address you provided.
I hope we can resolve the problem.
Thank you!Hello Amin,
I’ve created a new test site for you.
As I said before, the problem is definitely related to the Forminator plugin, because if I use another login form (for example, a standard WordPress login form or a login form created in Elementor) with Simple Cloudflare Turnstile protection enabled, everything works without problems.
If I use a login form created with Forminator plugin, I can’t log in through it.
See screenshot – https://i.imgur.com/sAzXzvy.pngAgain, as noted earlier – in other forms created through Forminator, there are no problems with sending data. The submission issues only affect the login form created through Forminator.
Also note
The test site does not use reverse proxy or any other mechanisms from Cloudflare, with the exception of Turnstile. Also, this site does not use WAF. No plugins or solutions for code optimization or minification are used.Test site configuration
PHP 7.4.33
WordPress 6.6.2
Kadence theme 1.2.16
Forminator 1.39.3
Simple Cloudflare Turnstile 1.30.0Hello Nithin,
Thank you for your response. I needed some time to further test your tips and try to help you understand the problem.
I am not using any specific login roles. In Forminator, in the login form behavior settings – it simply says where to redirect the user after a successful login.
I have tested the login form in different browsers – with and without browser add-ons enabled. It still doesn’t solve the problem.
I also created a clean test site to test the Login Form from Forminator in conjunction with the Simple Cloudflare Turnstile plugin. Test site configuration – listed below at the end of this post. The problem remains even on the test site.
Again, the problem (described in the very first post in this thread) occurs only in the login form that was created via Forminator. In other common forms (e.g. feedback form) created via Forminator there are no problems with form submission.
If the login form is created through Elementor, for example, there are no problems with login, even with the Simple Cloudflare Turnstile plugin enabled. There are also no problems when using the standard WordPress authorization form.
Based on what has been described above in this and my other posts, the problem is specifically with the Login Form functionality that was created through Forminator. In other words, the error is related to your plugin.
I hope my tests and clarifications will help you resolve the issue faster.
Thank you!
Test site configuration
PHP 7.4.33
WordPress 6.6.2
Twenty Twenty-One 2.4
Forminator 1.39.3
Simple Cloudflare Turnstile 1.30.0Hello Kris,
Thank you for your reply.
I am not using the “Upload file” field in any in forms. Also, I did an additional test and found that the problem only occurs with one type of form [Login Form]. I plan to use the Forminator plugin for the login form on the site, so that users can log into the private parts of the site through it.
In other forms created through Forminator, where standard fields are used (name, email, text, dropdown, checkbox, radio) – no problems with submission, even with Turnstile enabled.
The problem and sending error (described in the first post) occurs only in Login Form.
I have exported the Login Form to a text file and uploaded it to Google Drive (link below) so that you can better understand what the problem might be.
https://drive.google.com/file/d/1zpq-uefu1bAyhu2KvuKBrQ66BIYfnBzv/view?usp=sharing
Thank you for your reply and clarification. If this warning in Site Health does not pose any danger to the stable operation of the site, then I will ignore it. I think I have no more questions on this topic.
Hi @nintechnet,
Thank you for your detailed and clear answer.
Problem solved.Hi Darin (@dkotter),
Thank you for your detailed and clear answer.
Problem solved.Hello,
After commenting out the line, try again to see if the updates function as expected.
Thank you very much for your reply. Yes, your advice helped, I tested on several sites with different settings what you recommended and it helped to solve the update problem. Now when manually updating via “Dashboard -> Updates” plugins and themes are updated without problems.
If the changes made to the plugin code don’t adversely affect something else, then I guess we can consider the problem solved. Thank you for your help and I wish you success in your business.
Hello,
Thank you for your response and additional questions. I will try to answer in detail and also add additional information.
I specifically created a test setup to test and reproduce the problem. The problem is definitely there.
Full installation configuration
PHP 7.4.33
WordPress 6.4.3
Twenty Twenty-Two 1.7
Kadence 1.2.3 (Active Theme)
WP Hide & Security Enhancer 2.3.8.1 (all default settings except for the custom address for /wp-admin/ and wp-login.php)The test uses the Kadence 1.2.3 theme, and the default Twenty Twenty-Two 1.7 theme. I switched between themes – to test the problem.
Answers to your questions
Might be related to a specific option and value you’re using. Can you try to reset all options and keep just the custom admin and login URL customizations?
The test uses the default settings for WP Hide, except for the custom address for /wp-admin/ and wp-login.php
On the production sites I talked about in the first post, the problem occurs with any plugin settings, but the main condition, custom address for /wp-admin/ and wp-login.php.All your sites use PHP 7.4.33 or tried with other versions too?
Yes. All sites use the same version of PHP 7.4.33
Disabling all other plugins but WP Hide still produces the problem for you?
As I pointed out above, even on a test installation (its configuration is listed above) the problem is there. On working sites – the problem is there even when disabling all plugins, except WP Hide with custom address for /wp-admin/ and wp-login.php.
Is the issue started with the latest 2.3.8.1 but working fine with a previous version? Which one you used before?
The problems started with version 2.3.8.
Prior to the 2.3.8.x branch, there is no such problem.
On some client sites that are still using version 2.3.7 – no problem.I hope the information from me will help you solve the problem.
Thank you for your support, I look forward to your reply.Hello @anowerhossain16,
I have sent a support request to the link you provided. I hope it will help to solve the problem.