BeforePageIsResolvedEvent
Changed in version 13.0
The event no longer receives an instance of
Typo
, the
get
method has
been removed: The controller is instantiated after the event has been
dispatched, event listeners can no longer work with this object.
Instead, the event now contains an instance of the new
DTO
\TYPO3\
, which can be retrieved
and manipulated by event listeners, if necessary.
See Migration.
The PSR-14 event
\TYPO3\
is
fired before the frontend process is trying to fully resolve a given page by its
page ID and the request.
The events may not be dispatched anymore when the
middleware
\TYPO3\
creates early responses.
Tip
There are three events in the process around the resolving of a page and its root line or language based on the incoming request. They are triggered in the following order:
- BeforePageIsResolvedEvent
- AfterPageWithRootLineIsResolvedEvent
- AfterPageAndLanguageIsResolvedEvent
Example
Note
Currently, we do not have an example for this event. If you can provide a useful one, please open an issue with your code snippets or a pull request.
API
- class BeforePageIsResolvedEvent
-
- Fully qualified name
-
\TYPO3\
CMS\ Frontend\ Event\ Before Page Is Resolved Event
A PSR-14 event fired before the frontend process is trying to fully resolve a given page by its page ID and the request.
Event Listeners can modify incoming parameters (such as $controller->id) or modify the context for resolving a page.
Migration
Use the method
get
to retrieve the calculated page state
at this point in the frontend rendering chain. Event listeners that manipulate
that object should set it again within the event using
set
.
In case the middleware
Typo
no longer
dispatches an event when it created an early response on its own, a custom
middleware can be added around that middleware to retrieve and further
manipulate a response if needed.