Squiz Matrix Newsletter #384
29 JunSo quickly we are nearing the midpoint of 2012; it seems like only yesterday we were ringing in the new year. June is coming to a close and July is hot on its heels, promising a brand new branch of Squiz Matrix and a terrific array of new functionality.
On July 2nd, we will be releasing versions 4.8.4 and 4.10.0 of Squiz Matrix - our 4.6.x branch has been retired. Both of these releases will be available for download via our public CVS repository. In addition, Squiz Matrix v4.10.0 will be available as a VM release on the Squiz Matrix site.
Squiz Labs is excited to launch the 4.10.x branch of Squiz Matrix, boasting close to twenty-five new features and enhancements (including those that were introduced in last month's release candidate). New additions include the ability to nest keyword replacements within keyword modifiers, the option of specifying binary data to export on an LDAP Data Source, a new trigger event and condition to evaluate the response of a REST Resource, and a new trigger action to dynamically link a user to a user group.
The latest Squiz Matrix Automatic Upgrade scripts will also be available on Monday on the Squiz Matrix site.
Check out the Squiz Labs blog on Monday for all the latest on these new releases, including download links, release notes and more!
This week we have one new enhancement to report, a new keyword replacement to display front-end metadata in the HTML source code of an asset. Continue reading below for more information on all this week's developments.
New Keyword Replacement: asset_frontend_metadata
Due for release in version 4.10.0 (July 2nd 2012)
A new keyword replacement had been added to Squiz Matrix to display front-end metadata in the HTML source code of an asset.
%asset_frontend_metadata%
This keyword works in a similar manner to the Metadata Design Area, that prints the metadata tags within an asset's HTML source, as specified in the parse file of your design.
This keyword extends this functionality by allowing you to print this frontend metadata within the content of your asset (as viewed in the HTML source). This keyword can also be used for alternative purposes, such as on a Paint Layout, applied to specific assets within a site.
Please note that the Show On Frontend option must be enabled for a metadata field and its value to be displayed within the HTML source code using this new keyword replacement.