If you go to the revisions tab and select Delete for a revision, it will not delete the revision (even though the message says it was deleted). This is due to the deleteRevision implementation in ContentEntityStorageTrait.php:
public function deleteRevision($revision_id) {
// Do nothing by design.
}
So, the initial question is, is it simply the case that what multiversion is doing is simply not compatible with deletions of revisions; if there is a requirement that revision deletion is needed, then multiversion (and therefore the deploy suite) cannot be used?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | multiversion-revsision-delete-2735057-1.patch | 2.24 KB | brenk28 |
Comments
Comment #2
brenk28 commentedWould something like the attached patch be worthwhile? Something that sets the delete flag in order so that it doesn't appear in the revisions tab. Or are there too many implications and that is not feasible? Essentially, it's just removing the revision from the list in order for the end user not to be confused that a deleted revision is still showing up. I suppose if this isn't feasible, the alternative would be to override the RevisionOverview form to remove the delete option.
Comment #3
jhedstromSetting to needs review.