Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
base system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Dec 2007 at 08:49 UTC
Updated:
21 Dec 2007 at 17:01 UTC
Jump to comment: Most recent file
Comments
Comment #1
treksler commentedIt may be worse than that
it looks like it could be that the bullet doesn't show because cache doesn't get enabled AT ALL
I ran apache bench and results are same no matter what you choose
i get 13-15 requests per second (no matter which option i click)
Drupal 6.0B4
Path:/admin/settings/performance
OS: Red Hat Enterprise Linux AS release 4 (Nahant Update 4)
Server version: Apache/2.0.59
Server built: Feb 17 2007 06:24:55
PHP: PHP 5.1.6 (cli) (built: Feb 23 2007 06:56:38)
Zend Engine: v2.1.0
eAccelerator: v0.9.5
Xdebug: v2.0.0
anybody able to verify broken caching? b4 marking this as critical?
Comment #2
scoutbaker commentedDuplicated on a clean install of D6 HEAD.
Comment #3
scoutbaker commentedMarked http://drupal.org/node/198670 as a duplicate of this issue.
Comment #4
rkelly commentedThe problem is in the form implementation itself
In system.admin.inc on line 1187:
And then on line 1258:
Both form items are using the same key 'cache'
So come form submit the clear cache button #value is overwriting the cache setting.
Comment #5
catchI think this may have been fixed by: http://drupal.org/cvs?commit=90561
Could you test with a fresh drupal cvs checkout and report back?
Comment #6
hass commented@Catch: this patch only fixes the CSS and JS compression radio... not the caching mode bullet.
Comment #7
scoutbaker commented@catch: I also duplicated it last night with a fresh CVS install (#3).
Comment #8
catchQuite trivial, but critical nonetheless.
Comment #9
gábor hojtsySo does renaming $form['clear_cache']['cache'] to $form['clear_cache']['clear'] solve the problem? Seems to be a logical solution.
Comment #10
catchYes it does.
Comment #11
gábor hojtsyLook trivial, thanks, committed.
Comment #12
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.