Showing results 401 to 425 of 1561

Feature
New Fresh Site Handling, Site Sets & Routing

#90079 Slug improvements for heavy localisation

If you have regional content the slug generation function needs to be improved slightly to prevent duplicate slugs.

Case 1: Currently language ‘all’ is not checked when a new Slug is generated. If you e.g. use News with language ‘all’ and normal translations in the same Folder you will have the problem that they can have the same ‘path_segment’ which shouldn’t be the case since they will be shown at the same time. I added a Patch which fixes this issue.

Case 2: If you have regional content like e.g. a Folder ‘Global News [14]’ and then additional Folders like ‘NA News [15]’, ‘EA News [16]’, ‘LA News [17]’, then the slug generation options ‘uniqueInSite’ and ‘uniqueInPid’ are not enough anymore and you need an additional Option like ‘uniqueInGroups’ where you can configure groups of pid’s which need unique URLs, since you may want the same URL in each of the regional Folders but not if you compare the global Folder and the regional Folder.
I attached a patch for ‘typo3/sysext/core/Classes/DataHandling/SlugHelper.php’, then you just have to add the new eval value to files like ‘typo3/sysext/core/Classes/DataHandling/DataHandler.php’ and adapt your TCA configuration of the ‘path_segment’ field to something like:

'path_segment' => [
        'config' => [
            'eval' => 'uniqueInGroups',
            'generatorOptions' => [
                'pidGroups' => [
                    [14, 15],
                    [14, 16],
                    [14, 17],
                ]
            ]
        ]
    ]

Wenn generating a slug this function checks if your current pid is in a configured group and adds all pid’s of that group to the QueryBuilder. If your current pid is in none of the groups the behavior is the same as ‘uniqueInPid’.

Author Johannes Ender
Created 01/10/20, 09:33
Updated 11/19/26, 10:08
Bug
Needs Feedback Fresh TypoScript TYPO3 CMS 12

#103364 Site config settings can't be used to override constants anymore

Before TYPO3 12 it was possible to have recursive constants, which made it possible to set TS constants to values defined in the site config settings.

I get that the (undocumented) 10-step-recursion-resolving had to go. So no argument with that. But I’d like to find a solution for the evident drawback I’m facing now.

As soon as I include an extensions TypoScript (that is constants+setup, with constants usually set to empty values), it’s not possible to override those constants with “site constants” anymore.

A workaround could be to override those parts of the setup (where the constants are being read) and change the name of the constants! Since variables are often being used in multiple parts of the setup stack that cannot be the solution.

Take this (randomly chosen) snippet from EXT:powermail’s TypoScript setup:

plugin.tx_powermail.settings.setup.main.pid = {$plugin.tx_powermail.settings.main.pid}

In order to override that setting I would have to change the TypoScript setup to this e.g.

plugin.tx_powermail.settings.setup.main.pid = {$plugin.tx_powermail.settings.main.pid_override_from_site}

And add this new constant to the site config:

settings:
  plugin:
    tx_powermail:
      setup:
        main:
          pid_override_from_site_config: 123

Here’s a screenshot of how the constant stack is being put together:

With TYPO3 11 one simply had to set the extension’s constant to the custom constant (and it’s been resolves correctly) while the extension’s setup could remain untouched.

plugin.tx_powermail.settings.main.pid = {$plugin.tx_powermail.settings.main.pid_override_from_site}
Author Philipp Kitzberger
Created 03/11/24, 17:23
Updated 11/19/26, 13:49
Bug
Under Review Fresh FormEngine aka TCEforms TYPO3 CMS 10

#96992 Optimize reload after changing field in IRRE record with TCA "onChange"

When you have a scenario with multiple nested IRRE records and a field with TCA property onChange in a child record, the reload behaviour after the change event was triggered can become a usability nightmare as the whole record gets reloaded.

Sample case (from a real world extension): you have a survey, that can be structured into multiple sections (1st level IRRE record) and has multiple questions per section (2nd level IRRE record). Each question can have a type (multiple choice checkboxes, radio button group, plain text entry etc.) that determines, which question fields are available. This can be easily achieved with an onChange property on the question type field and displayCond on various other fields.

Problem: after changing the question type, the whole survey record reloads and all opened IRRE records are closed again. So you have to remember which record you were editing last and re-open the correnct section + question to continue editing the question. With a large survey (eg. 15 sections, 5-10 questions each) this quickly becomes a complete usability nightmare that drives editors insane.

