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.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...