Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
system.module
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Oct 2008 at 02:40 UTC
Updated:
21 Jan 2009 at 15:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
kbahey commentedComment #3
lilou commentedSee: #335122: Test clean HEAD after every commit and http://pastebin.ca/1258476
Comment #4
catchNice find, confirmed that hitting the button continues to clear CSS caches, RTBC.
Comment #5
dries commentedCommitted to DRUPAL-6 and CVS HEAD. Thanks!
Comment #6
damien tournoud commentedPlease revert.
The submit handler for system_performance_settings() is system_settings_form_submit(), so the explicit #submit calls to drupal_clear_css_cache and drupal_clear_js_cache *are* needed.
Comment #7
catchDamz is right - while you can clear those caches by hitting the button, we /also/ need to clear them when saving the form. My fault for RTBC-ing too quickly.
Comment #8
damien tournoud commentedFun! This was released in both 6.7 and 6.8...
Comment #9
damien tournoud commentedBumping to critical, if you change the page compression settings, a mix of compressed and uncompressed pages will be stored in the cache_page table...
Comment #10
dave reidYeah that is a bad, bad condition to have. Marking as RTBC since all that is need is a rollback of the patch in the top post.
Comment #11
dave reidWait, no we need a new patch to clear the cache if settings are changed, not just when the clear cache button is clicked.
Comment #12
swentel commentedSimple patch.
Comment #13
damien tournoud commented@Dave: it has never been the case. Form-level submit handlers are not called when button-level handlers are defined.
This patch tried to fix an issue that doesn't exist.
#12 is RTBC. Please commit on both D7 and D6.
Comment #14
dries commentedCommitted to CVS HEAD and DRUPAL-6. Thanks!
Comment #15
robertdouglass commentedDid this get rolled back? Does it need a status update? http://drupal.org/cvs?commit=162924