PKP Bugzilla – Bug 6212
export e-mail templates
Last modified: 2013-05-29 15:53:20 PDT
We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.
It would be nice to have an export/import plugin for the e-mail templates in use by a journal. While I can see and edit the initial e-mail templates in the xml-file, the modified e-mail templates of a particular journal are stored in the database (that can not and should not be manipulated by journal managers). For testing purposes, for migrating, or for adapting the e-mail templates to a second journal (e.g. of the same journal family) it would be nice to have a way to import and export the modified e-mail templates.
Marco, the reason that modified templates are stored in the database is precisely so that they *can* be modified by Journal Managers -- which is pretty commonly done. Did I misunderstand, or do you have a different requirement?
(In reply to comment #1)
> Marco, the reason that modified templates are stored in the database is
> precisely so that they *can* be modified by Journal Managers -- which is pretty
> commonly done. Did I misunderstand, or do you have a different requirement?
Sorry, I should have been more precise. What I had in mind is: The modified templates are (of course) stored in the database (that can not and should not be manipulated by journal managers *directly*). But whenever journal managers want to access all templates at once (e.g. bulk edit them (important!), adapt them for another journal etc.) they have no simple way to do so. They could ask someone to get a sql dump - but this is not very convenient and they probably would have to do some kind of sql -> xml/text -> sql process to store, modify and upload the templates. This is exactly what I'd like to suggest as another OJS feature: export and import email templates in XML.
Reassigning for eventual consideration. This should probably be considered with the broader journal-migration issue in mind, esp. from 2.4.x->3.x.