In-Portal Issue Tracker - In-Portal CMS
|Viewing Issue Advanced Details|
|ID:||Category:||Type:||Reproducibility:||Date Submitted:||Last Update:|
|1402||[In-Portal CMS] Data Management||refactoring||N/A||2012-09-16 13:03||2012-09-16 13:03|
|ETA:||none||Fixed in Version:|
|Change Log Message:||Unites /system/config.php file processing/usage code|
|Summary:||0001402: Create intermediate class to access /system/config.php file|
File /system/config.php is created during In-Portal installation and contains all core settings that are needed to be able to run In-Portal.
For example it contains database connection information. Then once connected to database In-Portal can get other settings from there.
This file very powerful, however code that uses it is scattered across the system. For example there is:
* kUtil::parseVars method, that returns contents of that file as array (used each time)
* some pieces of code in /core/kernel/startup.php file, that ensures default values for some settings, that might be missing (used each time)
* some pieces of code in /core/install.php file, that ensures default values for some other settings, that might be missing (used during install)
I'm proposing to create kSystemConfig class, that can be accessed from everywhere (due his static nature) and will ensure that all settings have their default values and can be accessed properly.
|Steps To Reproduce:|
|Additional Information:||Constants, that are defined based on /system/config.php file contents, like SQL_DB, ADMIN_DIRECTORY can stay of course.|
|2012-09-16 13:03||alex||New Issue|
|2012-09-16 13:03||alex||Reference||=> https://groups.google.com/d/topic/in-portal-dev/UJwlLFoq7WU/discussion|
|2012-09-16 13:03||alex||Change Log Message||=> Unites /system/config.php file processing/usage code|
|2012-09-16 13:03||alex||Estimate Points||=> 1|
|There are no notes attached to this issue.|