Component Cache Expiration

Experimental project

This is a sandbox project, which contains experimental code for developer use only.

This module allows blocks, panels, views and other page components to respond to cache expiration events triggered by the Cache Expiration module. This allows the individual components on a specific page (blocks, panels, views, etc.) to be purged when that specific page is being purged from the cache by the expire module.

Built in Support

There is currently built in support for the following components:

How does it work?

This module's design is similar to the Cache Tags module, but does not require any modifications to Drupal core. It works by creating lists of components used to render a page. When the page cache is expired by the expire module, this module will match against the list of components used to render the page being expired, and expire each of those components in turn.

When to use this module?

I want my authenticated user caches (block, views, panels) to be expired when the anonymous user (page) cache is expired.
I want a drop in solution for keeping views, panels, block content fresh.
I want to control my views, panels, block, and page cache from one place.
I want functionality similar to Cache Tags in Drupal 7.x without hacking core.

Basic Installation

Download the expire_components module to your drupal contrib modules folder.
Enable the expire_components_common module.
Create a view or panel with time-based expiration and set the cache lifetime to the maximum possible value.
Configure the Cache Expiration module as you normally would.