Project

General

Profile

Actions

Bug #105326

open

wrong path in instruction of Install Tool for classic way installation

Added by Franz Holzinger 1 day ago. Updated 1 day ago.

Status:
Under Review
Priority:
Should have
Category:
Install Tool
Target version:
-
Start date:
2024-10-16
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
13
PHP Version:
Tags:
Complexity:
trivial
Is Regression:
Yes
Sprint Focus:

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 !


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #102933: Install tool does not suggest creating FIRST_INSTALL file on first installClosed2024-01-26

Actions
Related to TYPO3 Core - Bug #104126: Prevent requiring "typo3conf" for Composer modeClosedGarvin Hicking2024-06-17

Actions
Related to TYPO3 Core - Task #104074: getFileSystemStatus checks for writeable typo3conf directory in composer modeClosed2024-06-12

Actions
Actions #1

Updated by Garvin Hicking 1 day ago

  • Category set to Install Tool
Actions #2

Updated by Garvin Hicking 1 day ago

  • Related to Bug #102933: Install tool does not suggest creating FIRST_INSTALL file on first install added
Actions #3

Updated by Garvin Hicking 1 day ago

  • Related to Bug #104126: Prevent requiring "typo3conf" for Composer mode added
Actions #4

Updated by Garvin Hicking 1 day ago

  • Related to Task #104074: getFileSystemStatus checks for writeable typo3conf directory in composer mode added
Actions #5

Updated by Gerrit Code Review 1 day ago

  • Status changed from New to Under Review

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86632

Actions #6

Updated by Garvin Hicking 1 day ago

  • Assignee set to Garvin Hicking
  • Is Regression set to Yes

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.

Actions

Also available in: Atom PDF