Hi,

I'm experiencing problems with the block cache.
The subscription form is supposed to be different depending on the available lists & whether you are anonymous or not (as per emf_subscription_list_form).
But when I turn on block caching, and follow the scenario where an anonymous user registers for an account and then subscribes to the newsletter, he is still urged to enter his email address (even though we already have it), and receives a form validation error upon submitting.

This is most likely caused by the BLOCK_CACHE_GLOBAL setting for emf blocks.

CommentFileSizeAuthor
#1 emf_block_cache-1095682.patch1.41 KBsvendecabooter

Comments

svendecabooter’s picture

svendecabooter
he/him
Primary language Dutch
Location Gent
commented
Status: Active » Needs review
StatusFileSize
new emf_block_cache-1095682.patch1.41 KB

Attached is a patch that changes BLOCK_CACHE_GLOBAL to BLOCK_NO_CACHE.
Initially i wanted to change this to BLOCK_CACHE_PER_ROLE, but that still gave problems: after the user updated the form to subscribe to the mailing list, the block was still visible after reload of the page, where it should have been gone, since he is already subscribed.

Hopefully this doesn't break any other logic :)