Upgrading to 2.2 (and 2.x-dev) breaks CCK Blocks when block caching is enabled
capellic - May 20, 2009 - 14:35
| Project: | CCK Blocks |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | duplicate |
| Issue tags: | block caching, CCK 2.2, CCK 2.x-dev, CCK blocks |
Jump to:
Description
Not sure if this is best resolved in CCK or CCK Blocks, but 2.2 has provided some problems with CCK Blocks. The gory details can be seen here: http://drupal.org/node/425186
Basically, if block caching is turned on, anonymous users can't see the blocks. If you're logged in, you see them, but they appear on every page and it's always the cck blocks for the last node saved.
#1
This only happens if block caching is enabled.
#2
Then this would be a CCK Blocks issue.
#3
Do you have a suspicion about what CCK Blocks might be doing incorrectly as of 2.2? THANKS KAREN!
#4
I think, we have a second issue for that problem in #425186: upgrading to CCK 6.x-2.2 causes CCK blocks to disappear.