Troubleshooting routing 

An invalid URL shows a page instead of a 404 error 

A routePath that consists of nothing but a variable matches every single path segment below a page. With the following configuration, https://example.org/does-not-exist shows the root page with the HTTP status code 200, and does-not-exist is passed to the plugin as an argument:

routeEnhancers:
  NewsPlugin:
    type: Extbase
    extension: News
    plugin: Pi1
    routes:
      - routePath: '/{news_title}'
        _controller: 'News::detail'
        _arguments:
          news_title: news

Without further information, TYPO3 cannot tell whether a value is valid. limitToPages limits the problem to the listed pages, but does not solve it. Use at least one of these options, so that an invalid value leads to a 404 error:

• Add a static segment to the route, for example /show/{news_title}.
• Add an aspect to the variable, for example a PersistedAliasMapper, which only accepts values of existing records.
• Add a requirements rule for the variable.

routeEnhancers:
  NewsPlugin:
    type: Extbase
    extension: News
    plugin: Pi1
    routes:
      - routePath: '/show/{news_title}'
        _controller: 'News::detail'
        _arguments:
          news_title: news
    aspects:
      news_title:
        type: PersistedAliasMapper
        tableName: tx_news_domain_model_news
        routeFieldName: path_segment

A generated URL still contains query parameters 

If no route fits the arguments of a link, TYPO3 generates the URL of the page and appends the arguments as query parameters. Check the following causes:

• No route contains this combination of arguments. You need a separate routePath for each combination, for example for a list with and without pagination.
• The value is unknown to the aspect. A StaticValueMapper with the entry march: '03' generates /news/march for the value 03, but not for the value 3. Compare the format of the value in the link with the values of the aspect, including leading zeros.
• The value is empty. Leave out the argument instead of linking with an empty value such as tx_news_pi1[category]=.

An optional variable does not work with the PageType decorator 

defaults make a variable optional only if it is at the very end of the routePath . The PageType decorator appends its suffix, such as / or .html, to the path of each route, so the variable is no longer the last part and a value is required.

Weakening the rule with requirements and .* is not a solution. It leads to URLs like /news/category// and /news/category/.html.

Configure one route with the variable and one route without it, and do not use defaults for this variable. This generates /news/category/ and /news/category/my-category/:

routeEnhancers:
  PageTypeSuffix:
    type: PageType
    default: '/'
    index: ''
    map:
      '/': 0
  NewsPlugin:
    type: Extbase
    extension: News
    plugin: Pi1
    routes:
      - routePath: '/category'
        _controller: 'News::list'
      - routePath: '/category/{category_name}'
        _controller: 'News::list'
        _arguments:
          category_name: overwriteDemand/categories
    aspects:
      category_name:
        type: PersistedAliasMapper
        tableName: sys_category
        routeFieldName: slug

The wrong route is used 

Several routes can fit the same URL. For an incoming URL, the routes of an enhancer are tested in the order of their configuration, and the first match wins. A route is skipped if an aspect of the route cannot resolve the value.

This has the following consequences for routes like /{news_title} and /{category_name}, which have the same structure:

• If all of them have an aspect, the URL resolves to the route with the matching record or value.
• A route without an aspect accepts every value, so the routes after it are never reached. Add an aspect, or move this route to the end of the list.

When generating a URL, defaults make a route fit even though the link does not supply all of its arguments. With a default value for page and the route /page-{page}, a list view without any argument can get the URL /news/page instead of /news/. Avoid defaults where possible, and configure a separate route for each case, such as / for the list view.

Only the last enhancer of an Extbase plugin works 

If two Extbase plugin enhancers for the same plugin apply to a page, only the last one has an effect, both for generating and for resolving URLs. The routes of the first one lead to a 404 error.

Use limitToPages to assign each enhancer to different pages. This way, one plugin can use different URLs in different areas of the website:

routeEnhancers:
  NewsArticles:
    type: Extbase
    limitToPages:
      - 8
    extension: News
    plugin: Pi1
    routes:
      - routePath: '/article/{news_title}'
        _controller: 'News::detail'
        _arguments:
          news_title: news
  NewsEvents:
    type: Extbase
    limitToPages:
      - 17
    extension: News
    plugin: Pi1
    routes:
      - routePath: '/event/{news_title}'
        _controller: 'News::detail'
        _arguments:
          news_title: news

Possible range of all mappers is larger than 10000 items 

To prevent cache flooding, the number of combinations in a route is limited. TYPO3 multiplies the number of items of all static, countable mappers of a route, such as the StaticRangeMapper. If the result is larger than 10000, the exception 1537696772 is thrown, when generating as well as when resolving URLs:

• 12 months × 30 years × 25 pages = 9000 combinations are allowed.
• 12 months × 30 years × 30 pages = 10800 combinations are not allowed.

Reduce one of the ranges, or use a custom aspect that does not implement \Countable .

A single StaticRangeMapper is limited to 1000 items. A larger range throws the exception 1537696771.