Task #2126

Implement sub routes support (routes should be configured globally in one place)

Added by Bastian Waidelich about 13 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Must have
Category:
Configuration
Start date:
2008-11-11
Due date:
% Done:

100%

Estimated time:
Sprint:
PHP Version:
Has patch:
Complexity:

Description

Routes should be configured globally at one place to avoid complexity and make it possible to disable/change existing routes in new distributions.
Currently every package can define it's own routes which might cause an unmanageable configuration and leads to the problem that the loading order of the packages matter.
TODO:
  • move all existing route definitions to the global Routes.yml file
  • make sure, that FLOW3 ConfigurationManager only loads global Routes
  • allow Packages to suggest Routes or to add Sub Routes (probably not in this release)

Related issues

Related to YAML - Feature #2322: Possibility to track filename and line number of a specific configuration settingNewRobert Lemke2008-12-15

Actions
Related to TYPO3.Flow - Bug #3433: Routes in packages are overruled by global configurationResolvedRobert Lemke2009-05-24

Actions

Also available in: Atom PDF