Bug #52927
New Site package should depend on neos not on flow
| Status: | New | Start date: | 2013-10-17 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | Base Distribution - 1.0 alpha 7 | Estimated time: | 0.10 hour | |
| PHP Version: |
Description
Hey,
I run into some troubles trying to override a TYPO3.Form setting within my Site package Settings.yaml.
The load order of packages was wrong so that TYPO3.Form was loaded after my package and by that overriding my changes.
The cause of this problem was, that the new created site package depends on TPYO3.flow and not on TYPO3.Neos.
This bug is very easy to fix and a big pain to find.
History
#1 Updated by Torsten no-lastname-given almost 2 years ago
Ok after taking a deeper look it is not that trivial to fix. I guess a extended PackageManger is needed because the require part of the composer manifest is hardcoded in TYPO3\Flow\Package\PackageManager on line 488.