[ 
http://jira.magnolia.info/browse/MAGNOLIA-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906#action_15906
 ] 

Ryan Gardner commented on MAGNOLIA-2081:
----------------------------------------

To get an easy way to test this bug on a live system, see: 
http://jira.magnolia.info/browse/MAGNOLIA-1095

> Development Tools - Backup should handle errors gracefully and notify of any 
> failures
> -------------------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2081
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2081
>             Project: Magnolia
>          Issue Type: Bug
>          Components: admininterface
>    Affects Versions: 3.5.4
>            Reporter: Ryan Gardner
>            Assignee: Philipp Bracher
>            Priority: Minor
>
> The backup in the development tools does not notify you when your backup 
> fails. If you do not monitor your server logs, you will have no way of 
> knowing the backup failed.
> The backup just says "files backed up successfully" to whatever path you 
> said, regardless of if they succeeded or not. 
> The expected behavior is to: 
>  - when a certain node has an error, mark that node as suspect, and continue 
> to backup the rest of the tree
>  - notify the user of all nodes that had errors... ideally pinpointing the 
> exact contentNode that had an issue (such as paragraph00 has an invalid XML 
> character (dumping the exception message))
> The current behavior is: 
>  - Regardless of what happens, tell the user the backup succeeded.

-- 
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/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to