Form error in consent boxes

When I accept the Polylang pll_language cookie, the number of failed submissions is almost zero, but when I reject them most of the time the forms have this failure behavior that I described before.

Sometimes forms work well, but sometimes they don’t. It depends. When I accept the polylang pll language cookie, the number of misbehaved submissions that I described in the previous post is lower than when I reject it.

I don’t understand what could be happening

Hi @snb8

I hope you are doing well.

It sounds like a language issue, can you double-check if that works in English but not in a different language?

We have a reported problem but it is with translatepress because it translates the “checked” value or any internal value, it would happen because the Forminator compares the front-end value with the backend to ensure no one tried to inject any extra content into your form.

However, I tried to replicate it on my end and it worked but I have some doubts, is it a manual translation or are you using Auto translation? I ask because it may requires the Pro version to test hence why the Free worked fine.

Could you duplicate the form and page, switch PayPal to sandbox and share the URL so we can try it and check the source code?

Best Regards
Patrick Freitas

Thank you very much for your answer,

The versions I’m using are free, both the forminator version and the Polylang plugin version.

My website offers the possibility to switch between two languages (US English) and Spanish. The first language is English and the second Spanish. The Polylang plugin does not automatically translate pages. The translations are done manually.

My WordPress (settings-> general-> site language) is in Spanish.

• I have been testing with the polylang “pll_language” cookie rejected (disabled) and at first it seems that all the tests carried out (both with the contact forms and with the payment forms that integrate the paypal button in “sandbox” mode) THEY WORK if the language I choose is English.
• I have been testing with polylang “pll_language” cookie rejected (deactivated) and at first it seems that all the tests carried out (both with the contact forms and with the payment forms that integrate the PayPal button in “sandbox” mode) THEY DO NOT WORK if the language I choose is Spanish.

Other points that I would like to comment on if they help to clarify the problem are the following:

Point 1: In case it helps or I could clarify something, that I think this problem began to manifest itself as a result of adding these consent boxes to my forms as new fields, since I was carrying out the process of legalizing the website and needed to add them so that users could accept the “Privacy Policy” on all forms and the “Terms and Conditions” also on payment forms.

Point 2: Also comment if I could be influencing the problem, which I do not remember well if when I created the forms for the pages in Spanish and the pages in English I changed the language settings of my WordPress to match because I did not know if this was necessary (i also don’t know if i did this on some forms and others i didn’t, since i created them last year and i don’t remember it). I thingk that after adding these consent boxes and an HTML field with a small extract of the privacy policy to the forms I had created I started experiencing all these problems. It seems that they were later fixed, but after recently upgrading to the new version 1.34 that came out a few days ago, they manifested themselves again.

Point 3: Also comment that when (after exporting the forms), for example, the contact form in English and the contact form in Spanish, I notice in the part of the code corresponding to the field Last Name (although in this field there is no problem), for example , that the value (message configured by me) of “lname required message”,
obviously, it is in English (“Surname is required.”) in the form for the page in English and in Spanish in the form for the page in Spanish (“El apellido es obligatorio.”). However, the value of mname required message (not configured by me) is always in Spanish both in the form for the page in English and in the form for the page in Spanish. The message that appears in both cases is: “El segundo nombre es obligatorio.”

Point 4: Also comment that when (after exporting the forms), for example, the contact form in English and the contact form in Spanish notice in the part of the code corresponding to “wrapper id”, that the number that appears is the same in the form in english (for the correspondig field) in the form in spanish. However, this number is different in the form in English with the one that appears in the form in Spanish for the fields that I have commented that were added later to the creation of the forms and as a result of which I began to experience these problems. These fields are, as I have commented previously, those corresponding to these consent boxes as well as the HTML field with the small extract of the privacy policy.

I hope this problem can be fixed or please tell me how to do it so that I can use this wonderful plugin on my website.

Thank you very much for everything.

All the best, Sonia.

I think I experienced the problems as a result of adding these fields (consent boxes and HTML field) after having set cookies, as a result of the legalization process of the web.

Thanks again.

Sonia

Hi @snb8

Please export both forms, upload them to Google Drive, and share links in your next reply. You can also make a copy of those forms, change email notifications emails, and then export them to Google Drive. We want to test them on our lab site following your described scenario.

