$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.137

Twitter updates

  • We added WebP image support this year and many have been adopting it in existing projects. We look at a process used for migrating existing websites to WebP images— from preliminary considerations to implementation & testing, w/lots of tips & tricks too: More
    16 August 2019
  • Core version 3.0.137 on the dev branch adds the ability to hook multiple methods at once, in a single call. This post details how it works and provides a useful example of how you might put it to use in your development environment— More
    2 August 2019
  • ProcessWire 3.0.136 updates our CKEditor version and adds a new backtrace() method to the core Debug class— More
    26 July 2019

Latest news

  • ProcessWire Weekly #275
    In the 275th issue of ProcessWire Weekly we're going to walk you through the new features included in ProcessWire 3.0.138, cover some WebP related stuff, and highlight recent forum posts and online resources. Read on!
    Weekly.pw / 17 August 2019
  • WebP images on an existing site
    In this post we’ll look at a process used for migrating an existing website to use WebP images. We’ll cover everything from preliminary considerations to implementation and testing, with lots of tips and tricks along the way.
    Blog / 16 August 2019
  • Subscribe to weekly ProcessWire news

“We chose ProcessWire because of its excellent architecture, modular extensibility and the internal API. The CMS offers the necessary flexibility and performance for such a complex website like superbude.de. ProcessWire offers options that are only available for larger systems, such as Drupal, and allows a much slimmer development process.” —xport communication GmbH