Attention: The Marketo Community will undergo scheduled maintenance on Tuesday, August 20th between 10-11 PM PDT. During this time, the Community and its content will not be accessible. We apologize for any inconvenience this may cause.
Hi all,
I read in a previous post that IE9 is no longer supported when redirecting a form. I'm worried because I can't control which browser somebody uses when they fill out a form and click submit. The form/landing page redirects just fine in Chrome and Mozilla. Has this been an issue for anybody else?
I appreciate your feedback. Would like to know if there is a way to work around this.
Thanks, Tom
This is not correct. IE9 is no longer supported for using the Marketo application, but is fully supported for user-facing content like landing pages and forms. Have you actually seen this occur, or is this just hearsay?
Hi Kenny,
I imported myself as a test and registered but in internet explorer once I click submit on form it won't redirect to thank you landing page like it's supposed to. But it works in Chrome and Mozilla.
There's likely some conflicting javascript on your page causing an error during the click or the submission. If you share a link where you're seeing this, we may be able to help you find the issue.
Hi Kenny,
Link is below...I fill out form in Chrome and form redirects to thank you page but I'm not seeing that after I click submit in Internet Explorer. I'm using IE v11 too.
https://info.dh.com/WBN-YYYY-MM-DD-Webinar-ID-Description_LP-Registration.html
It's working fine in IE11 and IE9 for me. Do you have any extensions running in your IE installation?
I was having some issues with the way IE was displaying pages and how forms were handled. I places this piece of code in the header of my landing page template
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
One of the issues I was experiencing is that Marketo uses a "foreach" loop in some of it's form script and IE doesn't recognize the "foreach" loop. Also, the CSS was being interpretted incorrectly. This code fixed all of the issues.
We have run into this too recenlty. We added <meta http-equiv="X-UA-Compatible" content="IE=11; IE=10; IE=9; IE=8; IE=7; IE=EDGE" />
Note, edge alone does not cover all IEs out there.