Kind Regards,
Kris

To whom it may concern,

Thank you very much for your response and for trying to help me solve this issue.

I exported the forms as I was told. However, before doing so, I deleted (from both forms) unnecessary configurations, since even without them the Spanish form still does not have a correct functioning and continues give error.

The settings I removed are as follows:

• Email Notifications
• Redirect to Thank You Page
• I also disabled the “Cloudflare” field (CAPTCHA) in these forms via the “Cloudflare Turnstile” plugin so that it does not appear either.

CLARIFICATION: At first I only exported the contact forms as they are easier to prove than the payment ones that also manifest the same wrong behavior. I imagine that once the cause in these I send you is discovered, the solution can be extended to any of the forms on my website.

send you the links to each of the forms:

• Contact form in English (Works fine)
• Contact form in Spanish (Gives error after submission in the consent box)

Thank you very much.
All the best, Sonia.

Hi @snb8,

Thank you for getting back to us.

To investigate the issue further, I imported the form to a test website, but I couldn’t replicate the issue. The form submission works fine with the Polylang plugin configured on the test site.

https://ibb.co/Ntz7nGd

The issue seems specific to your website. Could you please share a page URL where we can replicate the problem? This will help us examine the source code and check for any errors in the browser console.

We look forward to hearing back from you.

Kind Regards,
Nebu John

Thank you very much for trying to help me.

HERE is the URL where they can reproduce the error.

Here you will access the contact form in Spanish that is giving problems in case of rejecting functional cookies (language).
If I accept them the form seems to work well.
However, the rest of the forms on the website have the same misbehavior for the Spanish version.

Thank you very much.

All the best, Sonia.

If you switch the language, you can prove the form in English. It seems that it works indpendent on the cookies acceptation.

Thank you very much.

Kind Regards, , Sonia.

Hi @snb8,

I hope you are doing well today!

This issue seems to be related with a recent bug we have discovered. Please try the following code snippet as a mu-plugin until the fix is being released with the upcoming versions.

https://gist.github.com/wpmudev-sls/d1e1b64e21fa4cce14921cedd892f811

You can find more information below on how to use mu-plugins.
https://wpmudev.com/docs/using-wordpress/installing-wordpress-plugins/#installing-mu-plugins
and
https://www.ads-software.com/support/article/must-use-plugins/

It would be better to test this out on your staging/dev environment first before your live site and make sure you have the latest backups.

Kind regards,
Zafer

To whom it may concern,

Thank you so much for your response and for helping me resolve this issue so quickly.

Sorry for my delay in replying you. I’ve been doing tests on my website to make sure everything is working well.

All of the tests I have taken have been successful with both the English and Spanish forms. I have also tested both Polylang cookies enabled and disabled.

I’m so happy that this issue has been fixed and that I can use this wonderful plugin on my website.

I thank you very much for all the help you have received and I encourage you to continue with your work.

Thank you very much again. I wish you a happy day.

All the best, Sonia.

Hi again @snb8,

We are glad to hear that the information provided has been helpful for you and we are marking this thread as resolved accordingly. Please let us know in case you need further help.

Kind regards,
Zafer

To whom it may concern,

A new question has arisen and I would be very grateful if you could please guide me.

I currently have the version 1.34.1 installed, as well as the code that you provided me as mu-plugin to correct the error that I referred to in this thread in the consent boxes in the forms in Spanish.

I have seen that you have recently released version 1.35 and in the details it specifies that the error in submissions when the consent field is translated is fixed.

My doubt is whether before upgrading to this new version it is necessary to remove the mu-plugin that you provided me or, on the contrary, should I leave it?

What exactly would be the procedure to follow so that everything works correctly and not have any problems in this aspect?

Thank you so much.
Greetings. Sincerely, Sonia.

Hi @snb8

I hope you’re well today!

In such case the recommended process would be as follows:

1. remove the “mu-plugin” that was used as a fixed so far (but keep a copy of it so you could re-add it)
2. update plugin, purge all cache on site/server (if there is any in use) and test it

3A – if everything works fine, that’s it, nothing else needs to be done

3B – if the issue/error is back – add the mu-plugin back to the site and let us know here so we could recheck/retest the issue on our end and bring it back to developer’s table if necessary.

Best regards,
Adam