A little while ago I proposed something similar on the eZ internal developer's mailing list: allow to specify node_id, class_id, section_id or any combination thereof in override conditions, by simply baking them in filename of the template.
This idea was not well received, as some developers thought that the extra flexibility given by the current system is too much important to be lost.
But maybe we can find common ground: look up templates using a convention-filename first, and if not found using the override.ini rules (or in the opposite order). And throw in an ini setting to disable override.ini at all.
Maybe you can submit this to the roadmap tool?
btw: a similar feature request (existing in the tracker iirc): avoid usage of override.iini for templates used for ezflow blocks...
Principal Consultant International Business
Member of the Community Project Board
This idea was not well received, as some developers thought that the extra flexibility given by the current system is too much important to be lost.
But maybe we can find common ground: look up templates using a convention-filename first, and if not found using the override.ini rules (or in the opposite order). And throw in an ini setting to disable override.ini at all.
Yeah that was my idea - don't deprecate existing override.ini mechanism since huge amount of sites depend on it but add this new mechanism as additional mechanism of configuring overrides. First, system would check whether template with name matching convention exists and if not - use standard override.ini mechanism.
Gaetano referred to the new Roadmap we have on our community platform. You can find it here: http://share.ez.no/roadmap. You can submit your idea there.
Regards Robin
Board member, eZ Publish Community Project Board - Member of the share.ez.no team - Key values: Openness and Innovation.
This idea was not well received, as some developers thought that the extra flexibility given by the current system is too much important to be lost.
But maybe we can find common ground: look up templates using a convention-filename first, and if not found using the override.ini rules (or in the opposite order). And throw in an ini setting to disable override.ini at all.
Hi Gaetano!
Maybe i'm missing something but i don't see lost of flexibility here. As you say, if the system look for a 'convention-filename' template and use override in case not found, i think you're "adding" flexibility instead. ihmo, it won't hurt if, for example, you create a class called "book" the system looks for override/templates/node/view/full/book.tpl or override/templates/line/book.tpl when needed as exposed by Michal.
One note though. i was told to put in "override" folders all templates referenced by override.ini files... so, it we won't add that ini settings... where should we add those new templates? maybe in [design]/templates/node/view/whatever.tpl instead?
Gaetano referred to the new Roadmap we have on our community platform. You can find it here: http://share.ez.no/roadmap. You can submit your idea there.
Regards Robin
I added it to the roadmap yesterday but I don't see it published yet. Does it need to go through some approval process?
@Carlos I think the separation of templates in the templates and override directories does not add any value to eZP and that it should be eliminated at some point in the future...
Principal Consultant International Business
Member of the Community Project Board
