Bug #3433
Routes in packages are overruled by global configuration
| Status: | Resolved | Start date: | 2009-05-24 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Robert Lemke | % Done: | 100% |
|
| Category: | MVC | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 1 | |||
| PHP Version: | Complexity: | |||
| Has patch: | Affected Flow version: |
Description
In the current implementation the route configuration is first loaded from all packages, then overwritten or appended by the global configuration. When matching the routes, the configured routes are matched in reverse order.
- Packages
- Global packages
- Local packages
- Global configuration
- Global context dependent configuration
Since the default routes are in the global configuration, a package cannot put a new route after the default routes or overwrite them. So the route configuration in packages is currently pretty useless and will not be applied. This is not inituitive.
There has to be a prioritization at a later stage, but for now it should suffice to have the default routes in the FLOW3 package and an empty global routes configuration. But a problem that arises with this solution is, that the route order will be bound to the order of the packages when loading the configuration. But as local packages come last, the behaviour would be more intuitive.
Related issues
History
#1 Updated by Bastian Waidelich about 6 years ago
#2 Updated by Bastian Waidelich about 6 years ago
This is resolved now, right?
Context-Routes are loaded first, then global routes which can include subroutes at a distinct position. So prioritization should be possible without restrictions..
#3 Updated by Robert Lemke about 6 years ago
- Status changed from Needs Feedback to Resolved
- Target version set to 1.0 alpha 1
- % Done changed from 0 to 100
Yes, I considered this as resolved.