Feature Request: Recycle bin

[PeterBizQIT]

Describe the feature you'd like
When deleting a whole book, chapter or a single page it gets deleted immediately. I would like to see a recycle bin feature so books, chapters and pages don't get deleted right away. When a book, chapter or page is moved to the recycle bin the user can choose to delete it permanently. Also, there should be an administrator configurable setting for automatic removal of items in the recycle bin after x amount of days which can also be disabled.

Describe the benefits this feature would bring to BookStack users
This should prevent accidental removal of books, chapters or pages.

[derek-shnosh]

Excellent suggestion.

[qianmengnet]

Yes, it's very important, because the book might have been written very hard, and deleting it might have just clicked the button twice

[heroin-moose]

Yep, this is kinda must have. This is one of the last issuees that prevents us from moving the knowledge base to the BookStack.

[davidbremser]

We have spun up an internal BookStack environment and have been putting it through the paces to see if it fits as our internal Wiki / documentation portal. We are quite keen to move forward with it, but just discovered this "Achilles heal." We accidentally deleted a book (all chapters and pages included of course) and realized there is no Activity tracking, or even worse, no restore / undo / recycle option. We did take a look in the DB and could see reference to where it was, and the user id that deleted it, but for all purposes it was gone, along with the content. Fortunately we were able to restore from a snapshot, but this is a bit of a deal breaker.

We are looking at creating a separate "Recycle" shelf to hold items for deletion by a "super admin" but hardly a good solution. Any chance this enhancement or feature request is on the immediate roadmap?

Very nice product otherwise - appreciate the hard work!

[sexy-trousers]

I have to agree - not having the ability to undelete/restore items or elements is a major flaw.

It's just my 2 cents, but I'd stop any work on authentication API's and other features and focus on the basics as a) mistakes happen and b) image the disasters a disgruntled employee could do!

I would image adding a status flag to the elements wouldn't be too bad (active/inactive or visible/hidden) with an option to purge the hidden bits every X days - but I totally understand if its not that easy...

But I have to say, even though it's awesome, its not something I can recommend to my company or peers until an undelete/recycle bin feature is in place..

Thanks for all your hard work so far! TJ

[Rumcajsev]

I totally agree with this request - this seems like the last thing from the REALLY necessary basics.
As @sexy-trousers said, I believe that this should be at the highest priority.

[dopyrory3]

Yeah we really do need to get this working, we've had to setup cron jobs to keep daily backups and do manual SQL insertion to deal with recovery now.
This would be the most important feature for our deployment, accidents happen.