Feature #92532
open
Drop support for extension-in-extension installation
Added by Benni Mack over 3 years ago.
Updated over 1 year ago.
Category:
Extension Manager
Description
The feature was only implemented for EXT:introduction to ship a compatible RealURL version, but is actually very cumbersome if people want to use Composer for managing dependencies.
- Status changed from New to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Related to Bug #92536: Use correct issue number in breaking RST added
- Status changed from Resolved to Closed
- Tracker changed from Task to Feature
- Status changed from Closed to New
- Target version changed from 11.0 to Candidate for patchlevel
- TYPO3 Version deleted (
11)
Dear Benni,
after two years of manual installation, we wanted to get in touch with you. Would it be possible to revert this patch? Maybe for TYPO3 v12.
Our company respectively our infrastructure is based on the legacy installation of TYPO3 with shared symlinks to the core for the vHost’s per server. Our workflow had changed because of this patch and requires our developers to wait for the administrator to clone a dummy account for new instances. Our distribution extension from v10 was packed with all necessary extensions, files and had a an EventListener for tweaks after installation, which could be imported by the developer himself/herself.
Unfortunately, a composer-based installation is not possible to handle for every our dev’s and therefore we kindly ask if you could revert this. The suggestion to upload our extensions to the TER is also not an option for us because of trade secret.
Kind regards
Aleks
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by