-You have cleared your caches (at least ini and override)
-Your new template is located in /design/your_design/override/templates/my_file.tpl -either your ContentClass or attribute has the identifier "ezbinaryfile" (what I hardly believe, shouldn't this be more like "file"?)
Thanks for the answer, I've found a solution meanwhile.
The Match[] directives were a wrong approach, I wanted the override to be valid for any content class and any attribute name as long as the attribute datatype is "ezbinaryfile". So I had to remove the Match[] directive completly. Additionally, somewhere in the middle of override.ini.append.php there has been a block
while my own block was located right at the beginning of the file. I simply moved my block to the end of the file, and now it works.
But there is either a bug in the admin backend ( /visual/templateview/content/datatype/view/ezbinaryfile.tpl ) or in the override system itself, because the admin backend now lists my block as prioriy 2 and it still overrules the [file_binaryfile] block with priority 1.
You won't even need a rule for this approach. Simply put your new file in /design/your_design/templates/content/datatype/view/ezbinaryfile.tpl (basically the same place as the original, but in your own design), and template fallback will take care of the rest.
Ah, thanks for the hint, this is definitly a more elegant solution than mine. Worked fine for the "ezurl" datatype, for the "ezbinaryfile" I had to remove that other block pointing to the "base"-design which was added by default.
But I've to admit, I'm still unsure when to place template files into
/design/my_design/templates
and when to place them into /design/my_design/override/templates
<i>The special thing with override templates is that they can *conditionally* override default templates, only if cetain conditions are met, like node id or object class, using the Match specifier.</i>
You must be logged in to post messages in this topic!