|
Wednesday 31 March 2010 2:07:16 pm
Carlos, In the interim, note that the order in which you have your extensions declared in settings/override/site.ini.append.php affects how template overrides are dealt with. If you know what differs between 2 extensions who use the same template, you'll know what is the best order to declare them in the [ExtensionSettings] block - it being unlikely (possible though) that the exact same code has been modified in the same template for both extensions. Note also that the order of importance in this array is kinda upside-down. Extensions declared at the top override extensions declared below (In terms of their .ini settings, templates, design-files etc) one would think the ther way around would be more inuitive. There is a "gotcha" with this in that when you use the admin GUI to install a new extension, and you hit the "Regenerate autoload arrays" button, eZ destroys your lovely, well-crafted extension order in the [ExtensionSettings] block - so ensure you have a copy of your original order. This has bitten me a few times, and is especially important if you use the siteaccess+exension method of multiple siteaccesses in eZ See the bug-report (now resolved) I submtted on this a while back.
Cheers
Russ
Russell Michell, Wellington, New Zealand.
We're building! http://www.theruss.com/blog/
I'm on Twitter: http://twitter.com/therussdotcom
Believe nothing, consider everything.
|
