It is not possible to create multiple drafts of a node and selectively edit them.
Steps to repro:
Take an existing node - let's call it "original".
Create a new draft. This becomes "draft 1".
Create another new draft of "original" or "draft 1". This becomes "draft 2".
You'll now have original as current with 2 drafts above it.
There is no way to edit draft 1.
WIthout revision moderation enabled, revisions work pretty much the same way. You can't edit old revisions - only revert to them. Multiple drafts need to be editable, so we need to find a way to make it work differently.
Comments
Comment #1
webchickYeah, this is a limitation of core: you can't edit revisions, only view them.
I'm marking this "won't fix" for now, since it doesn't have anything to do with revision_moderation, although I may fix it eventually by adding a custom revisions tab where I can control more what's shown here.
Comment #2
webchickComment #3
webchickWell, actually. I should probably assign this to core.
How this would work is another op 'edit' would be added to node_revisions(). This would take you to a form which populated the various fields based on a $node->load() for that revision ID. Additionally, an "edit" operation would be added to the revision table in node_revision_overview().
Comment #4
webchickComment #5
coreb commentedMoving out of the "x.y.z" queue to a real queue.
Comment #6
pasqualleComment #7
tstoecklerStill valid. At least a proper CRUD API for revisions should be added, I think.
Comment #8
colanSubscribing.
Comment #9
jhedstromCore now has forward-revisioning. Marking this as a duplicate of #2477419: Codify mechanism to set a forward revision as the default revision.