Upgrade path test/document
| Project: | Revision Moderation |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Anyone tested upgrade path for this? RM itself shouldn't be an issue, but the "related" stuff has all changed:
- Actions moved to core
- Views completely changed and now handles revisions itself
- Workflow NG is gone and replaced by Rules
So we should probably at least document what this means for users (i.e. big fat warning) before they merrily go to upgrade. Notably, if they are using WorkflowNG, they are screwed, since we have no Rules equiv code in RM for D6. They will need to find a way to set up their workflows using core actions and triggers.
I suspect users will need to rebuild any kind of actions/workflows that were using in 5 and probably need to rebuild any views they were using. I've no idea if the views handlers, etc. RM provided in 5 are all replicated in Views' revision handling now.
#1
Regarding views, there are filters which are not replicated in revision handling. One of them is: only show revision under moderation, or published revisions or even older revisions. So, a filter for the revision state. Sorry I can't help further on the port. Nice work Addison!
#2
>Notably, if they are using WorkflowNG, they are screwed, since we have no Rules equiv code in RM for D6
Upgrading workflow-ng integration shouldn't be hard. Rules already makes use of the core actions too, so there is only an action for "Publish a content revision" missing. Then you could easily do an upgrade path by converting configured old actions to the new ones: see http://drupal.org/node/299303