Closed (fixed)
Project:
Drupal core
Version:
5.x-dev
Component:
base system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Jan 2008 at 23:11 UTC
Updated:
14 Oct 2008 at 06:38 UTC
Jump to comment: Most recent file
Comments
Comment #1
bdragon commentedSame for HEAD.
Comment #2
gerhard killesreiter commented1 line change, good to go, already live on drupal.org.
Comment #3
gerhard killesreiter commentedThis should go into D6 first.
Comment #4
gábor hojtsyGreat, committed to 6.x. RTBC for 5.x.
Comment #5
hass commentedAre you really sure this makes sense?
If a cache is not flushed successfully - the variable shouldn't tell it is flushed successfully. This change sounds very illogical and keeps stale data.
Comment #6
gábor hojtsyHass, the variable_set() never checked the success of the query, so there is no such change as you explained.
Comment #7
drummCommitted to 5.x.
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #9
etamar commentedHi guys,
I think the "well rounded" / "good" behavior would be adding a global variable to determine "being flushed", and not use the "flushed" variable as it is confusing and erratic as hass correctly mentioned.
This is from a good practices point of view,
To your review,
Etamar
Comment #10
mot commentedetamar, doesn't work the fix for you?
Comment #11
mot commentedNo answer, so a positive is assumed. Closed again.