[
http://jira.magnolia.info/browse/MAGNOLIA-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka updated MAGNOLIA-1191:
----------------------------------
Fix Version/s: Ideas
> ADMIN INTERFACE: Option to Remove Obsolete XML Files in Development Tools
> -------------------------------------------------------------------------
>
> Key: MAGNOLIA-1191
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1191
> Project: Magnolia
> Issue Type: Improvement
> Components: admininterface
> Affects Versions: 3.0 RC4
> Reporter: Sean McMains
> Assignee: Philipp Bracher
> Fix For: Ideas
>
>
> The new "backup configuration" option in RC4 is super, and makes doing
> backups much nicer. Thanks for adding that!
> One thing that would improve it even more is to have an option to remove
> obsolete XML files from the root directory specified.
> Consider, for example, a user who goes through this sequence.
> 1. Sets up a new Magnolia instance
> 2. Backs up his config, using the tool
> 3. Creates individual accounts, deletes superuser account
> 4. Backs up his config, using the tool
> 5. Has trouble with his installation
> 6. Deletes the repository, allowing Magnolia to bootstrap and recreate it
> At this point, because the superuser account was exported in Step 2, it is
> recreated, thereby opening a security hole, even though it wasn't present
> during the last backup in step 4.
> My suggestion: in step 4, the tool should remove the XML files that aren't
> from the current export, thereby ensuring that items that have been deleted
> don't come back to haunt you later on.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------