Showing results 626 to 650 of 1561

Feature
Under Review Quiet Form Framework

#109835 Form configuration translation using domain-based labels

All form YAML configuration files should use the domain-based translation syntax instead of naked translation keys.
This aligns form more with the core (e.g. TCA).
The configuration option “translationFiles” should be removed.

Note: The frontend translation handling should be untouched.

Author Josua Vogel
Assigned to Josua Vogel
Created 05/15/26, 06:37
Updated 10/12/26, 20:38
Bug
New Quiet Backend User Interface TYPO3 CMS 14

#108436 Improve error messages when a record cannot be saved

We should adjust these texts, they can happen to regular users when they try to save a record that was misconfigured or whatever:
Attempt to insert record on pages:42 where table “tx_myextension_domain_model_something” is not allowed.
And if feels like they are slapped on the finger…

Author Lina Wolf
Assigned to Lina Wolf
Created 12/09/25, 12:37
Updated 10/12/26, 19:46
Bug
Under Review Quiet Caching TYPO3 CMS 14

#110937 Page cache lock is released before the page cache entry is persisted, so waiting requests re-render the page

On a page cache miss, PrepareTypoScriptFrontendRendering acquires the exclusive pages lock, so concurrent requests for the same page wait instead of rendering in parallel. After waiting, a request re-reads the page cache and only renders if there is still no entry.

The lock is released in the finally block of PrepareTypoScriptFrontendRendering::process() (line 274) as soon as the inner middleware stack has returned. The page cache entry, however, is not written there: RequestHandler only enqueues it via $cacheDataCollector->enqueueCacheEntry() (line 206), and the outer middleware CacheDataCollectorAttribute persists it after $handler->handle() has returned (line 70 ff.).

So there is a window between “lock released” and “cache entry written”. A waiting request that obtains the lock in this window does not find a cache entry and renders the page itself — again holding the lock. The other waiting requests keep queueing behind it. Depending on timing, a burst of concurrent requests on an expired page turns into a chain of sequential full renderings instead of one.

Steps to reproduce:

1. Frontend page with a noticeable rendering time (several seconds), cached, short lifetime.
2. Wait until the page cache entry has expired (or flush the page cache).
3. Send 10 concurrent identical requests for that page, e.g.:
seq 10 | xargs -P10 -I{} curl -s -o /dev/null -w "%{time_total}\n" https://example.org/page/
4. With config.debug = 1, check the X-TYPO3-Debug-Cache header of each response.

Expected result:

One request renders the page; the other nine wait for the lock and are then served from the page cache entry written by the first one. Response times are roughly “rendering time” for all ten.

Actual result (measured on a staging system, TYPO3 14.3.7):

- 5 of 10 responses have no X-TYPO3-Debug-Cache header, i.e. rendered themselves, with response times 12.1 s / 14.3 s / 17.8 s / 20.1 s / 23.5 s – strictly increasing, i.e. sequential renderings under the lock.
- The other 5 were served from the cache, but from two different entries (different Expires values), i.e. the page was written to the cache more than once.
- With a warm cache, the same 10 concurrent requests take 1.7–2.2 s each.

Impact:

On a busy or attacked site, every expiry of a frequently requested page can block several PHP workers in a row for the full rendering time. We ran into this while hardening a site after an outage caused by a scanner (originally via no_cache=1, which renders under the same lock on every request).

Possible fix:

Persist the page cache entry before the pages lock is released, e.g. write the tsfe-page-cache entry directly in RequestHandler/@PrepareTypoScriptFrontendRendering@ instead of deferring it to CacheDataCollectorAttribute, or release the lock only after the deferred cache entries have been persisted.

Author Christian Huppert
Assigned to Wolfgang Klinger
Created 10/06/26, 17:54
Updated 10/09/26, 12:41
Bug
New Quiet Workspaces TYPO3 CMS 13

#110947 Send to stage modal is empty when workspace preview is opened inside the "View" module

Problem/Description
—————————-
When the workspace split preview (route `workspace_previewcontrols`) is rendered
inside the backend “View” module (Web > View), clicking “Send to stage …” opens a
modal with an empty body (no “Comments” textarea). “OK” does nothing, only
“Cancel” works. The console shows:

Uncaught TypeError: can’t access property “querySelectorAll”, r is null
convertFormToObject typo3/backend/utility.js
renderSendPageToStageWindow
typo3/workspaces/preview.js
_buttonClick @typo3/backend/modal.js

When the same preview is opened standalone in its own browser tab, the dialog
renders correctly and works.

The AJAX response of `sendPageToNextStage` is correct (contains `comments`,
`affects`, `stageId`), so this is a client-side issue only.

Steps to reproduce
—————————
1. Create a workspace (default stages are sufficient) and switch to it.
2. Reload the backend. Do NOT open the “Workspaces” module.
3. Modify a content element on a page.
4. Open that page in the “View” module. The workspace preview with the
“Send to stage” button is shown inside the module.
5. Click “Send to stage “Ready to publish”“.

Expected: Modal with “Comments” textarea, “OK” sends the records to the stage.
Actual: Empty modal, “OK” throws the TypeError above.

