- Issue created by @rp7
- Issue was unassigned.
- Status changed to Needs review
about 1 year ago 12:28pm 14 May 2024 - last update
about 1 year ago 1 fail The last submitted patch, 3: node_revision_delete-revision_creation_time-3447094-3.patch, failed testing. View results →
- last update
about 1 year ago Composer require failure - last update
about 1 year ago 1 fail - last update
about 1 year ago 1 fail - last update
about 1 year ago 1 fail - last update
about 1 year ago 5 pass - Status changed to Needs review
about 1 year ago 3:42pm 14 May 2024 - 🇨🇭Switzerland berdir Switzerland
> This is incorrect. A past revision can be changed.
Why should a revision get deleted if it has been updated?
- 🇧🇪Belgium rp7
Not sure if that even matters? The plugin is falsely claiming to base a deletion based on the revision creation time, but in fact it's using the changed time (while there's a creation time available).
FWIW, we have a project where we update old revisions retro-actively, when - for example - we add a new (required) fields to the content type.
- 🇬🇧United Kingdom Rob230
We have this problem as well. I don't know what caused revisions to have a different updated date than created date, but it makes this module appear to not do what it claims, because in the backend the revisions are listed with the created date being X time ago, but they don't get deleted.