Jump to content

Recommended Posts

Posted

A setting could work, but I'm not sure how best to implement it. Consider the following cases..

 

1. We add an https option for email templates, how do we enforce it? We could do a string replace for http:// and change it to https:// within the template before sending it, but if you add any http links in your templates, they would be converted as well, and this could be a big problem.

 

2. During install, (or immediately after), we could ask that question, and simply update all email templates to use that schema. This would be a one time conversion and mean that adding http:// links in your templates later work work fine and not be converted.

 

Do you have any suggestions?

 

I understand that manually updating all the email templates can be a pain, and we want to minimize the necessity to do so wherever possible. The only way I can see this working well, is some kind of post-install wizard that asks common questions like this.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...