Cms: Static Cache not invalidated when entry or term deleted, or global updates

Created on 9 Sep 2020  路  9Comments  路  Source: statamic/cms

Bug Description

If you use static caching and you delete an entry or a term, they are not removed from the static cache. Cache is not invalidated when globals are changed either.

How to Reproduce

  1. Enable static caching
  2. Create an entry
  3. confirm exists
  4. delete entry
  5. attempt to visit entry...it should fail but doesn't.

Environment

Statamic version: 3.0.7

bug caching critical

Most helpful comment

I've created a PR that implements the GlobalSet and Navigation part of this issue, #2639.

All 9 comments

Confirmed!

Seems critical to me, I'll leave that up to core.

Got the same problem. The same goes for collection ordering. Changing order doesn't trigger a clear cache.

Two clients on the phone today wondering what they did wrong.

Extra info: It also doesn't invalidate when make edits to a navigation.

I might be going out of line here, but I'm labeling this critical. This makes it hard to use caching in production.

Entry and term URLs will be invalidated when you delete them in 3.0.14

I want to get a release out today and didn't have time to add the global and nav handling. They'll come later.

Very nice Jason! Thanks.

I've created a PR that implements the GlobalSet and Navigation part of this issue, #2639.

Nice!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

aerni picture aerni  路  4Comments

wm-simon picture wm-simon  路  3Comments

riasvdv picture riasvdv  路  4Comments

mattrothenberg picture mattrothenberg  路  3Comments

ReneWeCode picture ReneWeCode  路  3Comments