Currently, if a module weighted equally to Block Cache Alter (most, unless the module specifies its weight) implements hook_block_info_alter(), and the module's short name comes after Block Cache Alter, that module's alterations of cache settings will override any setting selected through the Block configuration UI.

Seems like we should ensure block cache settings configured through the UI should always take precedence.

CommentFileSizeAuthor
#1 blockcache_alter-blockcache_ui_configs_take_precedence-2173799-1.patch688 bytesiamEAP

Comments

iamEAP’s picture

iamEAP commented
Status: Active » Needs review
StatusFileSize
new blockcache_alter-blockcache_ui_configs_take_precedence-2173799-1.patch688 bytes
fabianx’s picture

fabianx commented
Status: Needs review » Reviewed & tested by the community

**RTBM**

fabianx’s picture

fabianx commented
Status: Reviewed & tested by the community » Fixed

Committed and pushed to 7.x-1.x. Thanks!

  • Fabianx committed 88b0ed2 on 7.x-1.x authored by iamEAP 
    Issue #2173799 by iamEAP: Fixed Ensure block cache configuration made...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.