Forms with visibility rules enabled are not working

[Anonymous]

Hey guys,

So we tested two forms on the same landing page.

Both forms were basically identical, except for one big difference.

One form had visibility rules enabled, and one form did not.

The form with the visibility rules enabled is giving us issues. When the user clicks "submit", they are not taken to a thank you page.

When the user clicks "submit" on the form without the visibility rules, they are transferred to a thank you page as normal.

Anyone know why the form with visibility rule would behaving differently? Anyone run into this before?

[SanfordWhiteman]

Your URL.

Nothing can be done without it.

[Anonymous]

Thanks Sanford Whiteman​

Here's a sample LP that has the form with visibility rules: https://go.cq.com/Test-Wordpress-LP_testing-whit-2.html

and here's a sample LP that has a regular form: https://go.cq.com/Test-Wordpress-LP_testing-whit-2-no-visibility-rule.html

the first LP (with the visibility rules), when you fill out the form and press submit nothing happens (it should redirect you to a TY page).

Appreciate it!

[SanfordWhiteman · Accepted solution]

You forgot that you're using the (useless + misguided) "honeypot" logic on this page. The form doesn't have that field.  Just remove that code, it isn't doing anything anyway.

[Anonymous]

Sanford Whiteman​ does the code live on the landing page itself, or is it embedded in the form?

the reason why I ask is that the issue was also occurring on a Wordpress Landing page that was using a MKTO form with visibility rules enabled

here's a test wordpress LP with a MKTO form that has visibility rules enabled (same issue, submit button did not work): https://info.cq.com/cqrc-engage-request-a-demo-mg-experiment/

thanks again

[SanfordWhiteman]

It's not the same behavior.  On this page you have another error, because you're loading the form twice, once from the wrong instance.

You'll see the resulting error in your F12 Console.

Fix that error (remove the wrong loadForm()) and try again.

[Anonymous]

Okay great, so in Wordpress we need to remove the redundant code for the MKTO form.

And on the MKTO side < are we removing the code from the form or the landing page template? Sorry, just needed a bit clarification.

[SanfordWhiteman]

And on the MKTO side < are we removing the code from the form or the landing page template?

I don't know where that "honeypot" stuff is -- page or template -- but wherever it is, remove it.

[Anonymous]

Thanks Sanford Whiteman​ , working on getting it removed.