Project

General

Profile

Feature #65493

Updated by Benni Mack over 9 years ago

A new Routing API is introduced in order to streamline 
 the entrypoints to the TYPO3 Backend. 

 All previous patches by Wouter for the dispatched modules 
 are the foundation for this change. 

 Instead of using the term "module" for anything linkable 
 in the backend, the term "routes" fits more. a "module" 
 or an ajax call is a derivative of a route, which will 
 build on this foundation. 

 Routes can be registered via 
 Configuration/Backend/Routes.php in any extension 
 and are loaded solely on Backend requests. 

 The Routing API is inspired by the Symfony Routing 
 framework and mostly compatible for now 
 but the TYPO3 implementation only takes around 
 20% of the needed logic for now. 

 There are four new classes 
 - Route (a single route with a path some options) 
 - RouteCollection (holding all routes) 
 - Router (API to match paths and generate URLs) 
 - UrlGenerator (Generates the URL) 

 This patch changes the entrypoint for 
 login/logout to typo3/index.php?route=XY&token=... 
 making index.php the only entrypoint to the  
 TYPO3 Backend in the future. 

 The main RequestHandler of all Backend modules 
 detects where a GET parameter "route" is given and 
 then resolves to a controller/action logic and checks 
 for a valid token. 

 Once this patch is in, all non-module entrypoints 
 are moved to the new format. 

 See http://wiki.typo3.org/Blueprints/BackendRouting 
 for implementation details. 
 

 Change-Id: I91b5812c833c558794f70fd4504f2da452b1c3ce

Back