Skip to content
Snippets Groups Projects
Commit 180a6f47 authored by Helmut Hummel's avatar Helmut Hummel
Browse files

[TASK] Remove Environment::getFrameworkBasePath where easily possible

Environment::getFrameworkBasePath() API was created
under the assumption that TYPO3 core extensions are always installed
in a dedicated but fixed folder (typo3/sysext).

Additionally this folder is assumed to be publicly accessible
through a web server.

Therefore this API is used in two contexts.
1. To resolve and check file system paths
2. To create URLs to public resources

To at some point achieve the goal to allow all TYPO3 extensions
to be installed in arbitrary locations (a configurable
vendor folder), usage of such API must be removed.

As a first step all usages are removed, that reference
files within the boundaries of one extensions.
Relative paths (relative to the file that references) are used
instead, or, where possible EXT: syntax

Releases: master
Resolves: #95250

Change-Id: Ie7291b71d5d85d75add9bc5b352a4bd1cf065499
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71102


Tested-by: default avatarcore-ci <typo3@b13.com>
Tested-by: default avatarBenni Mack <benni@typo3.org>
Tested-by: default avatarOliver Bartsch <bo@cedev.de>
Tested-by: default avatarHelmut Hummel <typo3@helhum.io>
Reviewed-by: default avatarBenni Mack <benni@typo3.org>
Reviewed-by: default avatarOliver Bartsch <bo@cedev.de>
Reviewed-by: default avatarHelmut Hummel <typo3@helhum.io>
parent a1000353
Branches
Tags
No related merge requests found
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment