Opened 5 years ago
Last modified 4 months ago
#51717 new feature request
Emails in WordPress (Templating and Sending methodology)
| Reported by: | | Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Keywords: | 2nd-opinion | |
| Focuses: | Cc: |
Description
Hello,
One issue that has come up with clients and the ability to apply branding to emails consistently across website generated emails. Because plugin developers need to implement their own templating for emails.
Some Woo-commerce extensions use the Woo-commerce system, which is great, but some don't. Between contact forms (not WooCommerce related), Orders and WordPress emails etc, its quite problematic to implement a consistent presentation for emails across the system.
Another item I've noted - is with my custom apps built previously we have used a scheduling system to send system generated emails, this excludes delays for very important items like forgotten passwords. But essentially all it is, is a database table for to be sent emails, that are sent after that point in time. This could also be used as a log.
I understand this could be setup as a plugin, but if implemented well and inline with the desired future functionality of WordPress could be a nice addition to the system and could have some small performance improvements for requests that generate emails (this is was observed by myself moving to this setup with custom apps/sites/software in the past it is now my standard in any application of quality).
Change History (3)
#2 
@
5 months ago
- Keywords needs-patch 2nd-opinion added
One of the proposed ideas I was following along with was this one: implementing some sort of templating system for email messages.
This was originally proposed in #49661 but since that ticket is a mix with 5 or 6 proposals at the same time, I'm trying to dissect them into smaller pieces. I intended to create a new ticket regarding this topic, but since this already exists, I might be taking it to step forward in this direction.
Still, the original idea was to have a template to have a uniform internal mechanism for all emails, not really for the users. As you say, this seems a little more like food for extenders, as each single email content (and hopefully soon subject) using wp_mail has a specific hook to modify its content.
Let's keep this open until we find a solution for this.
Related: #18493