Mautic TWIG Advanced Templates Bundle

This looks like its stemming from another issue.

Try this, delete our plugin folder. Then try the plugin reload again. If it still fails then its confirmation its not this plugin.

If it no longer fails then, send me your specific mautic version and I’ll spin up another instance and test also let me know if you have other plugins installed that could cause conflicts so I can install those too while testing.

I am using the plugin now and I have no issues with it but I am willing to spend some time fixing a few edge case bugs.

I love your motivation! Many thanks.
The error is still there. It is some other issue.

I’ll keep on searching…

I’m using the latest 6.0.7 version.

My installed plugins are:

AmazonSesBundle MauticCloudStorageBundle MauticFullContactBundle MauticTagManagerBundle
AmazonSesBundle.bak MauticCrmBundle MauticGmailBundle MauticZapierBundle
GrapesJsBuilderBundle MauticEmailMarketingBundle MauticOutlookBundle
MauticClearbitBundle MauticFocusBundle MauticSocialBundle

The only difference with plugins between your instanec and mine is AmazonSesBundle.

Why are you using that plugin? According to the documentation “This plugin enable Mautic 5 to run AWS SES as a email transport and provide a callback to process bounces. Tested in Mautic 5.0.0 to 5.2.0

I am asking because I also use AWS SES to send all emails, but I do not have that plugin. I just plugged the SMTP details in the email settings and it works fine.

I think you should try debugging from that standpoint. Remove it clear cache, reload plugins and see what happens. You can plug your SMTP credentials from AWS directly in the email settings in the UI.

I’m using it to send my emails via Amazon SES.

I understand. What I’m saying is that I’m also sending emails using Amazon SES, but I don’t have that plugin installed. Instead, I entered the SMTP credentials directly in Mautic’s email settings, and it works fine.

Additionally, that plugin only guarantees compatibility with Mautic 5, which means it could be the cause of the issue you’re experiencing. Since this plugin is both potentially incompatible and unnecessary, and it’s the only difference between your setup and mine in terms of plugins, it’s a likely source of the problem which should be tested.

You Genius! That did the trick!

I deleted the AmazonSES Plugin, deleted the cache, reloaded the plugins and voila, there is your plugin!

Many thanks for your patience!

I’m excited using it now!

Have a merry, blessed Christmas.

Christian

Glad I could help!

1 Like

Sorry, for disturbing again. But I have the following issue:

I have a new segment email and added some conditional lines. Unfortunately, the conditions are not resolved, but show up in the email.

Any hint?

Read from here down. Seems you typed it all into the text editor. You have to edit the MLJM code. And use blocks. Link will take you to the specific section with that instruction

Many thanks. Makes sense.

Unfortunately, there is still something wrong:

	<mj-raw>{% if contactfield.title == '0' %}
	</mj-raw>
	<mj-raw>{% if contactfield.du_sie == 'Sie' %}
	</mj-raw>
	<mj-text>Sehr geehrter Herr {{ lead.lastname }}!
	</mj-text>
	<mj-raw>{% else %}
	</mj-raw>
	<mj-text>Lieber {{ lead.firstname }}!
	</mj-text>
	<mj-raw>{% endif %}
	</mj-raw>
	<mj-raw>{% else %}
	</mj-raw>
	<mj-raw>{% if contactfield.du_sie == 'Sie' %}
	</mj-raw>
	<mj-text>Sehr geehrte Frau {{ lead.lastname }}!
	</mj-text>
	<mj-raw>{% else %}
	</mj-raw>
	<mj-text>Liebe {{ lead.firstname }}!
	</mj-text>
	<mj-raw>{% endif %}
	</mj-raw>
	<mj-raw>{% endif %}
	</mj-raw>
	<mj-raw>{% else %}
	</mj-raw>
	<mj-text>Hallo {{ lead.firstname }} {{ lead.lastname }}!
	</mj-text>
	<mj-raw>{% endif %}
	</mj-raw>

Result, see screeshot.

That markup does not look right. I’d have to fully understand what you are doing. here is an sample real email template in use now tempmjml - Pastebin.com

The data you are using in conditions should be sent in token over api.

Many thank Ryon for your help! I really appreciate it very much!

I’ll check it and come back to you.

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.