Showing results 651 to 675 of 1561

Bug
Under Review Quiet Form Framework TYPO3 CMS 14

#110053 Validators of form element variants are not executed and mess up the stepType value when rendering them conditionally!

I think this is a follow up of #101455, that’s why I marked the issue as regression. But, maybe it’s also rather something due to #108704 or #108390.

I have a custom Form element with this rendering condition:

validators:
    - identifier: MyValidator
renderingOptions:
    enabled: false
variants:
    - identifier: showOnlyOnPages
      renderingOptions:
          enabled: true
      condition: 'stepType == "Page"'

This works up to the point that the element is actually only rendered on form pages, but not in finishers and not on summary pages. So the referenced issues is somehow solved.

But now a new bug seems to be present: as soon as there are validators, these validators are never executed in the conditional variants! If I drop the variants definition, the validators are executed. But then the element is also shown and “validated” also in finishers and summary pages, of course. Which is not desired, that’s why I have the conditions.

I think there’s also some kind of “off-by-one” error involved when having these conditonal variants. If I invert the conditions, like this:

validators:
    - identifier: MyValidator
renderingOptions:
    enabled: true
variants:
    - identifier: showOnlyOnPages
      renderingOptions:
          enabled: false
      condition: 'stepType != "Page"'

The Element is then NOT rendered on regular form pages. If I debug-dump the step type in this case, it is empty (empty string) – which is the reason why it is like this (because obvisouly ("" !== "Page") = true@). I think it should never-ever happen that a @stepType@ is empty. Additionally, the Element is then rendered on the summary page (if I dump there I get @stepType "Page"! totally wrong).

Somehow the variants are totally messing up the stepType and validator evaluation (or evaluation order).

I did not find a suitable workaround as of now.

Author S P
Created 06/12/26, 09:35
Updated 09/25/26, 06:33
Feature
Under Review Quiet Database API (Doctrine DBAL)

#110761 Let the Database Analyzer ignore configured tables on the Default connection

Problem

The analyzer introspects every table of the Default database. One column of a type Doctrine does not know aborts the whole analysis:

Doctrine\DBAL\Exception\InvalidArgumentException
Unknown database type "vector" requested, TYPO3\CMS\Core\Database\Platform\MariaDB110700Platform may not support it.

