Migrate config and load/config 1.0 subsystems to 2.0 format
Reported by dleffler | August 13th, 2011 @ 07:07 PM | in Stable (closed)
I already have this working locally and will push in the next week or so. The new 2.0 subsystem name will be 'expSettings' to differentiate from the expConfig model.
As a note, this will (should?) be the only 2.0 subsystem that must be manually loaded since we need the system settings (config.php) before we can crank up our php __autoloader override. The formate of the 2.0 subsystems is as a class with public static functions.
Comments and changes to this ticket
-
expNinja August 14th, 2011 @ 12:19 AM
- State changed from “open” to “resolved”
(from [01ce23be60c7421eaa765c5b8c2949ecef7cb9be]) Removes deprecated config & load/config.php 1.0 subsystems(cherry picked from commit 81ee2bf986395f20f355bae09cce562011563e8c) [#303 state:resolved] https://github.com/exponentcms/exponent-cms/commit/01ce23be60c7421e...
-
expNinja August 14th, 2011 @ 12:19 AM
(from [6c484a17e36a8c7fbafce711105bcaf2eeb6e58e]) Deprecate config & load/config.php 1.0 subsystems by creating a expSettings.php 2.0 subsystem. Unlike the other 2.0 subsystems, expSettings must be loaded as it's required BEFORE the exponent php __autoloader override is (can ) be loaded.(cherry picked from commit 9161bfb869dd67f267d3978036d8f6718f81f6fe) [#303 state:resolved] https://github.com/exponentcms/exponent-cms/commit/6c484a17e36a8c7f...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS
expNinja