First Time Installation doesn't need a "beforePackageStatesMigration.php" file
For a dummy blank new installation the Installer creates a LocalConfiguration.php in "old-school" way (with extList) and then converts that to PackageStates and moves the old file to LocalConfiguration.beforePackageStatesMigration.php.
This is ugly, as you find yourself with "old files" while you are just installing it for the first time.
Could be streamlined, so that the first time installation activates the packages automatically.
[TASK] Default active extension handling in package manager
Integrate the definition of packages that should be activated at
first installation and packages that are required for a minimal
usable system in the package manager.
There are now three possible properties in Classes/Package.php:
- protected - Package can not be uninstalled in em.
- partOfFactoryDefault - Package is activated at first installation.
- partOfMinimalUsableSystem - Package is activated if
PackageStates.php is missing. extensionmanager and t3skin are
affected here, if PackageStates.php is deleted, the install tool
will create a new one with those packages activated, so the backend
is "usable" enough to activate further packages.
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind
Reviewed-by: Thomas Maroschik
Tested-by: Thomas Maroschik
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring