Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.0.0-b1
-
Fix Version/s: 4.0.0-b1
-
Component/s: None
-
Labels:None
Description
Throughout the system we ask for HTML and Text versions for emails. Primarily through email templates, however, it is possible to send email directly to a client using the Email feature on their client profile page, and as of 4.0 via the Mass Mailer plugin.
At least in the case of sending a direct email to a client, no text version has to be entered and an email can be sent with an HTML only version. In mail clients that choose not to render HTML, these would appear as blank emails.
Instead, what we should do is automatically generate the text version if it does not exist at the time the message is sent. This would at minimum involve stripping tags and converting breaks to new lines. There may be some build in method to accomplish this already, but I'm not aware of it.
Issue Links
- blocks
-
CORE-2134 Mass Mailer: Do not require Text version of email
- Closed
No email currently needs either an HTML or Text version in order to be saved/sent.
The UI will need to be updated to denote the behavior that HTML is converted to Text if not provided, and will need to be added to the documentation.
Should this apply to email signatures? If so, the rule validating Text will need to be removed and the `email_signatures` table will need to be updated to allow for the text field to be null.
Should this apply to the package welcome email? If so, the Text version needs to be generated at the time the package is saved. Otherwise, the service creation email template will reference a
{package.email_text}tag in its Text version that could contain no information when sent.