ezpagedata is an webin operator that does page initialization in php for speed, and instead of being able to change it direclty you can customize it's result with persistent variable and / or parameter hash to operator.
plain site is old, and does not have any of this features that webin has been getting over the years, so hence it behaves a lot differently.
ezpagedata is an webin operator that does page initialization in php for speed, and instead of being able to change it direclty you can customize it's result with persistent variable and / or parameter hash to operator.
plain site is old, and does not have any of this features that webin has been getting over the years, so hence it behaves a lot differently.
Thank you Andre' for your explanation.
The one where I need to pass my extension package is somebody else's eZ installation and they have made it on a plain_site basis.
Since I am passing both my extension and ezwebin extension full packages, I was wondering if by enabling the two of them in the admin back-end> Setup> Extensions> Available extensions and so realoading the extensions' autoload arrays, will this make ezpagedata() works?
..by enabling the two of them in the admin back-end> Setup> Extensions> Available extensions and so realoading the extensions' autoload arrays, will this make ezpagedata() works?
I am having some problems with ezpagedata, my pagelayout menu does not display top menues, top information (tag cloud, login), left menu and bottom information.
As far as I have investigated the $pagedata = ezpagedata() is not working at all so at page_header.tpl the following will not work: {include uri=concat('design:menu/', $pagedata.top_menu, '.tpl')}