From: Katharina W. <wol...@fh...> - 2012-03-29 12:15:49
|
Hi again, now I've understood the principal of inheritance and overwriting, I'm looking for ways to use this technique where ever possible. ;-) After some reading I discovered the line local_overrides = config.local.ini in /usr/local/vufind/web/conf/config.ini - and I'm pleased I've found it. I'd like to suggest putting this option at the beginning of the config.ini-file, because it would save people (like me) from adapting the config.ini part for part and then finding this option towards the end of the file. ;-( Is the name config.local.ini changeable or "hardcoded" somewhere? In the vicinity of the line mentioned above, there are another few .ini-files configured (e.g facets = facets.ini). Can I use the same technique for theme-inheritance with those config-files (i.e. list my own version's name first and after that the original .ini-file-name) or can I at least duplicate an .ini-file I'd like to adapt and put the name of the adapted file into the config.local.ini? Lastly, are there any naming-conventions I should heed when making my own file-, class- or method-names etc? In the documentation I only found hits concerning vufind 2.0... Greetings Katharina |