# Return of "Expire Cache"

**URL:** <https://www.ruby-forum.com/t/return-of-expire-cache/152339>\
**Category:** Radiant CMS\
**Created:** [November 2, 2008, 5:48pm UTC](https://www.ruby-forum.com/t/return-of-expire-cache/152339 "2008-11-02T17:48:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mohits](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/bbe5ce/32.png) [@mohits](https://www.ruby-forum.com/u/mohits)\
**Post date:** [November 2, 2008, 5:48pm UTC](https://www.ruby-forum.com/t/return-of-expire-cache/152339/1 "2008-11-02T17:48:32Z")

</div>

Is it possible to have ‘Expire Page Cache’ to be returned to the UI…  
albeit as a configurable setting in a future version of Radiant?

I ask because there are some extensions that should affect cached pages

- the one I’m thinking of specifically is ‘Reorder’… after reordering,  
the page sequence of child pages can be altered and this may affect a  
navigation in a parent page. Previously, we could just hit the ‘expire  
page cache’.

Any ideas or suggestions?

Cheers,  
Mohit.  
11/3/2008 | 12:46 AM.

---

<div class="post-metadata">

**Author:** ![mohits](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/bbe5ce/32.png) [@mohits](https://www.ruby-forum.com/u/mohits)\
**Post date:** [November 2, 2008, 7:47pm UTC](https://www.ruby-forum.com/t/return-of-expire-cache/152339/2 "2008-11-02T19:47:30Z")

</div>

In the new RESTful controller design, we have an after\_filter that runs  
on all “modification” actions (create, update, destroy) to automatically  
clear the cache. It should be easy to add this in extensions. However,  
as far as the UI goes, I’ll leave that up to John and the UI team.

Sean

---

<div class="post-metadata">

**Author:** ![mohits](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/bbe5ce/32.png) [@mohits](https://www.ruby-forum.com/u/mohits)\
**Post date:** [November 2, 2008, 8:04pm UTC](https://www.ruby-forum.com/t/return-of-expire-cache/152339/3 "2008-11-02T20:04:35Z")

</div>

Thanks Sean. That would be great - I didn’t mean to criticize the  
extension itself - just meant that some times, the developer knows that  
a change s/he has made will affect numerous pages and it’s best to have  
the manual option to clear the page cache even though the system does  
its best to automatically clear the cache.

Cheers  
Mohit.