Extension configuration¶
Extension configuration is used for global settings which should be the same for the entire TYPO3 installation.
It is
configured in the backend, via Settings | Extension Configuation
or using the file settings.php.
EXT:backend¶
EXT:backend | login.loginLogo¶
Logo
Login tab
- default:
empty
Set the logo used in the Fluid email in the EXT:backend extension configuration:
$GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['backend']['login.loginLogo'] = 'EXT:my_theme/Resources/Public/Images/login-logo.png or //domain.tld/login-logo.png';
EXT:brofix¶
EXT:brofix | linkTargetCacheExpiresLow¶
External link target cache (in seconds) for checking
Checking tab
- default:
0 (means use TSconfig value linkTargetCache.expiresLow)
- available values:
any integer value
For a description see the TSconfig option linkTargetCache.expiresLow.
EXT:brofix | linkTargetCacheExpiresHigh¶
External link target cache (in seconds) for checking
Checking tab
- default:
0 (means use TSconfig value linkTargetCache.expiresHigh)
- available values:
any integer value
This should be a slightly higher value than EXT:brofix | linkTargetCacheExpiresLow or 0.
For a description see the TSconfig option linkTargetCache.expiresHigh.
EXT:brofix | excludeSoftrefs¶
Do not use these softreference parsers (comma separated list) when parsing content
Checking tab
default: url
available values: any softref parser keys, separated by comma
This is a workaround for a TYPO3 core bug, see see https://forge.typo3.org/issues/97937
EXT:brofix | excludeSoftrefsInFields¶
In which fields should excludeSoftrefs apply
Checking tab
- default:
"tt_content.bodytext"
- available values:
any softref parser keys, separated by comma
This is a workaround for a TYPO3 core bug, see see https://forge.typo3.org/issues/97937
Usually, you will want to apply this in any rich text fields where link tags are used.
EXT:brofix | tcaProcessing¶
Perform TCA processing
Checking tab
- default:
"default"
- available values:
"default" | "full"
Changes how the TCA processing is done. The default setting may not work for some configurations and especially for Flexforms. In that case, it should be set to "full". This setting is still experimental, so it is not on by default.
This setting results in 2 changes:
Use of the FormDataGroup
If the entire row is fetched for TCA processing. If "full" is on, the entire row is fetched. If the value is "default", only the fields defined in "searchFields" are fetched, in addition to some fields such as type, relevant fields for language evaluation and header.
By default, one of the following class names to use as FormDataGroup for TCA processing will be used based on the value of tcaProcessing:
"default": SypetsBrofixFormEngineFieldShouldBeChecked
"full": SypetsBrofixFormEngineFieldShouldBeCheckedWithFlexform
EXT:brofix | overrideFormDataGroup¶
Override FormDataGroup for processing TCA
Checking tab
- default:
"" (empty, which means the default FormDataGroup based on tcaProcessing is used)
- available values:
any valid class name which implements FormDataGroupInterface as fully qualified class name, for example MyvendorMyextensionFormEngineMyFormdatagroup
Changes how the TCA processing is done.
EXT:brofix | showEditButtons¶
(since TYPO3 v12)
Show button to edit entire record, only the field with a broken link or both.
Report tab
- default:
"Both" (both buttons are displayed)
- available values:
"Both", "Edit field", "Edit full"
EXT:brofix | showalllinks¶
(since TYPO3 v12)
Show all links, not just broken links.
Report tab
- default:
1 (on)
- available values:
1 (on) | 0 (off)
If this is on, all links can be displayed, not just the broken links. This requires a full recheck if the setting was previously off or the feature not yet available.
EXT:brofix | traverseMaxNumberOfPagesInBackend¶
Maximum number of pages to traverse in Backend ...
Report tab
- default:
1000
- available values:
any number, 0 turns feature off
Set the maximum number of pages traversed in the backend module. This should be limited so that loading the broken link list in the backend does not feel sluggish and slow. A good rule of thumb is to always keep the time required to load a page in the Backend always under 1 second. Depending on the performance of your site, you should use a limit such as 1000 (thousand).
$GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['brofix']['traverseMaxNumberOfPagesInBackend'] = 1000;
Note
Remember that even though pagination is applied, Broken Link Fixer will always traverse through all subpages of the current page (unless the level is restricted in the form). The traversing of the pages is not cached and may cause considerable delays.