Bug #66650
closed
Application context in short system overview does not reflect install tool setting
Added by Christian Buelter over 9 years ago.
Updated almost 9 years ago.
Category:
Backend User Interface
Description
In the new "short system overview" window in 7.2 the "Application context" does not reflect the configuration preset in the install tool.
I understand that the application context is set in the webserver environment, but since the same names are used for configuration preset (set in install tool) and application context (set for example in .htaccess) this may be irritating.
See also attached screenshot.
Files
- Status changed from New to Needs Feedback
the wording in the install tool has been updated
The configuration module suggests best matching configuration settings based on your system setup.
Alternatively TYPO3 can be run in a specific application context, by setting an environment variable in the web server configuration. The application context can then be accessed e.g. in the AdditionalConfiguration.php file or TypoScript configuration to customize settings accordingly.
Changed values are written to LocalConfiguration.php. The optional file AdditionalConfiguration.php is not controlled by the TYPO3 CMS core and may override single settings again. Administrators must maintain AdditionalConfiguration.php on their own and should use it with care.
IMO this should be no a lot clearer. any changes you would still like to suggest?
What I meant is the difference in the "application context" shown in the short system overview to the "Development / Production setting" in the install tool.
What do you think of adding the "Development / Production setting" (Development / Production / Custom) to the short system overview since both settings can affect the behaviour of the TYPO3 instance?
In the attached screenshot I tried to simulate what I'm thinking of.
- Status changed from Needs Feedback to New
- Category set to Backend User Interface
- Status changed from New to Rejected
The preset options have been changed to Debug + Live. Those are just a possibility and if just 1 setting would be different to the preset, it would also not be identified as the preset anymore.
Also available in: Atom
PDF