Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Installed dev version. No cached pages were being served (no http header generated, no footer on any page).
Installed beta1 version. Worked as expected.
Comment | File | Size | Author |
---|---|---|---|
#7 | boost-check_core_cache_enabled-1717506-7.patch | 863 bytes | soundstripe |
Comments
Comment #1
bgm CreditAttribution: bgm commentedCan you enable the boost debug and see if you can trace the issue?
You can also enable the boost block to see if there is something blocking the cache to be generated for anon users.
Comment #2
soundstripe CreditAttribution: soundstripe commentedI worked around this by installing the beta1 version. It worked. I will try the dev version again soon.
Comment #3
asistentweb CreditAttribution: asistentweb commentedI had the exact same problem. I couldn`t find the problem ( I am not the most advanced Drupal user).
Could enabling the query log in the Devel module be the problem? I gave permission for annonymous users to check the log for testing purposes.
But after disabling the query log, boost still wasn`t generating cache.
Anyway, my solution was to disable->uninstall->clear caches->run cron->delete boost folder->reinstall
Now it is working fine. If I manage to reproduce it and find out what is causing it I will post it here.
Comment #4
soundstripe CreditAttribution: soundstripe commentedJust reinstalled latest Boost dev version.
1) Delete old boost folder
2) Download/untar the new dev version
3) configure settings
4) no boost-cached pages being served
5) perfomance->clear caches
6) boost pages served correctly
Comment #5
bgm CreditAttribution: bgm commentedIs the core cache enabled? It should be disabled (otherwise the core cache can be generated before boost, and then subsequent calls to that page do not get a full run, so the boost cache is not generated). Can you confirm if this was the case?
(we should probably implement a hook_requirement() + disable core cache when boost is installed)
Comment #6
soundstripe CreditAttribution: soundstripe commentedBy core cache, you mean the checkbox that says, "cache pages for anonymous users," right? If so, then yes this was enabled. Didn't know it shouldn't be.
I agree with the recommendation to implement a hook_requirement() -- this way it could appear on the status page as a (potential) error in the configuration if both caches are enabled.
Comment #7
soundstripe CreditAttribution: soundstripe commentedhere is a patch against the 7.x-1.x branch
Comment #8
asistentweb CreditAttribution: asistentweb commentedSo the core cache and all the options in the Performance page should be disabled?
(Cache Blocks,Compress Cached and Aggregation) as the core shouldn`t cache anything, so there would be nothing to compress.
Am I correct?
Comment #9
bgm CreditAttribution: bgm commentedThanks for the patch! I will commit when I have a few mins.
We should also improve the documentation in the handbook: http://drupal.org/node/1459690 (+ there is a good comment about how the filesystem setting is unnecessarily confusing).
jynx_cj: you should still leave Aggregation enabled. Only core cache should be off. Block/Views cache can be on, iirc it can still be useful for logged in users. Depends on how dynamic you site is (the block cache could be stale when the boost cache is regenerated).
Comment #10
bgm CreditAttribution: bgm commentedPatch committed to 7.x-1.x (fixed in 7.x-1.0-beta2) and updated the handbook.