ini files

Next topic

Author	Message
Karsten Jennissen	Wednesday 30 April 2003 2:26:40 am I'd like to bring this up, since I am still not convinced that the recently changed way the ini files are created is good. If I install with the setup wizard, all the /settings/.ini are untouched, while my proprietary settings are created in the /settings/override/ folder named .ini.append.php. Since the override folder overrides all /settings/siteaccess/ (why??), all specific settings in the siteaccess folder will not be recognized. Specifically, if I want to use different databases or other critical settings that are configured via the /settings/override. Especially for a newbe, this is very confusing and not too logical. If you want to determine critical settings on a siteaccess basis, you would have to manually delete the override settings and move them to the siteaccess. Also, the naming is inconsistent. In the override, all files are .php while in other folders they are named .append or *.ini Uneccessary confusion, I would say. :-) Karsten
Paul Borgermans	Wednesday 30 April 2003 4:38:29 am I agree that the setup should copy them in the /settings/siteaccess/ by default and that users just move the common things to /settings/override manually. About the naming, I don't have much problems (low priority that is). Other things are more important now (like template caches, so we don't need a cluster of supercomputers to run ez publish or can host more on the same machine; and notifications of course). How large is your wanted_features list? (rethoric question) Paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
R_______________ D_________	Wednesday 27 October 2010 8:03:06 am I found a lot more inconsistencies and even more unnecessary confusion while testing this CMS. Althrough the concept of overrinding is nice, in practice, it is hell on earth for newbies (or even seniors I guess). After few trials the general idea was understood, but, it is really too easy to mess everything up as soon you edit the files by hand while creating files here and there or using the template edit mode in the frontend debug stuff. While not trying to do much (replace main menu) I had too often bad or no results, and finished with a broken design. Once you have done a mistake, or bad manip, there is no easy way back. Sorry, but ez received a quite bad appreciation from us. ps: Hire designers, more designers.
Gaetano Giunta	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