#109512Scheduler recycler garbage collection does not detect nested recycler folders in storages
Description
The TYPO3 scheduler task for fileadmin garbage collection currently only checks the direct subfolders of a storage root for a recycler folder. If a recycler folder is located deeper in the folder tree, it is not detected and therefore not cleaned up automatically.
This affects setups where editors work with file mounts pointing to subfolders of a real storage. In such cases, recycler folders inside these mounted subtrees are ignored by the scheduler task, because the task only inspects the first level below the storage root. The cleanup itself is recursive once a recycler folder has been found, but the detection of recycler folders is not recursive.
Expected behavior:
Recycler folders should either be detected recursively within a storage, or TYPO3 should clearly document that only recycler folders directly below the storage root are supported.
Actual behavior:
Only recycler folders on the first level below the storage root are considered. Nested recycler folders are ignored.
Additional note:
The public scheduler documentation currently says that “Fileadmin garbage collection” empties recycler folders in fileadmin, but it does not clearly mention this limitation for nested recycler folders.
Reviews 2
History 36
-
Garvin Hicking changed category <span data-processor="relativetime" data-value="2026-04-08T20:27:20+00:00" > 04/08/26, 20:27 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 96407 status
NewUnder Review <span data-processor="relativetime" data-value="2026-10-06T08:21:16+00:00" > 10/06/26, 08:21 </span> -
Gerrit Code Review pushed patch set 2 for main to change 96407 <span data-processor="relativetime" data-value="2026-10-06T08:42:48+00:00" > 10/06/26, 08:42 </span>
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 96410 <span data-processor="relativetime" data-value="2026-10-06T11:09:12+00:00" > 10/06/26, 11:09 </span>
-
Oliver Bartsch commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-10-06T11:15:11+00:00" > 10/06/26, 11:15 </span>Applied in changeset commit:cbbc97eb2256c4c359abecdda1f3dd157209399c.
Not sure if that is a feature. For me it’s a bug.
We have noticed this for a long time as well, and it’s really confusing because reading the documentation suggests that all recycler folders are emptied. We also use file mounts and have recyclers in subfolders so that editors have access to deleted files. We also have a scheduler task for garbage collection after X days, but the files are not removed in the subfolder recyclers. Furthermore, if you delete a folder with files inside a recycler from the subfolder, the folder is moved to the root recycler, but it’s empty. Deleted files are not moved.
*Basic solution:*
Delete all recyclers after a period of time via the scheduler.
*What would be even better:*
Make it configurable so that different recyclers can be emptied at different times (using multiple scheduler tasks).
To achieve this, find every recycler folder in file storages and show them in a “selectMultipleSideBySide” select element. Then, select the desired recycler folders and specify a time when those folders should be emptied. With multiple such scheduler tasks, you can configure the recyclers to be emptied at different times in different file mounts.