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.
Posted1 week 1 day ago by Martin Price | System Horizons Ltd (yorkshirepudding) in Weekly Meetings
Recent comments
I am guilty (in Drupal) of using PHP Filter in places just so I can use l() and url(), since my paths are very different between dev and prod servers.
For example, at the top of my Views,...
In the meantime I also need something like https://www.drupal.org/project/entityreference_autofill in Backdrop. Has anyone made progress on the port, or are there interesting alternatives...
Posted20 hours 25 min ago by Olaf Grabienski (Olafski) on:
- In Backdrop CMS the update.php file located in the /core folder (mydomain.com/core/update.php).
- For launch the update.php from address bar of the browser, without restrictions, you...
OK so I have tried several things among which are running Update.php as withe mysite,com/update.php Going to Home adn running update there coing to performance adn running ipdate there. I all...
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.