[BUGFIX] The Install Tool welcome text is outdated
[Packages/TYPO3.CMS.git] / typo3 / sysext / install / Resources / Private / Templates / Action / Tool / Welcome.html
1 {namespace i=TYPO3\CMS\Install\ViewHelpers}
2
3 <f:layout name="ToolAuthenticated" />
4
5 <f:section name="Content">
6 <f:if condition="{contextService.standaloneContext}">
7 <f:then>
8 <h3>Welcome</h3>
9 </f:then>
10 <f:else>
11 <h3>TYPO3 CMS {typo3Version} Install tool on site: {siteName}
12 </f:else>
13 </f:if>
14
15 <h4>How to configure TYPO3 CMS</h4>
16 <p>
17 Local configuration is done by overriding default values in the
18 included file, typo3conf/LocalConfiguration.php. In this file you enter the
19 database information along with values in the global array
20 TYPO3_CONF_VARS.
21 <br />
22 The options in the TYPO3_CONF_VARS array and how to use it for your
23 own purposes is discussed in the base configuration file,
24 EXT:core/Configuration/DefaultConfiguration.php. This file sets up the default values and
25 subsequently includes the LocalConfiguration.php file in which you can then
26 override values.
27 <br />
28 See this page for <i:constant name="TYPO3_URL_SYSTEMREQUIREMENTS" /> more
29 information about system requirements.</a>
30 </p>
31 <hr />
32
33
34 <h4>Using this script</h4>
35 <p>
36 These are the primary steps for you to take:
37 </p>
38 <p>
39 <strong>1: Important actions</strong>
40 <br />
41 This step provides an overview of the main system information
42 (operating system, PHP information and database).
43 <br />
44 The following actions are available here:
45 <ul>
46 <li><strong>Database Analyzer</strong> - compares the database table and field definitions of the
47 current database with the specification from all loaded extensions' ext_tables.sql.</li>
48 <li><strong>Clear all cache</strong> - works similar to the cache clearing in the backend, but
49 follows a more straight ahead approach and the according backend hooks are not executed.</li>
50 <li><strong>Check for broken extensions</strong> - checks whether the local extensions' ext_tables
51 and ext_localconf files can be included without errors, meaning they can be loaded without
52 breaking the system.</li>
53 <li><strong>Core update</strong> - automatically update the TYPO3 CMS core to its latest bugfix
54 release if certain criteria are met. <strong>Note:</strong> This is not supported on Windows hosts.</li>
55 <li><strong>Change install tool password</strong></li>
56 <li><strong>Change site name</strong></li>
57 <li><strong>Change encryption key</strong></li>
58 <li><strong>Create backend administrator user</strong> - you should use this function only if there
59 are no admin users in the database, for instance if this is a blank database</li>
60 </ul>
61 </p>
62 <p>
63 <strong>2: System environment</strong>
64 <br />
65 In this step your system environment is checked. If there are any settings that will prevent TYPO3 CMS from
66 running correctly, you'll get warnings and errors with a description of the problem.
67 </p>
68 <p>
69 <strong>3: Configuration presets</strong>
70 <br />
71 The following configuration preset groups are available here:
72 <ul>
73 <li><strong>Character set conversion settings</strong> - charset conversion.</li>
74 <li><strong>Development / Production settings</strong> - context can be defined with the environment
75 variable "TYPO3_CONTEXT" which is usually set through your webserver configuration
76 (e.g. in htaccess).</li>
77 <li><strong>Image handling settings</strong> - this module detects the available image handling
78 tools and configures the system.</li>
79 <li><strong>Extbase object cache</strong> - choose between APC / Database cache backend</li>
80 </ul>
81 </p>
82 <p>
83 <strong>4: Folder structure</strong>
84 <br />
85 This step checks the folder structure of your TYPO3 CMS installation and fixes errors that you might have
86 with files or folders.
87 </p>
88 <p>
89 <strong>5: Test setup</strong>
90 <br />
91 This gives you a set of tests for your TYPO3 CMS installation in order to test system settings:
92 <ul>
93 <li>Mail setup</li>
94 <li>True type font dpi settings</li>
95 <li>Convert image formats to jpg</li>
96 <li>Writing gif and png</li>
97 <li>Scaling images</li>
98 <li>Combining images</li>
99 <li>GDlib</li>
100 </ul>
101 </p>
102 <p>
103 <strong>6: Update wizard</strong>
104 <br />
105 If you upgrade your TYPO3 CMS installation from one version to another (e.g. 6.1 to 6.2),
106 then the Upgrade Wizards guide you through the necessary steps to upgrade your database records
107 or explicitly install extensions that ship with the latest TYPO3 CMS version.
108 </p>
109 <p>
110 <strong>7: All configuration</strong>
111 <br />
112 In this step you can change the configuration values of your TYPO3 CMS installation.
113 </p>
114 <p>
115 <strong>8: Clean up</strong>
116 <br />
117 Here you can clean up temporary files in the typo3temp/ folder and the database tables used for
118 caching. Furthermore you can reset the preferences of all backend users.
119 </p>
120 <hr />
121
122
123 <h4>Header legend</h4>
124 <h4 class="typo3-message message-notice">
125 Notice!
126 </h4>
127 <p>
128 Indicates that something is important to be aware of.
129 <br />
130 This does <em>not</em> indicate an error.
131 </p>
132
133 <h4 class="typo3-message message-information">
134 Just information
135 </h4>
136 <p>
137 This is a simple message with some information about something.
138 </p>
139
140 <h4 class="typo3-message message-ok">
141 Check was successful
142 </h4>
143 <p>
144 Indicates that something was checked and returned an expected result.
145 </p>
146
147 <h4 class="typo3-message message-warning">
148 Warning!
149 </h4>
150 <p>
151 Indicates that something may very well cause trouble
152 and you should definitely look into it before proceeding.
153 <br />
154 This indicates a <em>potential</em> error.
155 </p>
156
157 <h4 class="typo3-message message-error">
158 Error!
159 </h4>
160 <p>
161 Indicates that something is definitely wrong and that TYPO3 will most
162 likely not perform as expected if this problem is not solved.
163 <br />
164 This indicates an actual error.
165 </p>
166 </f:section>