Project

General

Profile

Actions

Bug #104126

closed

Prevent requiring "typo3conf" for Composer mode

Added by Garvin Hicking 5 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Should have
Category:
System/Bootstrap/Configuration
Target version:
-
Start date:
2024-06-17
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
12
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Second iteration from the previous issue https://forge.typo3.org/issues/104074

There was one place left where 'typo3conf' was used for file placement, the "Lock Backend" task.

The file LOCK_BACKEND should not be created in typo3conf/ in composer mode, but rather /var/transient/.

Only then 'typo3conf' is no longer needed (hopefully)


Related issues 4 (0 open4 closed)

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

Actions
Related to TYPO3 Core - Bug #104119: backend:lock does not work anymore in v12Closed2024-06-15

Actions
Related to TYPO3 Core - Bug #101298: Command backend:lock and backend:unlock using legacy pathsClosed2023-07-10

Actions
Related to TYPO3 Core - Bug #105326: wrong path in instruction of Install Tool for classic way installationResolvedGarvin Hicking2024-10-16

Actions
Actions

Also available in: Atom PDF