Downloads

Download tar.gz 11.15 KB
MD5: aa6299593998ad383abdc6d92281bc59
SHA-1: 6fd4257d6791d8e841b3c7b0dd66426e7c4c0de4
SHA-256: cb366497ee593a866f9f98284259e78f9184031b3a11a809536571eb9e3cdd92
Download zip 15.74 KB
MD5: 7853bd5de36547c57d3c35a8ffa63333
SHA-1: 7e2053a5c3a025191b39e40e85e62fed678b6a85
SHA-256: 6314904cfbf209011a4daea44d4fbfbe1fc42cbe4398906b132f08f1d9f8a5f4

Release notes

Summary
This fix adds a number of improvements to the way values are handled, locked and returned from the registry, as well as adding default information for the request, current user, and loaded node on node view pages.

Main changes

Callback entries
Entries can now be set using a callback instead of a fixed value. This ensures that the current value of the item is always loaded. The API function registry_set_callback() can be used to do this.

Set by reference removed
As a result, setting by reference has been removed completely.

Context
Registry entries can be set as a 'context', which adds extra information to the registry. Registry supports two default contexts:

  • Primary: For directly visible objects, such as the node on a node view page
  • Secondary: For related objects

Other contexts are also possible.
The API functions registry_set_context() and registry_set_context_callback() can be used to set these values.

Created by: xtfer
Created on: 22 Mar 2012 at 01:51 UTC
Last updated: 22 Mar 2012 at 01:55 UTC
New features
Bug fixes
Unsupported

Other releases