Forum Replies Created

Viewing 15 replies - 1 through 15 (of 15 total)
  • Thread Starter snb8

    (@snb8)

    Thank you for taking this into account.
    Yes. I started using this plugin more than a year ago and this problem already existed.
    But searching the forum, I was able to solve it thanks to the first mu-plugin that I found in this forum and I mentioned you. However, as I already told you, this one stopped working when I updated forminator to new versions and I had to change it again for another mu-plugin that someone make for me, because I didn’t know how solved the problem. Therefore, I thank you for taking this into account for future versions.

    Thank you very much again.
    Greetings. Kind regards, Sonia.

    Thread Starter snb8

    (@snb8)

    Hi,
    I am happy to be able to help and contribute something.
    You are right, the issue is only with incorrect validation error messages.
    I do not face any issues with Submission after I fill out all the required fields of the forms.
    Thank you very much for taking this into account.

    Kind Regards

    Sonia.

    Thread Starter snb8

    (@snb8)

    Hi,

    If I dont’ use the mu-plugin and I create new forms with new button paypal, the error happens.

    I don’t understand why the first time the error is “Paypal amount must be greater than Zero”, but if I press the button again and again the message changes and this is “Please, correct the errors before submission”.

    Here are the exported form in Live and Sandbox mode.

    Exported- form – Sandbox mode

    ExportedForm-Live mode

    Thanks.

    Thread Starter snb8

    (@snb8)

    To whom it may concern,

    Sorry for the delay in replying.

    I did not send you the exported form because I have doubts about whether the information for the keys associated with the PayPal button on that form is included or appears when exported the form. I did not want to compromise the privacy of my site by publishing my exported form until I consulted you.

    In case it helps, for now, I attach two screenshots:

    • screen-No-Mistake.png-> You can see an example of execution when I test the form with the PAYPAL BUTTON (for production mode) DISCONNECTED from Settings-> Payments of the plugin. The ERROR MESSAGES that your plugin throws are COHERENT.
    • Screen-Mistake-Confuse-Message: You can see an example of execution when I test the form with the PAYPAL BUTTON (for production mode) CONNECTED from Settings-> Payments of the plugin.
      The ERROR MESSAGES that your plugin throws are NOT COHERENT. It tells me that the amount in PayPal must be greater than zero despite having selected a service with a higher price. This happens when one of the required fields is left blank.

    In short, the confusing or inappropriate message appears when you click the paypal button (that is connected with the necessary keys in order it works in production) and there are one or more required fields not filled in . Until you test it with the keys provided by PayPal, you will not be able to reproduce the error and I cannot provide you with those keys since they are private.

    Version 1.35 still has this problem. I tested it by updating the version on a local test site. As I mentioned, I use a mu_plugin, but please consider fixing this for future versions, or at least keep the mu_plugin I use working or provide another one that will work for future versions as well.

    Let me know what you think. Thank you very much.
    Best regards. Sincerely, Sonia.

    Thread Starter snb8

    (@snb8)

    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.

    Thread Starter snb8

    (@snb8)

    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.

    Thread Starter snb8

    (@snb8)

    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.

    Thread Starter snb8

    (@snb8)

    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.

    Thread Starter snb8

    (@snb8)

    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:

    Thank you very much.
    All the best, Sonia.

    Thread Starter snb8

    (@snb8)

    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

    Thread Starter snb8

    (@snb8)

    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.

    Thread Starter snb8

    (@snb8)

    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

    Thread Starter snb8

    (@snb8)

    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.

    snb8

    (@snb8)

    Thank you so much for replying me.

    snb8

    (@snb8)

    Hello,
    I have recently installed version 1.33 of forminator and I still have the same problem as with the previous version. The problem remains unsolved. In payment forms that include a recaptcha v3 field, when I press the paypal button I get the error “Error! something went wrong during checkout and payment couldn’t be approved”. I beg, please, strongly, to fix it as soon as possible. If not, I will have to reconsider using another plugin to create the forms. It is essential that they are protected with recaptcha or give me another solution that does not require user interaction as happens with recaptcha v2 or hcaptcha since if the capthca expires or expires the payment cannot be completed and it damages the user experience a little.
    I am looking forward to your response.
    Thank you so much.

Viewing 15 replies - 1 through 15 (of 15 total)