The concrete case is MariaDB VECTOR (#106585), but any unmapped type does this, even for a table that is not declared in any ext_tables.sql. Today the only way out is a separate database, because the analyzer cannot be told to leave a table alone.

This is not a request for VECTOR support. It is a request for a way to mark tables as not managed by TYPO3.

Proposal

ConnectionMigrator::buildSchemaDiff() already sets a Doctrine SchemaAssetsFilter for non-default connections. Extend this to the Default connection with a configurable exclusion list:

  1. New key, e.g. TYPO3_CONF_VARS['DB']['Connections']['Default']['unmanagedTables'] (list of table names), empty by default.
  2. Apply it as SchemaAssetsFilter in buildSchemaDiff(); combine with the existing mapping filter on other connections.
  3. Remove the names from $toSchema as well, so a stray ext_tables.sql declaration produces no CREATE. The method does this for views already; same pattern.
  4. Open question: additionally a PSR-14 event so an extension can declare its own tables in code.
  5. Functional test, Feature changelog.

Measured (TYPO3 14.3.7, DBAL 4.4.4, MariaDB 11.8.8)

Doctrine checks the filter before it converts a table’s columns (AbstractSchemaManager::listTables()), so the unknown type is never touched.

Table in the TYPO3 database:

CREATE TABLE tx_zzprobe_vector (
    uid int unsigned NOT NULL AUTO_INCREMENT,
    v VECTOR(4) NOT NULL,
    PRIMARY KEY (uid),
    VECTOR INDEX (v)
);
Setup getUpdateSuggestions() for Default
unchanged core Unknown database type "vector"
setSchemaAssetsFilter() excluding the table no exception, no suggestions
for comparison: vector mapped to BINARY via driver middleware no exception, but proposes RENAME TO zzz_deleted_tx_zzprobe_vector

Out of scope

VECTOR in ext_tables.sql (#106585), custom Doctrine types (#93637), creating the excluded table (its owner does that).

Effort

Roughly 30 to 50 lines plus one functional test and a changelog entry.

Related: #106585, #93637

Disclaimer: this proposal was drafted with the help of an AI assistant (Claude). The code analysis and the measurements were verified by hand on a local DDEV TYPO3 14.3.7 installation.

Author Julian Mair
Created 09/22/26, 09:31
Updated 09/24/26, 11:19
Bug
New Quiet Backend User Interface TYPO3 CMS 12

#103083 Message to editors when deleting files

Hello,

when an editor tries to delete a referenced file he gets this message:

“Die Datei kann nicht gelöscht werden, weil sie noch an den folgenden Orten benutzt wird [record:tt_content:7947], [record:tt_content:8007]”

Deepl translation:
“The file cannot be deleted because it is still in use at the following locations [record:tt_content:7947], [record:tt_content:8007]”

This is not an easy task for the editor to handle, especially since a normal editor seems not to be allowed to search for tt_content elements by the given uids.

The easiest solution is probably to enhance the error message by linking straight to the referenced elements, so an editor can just one-click edit them in case.

Greetings,
Manuel

Author SICOR KDL GmbH
Created 02/08/24, 12:32
Updated 09/24/26, 09:34
Bug
New Quiet FormEngine aka TCEforms TYPO3 CMS 14

#110766 InlineControlContainer: initialization race condition (regression of #106371)

Since #109215 (039ba0f62c, “Convert InlineControlContainer to web component”) the <typo3-formengine-container-inline> element resolves its records container once in connectedCallback():

this.recordsContainer = this.querySelector(selector`[id="${this.id}_records"]`);

The previous await DocumentService.ready() was removed with the reasoning that “connectedCallback already guarantees DOM presence”. That only holds for the element itself, not for its children. Backend modules are loaded as <script type="module" async>, so on slow or streamed responses the element can be upgraded while the parser has not yet reached the _records container. recordsContainer then stays null for the lifetime of the element.

This is exactly the case #106371 (38e558813a) fixed in 12.4/13.4/main for files-control-container.ts (“we must never assume that DOM is fully loaded in connectedCallback”). Since #109226 file references use InlineControlContainer, so that fix no longer applies to file fields.

Symptoms

Production only, intermittent, never on a local DDEV setup:

  • Adding an image to a file field (e.g. Text & Media) via the element browser: TypeError: Cannot read properties of null (reading 'insertAdjacentHTML') at createRecord()
  • With appearance.useSortable = true already on load: TypeError: Cannot read properties of null (reading 'getAttribute') in registerEvents()

How to reproduce

Serve a FormEngine form whose HTML is flushed in two chunks with a delay between the opening <typo3-formengine-container-inline> tag and its _records child, or throttle the network in DevTools. Minimal standalone repro: a custom element defined by an async module script, queried children in connectedCallback(), HTML streamed with a 1 s pause. The child is null in 3/3 runs (headless Chrome).

Suggested fix

Restore the wait before querying children, as done in #106371:

public async connectedCallback(): Promise<void> {
  await DocumentService.ready();
  this.ajaxDispatcher = new AjaxDispatcher(this.objectGroup);
  this.recordsContainer = <HTMLDivElement>this.querySelector(selector`[id="${this.id}_records"]`);
  this.registerEvents();
}

Workaround / patch

The attached patch (typo3-backend-inline-control-container-race.patch) was created with the help of Claude (AI assistant), modeled on the approach of #106371. It applies to the compiled JavaScript of typo3/cms-backend 14.3.7 (applied via cweagans/composer-patches). Instead of an unconditional DocumentService.ready(), it defers the initialization to DOMContentLoaded only if the document is still loading and the _records container is not yet present; otherwise the behaviour is unchanged.

Verified on our production system (14.3.7): with the patch applied, the error no longer occurs.

Related: #106371, #102550, #109215, #109226

Author Markus A
Created 09/23/26, 09:42
Updated 09/23/26, 09:42
Bug
New Quiet TypoScript TYPO3 CMS 13

#109291 TypoScript of parent sys_templates is parsed although a sys_template has set "Clear" for setup

In my rootpage UID 1 I have a sys_template which has set “Clear” clear (for constants and setup) and “Rootlevel” root=true.
In this rootpage I have:
– in constants import ‘EXT:femanager/Configuration/TypoScript/Main/constants.typoscript’@ which contains the constant definition plugin.tx_femanager.settings.bootstrapCSS = 0
– in setup import ‘EXT:femanager/Configuration/TypoScript/Main/setup.typoscript’@ which contains the condition [0 < {$plugin.tx_femanager.settings.bootstrapCSS}]

Requesting the rootpage works without issues.

In a page UID 10 which is a subpage of UID 1 I have a sys_template which has also set “Clear” clear (for constants and setup) and “Rootlevel” root=true.

When I open “Included TypoScript” in the backend module on this subpage I see both definitions of the templates with Root and Clear:

When I open “Active TypoScript” in the backend module on this subpage I see in the setup section that the condition has $plugin.tx_femanager.settings.bootstrapCSS in white (instead of red like another constant $page.theme.cookieconsent.enable which is defined in the subpage-sys_template:

So apparently the “Clear” for constants on the subpage sys_template leads to the plugin.tx_femanager constants not being available.

So far so good, but requesting this page in the frontend adds the following message to the TYPO3 log:

Thu, 19 Mar 2026 12:48:06 +0100 [ERROR] request="f05913b46496b" 
component="TYPO3.CMS.Core.TypoScript.IncludeTree.Visitor.IncludeTreeConditionMatcherVisitor": 
TypoScript condition [0 < {$plugin.tx_femanager.settings.bootstrapCSS}] could not be parsed: 
Unexpected character "$" around position 5 for expression `0 < {$plugin.tx_femanager.settings.bootstrapCSS}`.- 
SyntaxError: Unexpected character "$" around position 5 for expression `0 < {$plugin.tx_femanager.settings.bootstrapCSS}`., 
in file /vendor/symfony/expression-language/Lexer.php:97

When parsing the typoscript for the frontend request the typoscript setup of the rootpage sys_template is parsed although “Clear” (for constants and setup) and “Rootlevel” are set to true on the subpage sys_template.

When I remove the “Clear” for constants on the subpage sys_template no more messages are added to the TYPO3 log.

I would have expected when “Clear” (for setup) on a subpage sys_template is set that the frontend request would completely ignore and not even parse the typoscript on all levels above.

Author Stephan Großberndt
Created 03/19/26, 12:47
Updated 09/23/26, 08:36
Bug
Author Simon Schaufelberger
Assigned to Simon Schaufelberger
Created 09/16/26, 20:36
Updated 09/22/26, 20:17
Task
Under Review Quiet TYPO3 CMS 15

#110389 Migrate labels to new domain syntax

Author Simon Schaufelberger
Assigned to Simon Schaufelberger
Created 08/06/26, 20:27
Updated 09/22/26, 15:10
Feature
Under Review Stale Backend User Interface

#97259 Add option to pass additionalFields to PageTreeRepository, when building the tree

Using the Hook $GLOBALS[‘TYPO3_CONF_VARS’][‘SC_OPTIONS’][\TYPO3\CMS\Core\Imaging\IconFactory::class][‘overrideIconOverlay’] it is possible to modify the overlay-icon for icons created with the IconFactory class. But it is not possible to add custom overlays based on new fields (pages table) for the page-tree because the row will never contain the fields you added.

The PageTreeRepository can receive additional fields to select in the constructor but the TreeController does pass a hard-coded empty array.

The hook to midify the icon overlay:
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/Imaging/IconFactory.php#L361

Called here:
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/backend/Classes/Controller/Page/TreeController.php#L370

PageTreeRepository instantiation responsible for loading the page record:
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/backend/Classes/Controller/Page/TreeController.php#L486

Query created by repository:
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/backend/Classes/Tree/Repository/PageTreeRepository.php#L520

What i want to achieve:

I simply added a field to the pages table to disable robots (recursive) for the page and all sub-pages. To show the setting to a logged in backend-user i want to display a overlay ontop of that page. Something like a stop-sign. At the moment there is no safe way (besides XClassing or firing a second query to fetch the new field inside the hook) of adding such a feature.

By adding a configuration like $GLOBALS[‘TYPO3_CONF_VARS’][‘BE’][‘pageTreeAdditionalFields’] and merging that field additionally inside the PageTreeRepository, this could be enhanced very easily.

Author Philipp Wrann
Created 03/30/22, 14:01
Updated 09/20/26, 05:46
Feature
Under Review Stale Backend API

#110434 PSR-14 event to add content around the record edit form

The page module provides `ModifyPageLayoutContentEvent` to render additional content above and below the module body. The record list provides `RenderAdditionalContentToRecordListEvent` for the same purpose. There is no equivalent for the record edit form rendered by `EditDocumentController`.

`EditDocumentController` already dispatches three events (`BeforeFormEnginePageInitializedEvent`, `AfterFormEnginePageInitializedEvent`, `AfterRecordOpenedEvent`), but none of them allows rendering markup around the form. Extensions therefore fall back to a middleware that rewrites the response body, which is fragile and breaks on markup changes.

Use case: EXT:xima_typo3_content_planner shows an editorial status bar above the edit form. It currently does this via a response-manipulating middleware, while the same information is rendered through the proper event API in the page module and the record list.

https://docs.typo3.org/p/xima/xima-typo3-content-planner/main/en-us/Usage/StatusChange.html#edit-form

Proposal: a new PSR-14 event, e.g. `ModifyEditDocumentContentEvent`, dispatched in `EditDocumentController::mainAction()` right before the body is assigned to the view. Scope intentionally narrow, mirroring `ModifyPageLayoutContentEvent`:

- header content, rendered above the form
- footer content, rendered below the form
- read access to the request and the `ModuleTemplate`

No interference with FormEngine internals, no access to the form result.

I am willing to provide the patch.

Author Konrad Michalik
Created 08/11/26, 10:17
Updated 09/17/26, 14:47
Feature
Under Review Stale Backend API

#110435 PSR-14 event to render additional content in the filelist module

`RenderAdditionalContentToRecordListEvent` allows extensions to render content above and below the record list. The filelist module has no equivalent. `FileListController` does not dispatch any event at all and has no `EventDispatcherInterface` injected.

This is an inconsistency rather than a missing feature in one specific place: the page module, the record list and (with the proposal in #110434 ) the edit form all offer a way to contribute content, the file module does not. Extensions that decorate backend modules consistently have to special case the filelist and fall back to response manipulation.

Use case: EXT:xima_typo3_content_planner renders editorial status information in the page module, the record list and the edit form. For the filelist it uses a middleware for that single case.

https://docs.typo3.org/p/xima/xima-typo3-content-planner/main/en-us/Usage/StatusChange.html#record-list

Proposal: `RenderAdditionalContentToFileListEvent`, modelled directly on `RenderAdditionalContentToRecordListEvent` (`getAdditionalContentAbove()` / `setAdditionalContentAbove()`, same for below), dispatched in `FileListController::processRequest()` and assigned to the template as `additionalContentTop` / `additionalContentBottom`.

Open question for the patch: `FileListController` has a second, earlier return in `handleRequest()` for the case where the folder object is null (invalid request or missing permissions). Whether the event should fire there as well is a design decision, dispatching only in `processRequest()` is the simpler option.

I am willing to provide the patch.

Author Konrad Michalik
Created 08/11/26, 10:18
Updated 09/17/26, 14:47
Task
New Stale File Abstraction Layer (FAL) TYPO3 CMS 14

#87528 VimeoHelper/AbstractOEmbedHelper must send Referer Header to fetch proper oEmbed.json for videos with restricted embedding.

VideoHelper uses an oEmbed request, as documented here: https://developer.vimeo.com/api/oembed/videos

curl 'https://vimeo.com/api/oembed.json?width=2048&url=https%3A%2F%2Fvimeo.com%2F123456789' | python -m json.tool
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   387  100   387    0     0   1646      0 --:--:-- --:--:-- --:--:--  1646
{
    "domain_status_code": 403,
    "height": 1152,
    "html": "<iframe src=\"https://player.vimeo.com/video/123456789?app_id=122963\" width=\"2048\" height=\"1152\" frameborder=\"0\" allow=\"autoplay; fullscreen\" allowfullscreen></iframe>",
    "provider_name": "Vimeo",
    "provider_url": "https://vimeo.com/",
    "type": "video",
    "uri": "/videos/123456789",
    "version": "1.0",
    "video_id": 123456789,
    "width": 2048
}

Note:
Due to privacy reasons, the video ID was replaced by 123456789.
To test this, create a Vimeo video, set the privacy settings to “Who can watch?” to “Anyone” and “Where can this be embedded?” to “Specific domains” and choose your domain.

The API docs (https://developer.vimeo.com/api/oembed/videos) state the following:

NOTE: In the case of a video with domain-level privacy, 
the oEmbed request returns a simplified response containing the embed code only and no private metadata. 
To get the complete response, send the Referer header along with the request, 
and set its value to the video's whitelisted domain.

This is the case here. As you see, the JSON response contains no title.

When adding the video in the TYPO3 filelist, it will be successfully saved as “.vimeo” ($oEmbed['title'] . '.' . $fileExtension in \TYPO3\CMS\Core\Resource\OnlineMedia\Helpers\AbstractOEmbedHelper::transformMediaIdToFile):

            if (!empty($oEmbed)) {
                $fileName = $oEmbed['title'] . '.' . $fileExtension;
            } else {
                $fileName = $mediaId . '.' . $fileExtension;
            }

Actually, $oEmbed['title'] is undefined (!isset()) here, but the script only checks if $oEmbed is empty, which is insufficient. (This is a bug on its own!)

Following, a success flash message is shown, but the file will not be visible because of the default filterHiddenFilesAndFolders filter defined in defaultFilterCallbacks.
When trying to create the vimeo file once more, \TYPO3\CMS\Core\Resource\OnlineMedia\Helpers\AbstractOnlineMediaHelper::findExistingFileByOnlineMediaId() will find the existing file, but not tell the user about it.
So again a green success flash message is shown. (This is another bug. The user should be informed that this video exists already in the folder.)

The actual solution, however, would be to send a referer header with the hostname, like:

curl 'https://vimeo.com/api/oembed.json?width=2048&url=https%3A%2F%2Fvimeo.com%2F123456789' -H 'Referer: https://example.com' | python -m json.tool 
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   950  100   950    0     0   4166      0 --:--:-- --:--:-- --:--:--  4166
{
    "account_type": "pro",
    "author_name": "Redacted",
    "author_url": "https://vimeo.com/redacted",
    "description": "",
    "domain_status_code": 200,
    "duration": 235,
    "height": 1152,
    "html": "<iframe src=\"https://player.vimeo.com/video/123456789?app_id=122963\" width=\"2048\" height=\"1152\" frameborder=\"0\" title=\"Redacted video title\" allow=\"autoplay; fullscreen\" allowfullscreen></iframe>",
    "is_plus": "0",
    "provider_name": "Vimeo",
    "provider_url": "https://vimeo.com/",
    "thumbnail_height": 540,
    "thumbnail_url": "https://i.vimeocdn.com/video/redacted_960.jpg",
    "thumbnail_url_with_play_button": "https://i.vimeocdn.com/filter/overlay?src0=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2Fredacted_960.jpg&src1=http%3A%2F%2Ff.vimeocdn.com%2Fp%2Fimages%2Fcrawler_play.png",
    "thumbnail_width": 960,
    "title": "Redacted video title",
    "type": "video",
    "upload_date": "2019-01-01 00:00:00",
    "uri": "/videos/123456789",
    "version": "1.0",
    "video_id": 123456789,
    "width": 2048
}

You can see the full response being sent due to the -H 'Referer: https://example.com' header. (For testing, use the hostname you applied as embed restriction in the vimeo privacy settings.)

Only now is a title sent, and $oEmbed['title'] . '.' . $fileExtension no longer results in .vimeo but, in this example case, in Redacted video title.vimeo.

A little gotcha:
Unfortunately the filelist module does not “know” which of the TYPO3 installation’s possibly many domain records match the video’s privacy restrictions.
Therefore, TYPO3 would have no choice but to try sys_domain records until the oEmbed request returns a video title.
Meaning: If only one of multiple sites within a TYPO3 installation is whitelisted for the video, then the video can be added.
Otherwise you might want to let the request fail or succeed with a warning to the user (using the video ID as filename and remaining unable to set a preview image (thumbnail).

Target:
Same in TYPO3 8 and 9.

Author Leonie Philine
Created 01/23/19, 19:31
Updated 09/17/26, 12:55
Feature
New Stale Backend API

#110720 Add the possibility to restrict TCA overwrites

Current situation

TYPO3’s main configuration API is TCA. The configuration could be set via
@EXT:<my_extension>/Configuration/TCA/<mytable>.php@</mytable></my_extension>

and could be modified via
- BeforeTcaOverridesEvent
- EXT:<my_extension>/Configuration/TCA/Overrides/<any_table>.php
- AfterTcaCompilationEvent

Any value set in the initial TCA configuration could be modified.
The collection of all TCA related configuration is done via TcaFactory .
In BootService the TCA configuration is handed to the TcaSchemaFactory .
The TcaSchemaFactory saves the `TCA` configuration and has no public API to modify, as the methods load and rebuild are internal.
Therewith, further modifications of $GLOBALS['TCA'] should never change the configuration provided by the TcaSchema.

Problem

Neither the TYPO3 core nor third-party extensions have an option to ensure that a TCA configuration set in EXT:<my_extension>/Configuration/TCA/<mytable>.php will not be modified, even if it is necessary to leave it unchanged.

Suggested feature

Provide the following two configuration options, which can only be set in EXT:<my_extension>/Configuration/TCA/<mytable>.php:

a) denyOverwrites (bool), default false

Denies any overwrites for a specific column configuration via any TCA overwrite.

Example:

EXT:<my_extension>/Configuration/TCA/<mytable>.php
    return [
        'columns' => [
            '<mycolumn>' => [
                'denyOverwrites' => true
                'label' => 'Config must not be changed',
                'config' => [
                    'type' => 'input'
                ]
            ]
        ]
    ];

Any configuration changing this column, like in EXT:<my_extension>/Configuration/TCA/Overrides/<any_table>.php, will not apply.
Furthermore, any change in columnOverwrides for this column will be removed as well.

The following configuration will not change the resulting TCA:
Example:

`EXT:<my_extension>/Configuration/TCA/Overrides/<any_table>.php`
    $GLOBALS['TCA']['<mytable>']['columns']['<mycolumn>']['config']['eval'] = 'trim';

    $GLOBALS['TCA']['<mytable>']['<mytype>']['columnOverrides']['<mycolumn>']['config']['eval'] = 'trim';

Changes via overwrideChildTca remain possible.

b) protectConfigOptions (array), default []

Denies overwrites for a specific list of TCA configuration keys of one column.
Every configuration key in <mycolumn> or <mycolumn> config in this list will be removed.</mycolumn></mycolumn>

Example:

EXT:<my_extension>/Configuration/TCA/<mytable>.php`
    return [
        'columns' => [
            '<mycolumn>' => [
                'protectConfigOptions' => ['type', 'displayCond']
                'displayCond' => 'HIDE_FOR_NON_ADMINS',
                'label' => 'Config must not be changed',
                'config' => [
                    'type' => 'input'
                ]
            ]
        ]
    ];

Results on TCA overwrites:

Example:

EXT:<my_extension>/Configuration/TCA/Overrides/<any_table>.php`
    // TCA modifications will apply
    $GLOBALS['TCA']['<mytable>']['columns']['<mycolumn>']['config']['eval'] = 'trim';

    // TCA modifications will not apply 
    $GLOBALS['TCA']['<mytable>']['columns']['<mycolumn>']['displayCond'] = 'REC:NEW:false';
    $GLOBALS['TCA']['<mytable>']['<mytype>']['columnOverrides']['<mycolumn>']['config']['type'] = 'select';

Benefits

The TYPO3 core and extensions could define TCA configurations, which must stay unchanged to ensure a working and secret environment. This also documents, which parts of the TCA are public API and could be changed.

Implementation

- Collecting denyOverwrites and protectConfigOptions from EXT:<my_extension>/Configuration/TCA in TcaFactory .
- Calculate the difference of every TCA modification.
- Remove protected modifications before applying the TCA overwrites
- Remove denyOverwrites and protectConfigOptions from TCA.

Performance considerations

As the result of TcaFactory is cached, only the first not cached hit will have more execution time. Due to the removal of the new introduced configuration options, no further RAM has been used after caching.
Possible refactoring after the introduction of this feature will increase runtime performance.

Example usages of this feature in the TYPO3 core

Short-term

a) core/Classes/Hooks/PagesTsConfigGuard.php
This hook ensures that only admins are allowed changing TSconfig in pages.
Ensuring that the configuration 'displayCond' => 'HIDE_FOR_NON_ADMINS'
stay unchanged will allow dropping this hook.

b) DataHandler->checkValueForPassword
A special condition ensures that passwords of fe_users and be_users are always hased.
Ensuring that the configuration 'hashed' => true stays unchanged will allow to dropping this special condition.

Mid-term

The page permissions could not be set (except for editlock ) via the usual page edit or creation using the EditDocumentController .
Changing page permissions always needs a context change to another module.
Adding the permissions as typical TCA types will allow streamlining the editing process for admins, streamlining data flow in DataHandler . This also requires a way to keep certain new TCA configurations unchanged.

Author Daniel Windloff
Assigned to Daniel Windloff
Created 09/16/26, 10:53
Updated 09/16/26, 10:53
Task
New Stale CLI TYPO3 CMS 14

#110021 Running fluid:analyse im CI pipeline

Right now, if I try to run fluid:analyse in my GitLab CI pipeline, I get a database connection error. I guess it is due to some dependency to database caches. It would be cool to have this command in pipelines, without having to bootstrap a whole TYPO3 instance just for fluid template analysis.

Author Nikita Hovratov
Created 06/08/26, 14:41
Updated 09/15/26, 11:07
Feature
New Stale Backend User Interface

#110709 Edit Lock should provide feedback to editors

As a user I want to have visual feedback, why edit is not possible. If editlock is set, you receive generic feedback, that permission are insufficient.

Sugeestion: Show a flash message in page module, if a page is locked

Author Stefan Busemann
Created 09/15/26, 09:19
Updated 09/15/26, 09:19
Bug
Needs Feedback Stale Backend JavaScript TYPO3 CMS 13

#107888 TCA onChange does not work sometimes.

Example field:

‘art’ => [
‘exclude’ => true,
‘onChange’ => ‘reload’,
‘label’ => ‘Pack Type’,
‘config’ => [
‘type’ => ‘select’,
‘renderType’ => ‘selectCheckBox’,
‘foreign_table’ => ‘tx_myextension_domain_model_art’,
‘minitems’ => 1,
],
],

When all options are not checked, the form will be reloaded and the record will be saved with this field empty. This is not good
After that when one option is selected, the form will not be reloaded.

Author bingquan bao
Created 10/28/25, 14:13
Updated 09/14/26, 21:10
Bug
Under Review Quiet TYPO3 CMS 14

#108394 Localized records no longer shown in Records module on pid=0

It seems like records listed in the Records module are no longer displayed if they have a language uid != 0 associated. This is different to TYPO3 v13.4; here, records in all languages are displayed.

For reproduction, create a new record (e.g. page) with pid=0 and a language uid != 0. The record should be available when inspected in the Records module, but it currently isn’t.

Author Elias Häußler
Created 12/03/25, 21:49
Updated 10/01/26, 14:06
Bug
Under Review Stale Localization TYPO3 CMS 14

#110199 PageLinkBuilder does not language-map numeric section fragments (t3://page?uid=X#<tt_content_uid>) to translated tt_content UID

When linking to a content element via the TYPO3 link browser (e.g. t3://page?uid=37#422), TYPO3 generates a frontend URL fragment using the default-language content UID (#c422) even in a translated language context where the translated content element exists (e.g. EN translation is UID 616, expected fragment #c616).

This causes links on translated pages to point to the wrong anchor.

Author M S
Created 07/15/26, 10:21
Updated 09/02/26, 21:10
Task
Under Review Stale Database API (Doctrine DBAL) TYPO3 CMS 15

#110430 Remove SchemaMigrator::install()

SchemaMigrator::install() only survived the analyzer rework because typo3/testing-framework creates the database of every functional test through it. It does nothing but delegate to applySafe() and flatten the result into a table name to error message map.

The testing framework calls applySafe() when the migrator offers it and keeps install() as a fallback, guarded by a capability check so it still works against v14. That leaves the wrapper in core without a consumer, and it is removed. The two core tests that still went through it apply their statements with the applySafeChanges() helper instead.

Breaking, with a Breaking changelog and the exclamation mark flag on the commit; the changelog of sub-task 9 is corrected accordingly, because it still announced install() as deprecated rather than removed.

No merge blocker

The change that adds the capability check – TYPO3/testing-framework pull request 739 – is merged, and typo3/testing-framework is raised to a state that contains it: composer.lock resolves dev-main of the upstream repository at commit 6cd6802. Nothing points at a fork any more, and no release has to be waited for.

A capability check rather than a version check is deliberate: v15 nightlies and every v15 dev state before this series report v15 while only carrying install().

Patch

Gerrit 95195, topic database-analyzer.

Releases: main

Author Stefan Bürk
Assigned to Stefan Bürk
Created 08/11/26, 01:25
Updated 09/02/26, 13:16
Feature
Under Review Stale Extbase

#75358 Synchronize Inline Relations pid field when aggregate pid has been changed

I recognized, that if you change a pid via extbase persistence the child records related inline are not adjusted as well.

So if you work with different groups for pagetrees and you move one record from Tree A to Tree B the users wont be able to edit the record because the child record is not moved along with the aggregate.

This works via FormEngine but not Extbase and should IMO have the same behaviour.

There are 2 possible Solutions:
1) Provide a Utility to adjust the pid, so developers would have to implement the feature manually
2) Synchronize all pids when persisting an aggregate object, maybe introduce some configuration to disable this (config.tx_extbase.persistence.classes.ENTITY.keepChildrenAtPartentPid)

Author Philipp Wrann
Created 04/01/16, 12:04
Updated 09/02/26, 04:53
Bug
Accepted Stale TypoScript TYPO3 CMS 14

#108719 Single TypoScript value can't be if a site + TS record i

Only on 14.x

  1. Given is a page with a site set + a TypoScript record.
  2. Switch to TypoScript > Active TypoScript
  3. Select a value and press update

=> exception “No template on page found”

Author Georg Ringer
Created 01/21/26, 19:56
Updated 08/28/26, 20:22
Feature
New Stale Backend User Interface

#97277 Clipboard: eliminate the distinction between single and multiple selection

It’s hard for an editor to understand the actual concept of “single record mode” and “multi-selection” clipboard.
Even when understood, the concept is pretty confusing IMHO.

I propose to move to a more common concept “choose the record(s) and then make the action”.

At the moment, this is the concept behind the “single record mode” but this lacks the possibility to select multiple records.

On the other hand, the “multi-selection” mode allows to select multiple records but the concept of “annotating” (because you’re not really transferring) these selected records in a virtual container (the clipboard) and then moving or copying them is difficult for most users to grasp. This current concept of “multi-selection” has some advantages, but I have rarely found them useful.

Instead, I propose to keep the multiple records selection of TYPO3 v11 but to eliminate the “transfer to clipboard” step in favor of a more direct and known “cut/copy and then paste”.

Author Christian Toffolo
Created 03/31/22, 18:13
Updated 08/28/26, 13:05
Bug
New Stale Workspaces TYPO3 CMS 13

#110528 Duplicate translation of same content element hidden without error

When a duplicate translation is created, one in LIVE and one in a WORKSPACE, for the same content elemen, TYPO3 silently hides one of them without any warning. The user creating the translation in LIVE has no way of knowing that a translation for the same element already exists in a workspace somewhere, since there is no cross-context visibility. This can lead to confusion, as the workspace translation appears to have no effect even when activated, with no indication as to why.

Here are the steps :

  • In LIVE, create a text block
  • In the WORKSPACE, create a translation for this block
  • Back in LIVE, create a translation
  • Once done, when returning to the workspace, you will see 2 translations for the same block. Only the LIVE translation is displayed (in our case, we believe it was hidden), even when activating the workspace one.
  • There is no error message explaining that our translation is a duplicate and that it will remain hidden.
Author Pierre Boivin
Created 08/24/26, 13:33
Updated 08/24/26, 13:33
Task
Under Review Stale TYPO3 CMS 15

#110519 Improve Symfony Messenger queue lookup performance

The sys_messenger_messages table currently has separate indexes for queue_name, available_at, and delivered_at. Symfony Messenger’s dequeue query filters and orders using these
columns together with id, so the individual indexes cannot efficiently cover the complete query.

Replace the three indexes with a composite index on:

(queue_name, available_at, delivered_at, id)

Benefits:

- Matches Symfony Doctrine Transport’s queue lookup pattern
- Avoids unnecessary row scans and temporary sorting
- Reduces index storage and write maintenance from three indexes to one
- Improves a synthetic 100,000-row query from approximately 1.479 ms to 0.004 ms (~369× faster)

Author Wouter Wolters
Assigned to Wouter Wolters
Created 08/21/26, 21:20
Updated 08/21/26, 21:21
Bug
Accepted Stale Link Handling & Redirect Handling TYPO3 CMS 13

#109199 Not possible to create redirects as non-admin user if no access to site root page

Reproduce

1. Create Backend user which has no access to the root page of a site (e.g. give editor DB mount to subpage)
2. With this Backend user, change the slug

result: The following error message appears:

> Attempt to insert record on pages:815 where table “sys_redirect” is not allowed

Analysis

Looks like a regression which was introduced by using DataHandler in sys_redirect: SlugService::createRedirects

It can be reproduced with latest commit 5f0a657f21fffafca697284a4176089f28fe85a0 in 13.4 branch

It is not reproducible with commit cbaa94d8962ec9014d736b041880a5be112b5621 where DataHandler is not yet used.

Versions

  • first reproduced in v13 but probably also occurs in v14

Log message

Tue, 10 Mar 2026 10:05:18 +0100 [ERROR] request="31faef49b52bc" component="TYPO3.CMS.Redirects.Service.SlugService": 
Could not create redirect record for source "site13.de/icbm/umweltbiochemie/forschung/tmap" - {"host":"site13.de","path":"/icbm/umweltbiochemie/forschung/tmap","persistedUid":null,"errorLog":["[1.1]: 
Attempt to insert record on pages:3 where table \"sys_redirect\" is not allowed"],"url":"https://site13.de/typo3/record/edit?token=77d886a527cfbfc0f2288ec6e6a507547fd5bae3&returnUrl=%2Ftypo3%2Fmodule%2Fweb%2Flayout%3Ftoken%3Db41757ee6cefde62123b4f1b8f2c767d2c9ea488%26id%3D15141&edit%5Bpages%5D%5B15141%5D=edit"}

Possible workaround

When overriding pages TCA, it is possible to add redirects:

$GLOBALS['TCA']['pages']['ctrl']['security']['ignoreWebMountRestriction'] = true;
Author Sybille Peters
Created 03/10/26, 10:52
Updated 08/20/26, 12:49
Bug
Under Review Stale WebHooks - Incoming = Reactions + Outgoing TYPO3 CMS 13

#105005 Webhooks Exception if invalid JSON in database field additional_headers

Given the following data in sys_webhook an exception is thrown upon opening the webhooks backend module:

| uid | pid | updatedon  | createdon  | deleted | disabled | starttime | endtime | description | name       | url                                     | method | secret                                                                                            | webhook_type                               | identifier                           | verify_ssl | additional_headers |

|   4 |   0 | 1707312708 | 1707312708 |       0 |        0 |         0 |       0 |             |            |                                         | POST   |                                                                                                   | typo3/redirect-was-hit                     | 012207ce-c08b-4c67-9455-1e233efbe87d |          1 | Array              |

(1/2) Doctrine\DBAL\Types\Exception\ValueNotConvertible
Could not convert database value to "json" as an error was triggered by the unserialization: Syntax error

in /var/www/html/TYPO3.CMS/vendor/doctrine/dbal/src/Types/Exception/ValueNotConvertible.php line 42
Author Benjamin Franzke
Assigned to Stefan Bürk
Created 09/17/24, 12:34
Updated 08/15/26, 23:17

Showing results 651 to 675 of 1561