overriding pagelayout kills global variables in content?

Wednesday 03 June 2009 12:32:40 am

I have hit a strange problem which im not sure if its in my head or some bug. I have tried to describe it here: http://projects.ez.no/paradoxpdf/forum/general/global_variables_lost

In short: paradoxpdf extension defines override to pagelayout. In this override it uses set-block to capture module.content in variable, to pipe it through pdf generation operator. Nothing is changed in content view part, exact same templates are used.

Now, i am defining some variables in a node full view override template:
{def $myvar='plah'}

Also i have defined ezxml custom tags, and i access these variables in it: {$#myvar}. It works fine and does its magic. But if paradoxpdf view is used, these variables will not be there in tag templates.. how can it be? Also i tried to use $persistent_variable and it seems to disappear similarly under paradoxpdf. How can changing pagelayout influence content? Probably im missing something here, but have hit brick wall with this problem and need it to work bad.. any ideas?

Certified eZ developer looking for projects.
zurgutt at gg.ee