I suspect your Content Security Policy may have something to do with that?
The redirect is inline JS, so if your CSP is blocking that… it won’t execute.
I’m not even seeing it be output though… so there may be a different issue, but that screenshot does not show me the field config… so I can’t tell for sure.
Here is a screenshot of the form configuration.
http://prntscr.com/y21bbv
Hope that helps?
FYI- There’s no need to have oid as a hidden field, the plugin passes that with the POST request automatically, and having it in your form code just invites direct spam to your via the web to lead API.
Unfortunately, that doesn’t help — it looks like the form is stuck on the validation step. As I don’t know everything that’s running on your site, and can’t duplicate the issue on my development setup… it’s virtually impossible to diagnose the actual issue from afar — as it’s unique to your site’s config and mix of plugins, themes, and CSP.
Are you:
– Seeing any leads in Salesforce?
– Receiving any confirmation emails from the plugin?
Does it work if the recaptcha is disabled?
We are seeing leads in salesforce but they are coming in as duplicates. Most likely because when users submit the form they are unsure if it worked the first time as there is no feedback and it does not redirect.
I disabled the recaptcha and it didn’t work.
Any other ideas?
Thank you.
@camarchi01 are you using WPBakery for your blog/page builder by chance? I’m having the same issue and another thread suspected WPBakery as the culprit
@jzmiles Ha, Hi Jeannie. This is actually “Archibald”. We are trying to troubleshoot the same thing. 🙂
@camarchi01
From what I can see on your site, the Javascript redirect is not even being output – so something else (possibly your page builder or a security plugin) is removing that before the shortcake output is included in the page.
OR
Something else is causing the submission to fail, but I can’t troubleshoot that from the front end, unfortunately.
Or, your content security policy (CSP) is causing the browser to remove the inline JS.
@camarchi01 wow! shows you how I much I read, I didn’t even notice that the link you originally posted was ours, hahahaha!
