I know i added some debug info to eZTemplateDesignResource and it finds the templates, but i think they may not be able to be matched as the code is not there for extensions... I really hope i am wrong.
Tony
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
anther thing also ...
I was tryung to match[class]=15 for line.tpl .. but the problem was is not matching it even by [node] .. and the probelem was that override path was the same for the overrided template ... so I changed to override/template/node/viewx/line.tpl .. and the match[class] work fine ... you may try to but the MatchFile in sub filder. . maybe this the mistake !
'pagelayout_mylayout.tpl' overrides the default 'pagelayout.tpl' in our override file just as we expect.
ez, is this correct behaviour for a module extension? do we need to declare which layout we want? Maybe there should be more documentation stating what effect the $Result value has on the template.
I'll second that Paul, and good eye for spotting it, I couldn't find it until you showed me. If more people are to produce modules then the basics needs to be documented like $Result['pagelayout'] etc.
To start with just the syntax and a brief overview will be enough and a tutorial module that had examples, very much like the useful "demo" site.
I think more people would delve into Modules if this was available.
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
