Our website was built by outside contractors. After updating Bean module from v. 7.x-1.2 to 1.7 we started seeing a problem similar to an old Issue #1216572. Basically, changes to our content blocks do not show up unless all caches are explicitly flashed. I tested the current Bean dev version and it has the same problem.

Comments

sherakama’s picture

StatusFileSize
new911 bytes

I am also having the same issue with the cache_block table not being cleared out on a save. This is a problem because even authenticated users see the old content instead of the new updates. Attached is a patch that adds a clear to the cache_block table.

sherakama’s picture

Priority: Normal » Major
Status: Active » Needs review
ibotvinn’s picture

I have applied sherakama's patch (bean-block-cache-clear-save-2201503-1.patch) - and the problem is gone. Many thanks!

sherakama’s picture

Status: Needs review » Reviewed & tested by the community

Based on the above comment I am marking as RTBC. Lets get this in!

jlyon’s picture

The patch from #1 was clearing all of my bean caches, but it wasn't clearing the block or page cache, so if a bean was saved and no node was saved soon after, the page with the bean would not updated until cron was run (or longer). This patch clears the `cache_page` and `cache_block` caches in addition to all of the bean caches every time a bean is saved, matching the cache clears when the node save form is submitted.

This is probably overkill, and this could probably be done more elegantly with the expire module, but it solved a recurring issue for me on a couple of sites.

  • fmitchell committed 1f40ae4 on 7.x-1.x authored by jlyon
    Issue #2201503 by jlyon, sherakama | ibotvinn: Fixed Block cache not...
fmitchell’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

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