Suggestions:

  1. Best case scenario: only reload the current question record, not the whole top parent record. When opening an IRRE record, data for this record gets loaded by AJAX and the form updates accordingly. Couldn’t that be done for reloads triggered by a TCA onChange event?
  2. Second best option: automatically re-open the last edited IRRE records (ie. section + question) after reloading. The UI already “remembers” things when editing + saving records, e.g. the tab that was last active. This suggests that the same should be possible for IRRE records as well?
Author Michael Stopp
Created 02/22/22, 10:30
Updated 11/18/26, 23:06
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 8

#91089 Edit single Field of multiple rows forces unneeded Reload in list view

Steps to reproduce:
This behavior is the same in all Versions since at least V6

Create a normal Content element cType – “Text and Media” . create translation to some language ( de / it / fr .. )
switch to list view and activate : show only tt content elements

add “cType” to listed field list. Click on top of the list of Field “cTYPE” to edit alle translations.
change cTypefrom Standard to “Headline” or anything else ..

As TCA of this field is configured with onChange=“reload” i get a popup with the question:
“Refresh Required“
This change will affect which fields are available in the form. Would you like to save now in order to refresh the display?

As in List Mode there ARE no other fields of that data record visible, this is a “useless” popup.

a very annoying UI issue if you did change the ctype with 16 translations, of 12 Pages …

Author Jörg Velletti
Created 04/17/20, 15:15
Updated 11/18/26, 23:06
Bug
Under Review Fresh Extbase TYPO3 CMS 13

#111494 ObjectStorage::removeAll() leaves half of the objects when given its own storage

Problem

Calling ObjectStorage::removeAll() with the storage itself removes only every other object, so the
relation is left half filled instead of empty. Measured on TYPO3 13.4.37, and read from main on
2026-11-18, where the method is unchanged:

objects before remaining after one call
2 1
3 1
5 2
8 4
10 5

Calling it again halves what is left, so code that “empties” a relation this way ends up with stale
objects that are written back to the database. PHP’s native SplObjectStorage::removeAll(), which this
class stands in for, removes all objects in the same situation.

The core itself never calls the method — every removeAll() call site in typo3/sysext is
@QueryBuilder::getRestrictions()->removeAll()@ or CategoryCollection::removeAll() — and the unit test
suite only ever passes a different storage, which is why this has not surfaced.

Steps to reproduce

Run this script against a Composer project with typo3/cms-extbase 13.4, or a checkout of main. No
TYPO3 bootstrap is needed, only the autoloader:

require __DIR__ . '/vendor/autoload.php';

$storage = new \TYPO3\CMS\Extbase\Persistence\ObjectStorage();
for ($i = 0; $i < 10; $i++) {
    $storage->attach(new \stdClass());
}

$storage->removeAll($storage);

echo count($storage);
  • Expected: 0
  • Actual: 5
  • Counter-proof that the method is fine for a foreign storage: build two storages holding the same ten objects and call $a->removeAll($b) — count($a) is 0.

Cause

ObjectStorage implements \Iterator over its own $storage array, using the internal array pointer
of that array: rewind() is reset(), current() is current(), next() is next().

removeAll() walks the storage it is given and calls detach() for every object the loop yields.
@detach()@ is offsetUnset(), an unset() of the entry the pointer currently stands on — and the
@next()@ the foreach then performs steps past the element that has shifted into that position. When
the given storage is the same object, every removal skips one object, so exactly half of them survive.

LazyObjectStorage::removeAll() delegates to this method and behaves the same.

Suggested fix

Iterate a snapshot instead of the live pointer; toArray() already exists on the class:

