This is great - thankyou. For me it is a great choice to put configuration for code-files into config.inc.php instead of db, this makes rolling out of new versions of code to staging and or production servers a lot easier. By the way: Please consider to put the aModules configuration also into the config. Maybe you could merge aModules from db for backward compatibility, oops that was a feature request, sorry...;-) best regards, Holger
2011/6/30 Vilma Liorensaityte <[email protected]>: > Hi, > > According to reported bug http://bugs.oxid-esales.com/view.php?id=1721, we > implemented suggested improvement for the next release: added > $this->aUserComponentNames array option to config.inc.php. With this option > it will be easier to override custom components array $_aUserComponentNames > (class names, that are defined in this array, will be executed before any > other regular operation) in oxubase. Till now the only way to override this > array in oxubase was extending view classes and sometimes all of them. > > Regards, > Vilma > _______________________________________________ > dev-general mailing list > [email protected] > http://dir.gmane.org/gmane.comp.php.oxid.general > -- Holger Kohnen (Webentwickler) Anklamer Str. 35 10115 Berlin [email protected] http://www.holgerkohnen.de 030 / 788 37 22 0173 / 38 62 791 _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
