Bug 6212 - export e-mail templates
export e-mail templates
Status: NEW
Product: OJS
Classification: Unclassified
Component: Journal Management
3.0
All All
: P3 enhancement
Assigned To: PKP Support
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-16 06:10 PST by Marco Tullney
Modified: 2013-05-29 15:53 PDT (History)
2 users (show)

See Also:
Version Reported In:
Also Affects:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Tullney 2010-11-16 06:10:43 PST
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.
Comment 1 Alec Smecher 2010-11-16 08:23:45 PST
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?
Comment 2 Marco Tullney 2010-11-16 10:05:17 PST
(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.
Comment 3 James MacGregor 2013-05-29 15:53:20 PDT
Reassigning for eventual consideration. This should probably be considered with the broader journal-migration issue in mind, esp. from 2.4.x->3.x.