Posted by Pustefix on May 13, 2008 at 12:35pm
| Project: | Tagadelic |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hello,
are the tadclouds meant to be refreshed by hand or is there any kind of cron-job, who updates the tags in the tagclouds, when a user adds a new tag?
thanks for Your help,
Josef
Comments
#1
Tagclouds are cached. When the cache is refreshed your tags will be refreshed. We decresased the cache time in the latest version, so the next release should show changes faster.
#2
Bèr, any indication from what value to what value the time is decreased. I'm using tagedelic and 24 hours ago I wrote a new story with some new tags, but they show neither in Tags of tags nor /tagadelic.
How long should I wait? 24 hours?
#3
My tags won't refresh until I run update.php
I consider this a bug.
#4
The problem is that the code only checks whether cached data exists -- not if it's out of date.
You can resolve this in several ways. One way is to simply delete all tagadelic caches whenever a node is saved. The new cloud will be generated upon the next view.
Here's a patch that does that. You probably could add additional checks (like, only delete the caches if the node's tags have actually changed), but that's beyond the amount of time I have to devote to this.
Thanks,
Curtis.
EDIT: Updating patch to fix stupid syntax error.
#5
For 1 hour reflesh change the code in tagadelic.module file at modules/tagadelic
cache_set($cache_name, $tags);
line with following
cache_set($cache_name, $tags, 'cache', time() + (60 * 60));
Drupal cache will do the rest, no cron, no click!
#6
I dropped in the .diff changes and it seemed to update the tagadelic (tags) page but not the Tag on Tags block. Is there somewhere else in the module that it needs a refresh command to? Is that stored in the same cache or a different one completely?
-UPDATE : I added a few tags and it seemed to update so it looks like the fix is in.. Thanks guys for a very nice module.
#7
then it is fixed?
Please, all people in here: maintaining a module is a LOT of work: you can help by cleaning out your issues, if they are solved! Saves me hours of issue administration. Hours I can then spend on fixing and improving a module!
#8
Line 232 in 6.x-1.x-dev for anyone who cares.
#9
Automatically closed -- issue fixed for two weeks with no activity.