--- a/typo3/sysext/extbase/Classes/Persistence/ObjectStorage.php
+++ b/typo3/sysext/extbase/Classes/Persistence/ObjectStorage.php
@@ public function removeAll(ObjectStorage $storage): void
 {
-    foreach ($storage as $object) {
+    foreach ($storage->toArray() as $object) {
         $this->detach($object);
     }
 }

LazyObjectStorage inherits the fix. The existing removeAll tests in
@typo3/sysext/extbase/Tests/Unit/Persistence/ObjectStorageTest.php@ all pass a second storage and keep
passing; what is missing is the case that hands the storage to itself:

#[Test]
public function removeAllRemovesObjectsWhenGivenItself(): void
{
    /** @var ObjectStorage&lt;Entity&gt; $storage */
    $storage = new ObjectStorage();
    $storage-&gt;attach(new Entity());
    $storage-&gt;attach(new Entity());
    self::assertCount(2, $storage);

    $storage-&gt;removeAll($storage);

    self::assertCount(0, $storage);
}
Author Sven Proffe
Created 11/18/26, 17:15
Updated 11/18/26, 21:04
Task
Author Oliver Bartsch
Assigned to Oliver Bartsch
Created 10/19/26, 07:26
Updated 11/18/26, 20:33
Task
Author Oliver Bartsch
Assigned to Oliver Bartsch
Created 10/09/26, 15:29
Updated 11/18/26, 20:33
Feature
Under Review Fresh Performance

#111412 Restrict queries to a page tree without a list of page ids

Several backend modules restrict their queries to the pages below a page: they first collect the uids of all these pages and then add them to the query as “pid IN (…)”:

  • the record list with search levels (DatabaseRecordList::getSearchableWebmounts())
  • the log module with a depth (LogEntryRepository)
  • the recycler (DeletedRecords, which even splits the list into chunks and caches it per request)

With large page trees, the uid list makes these queries slow, and it exceeds the number of placeholders a database accepts in one statement (“Prepared statement contains too many placeholders”, see #95812, #86859, #92493).

The PageDescendantsRepository (#111406) fetches the descendants of pages with one recursive common table expression (CTE). It gets a method that adds this CTE as a subquery to the constraint of another query, so the database resolves the page tree within the query itself, and no uid list is built anymore. The same workspace handling and access constraints (e.g. the page permissions of a backend user) apply as for fetching the descendants. If the queried table lives on another database connection than the pages table, the constraint falls back to a list of uids without placeholders.

The record list, the log module and the recycler use the new constraint. The record list then also searches pages that only exist in the workspace of the user.

The live search (#93937, Gerrit 96668) can make use of the same constraint.

Author Benni Mack
Created 11/11/26, 15:07
Updated 11/19/26, 08:45
Feature
Under Review Fresh Performance

#111406 Find the subpages of a page with one database query

Several parts of TYPO3 collect the subpages of a page – recursively, down to a given depth – by walking the page tree in PHP with one database query per page. Each of them implements this on its own, with different handling of workspaces, languages and permissions:

  • PageTreeRepository::getFlattenedPages() (record list, live search, belog, suggest wizard)
  • WorkspaceService::getTreeUids() (workspaces module)
  • Extbase BackendConfigurationManager (persistence.recursive of backend modules)
  • QuerySearchController (lowlevel database search)
  • AdministrationRepository (indexed_search)
  • DeletedRecords (recycler)

For a page tree of 780 pages, this means up to 907 queries, and in a workspace additional queries per versioned page.

A new PageDescendantsRepository fetches the descendants of one or more pages with one recursive common table expression (CTE):

  • only pages of the default language, resolved for a workspace: pages moved in the workspace are found at their new position, pages new in the workspace are included, pages deleted in the workspace are left out together with their subpages
  • access restrictions are handed in by the caller: query restrictions evaluated on the workspace version of a page (e.g. hidden), and a constraint evaluated on the live page, e.g. the page permissions of a backend user
  • the result is ordered depth-first by the “sorting” of the pages, with the level of each page, optionally with the full page records

The backend parts listed above use the new repository. Measured with 780 pages: PageTreeRepository::getFlattenedPages() needs 2 instead of 6 queries live and 5 instead of 130 in a workspace, WorkspaceService::getTreeUids() and the Extbase storage pids 1 instead of 907 / 905 queries. Extbase no longer returns the uids of workspace versions as storage pids.

Frontend usages (PageRepository::getDescendantPageIdsRecursive(), with mount points and extendToSubpages) are not changed yet.

Author Benni Mack
Created 11/11/26, 10:57
Updated 11/19/26, 08:41
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 13

#107369 Scrolling to level 3 in site settings does not work

See the screencast. If clicking on a link in level 3, the browser window is scrolled to this item but in the menu, this item is not selected

Author Georg Ringer
Created 09/01/25, 19:47
Updated 11/19/26, 09:50
Bug
New Fresh Site Handling, Site Sets & Routing TYPO3 CMS 13

#111504 PageContentErrorHandler returns HTTP 200 when error page cannot be resolved (InvalidRouteArgumentsException / SiteNotFoundException)

Category: Link Handling, Site Handling & Routing
TYPO3 Version: 13.4.x>
PHP Version: 8.3.x>

Description

If the page configured in errorContentSource cannot be resolved for the current request, the PageContentErrorHandler responds with HTTP status 200 instead of the configured error status code (e.g. 404).

Resolving the error page throws an InvalidRouteArgumentsException or a SiteNotFoundException. The handler does not fall back to a response with the expected status code, so the error is sent to the client as a regular, successful response.

Consequences:
  • CDNs / reverse proxies cache the error response as a valid page
  • Search engines index it (soft 404)
  • HTTP-based monitoring does not detect the error at all

Even if the cause is a misconfiguration, a handler configured for a specific error status must never answer with 200. Expected behaviour is a generic error response carrying the status code the handler was configured for (compare the reasoning in #103399).

Steps to reproduce

1. Site configuration:

errorHandling:
  - errorCode: 404
    errorHandler: Page
    errorContentSource: 't3://page?uid=<uid>'

2. Make the error page unresolvable for the request, e.g.: * <uid> lies outside the page tree of the site -&gt; SiteNotFoundException * <uid> is not available in the requested language -&gt; InvalidRouteArgumentsException<br>3. Request a non-existing URL: <code>curl -I <a href="https://example.org/<lang>/does-not-exist" target="_blank" rel="noreferrer">https://example.org/&lt;lang&gt;/does-not-exist</a></code></uid></uid>

Expected result

HTTP 404 (generic error content is acceptable), plus a log entry stating why the error page could not be resolved.

Actual result

HTTP 200, response body: <generic error output empty></generic>

Log / stack trace:

<stack trace from var/log>

Workaround

Custom error handler (errorHandler: PHP) that wraps PageContentErrorHandler, catches the exception, logs it and enforces the configured status code via $response->withStatus($statusCode).

Related

  • #103818 Streamline PageContentErrorHandler
  • #104828 config.contentObjectExceptionHandler sends 200 HTTP Status and regular cache headers
  • #103399 (fallback behaviour for unavailable error page content)
Author Mario Wilhelm
Created 11/19/26, 08:25
Updated 11/19/26, 08:25
Feature
Under Review Fresh Form Framework

#100022 Translate forms inside backend

As an editor, I want to translate my forms without:
1. customizing the YAML file or XLIFF files.
2. Create a copy of the form for the target language.

There should be a translate button, like for records. Whether this is better placed in the Form Manager or Form Editor would need to be clarified.
It is also open how the translations are saved. One could use the variants or a principle as with the site configuration.

Author Josua Vogel
Created 02/24/23, 10:28
Updated 11/19/26, 16:35
Bug
Under Review Fresh Workspaces TYPO3 CMS 13

#110114 Workspaces: moving a page into itself via its duplicate page-tree node creates a self-referential MOVE_POINTER (pid = t3ver_oid)

In a workspace, a page that has been moved is shown twice in the page tree — once at its original (live) position and once at its moved position. Dragging one representation into the other issues a “move page into itself”. The backend fails to reject this and writes a workspace MOVE_POINTER whose pid equals its own t3ver_oid. The page becomes its own parent, producing a rootline cycle (broken/looping page tree in the workspace, and a corrupt live tree on publish).

Preconditions

  • A workspace exists and the editor works inside it.
  • A page (here: live uid 12345) with move/edit permissions, located under some parent.

Steps to reproduce

1. Switch to a workspace.
2. In the page tree, drag page 12345 to a different parent (a normal, valid move). The page now appears twice in the tree: at its original position and at the new position.
3. Drag the moved representation back and drop it inside the other representation of the same page.
4. Confirm the move in the dialog.

Expected

The move is rejected — as it already is in the Live workspace, and as normal drag & drop prevents dropping a node into itself or its own subtree.

Actual

A self-referential workspace version is written.

Effective command: cmd[pages][12345][move] = 12345.

Resulting row:

uid pid t3ver_oid t3ver_wsid t3ver_state deleted
12346 12345 12345 1 4 0

i.e. pid t3ver_oid 12345 (a MOVE_POINTER pointing the page under itself).

Impact

Rootline becomes cyclic. Symptoms: looping/broken page tree and recursion errors in the workspace; on publish the live page’s pid is set to itself, corrupting the live tree. See #110092 as well.

Root cause

Two independent gaps combine:

1. Page tree. A workspace-moved page is rendered as two distinct nodes sharing the same identifier (uid) but different __treeIdentifier (path) — PageTreeRepository resolves the MOVE_POINTER to the live uid with the moved pid (PageTreeRepository.php:336-344, :465-474), and node identity/keying is path-based (tree.ts:624-630, render repeat() key at tree.ts:746). The drag guard only blocks on object identity or the target’s positional parents:

// Build/Sources/TypeScript/backend/tree/tree.ts (handleNodeDragOver), ~938-955
if (this.draggingNode == targetNode) { … return true; }
if (targetNode.__parents.includes(this.draggingNode.identifier)) { … return true; }

Dragging one representation onto the other passes both checks (different objects; the original-position node does not list its own uid as a parent), so a MOVE is armed.

2. DataHandler. The only server-side cycle guard is destNotInsideSelf(), but in moveRecord() it is called with the workspace version uid as source, not the live uid:

// typo3/sysext/core/Classes/DataHandling/DataHandler.php
$sourceUid = (int)($workspaceRecord[‘uid’] ?? $liveRecord[‘uid’]); // ~4413
…
if (!$this->destNotInsideSelf($updateFields[‘pid’], $sourceUid)) { // ~4470 -> uses version uid
… // rejected
}

A freshly created version uid never appears in the live rootline, so destNotInsideSelf() (definition at :7572) walks up the destination rootline and never matches → the move is wrongly accepted. In the Live workspace $sourceUid is the live uid and the same check correctly rejects the move ($destinationId === $id).

Suggested fix

  • Primary (server-side, covers every entry point): pass the live uid to the guard in moveRecord(). This also fixes the “move into a real descendant in a workspace” variant.
  • Secondary (page tree, optional hardening): in the page-tree drag guard, treat nodes with the same identifier as the same page (compare identifier, and include the dragged node’s own uid when testing the target’s rootline), and/or avoid rendering a moved page as two nodes.

Notes

The identical corrupt state is also reproducible via cut → “Paste into” the page itself in a workspace (the context menu’s canBePastedInto() and SimpleDataHandlerController::setPasteCmd() perform no self/subtree check and rely on the same broken server guard). A fix in destNotInsideSelf()/@moveRecord()@ closes all of these at once.

Author Philipp Kitzberger
Created 06/26/26, 14:29
Updated 11/14/26, 16:02
Task
Under Review Fresh Backend User Interface TYPO3 CMS 14

#111442 One notification for all deleted files instead of one for each

Instead of rendering a huge pile of notifications, one should be enough for all deleted files. If a file cannot be deleted for some reason, show a separate notification for all the failed ones.

Optional: maybe also use the js notifications instead?

steps to reproduce

  • go to media module
  • go into a folder with lots of files
  • select a lot of files
  • delete them
Author Simon Schaufelberger
Assigned to Simon Schaufelberger
Created 11/13/26, 20:08
Updated 11/14/26, 16:00
Feature
Author Oliver Bartsch
Assigned to Oliver Bartsch
Created 10/07/26, 21:15
Updated 11/01/26, 22:14
Bug
Under Review Quiet TYPO3 CMS 14

#107576 RecordProvider::$record may be null on system root pages

RecordProvider::$record should always be an (probably empty) and never null.

Author Elias Häußler
Assigned to Elias Häußler
Created 10/01/25, 10:03
Updated 10/02/26, 06:59
Bug
Under Review Stale Site Handling, Site Sets & Routing TYPO3 CMS 13

#110550 SiteSettingsService::writeSettings() silently swallows SiteConfigurationWriteException

Bug Description

SiteSettingsService::writeSettings() silently catches SiteConfigurationWriteException internally and never re-throws it. As a result, callers have no way to detect whether a write succeeded or failed.

Root Cause

In EXT:core Classes/Site/SiteSettingsService.php, writeSettings() calls SiteWriter::writeConfiguration() inside a try/catch block that catches SiteConfigurationWriteException, enqueues a flash message, and returns — silently discarding the exception.

try {
    $siteWriter->writeConfiguration($mergedSettings, $site->getIdentifier());
} catch (SiteConfigurationWriteException $e) {
    $flashMessage = GeneralUtility::makeInstance(
        FlashMessage::class,
        $e->getMessage(),
        '',
        ContextualFeedbackSeverity::ERROR,
        true
    );
    $flashMessageService = GeneralUtility::makeInstance(FlashMessageService::class);
    $flashMessageService->getMessageQueueByIdentifier()->enqueue($flashMessage);
    // exception is swallowed — no rethrow
}

Flash messages are invisible in CLI and API contexts. Callers are forced to verify writes by re-reading the settings file, which is fragile.

Affected Versions

Verified in:
  • TYPO3 13.4 (LTS)
  • TYPO3 14.3
  • TYPO3 main (future 15.x)

Expected Behavior

SiteSettingsService::writeSettings() should re-throw SiteConfigurationWriteException after enqueuing the flash message, so callers can handle write failures.

Proposed Fix

Add throw $e; after enqueuing the flash message:

} catch (SiteConfigurationWriteException $e) {
    $flashMessage = GeneralUtility::makeInstance(
        FlashMessage::class,
        $e->getMessage(),
        '',
        ContextualFeedbackSeverity::ERROR,
        true
    );
    $flashMessageService = GeneralUtility::makeInstance(FlashMessageService::class);
    $flashMessageService->getMessageQueueByIdentifier()->enqueue($flashMessage);
    throw $e; // re-throw so callers can handle the failure
}

Note: In TYPO3 main (v15), FlashMessage is final, so new FlashMessage(...) replaces GeneralUtility::makeInstance().

I will create a patch for this.

Author Simon Schmidt
Created 08/28/26, 05:19
Updated 09/15/26, 10:07
Bug
Under Review Stale FormEngine aka TCEforms TYPO3 CMS 14

#110192 Undefined array key in FormFlexAjaxController::containerAdd() on new records

Summary

Adding an item to a FlexForm `section/container` field fails on a new, unsaved record when the field’s data structure is resolved per-CType via `ds_pointerField`. `FormFlexAjaxController::containerAdd()` resolves the structure via `databaseRow.CType`, which is never populated for new records, so it falls back to the generic “default” structure – missing the CType-specific fields, hence the warning. No dot-notation needed to reproduce, so this is independent of the accordion fix already merged for #109727.

Steps to reproduce

Register a new `tt_content` CType with its own FlexForm data structure via the classic `ds_pointerField` pattern:

$GLOBALS['TCA']['tt_content']['columns']['pi_flexform']['config']['ds_pointerField'] = 'CType';
$GLOBALS['TCA']['tt_content']['columns']['pi_flexform']['config']['ds']['my_ctype'] = 'FILE:EXT:my_ext/Configuration/FlexForms/MyFlexForm.xml';
where MyFlexForm.xml defines a
with at least one <container> (e.g. a repeatable link field) – identifier without any dot, e.g. just <section>. Then: <ol> <li>Create a new `tt_content` record with `CType = my_ctype`, don’t save.</li> <li>Click “Add” on the section field.</li> </ol> <p><strong>Expected</strong> : new container item added.</p> <p><strong>Actual</strong> : uncaught promise rejection in console; PHP warning Undefined array key “<fieldname>“ at `FormFlexAjaxController.php:94`.</fieldname></p> <p><strong>Workaround</strong> : save the record once, then it works.</p> <h2>Root cause</h2> <p>Compared the actual installed code of the same project on v12.4 vs. v14: in v12.4, the client sends an already-resolved dataStructureIdentifier (computed while CType was still known), and the controller force-sets it into `$processedTca` via `FlexFormTools::parseDataStructureByIdentifier()` before compiling – so `databaseRow.CType`never matters. In v14, this mechanism was removed on both JS and PHP side; resolution now depends solely on `databaseRow.CType`, which stays empty for new records. Looks like an unintentional v12→v14 regression, separate from the Bootstrap Collapse change (#109267) that caused the toggle issue in #109727.</p> <h2>Suggested fix</h2> <p>Seed `databaseRow[$typeField]` from the already-available recordTypeValue inside the `command === ‘new’` branch:</p> <p>
if ($command === 'new') {
    $formDataCompilerInput['databaseRow']['uid'] = $databaseRowUid;
    $typeField = $processedTca['ctrl']['type'] ?? null;
    if ($typeField !== null && $recordTypeValue !== '') {
        $formDataCompilerInput['databaseRow'][$typeField] = $recordTypeValue;
    }
}
</p></section></container>
Author Martina Kratky
Created 07/13/26, 11:12
Updated 09/09/26, 05:36
Task
Under Review Stale Code Cleanup TYPO3 CMS 15

#110685 Centralize hash usages

Author Benni Mack
Assigned to Benni Mack
Created 09/11/26, 23:08
Updated 09/11/26, 23:10
Bug
Under Review Stale TYPO3 CMS 13

#109750 RedirectLoginErrorHandler won't respect proper target UIDs SiteConfiguration

TYPO3 CMS v13 introduced TYPO3\CMS\Core\Error\PageErrorHandler\RedirectLoginErrorHandler (https://forge.typo3.org/issues/101252)
But when having multiple SiteConfigurations, the resulting URL for the RedirectResponse generated by the handleLoginRedirect() method will be generated with the wrong hostname / SiteConfiguration.

Imagine having multiple site configurations:

[1] Homepage (project.ddev.site)
    [2] Page 1
        [3] Page 1.1
        [4] Page 1.2
    [5] Page 2
        [6] Page 2.1
        [7] Page 2.2
        [8] Page 2.3
    [9] Page 3
[10] Centralized Login (login.ddev.site)
    [11] Dashboard (available after login)
    [12] Login
[13] Another Site (another.ddev.site)
    [14] Publicly accessible Page 1
    [15] Restricted Page 2
    [16] Restricted Page 3

Here’s the relevant SiteConfiguration (effective for all SiteConfigurations):

errorHandling:
    -
        errorCode: 403
        errorHandler: PHP
        errorPhpClassFQCN: 'TYPO3\CMS\Core\Error\PageErrorHandler\RedirectLoginErrorHandler'
        loginRedirectTarget: 't3://page?uid=12'
        loginRedirectParameter: 'redirect_url'

Now when trying to access [11] Dashboard (available after login) without a valid logged in frontend user session, RedirectLoginErrorHandler::handleLoginRedirect() will generate the proper URL to [12] Login (https://login.ddev.site/login).
But when trying to access [15] Restricted Page 2 without a valid logged in frontend user session, RedirectLoginErrorHandler::handleLoginRedirect() will wrongly generate the URL to [12] Login by using the hostname of the current request, instead of the hostname of the login page, resulting in https://another.ddev.site/login instead of https://login.ddev.site/login.

Author Moritz Ngo
Created 05/04/26, 09:12
Updated 09/11/26, 21:46
Bug
Under Review Quiet Site Handling, Site Sets & Routing TYPO3 CMS 13

#100934 Typolink soft reference parsers does not consider links to currrent page

… if format t3://page?uid=current is used.

This manifests itself in

  1. links to current page with wrong anchor are not reported as broken in linkvalidator, see #100933
  2. no reference index entries are created for links to current page (this is described below)
  3. …?

no reference index entries are created for links to current page

Reproduce

  1. create several links (see below) as page links, to current page, with anchor
  2. update the reference index
  3. check the database entries in the reference index

Expected result

The result should be the same whether t3://page?uid=current or t3://page?uid=<current page id> are used. So either it creates a reference index in both cases or it does not create one at all.</current>

Actual result

The result is not the same:

No reference index entries are created for the links to current page (of format t3://page?uid=current or t3://page?uid=current#<anchor>). You can search for them by using the CE id, e.g.</anchor>

select tablename,recuid,field,softref_key,softref_id,ref_table,ref_uid,ref_string from sys_refindex where tablename='tt_content' and (recuid=36 or recuid=37);

2 reference index entries are created for this link with target URL:

t3://page?uid=209#38
select tablename,recuid,field,softref_key,softref_id,ref_table,ref_uid,ref_string from sys_refindex where tablename='tt_content' and (recuid=38);
+------------+--------+----------+--------------+------------------------------------+------------+---------+------------+
| tablename  | recuid | field    | softref_key  | softref_id                         | ref_table  | ref_uid | ref_string |
+------------+--------+----------+--------------+------------------------------------+------------+---------+------------+
| tt_content |     38 | bodytext | typolink_tag | 1                                  | pages      |     209 |            |
| tt_content |     38 | bodytext | typolink_tag | d5747c9ecb74651c68d8215ed0c095ac:1 | tt_content |      38 |            |
+------------+--------+----------+--------------+------------------------------------+------------+---------+------------+

No reference index entries are created for this link with target URL:

t3://page?uid=current#38

No reference index entries are created for this link with target URL:

t3://page?uid=current

Source code

This seems to be due to TypolinkTagSoftReferenceParser::parse not considering links with the format t3://page?uid=current#99999999. The parser does not return the t3://page?uid=current links.

This also concerns TypolinkSoftReferenceParser.

code:

} elseif ($linkDetails['type'] === LinkService::TYPE_PAGE && preg_match('/page\?uid=(\d+)#?(\d+)?/', $matches[1], $pageAndAnchorMatches)) {
Author Sybille Peters
Created 05/31/23, 07:16
Updated 10/02/26, 11:56
Bug
Under Review Quiet Workspaces TYPO3 CMS 14

#110888 Workspaces module fails with TypeError for a deleted or missing page

Problem

In a workspace, opening the Workspaces module (“Publish”) with the id of a deleted page fails with

TypeError
TYPO3\CMS\Backend\Template\Components\DocHeaderComponent::setPageBreadcrumb():
Argument #1 ($pageRecord) must be of type array, null given

Other page modules (Page, List, Preview, Permissions) show their “no page selected” state for the same id. Once #107213 lets a missing page id pass the BackendModuleValidator like a deleted page, editors hit this right after deleting a page created in the workspace. The module state keeps its id, and the next switch to the Workspaces module opens the module with it.

Steps to reproduce

  1. In LIVE, delete a page (it is marked deleted=1).
  2. Switch to a workspace.
  3. Open the Workspaces module with the id of that page, for example through the module state (select the page before deleting it) or with the URL parameter id.

Expected: the module renders without a page breadcrumb, as for the root page.
Actual: TypeError.

Cause

ReviewController::handleRequest() reads the page with

$pageRecord = BackendUtility::getRecord('pages', $pageUid);
...
$view->getDocHeaderComponent()->setPageBreadcrumb($pageRecord);

getRecord() returns null for a deleted or missing page, and setPageBreadcrumb() requires an array. The call was introduced with the breadcrumb API in change “[TASK] Deprecate MetaInformation API” (14.0).

Proposed fix

$pageRecord = BackendUtility::getRecord('pages', $pageUid) ?? [];

Verified on 14.3.7 and main with a new functional test for ReviewController (deleted page, missing page). Without the change both fail with the TypeError, with the change both render. A patch against main follows on Gerrit (Releases: main, 14.3).

Author Georg Tiefenbrunn
Created 10/02/26, 11:29
Updated 10/02/26, 11:37
Bug
Under Review Quiet Workspaces TYPO3 CMS 13

#107213 Error when deleting a new page in a workspace

Description

If you create a page in a workspace and delete it (without ever publishing it), you will get a RuntimeException.

Exact error message:
#1289917924 RuntimeException
You don’t have access to this page

How to reproduce?

  1. switch to a workspace
  2. create a new page
  3. select the page in the page tree
  4. open the page properties
  5. delete the page

Thanks for the great work on TYPO3 and all the effort

Author George Miller
Created 08/06/25, 11:27
Updated 10/02/26, 11:37
Bug
Under Review Quiet TYPO3 CMS 14

#110897 Enable tool credits in AGENTS.md

Include AI assistance git trailers as documented
as a requirement for commit messages on:
https://docs.typo3.org/permalink/h2document:commit-messages-format

Author Benjamin Franzke
Created 10/02/26, 18:04
Updated 10/02/26, 18:30
Task
Under Review Quiet TYPO3 CMS 15

#111200 Give custom package resource definitions precedence over defaults

Package resource definitions from Configuration/Resources.php are currently evaluated after the default definitions.

Since resource lookup returns the first matching definition, a default definition can mask an explicit custom declaration for the same path or a subdirectory. This prevents packages from overriding the default resource configuration.

Evaluate custom resource definitions before defaults, so explicit declarations take precedence. Paths without a matching custom declaration continue to use the defaults

Author Matthias Vogel
Created 10/22/26, 10:24
Updated 10/22/26, 12:38

Showing results 401 to 425 of 1561