de9e4c3d6a5babe1157aa66d2b29dd7378012f01
[Packages/TYPO3.CMS.git] / typo3 / sysext / install / Resources / Private / Templates / Action / Tool / Configuration.html
1 {namespace i=TYPO3\CMS\Install\ViewHelpers}
2
3 <f:layout name="ToolAuthenticated" />
4
5 <f:section name="Content">
6 <h1>Configuration presets</h1>
7
8 <f:for each="{actionMessages}" as="statusMessage">
9 <f:render partial="Action/Common/StatusMessage" arguments="{message: statusMessage}" />
10 </f:for>
11
12 <p>
13 The configuration module suggests best matching configuration settings
14 based on your system setup.
15 </p>
16 <p>
17 Alternatively TYPO3 can be run in a specific <a href="https://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/Bootstrapping/Index.html#bootstrapping-context" target="_blank">application context</a>,
18 by setting an environment variable in the web server configuration.
19 The application context can then be accessed e.g. in the AdditionalConfiguration.php file or
20 TypoScript configuration to customize settings accordingly.
21 </p>
22 <p>
23 Changed values are written to LocalConfiguration.php. The optional file AdditionalConfiguration.php
24 is not controlled by the TYPO3 CMS core and may override single settings again. Administrators
25 must maintain AdditionalConfiguration.php on their own and should use it with care.
26 </p>
27 <form method="post" class="form-horizontal">
28 <f:render partial="Action/Common/HiddenFormFields" arguments="{_all}" />
29
30 <div class="panel-group" id="accordion" role="tablist" aria-multiselectable="true">
31 <f:for each="{features}" as="feature">
32 <f:render partial="Action/Tool/Configuration/{feature.name}" arguments="{_all}" />
33 </f:for>
34 </div>
35
36 <div id="fixed-footer-handler">
37 <div id="fixed-footer">
38 <div class="footer-innerWrap">
39 <f:render partial="Action/Common/SubmitButton" arguments="{name:'activate', text:'Activate', className:'btn-save'}"/>
40 </div>
41 </div>
42 </div>
43
44 </form>
45 </f:section>