Problem/Motivation
In #2453153: [PP-1] Node revisions cannot be reverted per translation we are addressing the problem of reverting node revisions without overwriting changes in translations that were not affected by the reverted revision.
Several UI improvements were suggested but we decided to implement a minimal fix there a discuss a better UI in a separate task.
The following use-cases were identified that are poorly or not at all supported by the current UI:
- List only revisions affecting the current translation.
- Compare revisions affecting the same translations.
- Select translation languages to be reverted.
Proposed resolution
We have several suggestions that need feedback and validation from the UX team:
- Revision listing could be improved by simply filtering out from the revisions list non-relevant items, and improving contextual information so for the user is clear she is seeing revisions related to the current translation. This would match the Drupal 7 UI.
Alternatively we could list all revisions, provide an additional column displaying the affected translation languages and add a widget allowing to filter the revision list to show only items affecting the selected language. - Always filtering the revision list by language would automatically fix comparison, as we would match the Drupal 7 UI, the translation language would be implied by the current context.
Instead if mixed revisions were displayed, we would need to prevent the user from selecting revisions not affecting a common translation. The user would also need to specify which language translation should be compared in. - Again, if adopting the contextual approach we would just offer a link to revert the revision in the current language.
In the other scenario we would need to allow the user to specify the languages of the translations to be reverted.
Remaining tasks
- Evaluate the various proposals
- Propose an improved UI
- Implement it
- Review patches
User interface changes
TBD
API changes
None foreseen
