$cache->saveFor() method

Same as save() except with namespace

Namespace is useful to avoid cache name collisions. The ProcessWire core commonly uses cache namespace to bind cache values to the object class, which often make a good namespace.

Example

// save cache using manually specified namespace
$cache->save("my-namespace", "my-cache-name", $value);

// save cache using namespace of current object
$cache->save($this, "my-cache-name", $value);

Usage

// basic usage
$bool = $cache->saveFor($ns, string $name, $data);

// usage with all arguments
$bool = $cache->saveFor($ns, string $name, $data, $expire = 86400);

Arguments

NameType(s)Description
nsstring, object

Namespace for cache

namestring

Name of cache, can be any string up to 255 chars

datastring, array, PageArray

Data that you want to cache

expire (optional)int, Page

Lifetime of this cache, in seconds, OR one of the following:

  • Specify one of the WireCache::expire* constants.
  • Specify the future date you want it to expire (as unix timestamp or any strtotime compatible date format)
  • Provide a Page object to expire when any page using that template is saved.
  • Specify WireCache::expireNever to prevent expiration.
  • Specify WireCache::expireSave to expire when any page or template is saved.
  • Specify selector string matching pages that, when saved, expire the cache.

Return value

bool

Returns true if cache was successful, false if not


$cache methods and properties

API reference based on ProcessWire core version 3.0.236

Latest news

  • ProcessWire Weekly #547
    In the 547th issue of ProcessWire Weekly we're going to check out the latest core updates, introduce a couple of new modules, and more. Read on!
    Weekly.pw / 2 November 2024
  • Custom Fields Module
    This week we look at a new ProFields module named Custom Fields. This module provides a way to rapidly build out ProcessWire fields that contain any number of subfields/properties within them.
    Blog / 30 August 2024
  • Subscribe to weekly ProcessWire news

“Indeed, if ProcessWire can be considered as a CMS in its own right, it also offers all the advantages of a CMF (Content Management Framework). Unlike other solutions, the programmer is not forced to follow the proposed model and can integrate his/her ways of doing things.” —Guy Verville, Spiria Digital Inc.