[
https://issues.apache.org/jira/browse/ROL-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza closed ROL-1742.
---------------------------
Resolution: Won't Fix
Templates are just regular files, for the relative handful needing this
functionality, they can be emailed or stored in a version control system
without us needing to duplicate and maintain such functionality in Roller.
> Personal Theme (file) import/export functions
> ---------------------------------------------
>
> Key: ROL-1742
> URL: https://issues.apache.org/jira/browse/ROL-1742
> Project: Apache Roller
> Issue Type: New Feature
> Reporter: Dave Levy
> Assignee: Roller Unassigned
>
> I would like to see a better personal theme version control scheme.
> I suppose I'd like two buttons,
> a 'save theme version' button, this might have a names property as well
> and a 'revert to' button, these might be file based or all files in the theme
> could be collected into a theme
> while we're at it, an import/export file function might be good since one
> could develop the theme in a new blog user and then transfer across without
> roller administrator rights.
> This description does not create a definition for a theme file set.
> These features should be available to all individual users that have
> customised their theme.
> Good, I should make it clear that I expect the import and export buttons to
> > work from a browse dialogue and so the versions will be held in the Users
> > own non-roller file space. i.e. on their latop/network disk etc.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
