#105326wrong path in instruction of Install Tool for classic way installation
Description
In a classic TYPO3 installation I get this wrong message in the Install Tool:
For an existing TYPO3 installation, please create the file ENABLE_INSTALL_TOOL in the directory config/.
However the path in the classic way installation must be typo3conf !
Reviews 2
Related issues 3
History 710
-
Garvin Hicking changed category <span data-processor="relativetime" data-value="2024-10-16T16:16:00+00:00" > 10/16/24, 16:16 </span>
-
Garvin Hicking changed Related to #102933 <span data-processor="relativetime" data-value="2024-10-16T16:16:06+00:00" > 10/16/24, 16:16 </span>
-
Garvin Hicking changed Related to #104126 <span data-processor="relativetime" data-value="2024-10-16T16:22:30+00:00" > 10/16/24, 16:22 </span>
-
Garvin Hicking changed Related to #104074 <span data-processor="relativetime" data-value="2024-10-16T16:22:42+00:00" > 10/16/24, 16:22 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 86632 status
NewUnder Review <span data-processor="relativetime" data-value="2024-10-16T16:53:50+00:00" > 10/16/24, 16:53 </span> -
Garvin Hicking commented and changed assigned to Garvin Hicking Is Regression 1 <span data-processor="relativetime" data-value="2024-10-16T16:55:14+00:00" > 10/16/24, 16:55 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 86632 <span data-processor="relativetime" data-value="2024-10-25T07:08:49+00:00" > 10/25/24, 07:08 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 86738 <span data-processor="relativetime" data-value="2024-10-25T09:05:22+00:00" > 10/25/24, 09:05 </span>
-
Garvin Hicking commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2024-10-25T09:20:08+00:00" > 10/25/24, 09:20 </span>Applied in changeset commit:e054be79ec5ba971005b88b11b9acfb340fdc7d4.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T14:32:52+00:00" > 12/02/25, 14:32 </span>
Many thanks for bringing this to attention. Indeed it was caused by my wrong change of directory locations in #104126.
I’ve created a follow-up patch and hope to get this straight.