Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
base system
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Oct 2008 at 16:23 UTC
Updated:
14 Jul 2012 at 23:26 UTC
Jump to comment: Most recent file
Comments
Comment #1
dave reidLittle better title.
Comment #2
damien tournoud commentedThis is the combination of two issues:
1. DWTC->tearDown() don't flush the module_implements() static cache (this is bad)
2. there is no way to flush registry_cache_hook_implementations() static cache, so implementations of all modules loaded across a page request will get saved to the registry cache at the end of the request (when drupal_footer is called), even if the module_implements() static cache is properly flushed ===> the rogue implementations will be reloaded at the next request! (this is even worse)
(1) could be solved by a patch to DWTC... (2) is already solved by #298600: DBTNG: make module_implements work regardless of bootstrap phase.
Bumping to critical, since that could have other side-effects.
Comment #3
damien tournoud commentedNow that #298600: DBTNG: make module_implements work regardless of bootstrap phase when in, this is now worse: the implementation is permanently staying...
Comment #4
damien tournoud commentedEasy fix.
Comment #5
chx commentedThanks for the fix.
Comment #6
dries commentedCommitted to CVS HEAD. Thanks.