Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I might be understanding this wrong but it looks like the patch that got applied in #1154908: context_reaction_block.inc doens't load blocks as drupal core does, creating inconsistent behavior unset block caching.
unset($block_info["{$row->module}-{$row->delta}"]->status);
unset($block_info["{$row->module}-{$row->delta}"]->visibility);
unset($block_info["{$row->module}-{$row->delta}"]->cache);Due to this, blocks are not getting their cache settings respected. In my case I use BLOCKS_CACHE_PER_PAGE for all blocks on an anonymous site with cache_blocks saved in memcache. I see nothing in memcache, however if I comment out the above lines, blocks are cached properly as set.
Is there a reason for this and an alternative way to get caching working perhaps? I noticed the first patch http://drupal.org/files/issues/context-should-load-all-block-table-field... did not do the unsetting of $block_info attributes but was adding the last patch.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2037793-block_caching-2.patch | 676 bytes | marcelovani |
Comments
Comment #1
girishmuraly commentedSetting to major since caching is a major factor that needs to be working for all sites.
Comment #2
marcelovaniSince this patch has been applied, blocks are not being cached.
This affects only blocks placed by context.
I have removed the culprit line.
Comment #3
tekante commentedPatch committed. Thanks for the bug report and the patch.