I've just noticed that setting Marketo module scope (mktomodulescope) to "true" adversely affects the ability to edit string variables in my template. Here's what I'm seeing:
- Setting the mktomodulescope to "true" renders the variable fields in the email editor blank and ignores any changes to those fields.Oddly enough, the default values are retained in the email preview regardless of what I do in the editor.
- I can edit the variable values if I add a new version of the module to the draft (not ideal).
- Once I remove the mktomodulescope declaration from the variable's meta tag, the editor respects changes (but obviously I lose the benefit of confining variables to a single module).
Is this just me? The template syntax checks out, otherwise. I've seen a few discussions about the mktomodulescope declaration over the past week or so.