Skip to content

[Backport 13.4] [TASK] Remove mentions of TSFE in Bootstrapping and Middlewares chapters #4934

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 28, 2024
Merged

[Backport 13.4] [TASK] Remove mentions of TSFE in Bootstrapping and Middlewares chapters #4934

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions Documentation/ApiOverview/RequestLifeCycle/Bootstrapping.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@ calling :php:`Bootstrap::init()` and serves as an entry point for later calling
an application class, depending on several context-dependant constraints.

Each application class registers request handlers to
run a certain request type (e.g. eID or TSFE-logic, or Ajax requests in the Backend). Each application is handed
over the class loader provided by Composer.
run a certain request type (e.g. eID or Ajax requests in the backend). Each
application is handed over the class loader provided by Composer.

Applications
============
Expand All @@ -25,7 +25,7 @@ There are four types of applications provided by the TYPO3 Core:
-----------------------------------------

This class handles all incoming web requests coming through :file:`index.php`
in the public web directory. It handles all regular page (TSFE) and eID requests.
in the public web directory. It handles all regular page and eID requests.

It checks if all configuration is set, otherwise redirects to the TYPO3 Install
Tool.
Expand Down
4 changes: 2 additions & 2 deletions Documentation/ApiOverview/RequestLifeCycle/Middlewares.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ the configuration is not applied. This is usually no problem - Extbase plugins
are typically either included as :ref:`USER content object <t3tsref:cobj-user>`
(its content is cached and returned together with other content elements in
fully-cached page context), or the Extbase plugin is registered as USER_INT. In
this case, the :ref:`TSFE <tsfe>` takes care of calculating TypoScript before
this case, the TYPO3 Core takes care of calculating TypoScript before
the plugin is rendered, while other USER content objects are fetched from page
cache.

Expand All @@ -117,7 +117,7 @@ that already use Extbase in a middleware have the following options:

* Move away from the middleware and register the Extbase instance as a casual
:ref:`USER_INT <t3tsref:cobj-user-int>` object via TypoScript: Extbase is
designed to be executed like this, the TSFE bootstrap will take care of
designed to be executed like this, the bootstrap will take care of
properly calculating TypoScript, and Extbase will run as expected.

Note that with TYPO3 v12, the overhead of USER_INT content objects has been
Expand Down
Loading