Re: Unexpected behavior with page-specific Smarty data
Posted: Thu Jan 01, 2009 8:16 pm
I wrestled with this for a while today and finally found the answer in the 1.4.0 changelog:
The key is to add {process_pagedata} at the top of the template.* A new text area in the options tab of content pages allows specifying page specific data (as opposed to putting page specific data into the metadata section of the page)
* A new plugin {process_pagedata} processes the page specific data through smarty. It should be at the very top of all page templates