Sites Configuration should overrule package Configuration
This is not really a bug, more a missing feature, but I think, this is rather important:
It's currently not possible to override configuration from within a Sites Package.
If you want to change the default authentication redirect URI, you could add following to the Settings.yaml of your site package:
TYPO3: # redirect to login page when trying to access a protected page: FLOW3: security: authentication: providers: DefaultProvider: entryPoint: WebRedirect: uri: login.html
But this will be overriden by the respective configuration in the Settings.yaml of the TYPO3 package.
Of course, you can copy those lines to the global Settings.yaml, but our goal should be to be able to provide all required settings with your site package..
It should be possible to somehow configure the order of how package settings are merged..
Note: I'm setting the target version to 1.0 beta 1 because this would probably be a breaking change afterwards..
Updated by Stephan Schuler over 10 years ago
I agree that there has to be a certain ordre of packages. But I don't want to have all that stuff in the sites package.
As some projects will consist of many different parts, it should be allowed to split up such projects into different packages.
Especially, I want to be able to create a package "MyPackage" containing the functionality. This one may become public available. And I want to create another package "MyPackageCustom" that contains project specific changes like custom layout and settings.
So it should be possible to configure package dependencies in some way.
I would prefer to add package dependencies to the Package.php. That would simply allow the PackageManager to "usort" its internal array of packageInterfaces.