Project

General

Profile

Actions
Copy link

Bug #101298

closed

Command backend:lock and backend:unlock using legacy paths

Added by Benjamin Kott over 1 year ago. Updated 8 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
System/Bootstrap/Configuration
Target version:
-
Start date:
2023-07-10
Due date:
% Done:

0%

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

Description

In composer mode the backend:lock and backend:unlock are still pointing to the legacy file location e.g. `./public/typo3conf/LOCK_BACKEND`

Lock file should be created in `./var/transient/LOCK_BACKEND`

Related issues 1 (0 open — 1 closed)

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

Actions
Actions
Copy link
 #1

Updated by Georg Ringer 9 months ago

  • Status changed from New to Accepted
  • Sprint Focus set to On Location Sprint
Actions
Copy link
 #2

Updated by Gerrit Code Review 8 months ago

  • Status changed from Accepted to Under Review

Patch set 1 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/+/85263

Actions
Copy link
 #3

Updated by Garvin Hicking 8 months ago

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

Updated by Garvin Hicking 8 months ago

  • Category set to System/Bootstrap/Configuration
  • Status changed from Under Review to Closed

Closing in favor of 104126 - hope thats ok. Didn't see this one before.

Actions
Copy link

Also available in: Atom PDF