I've never tried this, so I might be far off, but you could check out set-blocks: http://www.ez.no/ez_publish/documentation/reference/template_functions/variables/set_block
And namespaces: http://www.ez.no/ez_publish/documentation/development/libraries/ez_template/basics/namespaces
Yup -- set_block seems like it should work, but it doesn't, if you're setting the var in the pagelayout and trying to access it from within $module_result.
Likewise with namespaces -- no success there either.
The point here is that the module (example content) is run first. This means that if you set a variable in the pagelayout this will be set after your content view _already_ is rendered.
What are you trying to do? If these are sitedefault variables, the wise thing to do is to put it in a inifile and use the templateoperator ezini to read the values from there.
Kristian, thanks for the inifile suggestion. That's actually exactly how I solved the problem -- I just declared a custom settings area in my site.ini.append, then stuck all of the required values in there.
I could choke on these words, but ... I thought that this was the problem that was causing all this strife ...
Xavier just mentioned it (above), that it was still in dier need of a clean room solution that didn't mean hacking apart your own life.
It works fine the first time, but (if I'm right) once the template is compiled, the content view doesn't set the global variable anymore. Any idea ? X+
________________________
Please help me on to find a cache resistant method to exchange parameters between templates :
http://www.ez.no/community/forum/developer/how_to_exchange_parameters_between_several_parts_blocks_on_a_page
hrmm... //kracker
<i>atmosphere : my song sage francis : inherited scars</i>
