|
Thursday 03 April 2008 2:29:40 pm
Along these same lines, there seems to be a definite bug in the template automatic fallback system in eZpublish 4.0. I've been working with eZpublish since around 3.8.6 and I've gotten pretty comfortable with the ins and outs of the override system. I often use simple includes such as:
{include uri="design:includes/breadcrumbs.tpl}
Which always automatically used the current site design and found the file successfully with a path such as: design/plain_site/override/templates/includes/breadcrumbs.tpl When I tried using this same convention in 4.0, the debug output would say that it was loading the template but it was clearly not. eZTemplate: Loading template "includes/breadcrumb.tpl" with resource "design" After struggling to figure out why, I decided to try to give it an explicit override in the siteaccess's override.ini:
[breadcrumb]
Source=includes/breadcrumb.tpl
MatchFile=includes/breadcrumb.tpl
Subdir=templates
This seems pretty pointless to me, as I'm overriding a file with the same file! But it worked. So, seems like there's something up here. You now have to explicitly set ALL of your overrides, even if they're in the same directory structure as the default templates.
|
