Add pageaction "clear recycler" to context menu of recycler (doktype 255)
Added by Daniel Wagner over 6 years ago.
Updated about 3 years ago.
Backend User Interface
User tidied up pagetree by moving pages into recycler.
Someone has to delete everything in the recylcler.
As user friendly solution could be adding a pageaction "clear recycler" to the context menu of any recycler icon (doktype 255).
Enable recursive deletion, delete every subtree within the recycler and do not forget to disable recursive deletion.
TYPO3 CMS 7.6.15
- Category set to Backend User Interface
- Status changed from New to Needs Feedback
Hi and sorry for the late answer
Maybe I am understanding this wrong, but... AFAIK the "recycler" pag (doktype=255) is not the "recycler" feature/module. The module lists all records (possibly filtered by table) that have been removed using the TYPO3 delete button (that marks them with "deleted=1").
If you move your pagetree inside a page with doktype=255 you are not "deleting" them but it's like moving them inside a sysfolder (still AFAIK).
you can enable the recursive deleting of pages in the user preferences
you can empty the recycler using a scheduler task
Please tell me if I understood it wrong or explain better your scenario.
- Status changed from Needs Feedback to New
You understand it right, it's about the sys_folder "recycler".
The request, as I understand it, is to have "recursive deleting" inside recycler sysfolders without changing user preferences. Which sounds logically.
Or maybe have a user prev "Allow recursive deleting inside recycler folder"
Sorry for the long absence, I return on this topic:
I sense here a wording problem here: if we add a "clear recycler" to the context menu of the pages with recycler icon (doktype 255), it....would not clear anything, but it would actually delete the pages and you should go the "true" recycler module and clear them again (for real, now!)
To be more correct, the context menu item should be called "send everything to recycler" (from a recycler!)
I don't know what would be the best way to proceed to disambiguate this situation (apart from deprecating and getting rid of the doktype 255 pages (I guess it is a leftover of the first TYPO3 versions)
One idea could be add a task to the scheduler module that deletes everything inside all the doktype=255 pages - I guess that this could be done with an external extension, too)
- Related to deleted (Bug #11538: Deleting page which has (deleted) subpages)
Also available in: Atom