Root cause
—————
- backend.ts (Workspaces module) registers the form element in the top frame:
topLevelModuleImport(‘@typo3/workspaces/renderable/send-to-stage-form.js’);
- preview.ts only imports it locally:
import ‘@typo3/workspaces/renderable/send-to-stage-form’;
so <typo3-workspaces-send-to-stage-form> is defined only in the<br> CustomElementRegistry of the preview iframe.<br>- @typo3/backend/modal.js delegates to parent.window.TYPO3.Modal /<br> top.TYPO3.Modal, so the modal is rendered in the top backend document.<br>- Workspaces::renderSendToStageWindow() (workspaces.ts) creates the element via<br> currentModal.ownerDocument.createElement(…), i.e. in the top document, where<br> it is not defined. The element is never upgraded and renders nothing,<br> currentModal.querySelector(‘form’) returns null and convertFormToObject() fails.</typo3-workspaces-send-to-stage-form>

When the preview runs in its own tab, the top window is the preview window itself,
so the element is defined and the dialog works. If the Workspaces module was
opened earlier in the same backend session, the element should already be defined
in the top frame, which would make the bug appear intermittent.

The relevant code is identical in 13.4 and main
(Build/Sources/TypeScript/workspaces/preview.ts, backend.ts, workspaces.ts).

Possible fix
——————
Add the same top level import to preview.ts as in backend.ts:

import { topLevelModuleImport } from ‘@typo3/backend/utility/top-level-module-import’;
…
topLevelModuleImport(‘@typo3/workspaces/renderable/send-to-stage-form.js’);

Environment
—————-
TYPO3 13.4.30 and 13.4.35, composer mode, PHP 8.3.
Reproduced in Firefox, Chrome and Edge.

Author m s
Created 10/07/26, 08:16
Updated 10/07/26, 08:16
Bug
Needs Feedback Quiet TYPO3 CMS 9

#83733 FlashMessage renderers must not escape user content

With https://forge.typo3.org/issues/78477, the flash message handling unfortunatey became worse compared to 7.6 because it tried to do things the right way but it didn’t have real life projects in mind.

These are the changes I struggle with a lot:

  • The FlashMessageRendererResolver resolves the Renderer by some hardcoded conditions. Backend, Frontend and CLI-Context. This is not only very breaking because the default rendering was the Bootstrap-Rendering in 7.6, it also takes away the possibility to configure the renderer. It’s a slap in the face when migrating templates to 8.7.
  • Due to security reasons, the renderers escape all output-, but the FlashMessageViewHelper is still configure to not escape its output-. This takes the option from me of not escaping stuff for single flash messages in case I need to. This has to change. Renderers must not htmlspecialchar and let the template engine user decide. I understand that we do not want to open the doors for XSS by default (and we can do so by using sane defaults for the renderer configuration letting the flashmessage viewhelper escape by default, which can then be overridden) but there are cases, and it’s many, where you want to disable escaping in flash messages.
Author Alexander Schnitzler
Created 01/30/18, 16:33
Updated 10/07/26, 06:45
Feature
New Quiet Backend User Interface

#99104 pasting records into a TCA TYPO3 group field doesn't work

This TCA-Definition:

        'related' => [
            'label' => 'LLL:EXT:bwmediathekasset/locallang_db.xml:tx_bwmediathekasset_item.related',
            'config' => [
                'type' => 'group',
                'internal_type' => 'db',
                'allowed' => 'tx_bwmediathekasset_item',
                'size' => 10,
                'autoSizeMax' => 20,
                'minitems' => 0,
                'maxitems' => 30,
                'fieldControl' => [
                    'editPopup' => [
                        'disabled' => false,
                    ],
                    'addRecord' => [
                        'disabled' => true,
                    ],
                    'listModule' => [
                        'disabled' => true,
                    ],
                    'elementBrowser' => [
                        'disabled' => false,
                    ],
                ],
                'suggestOptions' => [
                    'maxItemsInResultList' => 25,
                    'default' => [
                        'searchWholePhrase' => 1
                    ],
                ],
            ]
        ],

We want to paste a record from the TYPO3 Clipboard into this field.

TYPO3 8.7.47

Within TYPO3 8.7.47 this code works:

Copy record 6510
into the target record 6503

<a 
    onclick="setFormValueFromBrowseWin('data[tx_bwmediathekasset_item][6503][related]',unescape('tx_bwmediathekasset_item_6510'),'Krise\u0020bew\u00e4ltigen\u0020und\u0020Zukunft\u0020gestalten,\u002010.11.2022\u002016:09','Krise\u0020bew\u00e4ltigen\u0020und\u0020Zukunft\u0020gestalten,\u002010.11.2022\u002016:09');return false;" 
    class="btn btn-default" 
    href="#">

TYPO3 11.5.19

Within TYPO3 11.5.19 this code doesn’t work:

Copy record 6449
into the target record 6442

<a 
    id="t3js-formengine-fieldcontrol-63749b70924ea204373512" 
    data-element="data[tx_bwmediathekasset_item][6442][related]" 
    data-clipboard-items="[{&quot;title&quot;:&quot;[Kein Titel]&quot;,&quot;value&quot;:&quot;tx_bwmediathekasset_item_1&quot;}]" 
    class="btn btn-default" 
    href="#">

There will be a record wirh an empty title that disappears after saving.

<option value="tx_bwmediathekasset_item_1" title="[Kein Titel]">[Kein Titel]</option>
Author Ralph Brugger
Created 11/16/22, 08:29
Updated 10/06/26, 16:43
Feature
Under Review Quiet Localization

#76300 More intuitive selection of Trans.Orig.

Today working with multi language website is not so easy for editors.
To streamline the work one of things should be easy to implement.
Please see on my screenshot to check what i’m talking about.

