Wordpress update and Marketo Forms issues | Community
Skip to main content
A
Anonymous
April 3, 2018
Question

Wordpress update and Marketo Forms issues

  • April 3, 2018
  • 2 replies
  • 4518 views

Hi,

Anyone experiencing issues with embedding Marketo forms on their WordPress website?

We are using the Divi builder and all our forms were integrating nicely by using the Embedded script provided by Marketo interface.

This morning though none of our forms are appearing on our wordpress site, they do still work on Marketo Landing pages and our other website that uses a different CMS.

The console shows that the Marketoform2 element isn't being recognized.

Anyone has experienced similar issue?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

SanfordWhiteman
SanfordWhiteman
Level 10
April 3, 2018

Surely you must understand that without a URL, no one can troubleshoot this.

A
Anonymous
April 3, 2018

I guess sometimes with CMS updates people may have experienced the same issue.

But here is a URL as an example: https://www.console.com.au/consolepay/ 

the form usually sit under "Want to learn more about Console Pay"

SanfordWhiteman
SanfordWhiteman
Level 10
April 3, 2018

There's still no link.

A
Anonymous
April 3, 2018

We've found the issue.

We are not sure why it started to do this but because we had a line break in the script, Wordpress had started to add <p> markup in the middle of the tag, then it started to break.

We've removed those and the forms that seems to be working.

Our other CMS did not experience this issue.

SanfordWhiteman
SanfordWhiteman
Level 10
April 3, 2018

The page when I looked at it had this markup:

<p><script data-cfasync="false" src="/cdn-cgi/scripts/d07b1474/cloudflare-static/email-decode.min.js"></script><script src="//app-sn04.marketo.com/js/forms2/js/forms2.min.js"></script></p>
<form id="mktoForm_1237"></form>
<p><script>MktoForms2.loadForm("//app-sn04.marketo.com","412-OQY-612",1237);</script></p>

That wasn't causing an error in Firefox nor Chrome unless Tracking Protection was enabled. It's valid HTML5.

You'll find the form still doesn't load with Tracking Protection enabled.

A
Anonymous
April 3, 2018

Thanks - We've tested on several browsers and machines.

You may have looked at the page once it was fixed as we had someone looking at.

Removing that spacing in all our pages seems to have fixed the pbs on all browsers.

Terms & ConditionsAccessibility statement

Loading footer...