Posted by traxer on November 22, 2008 at 11:11am
Jump to:
| Project: | Cache Disable |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | postponed |
Issue Summary
The 6.x version does not work at all.
The cache API is included during DRUPAL_BOOTSTRAP_EARLY_PAGE_CACHE. At that time, the database layer is not yet initialized (that's done during DRUPAL_BOOTSTRAP_DATABASE). All variables that are available during DRUPAL_BOOTSTRAP_EARLY_PAGE_CACHE come from settings.php. The full blown variable system is initialized even later during DRUPAL_BOOTSTRAP_LATE_PAGE_CACHE.
Comments
#1
This is a drupal issue but it's a feature not a bug
#2
This means, the variable that the cache_disable module sets in hook_enable() will not be available during Drupal's bootstrap phase. So the cache implementation provided by this module is actually never used. This makes the 6.x-version of the module essentially useless.
According to http://drupal.org/node/156119, the status 'by design' indicates: "The reported issue has been deemed not to be an issue. It is either an intentional part of the project, or the issue is caused by manually applied customizations of a user (wrong configuration, code alterations, theme override functions)."
I mark it as 'postponed', because there is no way of fixing the 6.x-version of this module.
#3
> All variables that are available during DRUPAL_BOOTSTRAP_EARLY_PAGE_CACHE come from settings.php.
Could this be fixed by requiring variables to be set in settings.php?