[CLEANUP] Clarify configuration preset description 90/35090/3
authorHelmut Hummel <helmut.hummel@typo3.org>
Fri, 5 Dec 2014 23:51:44 +0000 (00:51 +0100)
committerChristian Kuhn <lolli@schwarzbu.ch>
Sat, 13 Dec 2014 13:45:36 +0000 (14:45 +0100)
The description of the configuration preset in
install tool is a bit misleading which causes people
to confuse this with the Application Context feature.

Remove the mentioning of application context from context preset
and move it to the top.

Releases: 6.2, master
Resolves: #63622
Change-Id: I8acc9032333f0ead6a35c2c7202a07d2668e7c51
Reviewed-on: http://review.typo3.org/35090
Reviewed-by: Wouter Wolters <typo3@wouterwolters.nl>
Tested-by: Wouter Wolters <typo3@wouterwolters.nl>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
typo3/sysext/install/Resources/Private/Partials/Action/Tool/Configuration/Context.html
typo3/sysext/install/Resources/Private/Templates/Action/Tool/Configuration.html

index c5d94f4..4245535 100644 (file)
@@ -6,22 +6,13 @@
        <div class="toggleData" style="display:none">
                <div class="toggleDataContent">
                        <p>
-                               TYPO3 can be run in a specific application context by using the environment
-                               variable "TYPO3_CONTEXT", which is usually set in your webserver configuration
-                               (e.g. in htaccess). Built-in contexts are "Production" (default), "Development"
-                               or "Testing".
-                               This can be used to provide specific configuration sets for each context.
+                               In this panel it is possible to select a configuration preset which optimizes multiple settings
+                               to be suited best for production or development environments.
+                               The "Production" preset configures your TYPO3 installation for maximum performance
+                               and suppresses debug and error messages, so that nothing is disclosed to website visitors.
+                               The "Development" preset enables most debug and error messages which is helpful during development.
+                               As a third option it is possible to manually customize each setting for specific needs.
                        </p>
-                       <p>
-                               However, if you don't set a context environment variable, you can still
-                               use the install tool to select a configuration preset for "Production"
-                               or "Development" context. The goal is to configure a production instance
-                               with maximum performance and no debug output that is possibly shown to users,
-                               while development instances should enable error output. The configuration
-                               preset for "Production" is set by default.
-                               As a third alternative, you can enter a custom configuration.
-                       </p>
-
                        <f:for each="{feature.presetsOrderedByPriority}" as="preset">
                                <f:render partial="Action/Tool/Configuration/{feature.name}/{preset.name}" arguments="{_all}" />
                        </f:for>
index 0b0b93c..e9c63df 100644 (file)
                The configuration module suggests best matching configuration settings
                based on your system setup.
        </p>
-
+       <p>
+               Alternatively TYPO3 can be run in a specific <a href="http://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/Bootstrapping/Index.html#bootstrapping-context" target="_blank">application context</a>,
+               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.
+       </p>
        <form method="post">
                <f:render partial="Action/Common/HiddenFormFields" arguments="{_all}" />