Closed (duplicate)
Project:
Drupal core
Version:
8.0.x-dev
Component:
node system
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
20 May 2014 at 05:13 UTC
Updated:
10 Nov 2014 at 17:20 UTC
Jump to comment: Most recent
Comments
Comment #1
rooby commentedI have not yet checked whether or not this is an issue in Drupal 8.
Comment #2
dcam commentedThe same is still true in 8.x.
Comment #3
johnpitcairn commentedPersonally I think some local tasks should be present on all revisions. The Revisioning module is a good starting point.
When viewing an older entity revision, the "revisions" local task should remain active, and there should be a "view published" (or "view current") primary local task to get you back to the current revision.
There should also be secondary local tasks corresponding to actions you can perform on the revision you are viewing: "revert to this revision", "delete this revision", etc. Perhaps an active secondary local task "revision [vid]".
Way back in Drupal 6 I wrote an extension of that model which also provided "next revision" and "previous revision" secondary local tasks - my clients were very appreciative of the ability to step through revisions.
View current | Revisions
<< Previous | Revision 1196 | Revert to this | Delete this | Next >>
Comment #4
rooby commented@John Pitcairn:
I agree.
As far as hook_menu() goes, what you describe as primary local tasks would be MENU_LOCAL_TASKs and what you describe as secondary tasks would be MENU_LOCAL_ACTIONs.
Comment #5
johnpitcairn commentedI think I might also expect the draft revision and edit to remain directly accessible if appropriate. Draft always points to the latest revision (if that is newer than the published revision). Assuming full permissions:
View current | View draft | Edit draft | Revisions
<< Prev | Revision 1196 | Revert to this | Delete this | Next >>
There are perhaps some UI issues around this: what happens when the user steps through revisions and arrives at the current revision or draft revision? Does the primary active tab change? Do the local tasks remain? Or do we stay on the "Revisions" tab and the "Revision xyz" label changes to "Current revision" (and revert/delete disappear)?
Comment #6
rocketeerbkw commentedClosing this as duplicate of #1108888: Add actions and/or tabs to a node's revision view