Page 1 of 1

Why two config files?

Posted: Tue Sep 11, 2007 4:06 pm
by rvences
Hi there, in some times I'm paranoid and check parts of code, and now i do it and  have one question, why the Joomla 1.5RC2 have two config files, one in [JOOMLA DIRECTORY]/configuration.php and other in [JOOMLA DIRECTORY / LIBRARIES / JOOMLA]/config.php
They are in different classes, but the information in configuration.php overwrite the information in config.php if they exist to use it later in one Object, so my question is you use this to put some information in config.php and the rest in configuration.php to security reason or you use config.php to test or why ???

Thanks a lot for read this and for your answer

Best Regards

Re: Why two config files?

Posted: Mon Sep 17, 2007 5:22 pm
by RobS
rvences wrote: Hi there, in some times I'm paranoid and check parts of code, and now i do it and  have one question, why the Joomla 1.5RC2 have two config files, one in [JOOMLA DIRECTORY]/configuration.php and other in [JOOMLA DIRECTORY / LIBRARIES / JOOMLA]/config.php
They are in different classes, but the information in configuration.php overwrite the information in config.php if they exist to use it later in one Object, so my question is you use this to put some information in config.php and the rest in configuration.php to security reason or you use config.php to test or why ???
There are two configuration files because Joomla! 1.5 is essentially two systems built in a stack whereas Joomla! 1.0.x was one big system.  Joomla! 1.5 consists of the new Joomla! Content Management Framework and the Joomla! 1.5 Content Management System.  When using Joomla! 1.5 as a CMS, all you need to be concerned about is the configuration.php file in the root of the Joomla! installation.  There is another configuration file in the libraries folder that is strictly for the Joomla! 1.5 Content Management Framework so that it could be used as a stand-alone framework for other applications.  The configuration file in the libraries folder is mostly for documentation purposes and to keep track of which configuration parameters the framework itself depends on.

I hope that answers your question.