Incorrect interpretation of root and workspace params in email templates

[michael-e]

Posted on the Symphony website (by Komb):

Root solves to "http://hostname/var/www/blah/blah/emailnewslettermanager/lib/" Workspace behaves the same, but with added workspace folder of course.

Very bad for building absolute image paths and such.

[michael-e]

This is not related to ENM but to the ETM (Email Template Manager). I will close the issue here and post it over there.

[michael-e]

See michael-e/email_template_manager#27

[creativedutchmen]

Oh yes this is an ENM bug alright. The reason for this is that the background process is not an apache process, so the DocumentRoot variable does not make sense to it. Will fix!

[michael-e]

Any news on this? It's a bit of a showstopper for me at the moment.

Or is there a workaround I don't think of?

[michael-e]

For now I worked around this by adding another datasource which contains the root param's value.

[michael-e]

I thought about this a bit more. Symphony can run on several domains, so the only safe solution would be to pass the domain with the ENM's API call and save it to the newsletter table. (The deprecated Email Newsletters extension did exactly this.)

If it's about images, you can add a hardcoded $root-email parameter to your email templates and work with that. The real problem I see will be authors who have been told to use links like the following when writing in Symphony:

[visit our contact page](/contact/)

This, of course, won't work with a "universal image domain" if your Symphony website delivers content based on the domain name.

I may address this when all the other bugs are fixed. I'd like to know if anybody has a better idea than the one I outlined above.