Most pages, like blog posts, are never touched again, so the check never runs again. Their revisions should still be cleaned up after the time period. Some of ours had YAML linting issues. We had to delete those via the CLI now.
It would be great, if there was an option to do this via the Grav scheduler or a separate CLI command.
I just realized there were still revisions in the pages, even though they have been expired according to the
limits.older
timeframe. Checking the CLI and docs, I didn't find any commands that I would need to trigger. Checking the code it became clear, that there is no process run on the Grav schedule, but only a check when a page is modified: https://github.com/david-szabo97/grav-plugin-admin-addon-revisions/blob/0dc9c9a6cb64a58b3a2c8aadc4af1a35dc3a8702/admin-addon-revisions.php#L228-L241Most pages, like blog posts, are never touched again, so the check never runs again. Their revisions should still be cleaned up after the time period. Some of ours had YAML linting issues. We had to delete those via the CLI now.
It would be great, if there was an option to do this via the Grav scheduler or a separate CLI command.