This changes the default paths that the base CLI and web applications use to lookup configuration files to use the JPATH_CONFIGURATION path constant which is in line with how the rest of the CMS is configured.
This also removes overloading the configuration object created by the application. This actually causes some configuration values set by the parent constructors to be lost.
Testing Instructions
The JConfig object is still correctly read into the application class' $config store and downstream uses continue to read the configuration data from this source correctly.
I have tested this item✅ successfully on 2015e3a
Applied patch, tested frontend and backend and worked fine.
Made a
print_R($app);
in isis and protostar index.php and config is there.This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11838.