Why am I getting an "Invalid Module" error? Please help.

Question

I'm getting an "Invalid Module: #rich-text-one-button-1" error when trying to approve my Marketo email template. I'm not a Marketo expert but I'm the closest thing my client has to one and I'm stumped.
The error specifically mentions #rich-text-one-button-1. Looking at my template, I have two "Rich Text One Button" modules - one with id rich-text-one-button and another with id rich-text-one-button-1. Both modules appear to use the same variable names for their buttons.
Here's the relevant structure:
Variable Declarations in Head:
html

First Module (this one works):
html

${richTextOneLinkText1}

Second Module (this one causes the error):
html

If you haven't already, you will soon be receiving your first invoice. To ensure everything is clear and easily understood, we've wanted to provide this helpful visual guide and glossary of terms that will walk you through each part of your invoice.

${richTextOneLinkText1}

The container structure:
html

Both modules appear to reference the same variables (${richTextOneLink1} and ${richTextOneLinkText1}), and the second module has id="rich-text-one-button-1" which matches the error message. The template has many other modules defined as well (Rich Text Only, Rich Text with two buttons, Rich Text Grey Background, Split Column modules, Featured sections, Icon variants, etc.).

Dave_Roberts · Answer

Here's a link to the Marekto Docs on email modules:https://docs.marketo.com/display/public/DOCS/Email+Template+Syntax#EmailTemplateSyntax-ModulesHere's an excerpt from that, I've highlighted in red the rule about modules inside a container, I think that might be what's messing up your validation.ModulesModules are templatized sections defined at the template level that will show up for end users to insert into their email. Because you have pre-built these modules, you can ensure they will interact with the rest of your email content gracefully (in a fully responsive manner). You can only put a module in a container.For containers of type, , , or :Specified using with class=”mktoModule”For containers of type

:Specified using with class="mktoModule"It looks like the error your getting relates to the first module in the 2nd "container" (

) in the HTML.In a fairly standard setup you'd have one large body

that had themktoContainer class and then every inside of that would have themktoModule class. The key ingredient here is that the container must be the "parent" element and the modules must be a direct "child" of that parent element.I'd try to have the architecture of the html rewritten so that you've got one

that's the parent container (like a body table) and then directly inside that table, row-over-row, you'd include a (module). In short, you could try to combine the table wrappers you're using into a single wrapper (

) and give that the "mktoContainer" class.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded