Project

General

Profile

Actions

Bug #88088

closed

cli binary is stored in wrong path

Added by Helmut Hummel about 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2019-04-05
Due date:
% Done:

100%

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

Description

With the change in #86513, the cli binary is now automatically generated on composer install.

Unfortunately it is written to a wrong path.
Currently we distinguish 3 paths within TYPO3 in Composer mode.

  1. TYPO3_PATH_COMPOSER_ROOT This is the path the root composer.json of the project is located
  2. TYPO3_PATH_ROOT This is TYPO3 base path formerly exposed by the constant PATH_site, now accessible with Environment::getProjectPath()
  3. TYPO3_PATH_WEB This is the path to the publicly available document root, accessible with Environment::getPublicPath()

In default TYPO3 installations, even in composer mode the two latter are the same. However with the goal of at some point being able to have a directory with only public assets,
it is important to distinguish them in the code. It becomes important already now, when using helhum/typo3-secure-web, which exposes TYPO3_PATH_WEB to a different directory and
publishes all public assets to it.
TYPO3 currently writes the cli binary to the public folder then, which should be changed


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #86513: typo3/sysext/core/bin/typo3 does not work in composer modeClosed2018-10-01

Actions
Actions

Also available in: Atom PDF