Author Rafal Brzeski
Created 05/25/16, 17:04
Updated 10/02/26, 22:07
Bug
Under Review Quiet Workspaces TYPO3 CMS 14

#110905 MM relation added in a workspace to an already versioned record is invisible and gets lost on publish

MM rows of records in a workspace point to the workspace uids on both sides: if tt_content:297 has the workspace version 299, its relations in the workspace are the MM rows with uid_foreign = 299.

When a relation to such a record is added in the workspace from the other side, e.g. by creating a new record and selecting tt_content:297 in its local side MM field, the MM row is written with the live uid 297 instead of the version uid 299.

Consequences:

  • In the workspace, the versioned record does not show the new relation, the workspace preview is wrong.
  • When both records are published, publishing the versioned record replaces the MM rows of the live uid by the rows of its version, so the new relation is deleted. The relation is lost even though everything has been published.

How to reproduce

Core functional test fixture EXT:core/Tests/Functional/Fixtures/Extensions/test_mm, data set DataScenarios/ManyToMany/DataSet/ImportDefaultWorkspaces.csv:

  • tx_test_mm.group_mm_1_local (local side, MM_oppositeUsage) <-> tt_content.group_mm_1_foreign (foreign side, MM_opposite_field), MM table group_mm_1_relations_mm

In workspace 1:

  1. Modify tt_content:297 (creates version 299)
  2. Create a new tx_test_mm record (uid 32) with group_mm_1_local = tt_content_297

MM table afterwards:

_.uid_local _.uid_foreign _.sorting _.sorting_foreign
28 297 0 1 live
29 297 0 2 live
32 297 1 0 new relation, points to the live uid
28 299 0 1 version of tt_content:297
29 299 0 2 version of tt_content:297
  1. Workspace preview of page 89: content element 297 lists “Surf A” and “Surf B”, but not the new record
  2. Publish tx_test_mm:32 and tt_content:297: the MM row of tx_test_mm:32 is gone

The opposite direction (new content element related to tx_test_mm:28, which has a workspace version) has the same cause. It is covered by the patch for #105578, which keeps MM rows pointing to workspace records on publish.

Expected behaviour

A relation added in a workspace to a record which has a version in this workspace is stored with the uid of that version, so the version shows it and the relation is moved to the live uid when the version is published.

Author Georg Ringer
Created 10/03/26, 06:09
Updated 10/03/26, 06:26
Bug
Under Review Quiet Workspaces TYPO3 CMS 14

#110904 Creating a workspace version modifies live MM rows and deletes MM rows of other workspaces

Description

When a record holding an MM relation is versioned, DataHandler::remapListedDBRecords_procDBRefs() runs the block “If record has been versioned/copied in this process, handle invalid relations of the live record”: it reads the MM relations of the live record in workspace 0, purges all workspace records from them and, if anything was purged, writes the remaining relations back to the live record with RelationHandler::writeMM().

This has two side effects, although the editor only works in a workspace:

  • writeMM() renumbers the sorting of the live MM rows, so live data changes. The reference index of the live record is not updated accordingly and is left dirty.
  • All MM rows of the live record pointing to workspace records are deleted, including the ones belonging to versions in other workspaces.

How to reproduce

Core functional test fixture EXT:core/Tests/Functional/Fixtures/Extensions/test_mm, data set DataScenarios/ManyToMany/DataSet/ImportDefaultWorkspaces.csv:

  • tx_test_mm.group_mm_1_local (local side, MM_oppositeUsage) <-> tt_content.group_mm_1_foreign (foreign side, MM_opposite_field), MM table group_mm_1_relations_mm
  1. Workspace 2: modify tt_content:297 (creates version 299). The MM rows 28 -> 299 and 29 -> 299 are created for the version.
  2. Workspace 1: modify tx_test_mm:28 (creates version 32)

MM table afterwards:

_.uid_local _.uid_foreign _.sorting _.sorting_foreign
28 297 1 1 live row, sorting changed (was 0)
29 297 0 2 live
32 297 1 0 version of tx_test_mm:28 in workspace 1
29 299 0 2 version of tt_content:297 in workspace 2

The row 28 -> 299 of workspace 2 has been deleted. In workspace 2, content element 297 loses its relation to tx_test_mm:28 (“Surf A”), and publishing workspace 2 removes the relation from live.

The live sorting change also happens within one workspace: modify tt_content:297 and then tx_test_mm:28 in workspace 1, the live row 28 -> 297 changes from sorting=0 to sorting=1.

Expected behaviour

Creating a workspace version neither modifies MM rows of the live record nor MM rows of other workspaces.

Author Georg Ringer
Created 10/03/26, 06:03
Updated 10/03/26, 06:21
Task
Under Review Quiet TYPO3 CMS 15

#110465 Resolve TODO for "inlineStructure" in FormInlineAjaxController and FormFilesAjaxController

inlineStructure is marked with a TODO that is not needed anymore. Resolve this.

Author Wouter Wolters
Assigned to Wouter Wolters
Created 08/12/26, 20:31
Updated 10/05/26, 16:46
Bug
Under Review Fresh Site Handling, Site Sets & Routing TYPO3 CMS 12

#102076 PageSlugCandidateProvider puts a serious load on the database

The query in is quite inefficient and stresses the database a lot:

        $statement = $queryBuilder
            ->select('uid', 'sys_language_uid', 'l10n_parent', 'l18n_cfg', 'pid', 'slug', 'mount_pid', 'mount_pid_ol', 't3ver_state', 'doktype', 't3ver_wsid', 't3ver_oid')
            ->from('pages')
            ->where(
                $queryBuilder->expr()->eq(
                    'sys_language_uid',
                    $queryBuilder->createNamedParameter($languageId, Connection::PARAM_INT)
                ),
                $queryBuilder->expr()->in(
                    'slug',
                    $queryBuilder->createNamedParameter(
                        $slugCandidates,
                        Connection::PARAM_STR_ARRAY
                    )
                )
            )
            // Exact match will be first, that's important
            ->orderBy('slug', 'desc')
            // versioned records should be rendered before the live records
            ->addOrderBy('t3ver_wsid', 'desc')
            // Sort pages that are not MountPoint pages before mount points
            ->addOrderBy('mount_pid_ol', 'asc')
            ->addOrderBy('mount_pid', 'asc')
            ->executeQuery();

MySql:

MariaDB [prod12]> explain SELECT `uid`, `sys_language_uid`, `l10n_parent`, `l18n_cfg`, `pid`, `slug`, `mount_pid`, `mount_pid_ol`, `t3ver_state`, `doktype`, `t3ver_wsid`, `t3ver_oid` FROM `pages` WHERE (`sys_language_uid` = ?) AND (`slug` IN (?)) AND (((`pages`.`deleted` = 0) AND (((`pages`.`t3ver_wsid` = 0) AND (`t3ver_state` <> 2))))) ORDER BY `slug` desc, `t3ver_wsid` desc, `mount_pid_ol` asc, `mount_pid` asc;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '?) AND (`slug` IN (?)) AND (((`pages`.`deleted` = 0) AND (((`pages`.`t3ver_ws...' at line 1
MariaDB [prod12]> explain SELECT `uid`, `sys_language_uid`, `l10n_parent`, `l18n_cfg`, `pid`, `slug`, `mount_pid`, `mount_pid_ol`, `t3ver_state`, `doktype`, `t3ver_wsid`, `t3ver_oid` FROM `pages` WHERE (`sys_language_uid` = 0) AND (`slug` IN ('')) AND (((`pages`.`deleted` = 0) AND (((`pages`.`t3ver_wsid` = 0) AND (`t3ver_state`
<> 2))))) ORDER BY `slug` desc, `t3ver_wsid` desc, `mount_pid_ol` asc, `mount_pid` asc;
+------+-------------+-------+------+---------------+------+---------+-------+------+-----------------------------+
| id   | select_type | table | type | possible_keys | key  | key_len | ref   | rows | Extra                       |
+------+-------------+-------+------+---------------+------+---------+-------+------+-----------------------------+
|    1 | SIMPLE      | pages | ref  | slug          | slug | 384     | const | 2    | Using where; Using filesort |
+------+-------------+-------+------+---------------+------+---------+-------+------+-----------------------------+
1 row in set (0.000 sec)

So where + filesort.

For now I was able to fix this by adjusting slug key like this:

alter table pages add key slug2 (slug(127),`t3ver_wsid`,`mount_pid_ol`,`mount_pid`);

Check the result:

MariaDB [prod12]> explain SELECT `uid`, `sys_language_uid`, `l10n_parent`, `l18n_cfg`, `pid`, `slug`, `mount_pid`, `mount_pid_ol`, `t3ver_state`, `doktype`, `t3ver_wsid`, `t3ver_oid` FROM `pages` WHERE (`sys_language_uid` = 0) AND (`slug` IN ('')) AND (((`pages`.`deleted` = 0) AND (((`pages`.`t3ver_wsid` = 0) AND (`t3ver_state`
<> 2))))) ORDER BY `slug` desc, `t3ver_wsid` desc, `mount_pid_ol` asc, `mount_pid` asc;
+------+-------------+-------+-------+---------------+-------+---------+------+------+-------------+
| id   | select_type | table | type  | possible_keys | key   | key_len | ref  | rows | Extra       |
+------+-------------+-------+-------+---------------+-------+---------+------+------+-------------+
|    1 | SIMPLE      | pages | range | slug,slug2    | slug2 | 388     | NULL | 2    | Using where |
+------+-------------+-------+-------+---------------+-------+---------+------+------+-------------+
1 row in set (0.001 sec)

No filesort.

Author Dmitry Dulepov
Created 10/02/23, 08:56
Updated 11/14/26, 11:07
Task
Under Review Fresh Performance TYPO3 CMS 15

#111445 Build the record path of a page along the cached page ancestry

BackendUtility::getRecordPath() builds the path of a page (“/Root/Section/Page”) shown in the record list, the live search, FormEngine wizards, the preview of content elements, the move page wizard, the workspaces module, the import/export module and others. It uses BackendUtility::BEgetRootLine(), which fetches one page per query via BackendUtility::getPageForRootline(), plus a workspace overlay per page in a workspace. An optional SQL clause – typically the page permissions of the backend user – ends the path at the first page not matching it.

The PageAncestryResolver resolves the ancestry of a page with one query and caches it for the request. It gets a method resolveMatching(), which ends the ancestry at the first page not matching an SQL clause. The clause is evaluated on the live pages of the ancestry with one further query, so any clause works as before, also one modified by the “getPagePermsClause” hook.

getRecordPath() uses it, the paths stay the same. For a page on level seven, a path needs 1 instead of 7 queries in live, and 2 instead of 14 queries in a workspace, plus one query for a permission clause.

Afterwards, BEgetRootLine() is only used by BackendUserAuthentication::isInWebMount() with a custom permission clause, which is the next step towards deprecating BEgetRootLine() and getPageForRootline().

