[2010-07-11] Partial Caching should invalidate on ?flush=all

[silverstripe-issues]

created by: @chillu (ischommer)
assigned to: hfried
created at: 2010-07-11
original ticket: http://open.silverstripe.org/ticket/5807

---

Currently its too complicated to invalidate partial caches in templates (you basically have to comment out the <% cache %> part. I've talked to Hamish a while ago, we think it'd be more intuitive to invalidate caches on ?flush=all as well (it roughly fits in the "clear template cache" thinking). This has to be limited to ADMIN access of course, to avoid denial of service attacks.

[halkyon]

This is something I ended up doing in my own _config.php on a project, seems like a good idea for it to happen in the core though.

[froog]

+1 for this feature, I always thought it strange (and frustrating) that ?flush=all didn't clear partial caches.

[kinglozzer]

Well, it seems this feature was accidentally added in d3b63da, and then accidentally removed by me in d012b79. Shouldn’t be too hard to implement, just need to flush the cache named “cacheblock”.

I appreciate this should be master, but would it be better to make this 3.1 instead? Given that the behaviour, although a bug, has existed throughout versions 3.0 - 3.1.5.

[kinglozzer]

Scratch that, it seems the new Flushable stuff has resolved this