Your software
My Mautic version is: 3.1.0
My PHP version is: 7.4
Your problem
My problem is:
I want to use dynamic web content in an email, but it seems that the {dynamiccontent=“XXX”} token only works to refer to dynamic content specific to that email.
Ideally, I’d like to reference one piece of content across multiple emails. Specifically, I’m trying to promote an upcoming webinar across multiple campaign emails. When the webinar is done, the campaign emails will remain, and I"ll want to update all of them again to reference the next webinar and so-on.
Dynamic Web Content seemed like an ideal way to do that, and the Variables documentation page referenced the {dynamiccontent=“XXX”} token under “Dynamic Web Content” but when I put a slot name in the token, it doesn’t work. The token remains in the email after it’s sent.
What am I missing? Is there no way to re-use content between campaign emails?
I just tried it, and unfortunately your workaround didn’t work for me. It seems that Mautic (now?) strips html from merge fields. So to do this, I’d have to create a field for every single snippet of text, every image, and every target url. That’s too many fields, considering the 64-field limit is still in place
I also want to mention Kuzmany’s MauticCustomTags plugin, which would allow me to pull in the content via an html file stored somewhere convenient. Twig Tempaltes is faster, though, because my team doesn’t have to create the HTML file and upload it.
Ultimately, I’d love to use the Dynamic Content twig extension in the Mautic Advanced Templates Plugin that @joeyk mentioned, but it’s not compatible with Mautic 3, which we are now on and we’re working to migrate all clients to in the next few months. That is the best solution to this challenge because it gets us a WYSIWYG editor and logic for personalization.
I think this is a fantastic idea and I imagine these codes working similar to how Wordpress shortcodes work. This feature should be part of Mautic core.
Funny how they think they can charge for it. The virality of the GPL license makes this licensing impossible since they cannot forbid distribution of “infected” code. The only way around it is to not distribute part of the code and build a client-server model, ensuring the server does not depend on GPL’d code.
This reminds me of Wordpress where no one seems to understand how the GPL works…