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.
Posted2 weeks 4 days ago by Martin Price | System Horizons Ltd (yorkshirepudding) in Weekly Meetings
Recent comments
I second this-- I have a module in contrib now that I just marked as "deprecated", and I removed its sole alpha release (because a fix in Core made it obsolete). Just plain deleting the module...
If there's some time left in the dev meeting - although it might rather be a topic for the PMC:
We have nice documentation and procedures, how to provide projects in backdrop-contrib space...
You can edit this View (/admin/structure/views) to suit your needs. The MORE link is used to display additional results, which can sometimes be useful.
Hello,
I have a question about the block “Recent blog posts”.
I've set it up so that the five most recent blog posts are always displayed on the page (mybackdrop.de/blog) at the TOP...
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.