Wednesday 27 October 2010 12:41:33 pm
@RD it looks like you are talking about templates in answer to a dead-and-buried post that talks about ini settings - I'll try to give some advice about both 1. use theSetup/Ini settings page to keep your ini settings under control (ie. read them). Edit them by hand, put a lot of comments in them, and never copy in a new ini file a setting that you do not need to change 2. it can get very messy, but it is extremely flexible. In every discussion about the config system we have had here, there where different parties using it in different ways, so we could not decide upon a particular kind of configuration to desupport r(that would have made the code easier to maintain and faster to execute) You should decide a strategy for ini files that works for your site (all in the override, all in the siteaccess, all in an extension) and stick to it. Just do not scatter your settings all over the place 3. templates: edit them with a decent code editor (there are tpl syntax highlighter plugins you can use for many), use the debug info w. used template list at the bottom of the page to always have a clear picture of which templates are in use and you need to override 4. keep the override.ini file in a single place, do not split it over many locations, as order of its config blocks is important And last but not least: call eZ for a Dev Basics training. 4 days of time spent there can really save you a month of hair pulling down the road :-)
Principal Consultant International Business
Member of the Community Project Board
|