The Cleaner module allows the admin to set a schedule for clearing caches, watchdog, and old sessions.
There are still times and/or cache tables that don't get cleared in any of those scenarios. Many sites will not be impacted by this, but a few will (just search on drupal.org and you will see many posts from people having problems).
Before you dismiss this module as "silly," which I did for a while after writing it, consider an actual experience. I maintain a site that is based on Panels, NodeQueue, and Views. In this set up, the cache entries can get very large after some time. MySQL has a parameter ("max_allowed_packet") that limits how much data can be read in. If this limit is exceeded, MySQL does not throw an error, rather it just provides what data it could read. With no error indication, the site just goes merrily on its way with what was given to it. In this case both the panel definition and NodeQueue contents went haywire. Clearing the cache resolved the issue for the moment.
Then I remembered this module that I had written and dismissed as "silly" after getting it working. Now, I will admit that the hooks provided here probably are "silly" but I had included them originally, so they are still there. I don't know why anyone would use them, but if you want, knock yourself out.
Drupal 7 Status
All functionality has been ported to the Drupal 7!
Drupal 8 Status
All functionality has been ported to the Drupal 8!
Found a bug or have a new feature idea?
Welcome -> Create an issue queue
- Maintenance status: Actively maintained
- Development status: Under active development
- Module categories: Administration, Performance and Scalability, Utility
- Reported installs: 507 sites currently report using this module. View usage statistics.
- Downloads: 8,724
- Automated tests: Enabled
- Last modified: June 5, 2016
- Stable releases receive coverage from the Drupal Security Team.
Look for the shield icon below.