You have a valid point regarding comments, as for pagelayout now compared to a few years back some effort was put into making it more customizable and less cluttered so same pagelayout could be used across ezwebin and flow for instance.
I understand the reasons for the pagelayout.tpl evolving over time, but that is not a reason for letting it become cluttered and hard to understand.
For instance - what is the reason for adding a variable for the ez basket in pagelayout.tpl - if you dont even use the shop in your site...?
Well, as always with eZ Publish, I would be happy if we at least could get proper documentation and comments in place. That is the weakest point in this otherwise rock solid system.
Cheers,
Nicklas
Nicklas Lundgren, Managing Director
Novitell AB, Sweden
You can always start from scratch with a clean pagelayout and avoid usage of ezpagedata and most other stuff (I'd just recommend to go with ezcss_load and ezscript_load) if you want. In fact that's the approach we usually take for eZ Publish trainings, as the flexibility and modularity of the ezflow/ezwebin pagelayouts comes at the price of simplicity.
Principal Consultant International Business
Member of the Community Project Board
In my experience, the best policy is just to make some minor modifications to the file you're wondering about and see what happens (I mean the files which are not commented). It may be a n00b approach, but it's the best we've got (as far as non-documented files are concerned).
You must be logged in to post messages in this topic!