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.
As I work through things I flush the caches after every change I make.
As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
If you haven't already, flush all the caches.
If it is in the modules folder whether directly or in a custom folder it will show up. If not, something else is wrong with your site; check...
Posted12 hours 59 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
Awful idea! That's not how modules get installed! The number in db indicates the installed state and schema version. You're not supposed to fiddle in the database directly. There's an...
... had a status of '0' that I changed to '1' directly in th edb, in line with other custom modules
Awful idea! That's not how modules get installed! The number in db...
Yes that much I know :)
Thanks for the quick reply...
My info file contains:
name = Fix Zero Search
description = Fixes leading zeros in search.
type = module...
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.