Caching issues

[laryn]

I'm not sure if it's my server or recent changes to Backdrop caching, but I've been noticing really aggressive caching on CiviCRM webforms -- changes don't show up for a long time or until I manually clear caches. What do you think about including a node-specific cache clear upon saving changes?

From Zulip in a separate topic:

Luckily, turns out Backdrop allows clearing cache for individual node pages with cache('cache_entity_node')->flush();.

[laryn]

Potentially related comment from @herbdool in a separate module's issue queue:
backdrop-contrib/corresponding_node_references#2 (comment)

[herbdool]

What part of the Webform is not updating? Does the problem appear with Webform even without CiviCRM?

[laryn]

@herbdool I haven't noticed it happening on the main Webform > Components page when adding normal components. When I add contacts in the CiviCRM tab and check the box on one or more fields to add to the form, it sends me back to the Webform > Components page but the components aren't showing until I clear the "Page and else" cache.

[herbdool]

I'm not sure if entity cache would affect this. We'd need to find out if Webform takes advantage of entity_cache at all.

[jackaponte]

When I add contacts in the CiviCRM tab and check the box on one or more fields to add to the form, it sends me back to the Webform > Components page but the components aren't showing until I clear the "Page and else" cache.

Confirming that I've observed the same behavior!

[laryn]

This note from @indigoxela may be relevant here, too?
backdrop/backdrop-issues#5304 (comment)

[herbdool]

@laryn I think you were right about entity cache. Oddly github search wasn't bringing up any results when I searched for "cache" or "cache_entity_node" in this project so I was initially at a loss. Luckily a local search brought it up. Fixed 4ee1eec. I think I'll make a patch release.