The admin panel has been extracted into an own extension. To enable
users to de-activate the admin panel completely, the hard coupling
between the extension and other parts of the core had to be resolved.
With this change, the initialization of both adminPanel and feedit
were moved into PSR-15 middlewares. Additionally all parameters
related to the adminPanel were removed from the FrontendBackend-
UserAuthentication.
As feedit is tigthly coupled with the adminPanel some changes had
to be made to its initialization, too.
The flow of the adminPanel initialization and rendering were
streamlined to allow modules to make use of the request object.
Due to these changes in the control flow of the application the
two existing tests were removed and new tests will be rewritten
once the API is declared as stable.
Releases: master
Resolves: #84641
Change-Id: I72beefde0d792d3f4295c45aa27204c817d2de7a
Reviewed-on: https://review.typo3.org/56558
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Tested-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Reviewed-by: Benni Mack <benni@typo3.org>
Tested-by: Benni Mack <benni@typo3.org>
Composer license definition GPL-2.0+ has been deprecated
and has to be replaced with GPL-2.0-or-later.
Resolves: #83607
Releases: master, 8.7, 7.6, 6.2
Change-Id: I6113bc3a90cb6a56830b930522dde2eaacd5025e
Reviewed-on: https://review.typo3.org/55404
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Oliver Klee <typo3-coding@oliverklee.de>
Reviewed-by: Riccardo De Contardi <erredeco@gmail.com>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: Oliver Hader <oliver.hader@typo3.org>
To be able to install subtree split packages in dev-master
the package dependencies between them need to allow exactly that.
Releases: master
Resolves: #83309
Change-Id: If2b8ea86958a425a6a047207bc064a41698215a4
Reviewed-on: https://review.typo3.org/55062
Reviewed-by: Nicole Cordes <typo3@cordes.co>
Tested-by: Nicole Cordes <typo3@cordes.co>
Reviewed-by: Helmut Hummel <typo3@helhum.io>
Tested-by: Helmut Hummel <typo3@helhum.io>
It's better to fix the current minor release in the branch version too,
so depending projects can use the dev version of this specific minor
release and will not have any headaches when 9.0 gets released.
Resolves: #77984
Releases: master
Change-Id: I36def811213dd99a3bf938af0459026d6233f645
Reviewed-on: https://review.typo3.org/49966
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Susanne Moog <susanne.moog@typo3.org>
Tested-by: Susanne Moog <susanne.moog@typo3.org>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
All system extensions should have a dependency on
"typo3/cms-core" with a fixed version set to "9.0.0".
Additionally, EXT:core ("typo3/cms-core") needs to have all
dependencies of the root composer.json in order
to work as standalone composer package.
Releases: master
Resolves: #83270
Change-Id: Iaf0e925b46548914dcd0ffff49aedf5fc89107b6
Reviewed-on: https://review.typo3.org/55000
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Susanne Moog <susanne.moog@typo3.org>
Tested-by: Susanne Moog <susanne.moog@typo3.org>
Reviewed-by: Stefan Neufeind <typo3.neufeind@speedpartner.de>
Tested-by: Stefan Neufeind <typo3.neufeind@speedpartner.de>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Benni Mack <benni@typo3.org>
Tested-by: Benni Mack <benni@typo3.org>
Description, dependencies between core packages and
core package versions are now in sync in ext_emconf.php
and composer.json
Now also added extension key information explicitly
in composer.json
What still should be done later is adding further
dependencies to these files if required.
This change was mostly automated using
helhum/ext-tools with the command:
typo3cms composerjson:sync 'typo3/sysext/*'
Resolves: #82003
Releases: master, 8.7
Change-Id: Ife913038142e8ecc137d21d4d43e2cdf467fb0f9
Reviewed-on: https://review.typo3.org/53621
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Riccardo De Contardi <erredeco@gmail.com>
Reviewed-by: Philipp Gampe <philipp.gampe@typo3.org>
Reviewed-by: Georg Ringer <georg.ringer@gmail.com>
Tested-by: Georg Ringer <georg.ringer@gmail.com>
Reviewed-by: Wouter Wolters <typo3@wouterwolters.nl>
Tested-by: Wouter Wolters <typo3@wouterwolters.nl>
Core extensions installed individually (from subtree split)
must never be installed together with the typo3/cms package
We can avoid this, by adding a conflict section in each
composer.json
Resolves: #81982
Releases: master, 8.7
Change-Id: Ia6a346227852237f58875a3e3216d3cad298f8bf
Reviewed-on: https://review.typo3.org/53603
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Markus Klein <markus.klein@typo3.org>
Reviewed-by: Sascha Egerer <sascha@sascha-egerer.de>
Reviewed-by: Helmut Hummel <typo3@helhum.io>
Tested-by: Helmut Hummel <typo3@helhum.io>
To ease installation of master versions of
system extensions from subtree splitted repos,
we add a branch alias to all of them.
Resolves: #81979
Releases: master
Change-Id: Ic7f4aa4762286e4e881447d6ecdbead411e6635f
Reviewed-on: https://review.typo3.org/53600
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Benni Mack <benni@typo3.org>
Tested-by: Benni Mack <benni@typo3.org>
Reviewed-by: Georg Ringer <georg.ringer@gmail.com>
Tested-by: Georg Ringer <georg.ringer@gmail.com>
Since http://typo3.org has been changed to https, adopt all links
in the core as well. Replace some outdated links to newer once
(if it could be replaced).
Resolves: #69989
Releases: master
Change-Id: I5d612b3b01cb75b613483649e8c754336c0fe516
Reviewed-on: http://review.typo3.org/43459
Reviewed-by: Andreas Fernandez <typo3@scripting-base.de>
Tested-by: Andreas Fernandez <typo3@scripting-base.de>
Reviewed-by: Josef Glatz <jousch@gmail.com>
Tested-by: Josef Glatz <jousch@gmail.com>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
This resolves problems with composer dependencies and Extension name /
Composer package name differences.
Resolves: #68700
Releases: master
Change-Id: I07f57f24ef7e9337e7ef8f6ee69538c038f2c0ff
Reviewed-on: http://review.typo3.org/42615
Reviewed-by: Alexander Opitz <opitz.alexander@googlemail.com>
Reviewed-by: Nicole Cordes <typo3@cordes.co>
Tested-by: Nicole Cordes <typo3@cordes.co>
Reviewed-by: Markus Sommer <markussom@posteo.de>
Tested-by: Markus Sommer <markussom@posteo.de>
Reviewed-by: Helmut Hummel <helmut.hummel@typo3.org>
Tested-by: Helmut Hummel <helmut.hummel@typo3.org>
In order to deliver more information
in custom installations for use with composer,
the namespaces for using the composer
autoloader are added to each composer.json
of all system extensions.
Releases: master, 6.2
Resolves: #64356
Change-Id: Ic0fa9e0969a48f68cce8ceeb77dbef3b75e6e6f1
Reviewed-on: http://review.typo3.org/36076
Reviewed-by: Helmut Hummel <helmut.hummel@typo3.org>
Tested-by: Helmut Hummel <helmut.hummel@typo3.org>
Reviewed-by: Anja Leichsenring <aleichsenring@ab-softlab.de>
Tested-by: Anja Leichsenring <aleichsenring@ab-softlab.de>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Update version number of all sysext and dependency definitions.
Resolves: #62341
Releases: master
Change-Id: Ic8b1b8ead08432917a28b226bbb43347dac42087
Reviewed-on: http://review.typo3.org/33395
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Wouter Wolters <typo3@wouterwolters.nl>
Tested-by: Wouter Wolters <typo3@wouterwolters.nl>
Resolves: #53753
Releases: 6.2
Change-Id: I3acb81c71796bc84ada29e6cdf6141be07f69ca3
Reviewed-on: https://review.typo3.org/25503
Reviewed-by: Christian Opitz
Reviewed-by: Fabien Udriot
Tested-by: Fabien Udriot
Reviewed-by: Felix Kopp
Tested-by: Felix Kopp
Reviewed-by: Thomas Maroschik
Tested-by: Thomas Maroschik
The current composer type of system extensions is "typo3cms-framework".
In the composer installer for TYPO3 CMS the composer type of extensions
is "typo3-cms-extension". In order to align our composer type with the
community defined it is changed to "typo3-cms-framework".
Resolves: #52831
Releases: 6.2
Change-Id: I1f43a60bd4cf59b47163123b57c8ba09e35e6526
Reviewed-on: https://review.typo3.org/24780
Reviewed-by: Sebastian Fischer
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Change-Id: Iaf88fc46903400d97f6f1dc3acedb3c9b438e8dd
Releases: 6.2
Resolves: #52740
Related: #47018
Reviewed-on: https://review.typo3.org/24667
Reviewed-by: Thomas Maroschik
Tested-by: Thomas Maroschik
Reviewed-by: Alexander Opitz
Tested-by: Alexander Opitz
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn