MantisBT - v3.0 Release
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000910v3.0 Release[All Projects] Generalpublic2011-07-31 11:142013-10-31 06:19
Reporteropto 
Assigned Tocaseydk 
PrioritynormalSeverityfeatureReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version3.0.0 
Summary0000910: put ntotification emails into separate php file for better update handling
DescriptionI think the emails are a good point for individual coding.
It would be nice if they could be put into a file/class only for email notifications and included into the other code.

That way, the filename to include could be given as system value e.g. email.defauöt.php could be included as default, and other filenames for modified vers entered into a field in sysadmin.

Advantage: we won't have to touch core code to maintain our email code changes after every update. Similiar to email templates in other oss software, but we don't need such a complicated approach..
TagsNo tags attached.
Relationships
child of 0000154new  Pending Requests Hard-coded System Parameters 
Attached Files

Notes
(0002102)
caseydk   
2011-07-31 21:07   
(Last edited: 2011-08-09 12:51)
Completely agreed.. it's on the agenda for v3.0 in September.

The class - classes/w2p/Output/EmailManager.class.php - is an attempt to do just that. I see it working out as three steps:

- First, collect all the email, etc templates to one place (that classes);
- Next, flesh out a token-based replacement system when we can take a template and feed in the data and get a correct email out;
- Finally, move all the email templates into the database and build a simple interface for editing them in the admin.
(0002289)
caseydk   
2011-11-12 22:24   
This is getting merged into core later today;

Issue History
Date ModifiedUsernameFieldChange
2011-07-31 11:14optoNew Issue
2011-07-31 20:58caseydkRelationship addedchild of 0000154
2011-07-31 20:59caseydkProjectv2.4 Release (Closed) => v3.0 Release
2011-07-31 21:07caseydkNote Added: 0002102
2011-08-09 12:51caseydkNote Edited: 0002102
2011-09-27 23:50caseydkStatusnew => assigned
2011-09-27 23:50caseydkAssigned To => caseydk
2011-11-12 22:24caseydkNote Added: 0002289
2011-11-12 22:24caseydkStatusassigned => resolved
2011-11-12 22:24caseydkResolutionopen => fixed
2013-08-28 11:13caseydkFixed in Version => 3.0.0
2013-10-31 06:19caseydkStatusresolved => closed