While working on http://drupal.org/node/209242, I noticed that we don't flush the available update cache during update.php. That'd be another smart time to invalidate the cache, since whenever we're running update.php, it almost certainly means we installed a newer version of something, in which case, we want to check for available update data again.

Splitting this off into a separate issue/patch, since regardless of what you think about all the mtime business over at http://drupal.org/node/209242, this is still worth doing.

CommentFileSizeAuthor
#2 update_flush_caches_comment.patch1.04 KBdww
update_flush_caches.patch645 bytesdww
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Dries’s picture

Dries CreditAttribution: Dries commented
Status: Needs review » Fixed

I've added some code comments and committed this to CVS HEAD. Thanks, Derek.

dww’s picture

dww
we/he/they
CreditAttribution: dww commented
Status: Fixed » Reviewed & tested by the community
FileSize
update_flush_caches_comment.patch1.04 KB

Cool, thanks.

Minor followup patch to clean up the comment to meet our current conventions:
- First sentence of the phpdoc should be a summary and on its own line.
- No 2 spaces after periods.
- Wrap everything to 80 cols.

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy commented
Status: Reviewed & tested by the community » Fixed

Thanks, committed.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.