Yep, just tried that. Doesn't help. If my custom tags were getting replaced in those message I would not think it matters whether or not the message is sent as plain text or html, but a good thought.
Something else I've noticed... I added a new global to one of my templates in hopes of using it in the mail templates (ie <%base_url%> to provide a different website url in the automated emails depending upon which domain a person signs up for). Instead the script now throws a 500 Internal Server Error on the last step of signing up, I assume when it tries to send one of the automated e-mails and runs into my new tag. Fortunately they still get signed up and can sign in if the go to the sign in page.
Any other ideas on a work around. This seems like it should be a pretty standard feature when working with multiple domains.
cheers,
Michael
seaturtle.org
Something else I've noticed... I added a new global to one of my templates in hopes of using it in the mail templates (ie <%base_url%> to provide a different website url in the automated emails depending upon which domain a person signs up for). Instead the script now throws a 500 Internal Server Error on the last step of signing up, I assume when it tries to send one of the automated e-mails and runs into my new tag. Fortunately they still get signed up and can sign in if the go to the sign in page.
Any other ideas on a work around. This seems like it should be a pretty standard feature when working with multiple domains.
cheers,
Michael
seaturtle.org