Author Benni Mack
Created 11/14/26, 09:42
Updated 11/14/26, 10:14
Bug
Under Review Fresh DataHandler aka TCEmain TYPO3 CMS 11

#98050 Non translatable inline records only updates on second save.

Hi,

I’m sorry if this gets a bit long, but I have no idea how to describe this any other way.

Consider the following setup:

Main table is translatable tx_demo_domain_model_main and has inline records of tx_demo_domain_model_sub which are not translatable in it self and should only be changeable in the default language of main.

return [
  'ctrl' => [
    'title' => 'Main',
    'label' => 'title',
    'tstamp' => 'tstamp',
    'crdate' => 'crdate',
    'cruser_id' => 'cruser_id',
    'sortby' => 'sorting',
    'versioningWS' => true,
    'languageField' => 'sys_language_uid',
    'transOrigPointerField' => 'l10n_parent',
    'transOrigDiffSourceField' => 'l10n_diffsource',
    'delete' => 'deleted',
    'enablecolumns' => [
      'disabled' => 'hidden',
      'starttime' => 'starttime',
      'endtime' => 'endtime',
    ],
    'searchFields' => 'title',
    'iconfile' => 'main.svg',

  ],
  'types' => [
    '1' => [
      'showitem' => '
        title, subs, 
        --div--;LLL:EXT:core/Resources/Private/Language/Form/locallang_tabs.xlf:language, sys_language_uid, l10n_parent, l10n_diffsource, 
        --div--;LLL:EXT:core/Resources/Private/Language/Form/locallang_tabs.xlf:access, hidden, starttime, endtime
      ',
    ],
  ],
  'columns' => [
    'sys_language_uid' => [
      'exclude' => true,
      'label' => 'LLL:EXT:core/Resources/Private/Language/locallang_general.xlf:LGL.language',
      'config' => [
        'type' => 'language',
      ],
    ],
    'l10n_parent' => [
      'displayCond' => 'FIELD:sys_language_uid:>:0',
      'label' => 'LLL:EXT:core/Resources/Private/Language/locallang_general.xlf:LGL.l18n_parent',
      'config' => [
        'type' => 'select',
        'renderType' => 'selectSingle',
        'default' => 0,
        'items' => [
          ['', 0],
        ],
        'foreign_table' => 'tx_demo_domain_model_main',
        'foreign_table_where' => 'AND {#tx_demo_domain_model_main}.{#pid}=###CURRENT_PID### AND {#tx_demo_domain_model_main}.{#sys_language_uid} IN (-1,0)',
      ],
    ],
    'l10n_diffsource' => [
      'config' => [
        'type' => 'passthrough',
      ],
    ],
    'hidden' => [
      'exclude' => true,
      'label' => 'LLL:EXT:core/Resources/Private/Language/locallang_general.xlf:LGL.visible',
      'config' => [
        'type' => 'check',
        'renderType' => 'checkboxToggle',
        'items' => [
          [
            0 => '',
            1 => '',
            'invertStateDisplay' => true,
          ],
        ],
      ],
    ],
    'starttime' => [
      'exclude' => true,
      'l10n_mode' => 'exclude',
      'label' => 'LLL:EXT:core/Resources/Private/Language/locallang_general.xlf:LGL.starttime',
      'config' => [
        'type' => 'input',
        'renderType' => 'inputDateTime',
        'eval' => 'datetime,int',
        'default' => 0,
        'behaviour' => [
          'allowLanguageSynchronization' => true,
        ],
      ],
    ],
    'endtime' => [
      'exclude' => true,
      'l10n_mode' => 'exclude',
      'label' => 'LLL:EXT:core/Resources/Private/Language/locallang_general.xlf:LGL.endtime',
      'config' => [
        'type' => 'input',
        'renderType' => 'inputDateTime',
        'eval' => 'datetime,int',
        'default' => 0,
        'range' => [
          'upper' => mktime(0, 0, 0, 1, 1, 2038),
        ],
        'behaviour' => [
          'allowLanguageSynchronization' => true,
        ],
      ],
    ],
    'title' => [
      'exclude' => true,
      'label' => 'title',
      'config' => [
        'type' => 'input',
        'size' => 30,
        'eval' => 'trim,required',
        'default' => '',
      ],
    ],

    'subs' => [
      'exclude' => true,
      'l10n_mode' => 'exclude',
      'label' => 'Sub',
      'config' => [
        'type' => 'inline',
        'foreign_table' => 'tx_demo_domain_model_sub',
        'foreign_field' => 'main',
        'maxitems' => 9999,
        'appearance' => [
          'collapseAll' => 1,
          'levelLinksPosition' => 'top',
          'showSynchronizationLink' => 1,
          'showPossibleLocalizationRecords' => 1,
          'showAllLocalizationLink' => 1,
        ],
      ],
    ],
  ],
];

Here the setup of tx_demo_domain_model_sub


