Routing

Table of Contents

Namespaces

Aspect
Enhancer

Interfaces

RouteResultInterface
An object that is usually returned by a Router to contain all results.
RouterInterface
Base Router to be used all over the TYPO3 Core. Its base lies around PSR-7 requests + URIs, and special "RouteResult" objects.

Classes

BestUrlMatcher
InvalidRouteArgumentsException
Exception thrown when a route does not exist or does not match the Route Arguments
MatchedRoute
PageArguments
Contains all resolved parameters when a page is resolved from a page path segment plus all fragments.
PageRouter
Page Router - responsible for a page based on a request, by looking up the slug of the page path.
PageSlugCandidateProvider
Provides possible pages (from the database) that _could_ match a certain URL path, but also works for fetching the best "slug" value for multi-lingual pages with a specific language requested.
PageUriMatcher
Internal class, which is similar to Symfony's Urlmatcher but without validating - conditions / expression language - host matches - method checks because this method only works in conjunction with PageRouter.
Route
TYPO3's route is built on top of Symfony's route with some special handling of "Aspects" built on top of a route
RouteCollection
Extensible container based on Symfony's Route Collection
RouteNotFoundException
Exception thrown when a route does not exist
RouteSorter
Pre-processing of given routes based on their actual disposal concerning given parameters.
SiteMatcher
Returns a site based on a given request.
SiteRouteResult
Class, usually available within request attribute "routing" containing all the findings of the Routers.
UnableToLinkToPageException
Exception thrown when a link to a page (or page in a specific translation) cannot be built.
UrlGenerator

        
On this page

Search results