Updating node blocks on node save
chrissearle - January 1, 2009 - 09:44
| Project: | Tagadelic |
| Version: | 6.x-1.2 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
Jump to:
Description
At present - tagadelic blocks use the cache tables for their information.
When the cache is not present - it regenerates the blocks.
The cache is emptied by cron.
This means that all changes have to wait for the next cron run.
The attached patch (against DRUPAL-6--1) would give the administrator the option to set for tagadelic to clear its values from the cache at (any) node save.
Not sure if its useful for the module - but its a change I find useful personally - so I thought I'd just throw it out there :)
| Attachment | Size |
|---|---|
| clear_cache_on_save.patch | 1.96 KB |
#1
First: there are API-functions to clear a cache. Please use these instead of poking around in the Database.
Second: a recent change to the cache (see -dev release) should probably fix your issue: cache is now less stale.
Third: even if it does not really solve your issue: we still do not want a full cache-wipe on every node-save. On many sites this is unwanted behaviour: it will render caching almost useless on sites like drupal.org.