return [
  'ctrl' => [
    'title' => 'Sub',
    'label' => 'price',
    'tstamp' => 'tstamp',
    'crdate' => 'crdate',
    'cruser_id' => 'cruser_id',
    'default_sortby' => 'price ASC',
    'versioningWS' => true,
    'delete' => 'deleted',
    'enablecolumns' => [
      'disabled' => 'hidden',
      'starttime' => 'starttime',
      'endtime' => 'endtime',
    ],
    'searchFields' => '',
    'iconfile' => 'sub.gif',
  ],
  'types' => [
    '1' => [
      'showitem' => '
        price, 
        --div--;LLL:EXT:core/Resources/Private/Language/Form/locallang_tabs.xlf:access, hidden, starttime, endtime
      ',
    ],
  ],
  'columns' => [
    'hidden' => [
      'exclude' => true,
      'label' => 'LLL:EXT:core/Resources/Private/Language/locallang_general.xlf:LGL.visible',
      'config' => [
        'type' => 'check',
        'renderType' => 'checkboxToggle',
        'items' => [
          [
            0 => '',
            1 => '',
            'invertStateDisplay' => true,
          ],
        ],
      ],
    ],
    'starttime' => [
      'exclude' => true,
      'label' => 'LLL:EXT:core/Resources/Private/Language/locallang_general.xlf:LGL.starttime',
      'config' => [
        'type' => 'input',
        'renderType' => 'inputDateTime',
        'eval' => 'datetime,int',
        'default' => 0,
        'behaviour' => [
          'allowLanguageSynchronization' => true,
        ],
      ],
    ],
    'endtime' => [
      'exclude' => true,
      'label' => 'LLL:EXT:core/Resources/Private/Language/locallang_general.xlf:LGL.endtime',
      'config' => [
        'type' => 'input',
        'renderType' => 'inputDateTime',
        'eval' => 'datetime,int',
        'default' => 0,
        'range' => [
          'upper' => mktime(0, 0, 0, 1, 1, 2038),
        ],
        'behaviour' => [
          'allowLanguageSynchronization' => true,
        ],
      ],
    ],
    'price' => [
      'exclude' => true,
      'label' => 'price',
      'config' => [
        'type' => 'input',
        'size' => 30,
        'eval' => 'double2',
      ],
    ],
    'main' => [
      'config' => [
        'type' => 'passthrough',
      ],
    ],
  ],
];

Now create a main record and add sub records.
If the main record is now translated everything is fine.

But if now the main record with language id 0 is opened, the value of one the sub records is changed, and you hit save.
This has no effect on the value of the sub records for the main record language id 1.

Only if you click save for main record language id 0 again this change is also made for the records language 1.

Even worse, this the sub record value always get the old value of the default language on save.

Which looks like this

1. Step create

tx_demo_domain_model_main
id, language, parent, title
1,  0.        0,      'default language'
tx_demo_domain_model_sub
id, price, main
1,  1.5,   1

2. Step translate

tx_demo_domain_model_main
id, language, parent, title
1,  0.        0,      'default language'
2,  1,        1,      'second language'
tx_demo_domain_model_sub
id, price, main
1,  1.5,   1
2,  1.5,   2

3. Step edit and save

tx_demo_domain_model_main
id, language, parent, title
1,  0.        0,      'default language'
2,  1,        1,      'second language'
tx_demo_domain_model_sub
id, price, main
1,  2,     1
2,  1.5,   2

The price in changed but only for the default language sub record

4. Step just save again

tx_demo_domain_model_main
id, language, parent, title
1,  0.        0,      'default language'
2,  1,        1,      'second language'
tx_demo_domain_model_sub
id, price, main
1,  2,     1
2,  2,     2

Now also the sub record for the second language is updated.

5. Step edit again

tx_demo_domain_model_main
id, language, parent, title
1,  0.        0,      'default language'
2,  1,        1,      'second language'
tx_demo_domain_model_sub
id, price, main
1,  3,     1
2,  2,     2

6. Step edit again

tx_demo_domain_model_main
id, language, parent, title
1,  0.        0,      'default language'
2,  1,        1,      'second language'
tx_demo_domain_model_sub
id, price, main
1,  4,     1
2,  3,     2

As you can see in step 5 and 6 the translated record is updated to the old value of the default language but not to the new one.

Author JAKOTA Design Group GmbH
Created 07/28/22, 20:27
Updated 11/13/26, 19:24
Bug
Under Review Fresh TYPO3 CMS 13

#106851 Form Validation fails with "token" as Form Name

Description

If you set the name of an Extbase form, in my case that of a backend controller, to “token”, the validation of the form always fails.

Example

<f:form action="verifyPin" name="token" object="{token}">
    ...
</f:form>

Preliminary error analysis

Since the request token is apparently always transmitted as a GET parameter, the simplest solution would probably be to swap the order of this POST-GET parameter check.

Author George Miller
Created 06/09/25, 15:06
Updated 11/13/26, 18:06
Task
Under Review Fresh Security TYPO3 CMS 14

#108197 Add shortcut-method for decrypting

suggested by @supergarv in https://review.typo3.org/c/Packages/TYPO3.CMS/+/91439/comments/dee21c5c_4a205052

$secretKey = $this->keyFactory->deriveSharedKeyFromEncryptionKey('api-tokens');
$cipherValue = CipherValue::fromSerialized('eyJub25jZSI6IktvUkFxbkNMaktoT0Y2a1c5Y04zdklUeFpvd0NhLWhwIiwiY2lwaGVyIjoiN2NxazlaQjZXRDVoOV9PaWVmbFV1UlFLQndVIn0');
$decrypted = $this->cipherService->decrypt($cipherValue, $secretKey);

to be simplified as

