digitalpoint
Well-known member
There are a few issues here...
1. Email templates are hard-coded to be blue... At the very least, shouldn't they be using the style variables like @PrimaryLight?
2. Admin templates aren't saved as files when you have that option, so there ends up being a lot of PHP code that needs to be compiled on the fly rather than being able to use an opcode cacher (any time the system sends an email).
3. This is more an overall thing, but why are admin templates completely separated from normal templates? We end up with two totally different systems that ultimately serve the same purpose. To make it worse, the admin template system isn't kept in-line with the normal templates. Wouldn't it make more sense to have one consolidated template system and just have an "admin" flag for admin templates? Then we could edit and search admin templates (which include non-admin things like outgoing emails) as well as the advantages as having admin templates (and emails) saved as files so the opcode cachers can do their magic...
1. Email templates are hard-coded to be blue... At the very least, shouldn't they be using the style variables like @PrimaryLight?
2. Admin templates aren't saved as files when you have that option, so there ends up being a lot of PHP code that needs to be compiled on the fly rather than being able to use an opcode cacher (any time the system sends an email).
3. This is more an overall thing, but why are admin templates completely separated from normal templates? We end up with two totally different systems that ultimately serve the same purpose. To make it worse, the admin template system isn't kept in-line with the normal templates. Wouldn't it make more sense to have one consolidated template system and just have an "admin" flag for admin templates? Then we could edit and search admin templates (which include non-admin things like outgoing emails) as well as the advantages as having admin templates (and emails) saved as files so the opcode cachers can do their magic...
Upvote
49