Cms Composer Installers Laravel Package

This release contains a couple of bugfixes related to newer PHP versions.

This release contains a couple of bugfixes related to newer PHP versions.

This release contains a couple of bugfixes related to newer PHP versions

This release contains a couple of bugfixes related to newer PHP versions

This release is identical to 4.0.0-RC1 and done to make it possible for TYPO3 12LTS to depend on it, without forcing TYPO3 11LTS users to use it.

This release contains a couple of bugfixes related to newer PHP versions

Features

• All extensions are now installed in the vendor folder. This means all extension files will not be accessible by the web server any more. Public resources from extensions must be in the Resources/Public folder, which will automatically be published by TYPO3 using symlinks. See "breaking changes" for more implications on that change.

Breaking changes

All extensions are now installed in the vendor folder.

While this is a great feature, it also comes with some implications that need to be considered:

1. All files from extensions, that require to be accessed by the web server directly MUST reside inside the Resources/Public folder.
2. The public resource URL can not be derived any more from the absolute path to the file by stripping off some path part, but only by passing the absolute path to \TYPO3\CMS\Core\Utility\PathUtility::getAbsoluteWebPath Example:

use TYPO3\CMS\Core\Utility\PathUtility;
use TYPO3\CMS\Core\Utility\GeneralUtility;

PathUtility::getAbsoluteWebPath(GeneralUtility::getFileAbsFileName('EXT:ext_key/Resources/Public/Icons/Extension.svg'));

3. Every TYPO3 extension (Composer package of type typo3-cms-extension) must define its extension key explicitly in composer.json
4. It is not possible any more to change app-dir or root-dir within the root composer.json Only web-dir can still be changed, but it needs to be a sub directory of the composer.json directory

General remarks

It is planned to release a stable version 4.0.0 in a few weeks and new projects with TYPO3 11.5 will then install this version of composer installers. If the extension you require in your project have hard coded paths that reference e.g. typo3conf/ext/ directly, you can still pin this package to version ^3.1 within your root composer.json

Allow composer/installers 2.0 and higher

Fixes an bug with installers when using composer.typo3.org as repository

Mark as compatible with all bugfix versions of PHP 7.4

Mark as compatible with all bugfix versions of PHP 7.4

Mark as compatible with PHP 7.4

Fix replace section parsing in ExtensionKeyResolver

Fix replace section parsing in ExtensionKeyResolver

Fix replace section parsing in ExtensionKeyResolver

Mark as compatible with PHP 7.4

Mark as compatible with PHP 7.3

Changes since 1.4.1:

• Avoid fatal error when upgrading from 1.3.x

Full list of changes since 1.4.1

Changes since 1.4.0:

• Improve deprecation message for cms-package-dir

Full list of changes since 1.4.0

Changes since 1.4.0 RC4:

• Improve deprecation message for cms-package-dir

Full list of changes since 1.4.0 RC4

Changes since 1.4.0 RC3:

• Harden t3x extraction
• Add experimental root-dir

Full list of changes since 1.4.0 RC3

Changes since 1.4.0 RC2:

• Fixed a bug in path calculations

Full list of changes since 1.4.0 RC2

Changes since 1.4.0 RC1:

• Changed extra -> typo3/cms -> extensionKey to extra -> typo3/cms -> extension-key

Full list of changes since 1.4.0 RC1

Changes since 1.3.0:

• Deprecated config options extensions-in-vendor-dir, prepare-web-dir and setting web-dir to . (since . is still default, not setting web-dir also issues a deprecation warning)
• Raise minimum required PHP version to 7.0
• Expose essential paths that are only know at composer build time as environment variables
• Respect extra -> typo3/cms -> extensionKey in package composer.json to explicitly set the extension key for an extension
• Added API that packages (especially typo3/cms) can easily hook into composer build time
• Bugfixes

Full list of changes since 1.3.x

Changes since 1.3.0 RC1:

• Replaced extension-dir and imply-extension-key with extensions-in-vendor-dir (see README) to reduce complexity
• Moved to PSR-4 autoloading standard
• Bugfixes

You can view the full list of changes compared to 1.2.x and compared to 1.3.0 RC1

Changes:

• Using PSR-2 now
• Added documentation in README file
• Added several new options (prepare-web-dir, extension-dir, imply-extension-key) (see README)
• TYPO3 core and extensions can now configure binaries to be installed by composer

• The composer installer has been largely rewritten to use current composer plugin API
• TAR Downloading of the TYPO3 CMS Core has been implemented
• Extension Installation has been implemented