Cache Class

Namespacing

You may want an extra layer of organization to your cache items, either for easy management or to prevent collisions with other keys in the system.

For example, let’s say we have an add-on called MyAddon and we want to make sure our cache keys don’t conflict with any others in ExpressionEngine, whether they be from other add-ons or native code. We’ll save and access our data like so:

ee()->cache->save('/myaddon/mykey', $data);
$data = ee()->cache->get('/myaddon/mykey');

We can go even further and nest our namespacing as deep as we want for further organization:

ee()->cache->save('/myaddon/entries/239', $data);

Where this comes in handy is clearing subsets of our own cache. If a condition arises in which we must flush all the items in our /entries/ namespace, we make this call to Cache::delete:

ee()->cache->delete('/myaddon/entries/');

With that, all the items we saved under /entries/ will be deleted while the rest of the items stored under our root namespace are kept. We can also clear the entire cache for our add-on without flushing out cache items for other add-ons or native components:

ee()->cache->delete('/myaddon/');

Namespacing gives you granular control over which items in your cache should be purged without affecting other parts of your add-on or ExpressionEngine.

Note: When flushing a namespace, the key must end with the namespace separator (/) so the Cache class knows to clear a namespace instead of trying to delete a key with the name of your namespace.

Scoping

Items stored in the cache by default are scoped to the site currently saving or retrieving from the cache. This prevents cache keys from colliding when the same keys are used in multiple sites in the same ExpressionEngine install.

But you may want the same cache item available across all sites in your ExpressionEngine install. In that case, you must specify a global scope by passing the Cache::GLOBAL_SCOPE constant when saving or retrieving from the cache:

ee()->cache->save('mykey', $data, 500, Cache::GLOBAL_SCOPE);
ee()->cache->get('mykey', Cache::GLOBAL_SCOPE);

By default, the scope parameter is Cache::LOCAL_SCOPE. Setting a global scope allows cache keys to be shared across the installation, while a local scope keeps keys specific to individual sites.

Class Methods

class Cache

ee()->cache->save('/mymodule/mykey', $results, 3600);

$data = ee()->cache->get('/mymodule/mykey');

ee()->cache->delete('/myaddon/mykey');

ee()->cache->delete('/myaddon/');

ee()->cache->clean();

$info = ee()->cache->cache_info();

$info = ee()->cache->get_metadata('/myaddon/mykey');

ee()->cache->memcached->is_supported();