$decrypted = $this->cipherService->decryptFromSerialized(   'eyJub25jZSI6IktvUkFxbkNMaktoT0Y2a1c5Y04zdklUeFpvd0NhLWhwIiwiY2lwaGVyIjoiN2NxazlaQjZXRDVoOV9PaWVmbFV1UlFLQndVIn0', 'api-tokens');
Author Oliver Hader
Assigned to Oliver Hader
Created 11/19/25, 14:32
Updated 11/14/26, 12:57
Bug
Under Review Fresh FormEngine aka TCEforms TYPO3 CMS 14

#111419 selectTree ignores workspace changes of the parent field and queries every node again

A select field with `renderType => selectTree` and `treeConfig.parentField` (e.g. `sys_category.parent`, as used by EXT:news) builds its tree by querying the live table for each node, although FormEngine already fetched all workspace-overlaid rows of the foreign table.

## Effects

  • Moving a category to another parent in a workspace still shows it below its live parent in the select tree.
  • Building the tree runs about three queries per node (`BackendUtility::getRecord()`, a `FIND_IN_SET` query on the parent field, `BackendUtility::getRecordWSOL()` for the label).

## Steps to reproduce

1. Create the categories 1 and 2 on root level and category 3 below category 1.
2. In a workspace, change the parent of category 3 to category 2.
3. Open a record with a selectTree field on sys_category with `parentField => ‘parent’` in that workspace.

Expected: category 3 is shown below category 2. Actual: it is shown below category 1.

`type => category` fields already reuse the fetched rows (`TcaCategory` hands them over via `setAvailableItems()`), `TcaSelectTreeItems` does not.

Author Benni Mack
Created 11/12/26, 09:48
Updated 11/14/26, 11:39
Bug
Under Review Fresh Install Tool TYPO3 CMS 12

#105345 Simulate BE-User does not show Install-Tool modules for system maintainers

When switching to another user via “simulate backend user”, the install tool modules “Maintenance”, “Settings” etc. are not displayed, event if the user is a system maintainer and/or the TYPO3_CONTEXT is “Development”.

Author Nikita Hovratov
Created 10/18/24, 13:18
Updated 11/13/26, 15:31
Bug
Under Review Quiet Content Security Policy TYPO3 CMS 13

#110601 Directive "strict-dynamic" not allowed for hash based Content Security Policy (CSP)

In TYPO3, the directive “strict-dynamic” is not allowed when using a hash based instead of nonce based CSP.

According to the MDN documentation, and others, it should be allowed for hash based CSP as well:
> The ‘strict-dynamic’ source expression specifies that the trust explicitly given to a script present in the markup, by accompanying it with a nonce or a hash , shall be propagated to all the scripts loaded by that root script. At the same time, any allowlist or source expressions such as ‘self’ or ‘unsafe-inline’ will be ignored.

In TYPO3 the directive is only allowed when using nonces, which is not right.

Author Patrick Broens
Created 09/02/26, 11:41
Updated 10/01/26, 07:55
Bug
Under Review Quiet Site Handling, Site Sets & Routing TYPO3 CMS 14

#109570 Context Menu in Site Setup Module on Breadcrumb menu throws exception

While editing a site config in BE, click on the page icon in breadcrumb leads to exception

  1. RuntimeException
    Either site identifier to edit a config or page uid to add new config must be set
Author Anja Leichsenring
Created 04/14/26, 04:25
Updated 10/01/26, 07:47
Bug
Under Review Quiet File Abstraction Layer (FAL) TYPO3 CMS 13

#110318 ProcessedFile::getForLocalProcessing() asks the processing storage for a file that points to the original

Problem

When processing produces no new file (for example if the original is already smaller than the requested size) the processed file is only a pointer to the original: usesOriginalFile() is true and getIdentifier() returns the identifier of the original file, while getStorage() returns the processing storage.

Every accessor compensates for that mismatch (exists(), getName(), getMimeType(), getSize(), getPublicUrl(), toArray()).
@getForLocalProcessing()@ does not, because ProcessedFile never overrides it:

// AbstractFile::getForLocalProcessing()
return $this->getStorage()->getFileForLocalProcessing($this, $writable);

The identifier of the original file is therefore handed to the driver of the processing storage.
This is not a problem when:
- both are the same storage
- a local driver is used (this just returns a path to a non-existing file, also not great but not breaking)

But when you have the processingfolder of one storage pointing to another one (2:_processed_/) and using a remote driver (in my case S3) this means that the image does not exist and it throws an error and the image rendering fails.

Steps to reproduce

  1. Add a second Local storage, base path fileadmin/processed_storage/.
  2. Set Processing folder of storage 1 to 2:/.
  3. Upload a (for example) 200×200 image and render it without scaling, for example <f:image image="{file}" maxWidth="1000" />.
$processed = $file->process(ProcessedFile::CONTEXT_IMAGECROPSCALEMASK, ['maxWidth' => 1000]);

$processed->usesOriginalFile();      // true
$processed->getPublicUrl();          // fileadmin/user_upload/image.jpg            <- correct
$processed->getForLocalProcessing(); // .../fileadmin/processed_storage/...        <- wrong storage

Expected: getForLocalProcessing() returns a local copy of the original file, consistent with getPublicUrl().

Regression

ProcessedFile never had an override of the method but it became a problem with the change in #106518, where ImageResource::createFromProcessedFile() was switched from getPublicUrl() to getForLocalProcessing()

Affected: 13.4.10 and newer

Related

  • #106518 – introduced the call
  • #89004 – describes how the empty-identifier state arises
  • #106985 – same call chain
Author Riny van Tiggelen
Created 07/29/26, 11:09
Updated 10/01/26, 07:47
Feature
Under Review Quiet File Abstraction Layer (FAL)

