Project

General

Profile

Actions
Copy link

Feature #89518

open

Decouple static routes from site config

Added by Daniel Goerz over 4 years ago. Updated 15 days ago.

Status:
Under Review
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2019-10-25
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Regarding the restrictions of static routes, we tried to find a solution for all use cases but unfortunately this is not possible with the current architecture of static routes. The main design flaw is that static routes are bound to sites but sites do not have to be exclusive in terms of their base. This leads to an arbitrary static route resolving.

To circumvent the current restriction on site configurations that have no dedicated entry point "/" the only solution would be to consider rearranging the Middlewares in your installation.

Goal:

We need to decouple static routes from site configuration and treat them more like redirects are treated now. They need to be globally defined to remove the arbitrariness when resolving. In this case we could think about serving them in a dedicated sysext (like redirects) because then the functionality could be removed completely if not needed (to reduce bloat).

To keep static routes "deployable" they could live in a yaml file instead of the database and probably be editable through a dedicated backend module.

Related issues 4 (1 open — 3 closed)

Related to TYPO3 Core - Bug #86615: Static route sitemap.xml is not working on single-page treeClosed2018-10-10

Actions
Related to TYPO3 Core - Bug #87095: Robots.txt not reachable if base is not "/"Closed2018-12-07

Actions
Related to TYPO3 Core - Bug #88543: Static routes does not work if no language serves root levelClosed2019-06-12

Actions
Related to TYPO3 Core - Bug #86835: Static route sitemap.xml is still not working on single-page treeNew2018-11-02

Actions
Actions
Copy link

Also available in: Atom PDF