FE - frontend configuration

Additional relative paths where resources may be placed. Used in some frontend-related places for images and TypoScript. It should be prefixed with /. If not, then any path whose the first part is like this path will match. That is, myfolder/ , myarchive will match, for example, myfolder/, myarchive/, myarchive_one/, myarchive_2/, etc.

No check is done whether this directory actually exists in the root folder of the site.

If enabled, the total parse time of the page is added as HTTP response header X-TYPO3-Parsetime. This can also be enabled/disabled via the TypoScript option config.debug = 0.

Determines output compression of FE output. Makes output smaller but slows down the page generation depending on the compression level. Requires

• zlib in your PHP installation and
• special rewrite rules for .css.gz and .js.gz (before version 12.0 the extension was .css.gzip and .js.gzip)

Please see EXT:install/Resources/Private/FolderStructureTemplateFiles/root-htaccess for an example. Range 1-9, where 1 is least compression and 9 is greatest compression. true as value will set the compression based on the PHP default settings (usually 5 ). Suggested and most optimal value is 5.

If TRUE, a page not found call is made when cHash evaluation error occurs, otherwise caching is disabled and page output is displayed.

If TRUE, every frontend page is shown as "unavailable". If the client matches [SYS][devIPmask], the page is shown as normal. This is useful during temporary site maintenance.

If set, the pid of fe_user logins must be sent in the form as the field pid and then the user must be located in the pid. If you unset this, you should change the fe_users username eval-flag uniqueInPid to unique in $TCA.

This will do $TCA[fe_users][columns][username][config][eval]= nospace,lower,required,unique;

Maximum amount of login attempts for the time interval in [FE][loginRateLimitInterval], before further login requests will be denied. Setting this value to "0" will disable login rate limiting.

Allowed time interval for the configured rate limit. Individual values using PHP relative formats can be set in config/system/additional.php.

IP addresses (with *-wildcards) that are excluded from rate limiting. Syntax similar to [BE][IPmaskList] and [BE][loginRateLimitIpExcludeList]. An empty value disables the exclude list check.

If activated, Frontend Users are locked to (a part of) their public IP ( $_SERVER[REMOTE_ADDR]) for their session, if REMOTE_ADDR is an IPv4-address. Enhances security but may throw off users that may change IP during their session (in which case you can lower it). The integer indicates how many parts of the IP address to include in the check for the session.

Have also a look into the security guidelines.

If activated, Frontend Users are locked to (a part of) their public IP ( $_SERVER[REMOTE_ADDR]) for their session, if REMOTE_ADDR is an IPv6-address. Enhances security but may throw off users that may change IP during their session (in which case you can lower it). The integer indicates how many parts of the IP address to include in the check for the session.

If greater than 0 and the option permalogin is greater or equal 0, the cookie of FE users will have a lifetime of the number of seconds this value indicates. Otherwise it will be a session cookie (deleted when browser is shut down). Setting this value to 604800 will result in automatic login of FE users during a whole week, 86400 will keep the FE users logged in for a day.

Server side session timeout for frontend users in seconds. Will be overwritten by the lifetime property if the lifetime is longer.

If greater than 0, the session data of an anonymous session will timeout and be removed after the number of seconds given (86400 seconds represents 24 hours).

-1

Permanent login for FE users is disabled

0

By default permalogin is disabled for FE users but can be enabled by a form control in the login form.

1

Permanent login is by default enabled but can be disabled by a form control in the login form.

2

Permanent login is forced to be enabled.

In any case, permanent login is only possible if [FE][lifetime] lifetime is greater than 0.

Same as $TYPO3_CONF_VARS[SYS][cookieDomain]<_typo3ConfVars_sys_cookieDomain> but only for FE cookies. If empty, $TYPO3_CONF_VARS[SYS][cookieDomain] value will be used.

Sets the name for the cookie used for the front-end user session

Indicates that the cookie should send proper information where the cookie can be shared (first-party cookies vs. third-party cookies) in TYPO3 Frontend.

Enter lines of default TypoScript, constants-field.

Enter lines of default TypoScript, setup-field.

