Closed (works as designed)
Project:
Drupal core
Version:
6.10
Component:
update.module
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
26 Mar 2009 at 22:04 UTC
Updated:
1 Jan 2011 at 19:01 UTC
Update.module seems to be forgetting its data, even just a few minutes after the last check. Doesn't matter whether I check manually or run cron, it only retains its data very briefly. It looks like it forgets it's data every time the modules page is submitted (not just loaded).
Steps to reproduce:
I do have two modules installed which are works in progress and thus not in CVS yet (so they lack version info). Could that be related?
Comments
Comment #1
dwwEvery time you submit the modules page, update status clears its cache of available update data. That's because you might have enabled modules, and it wouldn't have the info about those. This is expected behavior, not a bug.
Comment #2
seanrWhy not have it re-fetch the update data on submit? I think this is actually a usability issue - the current behavior is rather unintuitive. If it confused me (I've been building Drupal sites for five years), it'd definitely be an issue for new users.
Comment #3
darrellduane commentedI agree that this is confusing, and I've been using Drupal for 3 years. I think seanr's idea is good. Alternatively, rather than clearing the entire cache, perhaps there is a way to preserve the cache data and update it as needed only for the modules that have been turned on and turned off .
I think the way to fix this is to override the submit form handler #submit to call a new function which re-fetches the update data, and then perhaps add it as an option to the DrupalTweaks module or something. I did some work on this 'cos it was bugging me.
Here's a quick snippet you can put in one of your custom modules to make this fix:
Comment #4
darrellduane commentedhttp://drupal.org/node/1010526 has been submitted for a feature request for the the Drupal Tweaks module.
Comment #5
dwwNote: tweaks and UI fixes for update status module that can't make it into core b/c of string freeze and other rules generally go into http://drupal.org/project/update_advanced
Cheers,
-Derek