[ http://jira.magnolia.info/browse/MAGNOLIA-1678?page=comments#action_15230 ] Vivian Steller commented on MAGNOLIA-1678: ------------------------------------------
done for core module filters with r13228: - filters will be backed up completly (under config:/backup/filters) - warnings will be displayed if either class, priority, parameters or bypasses have changed (or the filter even didn't exist before) To complete this task, a warning message should be displayed if a module still has filters registered in its configuration. > Update of filter configuration > ------------------------------ > > Key: MAGNOLIA-1678 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1678 > Project: Magnolia > Issue Type: Task > Components: updatemechanism > Affects Versions: 3.1 M3 > Reporter: Grégory Joseph > Assigned To: Vivian Steller > Fix For: 3.5 RC2 > > > We should at least > - check if the current filter configuration is the same as the 3.0 default. > - if so, just replace it with the new default > - if not, copy it somewhere so that users can reproduce their existing > customisations, and bootstrap the default > Being more fine grained seems too complex at the moment, since the filters > config was changed drastically. -- 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 ----------------------------------------------------------------
