!!! TASK: Load Neos Routes from settings #1343
Conversation
This adjusts the Configuration to include Neos default routes via Settings. Background: Since version 3.1 Flow supports sub routes to be included via configuration (see http://flowframework.readthedocs.io/en/stable/TheDefinitiveGuide/PartIII/Routing.html#subroutes-from-settings). This is the recommended way to register routes as it provides greater flexibility. Note: Any existing `Routes.yaml` file in the global `Configuration` folder take precedence over routes loaded via Settings. Resolves: #1342 Related: neos/flow-development-collection#789
|
@bwaidelich, thanks for your PR! By analyzing the history of the files in this pull request, we identified @kdambekalns, @robertlemke and @johannessteu to be potential reviewers. |
| mvc: | ||
| routes: | ||
| 'Neos.Neos': | ||
| position: 'start' |
There was a problem hiding this comment.
how about the defaultUriSuffix variable?
There was a problem hiding this comment.
And position: 'start' seems to be breaking, custom routes, wich should always be loaded before neos subroutes should still be loaded before neos.neos
|
#1305 takes care of removing media browser routes as well |
| mvc: | ||
| routes: | ||
| 'Neos.Neos': | ||
| position: 'start' |
There was a problem hiding this comment.
And position: 'start' seems to be breaking, custom routes, wich should always be loaded before neos subroutes should still be loaded before neos.neos
| @@ -560,6 +560,10 @@ Neos: | |||
| applicationPackageKey: Neos.Neos | |||
| applicationName: Neos | |||
|
|
|||
| mvc: | |||
| routes: | |||
| 'Neos.Neos': TRUE | |||
There was a problem hiding this comment.
how about defaultUriSuffix?
bwaidelich
changed the title
With version 4.0 Neos registers its own sub routes by default via configuration (see neos#1343). In order to change the "defaultUriSuffix" add the following to your `Settings.yaml`:: Neos: Flow: mvc: routes: 'Neos.Neos': variables: 'defaultUriSuffix': '' (an empty string will remove the suffix) Related: neos#1343
This adjusts the Configuration to include Neos default routes
via Settings.
Background:
Since version 3.1 Flow supports sub routes to be included via configuration
(see http://flowframework.readthedocs.io/en/stable/TheDefinitiveGuide/PartIII/Routing.html#subroutes-from-settings).
This is the recommended way to register routes as it provides greater flexibility.
Note: Any existing
Routes.yamlfile in the globalConfigurationfolder takeprecedence over routes loaded via Settings.
This change should not break existing installations, but it might lead to routes being loaded twice
or (in rare cases) in a different order.
To make sure, any existing
Routes.yamlfile should be removed from the globalConfigurationfolders and the respective routes should be loaded via Settings (see documentation above).
In order to change the "defaultUriSuffix" from Neos Routes, add the following to your
Settings.yaml:(an empty string will remove the suffix)
Resolves: #1342
Related: neos/flow-development-collection#789