Details
-
Type:
New Feature
-
Status: Won't Do
-
Priority:
Minor
-
Resolution: Won't Do
-
Affects Version/s: 4.3.0
-
Fix Version/s: Unscheduled
-
Component/s: Core CiviCRM
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:Developer Doc
-
Funding Source:Needs Funding
Description
The current upgrade process with message templates seems a bit fragile. A developer needs to remember that a message template has changed. Copy the file to the Upgrade directory and add some boiler plate code in that directory. A lot of redundancy and hence potential for manual error
Ideally after any upgrade, we basically should update all the default message templates to the latest version. We can be smart and only do the update if the templates have changed (but since there are only 33 templates, doing all of them might not be too bad)