#110832 Introduce upload constraints for file uploads

Problem

The rules that decide whether a file may be uploaded are hard-coded and spread across several places. Each one is implemented twice: once as a client-side hint for the drag uploader, once as the actual server-side check.

  • Maximum file size: GeneralUtility::getMaxUploadFileSize(), checked in ResourceStorage::assureFileUploadPermissions() and passed to the client by FilesControlContainer, FileListController and CreateFileBrowser (data-max-file-size)
  • File deny pattern: $GLOBALS['TYPO3_CONF_VARS']['BE']['fileDenyPattern'], checked through FileNameValidator and passed to the client by FileListController and CreateFileBrowser (data-file-deny-pattern)

Extensions cannot add their own rules. Examples:

  • a lower size limit for certain user groups (#108660)
  • rejecting files after a virus or content scan
  • restricting uploads per storage or folder
  • informing editors that uploads are post-processed (e.g. spell-checked, resized)

The two halves also drift apart easily: the limit shown in the UI and the limit the server enforces can differ.

Proposal

Introduce upload constraints: services tagged file.upload_constraint that implement an interface with two methods:

interface UploadConstraintInterface
{
    public function describe(UploadContext $context): ?UploadConstraintDescription;
    public function validate(UploadedFileInterface $file, UploadContext $context): ?UploadRejection;
}
  • UploadContext holds the storage, the target folder and the user.
  • describe() runs before the upload, when there is no file yet. It returns a human-readable label and optional machine-readable client hints (maximum file size, deny pattern). The core merges the hints of all constraints: the lowest size wins, and the patterns are combined.
  • validate() runs in ResourceStorage for every uploaded file. A rejection carries a reason, which is shown to the user as a flash message.

Because one class describes and enforces a rule, the hint in the UI and the server-side check stay consistent.

Scope of this issue

  • Add the interface, the value objects and a registry collecting all tagged constraints
  • Port the existing core rules (PHP upload limit, file deny pattern) to constraints
  • Validate uploads in ResourceStorage through the registry, keeping today’s exceptions and flash messages for the ported rules
  • Feed the existing data attributes of the drag uploader from the registry
  • No change in behaviour for existing installations
  • Deprecating GeneralUtility::getMaxUploadFileSize()

Out of scope / follow-ups

  • Rendering constraint labels in the upload UI (separate issue)

Supersedes #108660 and https://review.typo3.org/c/Packages/TYPO3.CMS/+/92360, following the review feedback there.

Author Sebastian Michaelsen
Assigned to Sebastian Michaelsen
Created 09/29/26, 12:58
Updated 09/30/26, 08:51
Bug
Under Review Quiet Extbase TYPO3 CMS 11

#95823 Extbase does not support private domain object properties

Internally, Extbase does not use getters to gather internal property values but uses method _getProperty() which then calls return $this->{$propertyName};

This however cannot access private properties of the child class.

One idea to get rid of this and other “magic” methods would be to rely on proper access via getters/setters. That way, Extbase could internally use symfony/property-access.

A downside of this is that it’s a huge change for those users that don’t use getters to expose the internal value directly but add their own logic as well. We would need to make this change very visible to the community so people check and adjust their getters/setters/hassers.

Author Alexander Schnitzler
Created 10/30/21, 11:09
Updated 09/29/26, 14:11
Feature
New Quiet Linkvalidator

#103478 Linkvalidator should check fields with type "file"

e.g. pages.media

see documentation: https://docs.typo3.org/c/typo3/cms-linkvalidator/main/en-us/Configuration/Index.html

LinkAnalyzer.php:

if (($conf['type'] ?? '') === 'link' && empty($conf['softref'])) {
    $conf['softref'] = 'typolink';
}
Author Sybille Peters
Created 03/25/24, 05:47
Updated 09/28/26, 20:32
Bug
Under Review Quiet TYPO3 CMS 10

#93972 Files with "+" in filename can't be replaced

In TYPO3 10 LTS, files with “+” in filename can’t be replaced using the replace tool in Filelist module.
Instead, the new file is uploaded but it doesn’t replace the old one.

Author Christian Toffolo
Created 04/22/21, 16:06
Updated 09/27/26, 18:07
Bug
Under Review Quiet Linkvalidator TYPO3 CMS 12

#105413 Linkvalidator BE-Module wrong permissions for invalid links in page attributes

*Steps to Reproduce*
1. Create a page and disallow editing that page using the Access-Module
2. Create external-url Page below the previously created page and set an invalid url
3. Run the Linkvalidator Task
4. Login as User without Admin privileges
5. Select the external-url page and open the LinkValidator Backend Module

The invalid Link won’t be shown even though the user should have access to the page, because only the parent page is restricted.
Invalid links in Content-Elements are not affected by this issue.

*Technical Analysis*
The Linkvalidator creates an entry for every invalid link. This entry contains a record_pid. For links within Content-Elements this pid is the page containing the Content-Element. For links in page attributes the pid is the parent page of the page with affected attribute.

When fetching the links for the BE-Module the page-table is joined using the record_pid. (see https://github.com/TYPO3/typo3/blob/main/typo3/sysext/linkvalidator/Classes/Repository/BrokenLinkRepository.php#L105)
This means the EditableRestrictions are be applied to the page referenced in record_pid.

Author Roman Schilter
Assigned to Sybille Peters
Created 10/23/24, 13:44
Updated 09/25/26, 18:00

Showing results 626 to 650 of 1561