Clean old revisions about bookstack

[Eragaus]

Old and useless revisions can take a lot of space because the number of them can increase significantly. Moreover, the useless ones can be removed. That is why it would be nice, being able to clean revisions, like cleanup image buttons. We could also remove them according to a date filter. Le mer. 12 juin 2024 à 12:23, Dan Brown ***@***.***> a écrit :

…

Thanks for the request @Eragaus <https://github.com/Eragaus>. Can you confirm specifically what you want to achieve as a result of cleaning revisions? What is your functional end goal via such a feature? You mention clearing the database, but I want to further understand why that's important to you. — Reply to this email directly, view it on GitHub <#5063 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKP3L7ZSGROADUDIH3XKZ43ZHAORRAVCNFSM6AAAAABJFEDNY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSGY2TCOJUG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ssddanbrown]

Thanks for the request @Eragaus.
Can you confirm specifically what you want to achieve as a result of cleaning revisions? What is your functional end goal via such a feature? You mention clearing the database, but I want to further understand why that's important to you.

[szabeszg]

We could also remove them according to a date filter.

+1 as currently I manually delete old revisions one by one, which is quite tedious. A cron job would be also welcome to clean up old revisions.

For the GUI side of things, here are two screenshots from ProcessWire showing how admins can manage log entries in the backend (chop / burn):

I could imagine something similar regarding BookStack's revisions, both globally and on a page-by-page basis.

[Eragaus]

I imagined the same UI, it perfectly fit with the main Bookstack theme. Le sam. 15 juin 2024 à 16:32, Szabesz ***@***.***> a écrit :

…

We could also remove them according to a date filter. +1 as currently I manually delete old revisions one by one, which is quite tedious. A cron job would be also welcome to clean up old revisions. For the GUI side of things, here are two screenshots from ProcessWire showing how admins can manage log entries in the backend (chop / burn): ProcessWire-log-manager.png (view on web) <https://github.com/BookStackApp/BookStack/assets/7194945/40694512-7d5b-4830-9f03-de2ae56272e6> ProcessWire-log-manager-chop.png (view on web) <https://github.com/BookStackApp/BookStack/assets/7194945/383c4f0b-8af0-44d8-bacf-2e1875c3bb58> I could imagine something similar regarding BookStack's revisions, both globally and on a page-by-page basis. — Reply to this email directly, view it on GitHub <#5063 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKP3L732ZX5GEZ3U6V4HC53ZHRF7JAVCNFSM6AAAAABJFEDNY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRZG44DMNZTHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>