Enter additional directories to be prepended with absRefPrefix. Directories must be comma-separated. TYPO3 already prepends the following directories public/_assets/, public/typo3temp/ and all local storages including public/fileadmin/.

In Classic mode installations without Composer typo3conf/ext and typo3/ are also prefixed.

If enabled, the mount_pid feature allowing symlinks in the page tree (for frontend operation) is allowed.

If enabled, pages that have no translation will be hidden by default. Basically this will inverse the effect of the page localization setting "Hide page if no translation for current language exists" to "Show page even if no translation exists"

Array of key/value pairs where the key is tx_[ext]_[optional suffix] and value is relative filename of class to include. Key is used as "?eID=" for \TYPO3\CMS\Frontend\Http\RequestHandlerRequestHandler to include the code file which renders the page from that point.

(Useful for functionality that requires a low initialization footprint, for example frontend Ajax applications)

If set, the no_cache request parameter will become ineffective. This is currently still an experimental feature and will require a website only with plugins that dont use this parameter. However, using "&no_cache=1" should be avoided anyway because there are better ways to disable caching for a certain part of the website (see COA_INT/USER_INT<t3tsref:cobj-coa-int>).

The given parameters will be included when calculating canonicalized URL. See Including specific arguments for the URL generation for details.

If set, points to an HTML file relative to the TYPO3_site root which will be read and outputted as template for this message. Example fileadmin/templates/template_workspace_preview_logout.html.

Inside you can put the marker %1$s to insert the URL to go back to. Use this in <a href="%1$s">Go back...</a> links.

If enabled, included CSS and JS files loaded in the TYPO3 frontend will have the timestamp embedded in the filename, for example, filename.1676276352.js. This will make browsers and proxies reload the files, if they change (thus avoiding caching issues).

If disabled, the last modification date of the file will be appended as a query string.

Array to define the TypoScript parts that define the main content rendering.

Extensions like fluid_styled_content provide content rendering templates. Other extensions like felogin or indexed search extend these templates and their TypoScript parts are added directly after the content templates.

See EXT:fluid_styled_content/ext_localconf.php and EXT:core/Classes/TypoScript/IncludeTree/TreeBuilder.php

Matches the LinkService implementations for generating URLs and link texts via typolink. This configuration value can be used to register a custom link builder for the frontend generation of links.

[
    'page' => \TYPO3\CMS\Frontend\Typolink\PageLinkBuilder::class,
    'file' => \TYPO3\CMS\Frontend\Typolink\FileOrFolderLinkBuilder::class,
    'folder' => \TYPO3\CMS\Frontend\Typolink\FileOrFolderLinkBuilder::class,
    'url' => \TYPO3\CMS\Frontend\Typolink\ExternalUrlLinkBuilder::class,
    'email' => \TYPO3\CMS\Frontend\Typolink\EmailLinkBuilder::class,
    'record' => \TYPO3\CMS\Frontend\Typolink\DatabaseRecordLinkBuilder::class,
    'telephone' => \TYPO3\CMS\Frontend\Typolink\TelephoneLinkBuilder::class,
    'unknown' => \TYPO3\CMS\Frontend\Typolink\LegacyLinkBuilder::class,
]

Special settings for specific hashes.

Defines the password policy in frontend context.

If set, redirects executed by TYPO3 publicly expose the page ID in the HTTP header. As this is an internal information about the TYPO3 system, it should only be enabled for debugging purposes.

Configure the reporting HTTP endpoint of Content Security Policy violations in the frontend; if it is empty, the TYPO3 endpoint will be used.

Setting this configuration to '0' disables Content Security Policy reporting. If the endpoint is still called then, the server-side process responds with a 403 HTTP error message.

If defined, the site-specific configuration in config/sites/my_site/csp.yaml takes precedence over the global configuration.

$GLOBALS['TYPO3_CONF_VARS']['FE']['contentSecurityPolicyReportingUrl']
    = 'https://csp-violation.example.org/';

// Disables Content Security Policy reporting
$GLOBALS['TYPO3_CONF_VARS']['BE']['contentSecurityPolicyReportingUrl'] = '0';

Use $GLOBALS['TYPO3_CONF_VARS']['BE']['contentSecurityPolicyReportingUrl'] to configure Content Security Policy reporting for the backend.