• Resolved peopleinside

    (@peopleinside)


    Hi,
    in two different website that use the same theme and plugin I have an issue.
    I use Forminator to create a contact form.
    Forminator provide the possibility to add Captcha to prevent Spam and Compilanz use a placeholder that require to the user to accept cookie before can validate captcha.

    All works on the contact page [ redundant link removed ] where user cannot compile the form if never accept cookies but is not working on the homepage footer where user are able to compile the form then send the form and loose all text then get the error to accept cookie.

    Can you help me to fix this, there is a way to block also this form until is not compiled? It’s an issue of with extension or theme? Can be resolved?

    I expect that the form in the home page footer is disabled until cookies for captcha are not accepted, this avoid the text loosing on page refresh.

    Thanks.

    • This topic was modified 1 year, 9 months ago by Yui.
    • This topic was modified 1 year, 9 months ago by Jan Dembowski. Reason: Link moved to link field where it belongs

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor jarnovos

    (@jarnovos)

    Hi @peopleinside,

    I suspect that the behavior whereby these form fields are disabled before ReCaptcha is loaded, is performed by Forminator itself.

    Do you use any different settings between these forms? Could you try it with the same form as you have on the /contact/ page, to see if that does result in the ‘expected’ behavior appearing on the other page as well?

    If it does, it’s most-likely due to a specific configuration in the form itself.

    Kind regards, Jarno

    Thread Starter peopleinside

    (@peopleinside)

    Hi @jarnovos thank you for your reply!

    The form you see is the same in the home page and in the contact form, the difference is where the form is placed.

    I will try to report to Forminator but looks strange they know your plugin and lock the form. The issue seems caused by the fact the same form are placed in two different place.

    In the contact form is inserted like editor widget, in the home page just with a short code in a theme filed.

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @peopleinside,

    What I meant to say with the above is that Complianz blocks the ReCaptcha implementation, but as far as I can tell, we do not determine whether the input fields are also ‘locked’.

    If the forms are the same, and it’s mainly the implementation method that differs between the two; perhaps you could try the same implementation as used on the /contact/ page, to see if it results in the same behavior?

    Kind regards, Jarno

    Thread Starter peopleinside

    (@peopleinside)

    If the forms are the same, and it’s mainly the implementation method that differs between the two; perhaps you could try the same implementation as used on the /contact/ page, to see if it results in the same behavior?

    Unfortunately I can’t: for place a contact form where is in the home page the theme provide just a text filed where insert the short code.
    I tried to ask help on Forminator support form.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Issue with ReCpatcha placeholder, Forminator and Hestia’ is closed to new replies.