Those six hours is the reason why temporary file aren't immediately deleted when cron tasks run. If then there are many temporary file to delete, a single run isn't sufficient to delete all the files.
Hello @herb,
I think your way of describing it is quite elegant.
Speaking for myself, I find rooting around for settings to be quite the drag.
A nice feature of the /admin/...
Posted3 hours 28 min ago by Graham Leach (Graham Leach) on:
I think a use case would be helpful in me understanding your question.
Of the top of my head, it sounds like what you are looking for are module-specific settings. Each module can "own"...
For me, while I do find it a little tedious to try and search on the module page or scroll down a long list...
I do know where the functionality is, so I don't have to try and find the...
@robertgarrigos
I understand now. In terms of using config files as a shortcut to building content types, fields, and views - I think that you are good and don't need to worry about that...
In case anyone is coming to this issue now. Paragraphs was released quite a while ago and is a pretty popular module for Backdrop CMS.
https://backdropcms.org/project/paragraphs
Comments
The cron job system_cron() will delete temporary files after the max time stipulated by a constant (6 hours)
Those six hours is the reason why temporary file aren't immediately deleted when cron tasks run. If then there are many temporary file to delete, a single run isn't sufficient to delete all the files.