Showing results 176 to 200 of 1561

Task
New Fresh File Abstraction Layer (FAL) TYPO3 CMS 14

#107053 Allow renaming text-y files

Renaming a file like “test.txt” to “test.css” should be possible, if both the “old” and “new” MIME Types are allowed and valid.

Also renaming “test.css” back to “test.txt” should not fail due to MIME types.

Author Garvin Hicking
Created 07/07/25, 18:44
Updated 11/10/26, 19:02
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 12

#108376 Page linkbrowser should not link to content elements inside a non-linkable page

If a page/folder is one of the non-linkable types the Page link browser will not allow linking to that page record. It will however list the content elements in such a page (this happens for example with folder with news records. Content elements in News records will show up in the link browser in a News folder).
In frontend such links will end up as a 404 because the URL will link to the page with the content element as URL fragment. If the page/folder in non-linkable then content elements inside that page/folder should also be considered as non-linkable (at least for the Page link browser).

Solution: in \TYPO3\CMS\Backend\LinkHandler\PageLinkHandler::getRecordsOnExpandedPage() an early check if the active page record is non-linkable could result in an early return.

Author Jigal van Hemert
Assigned to Maike Kiebele
Created 12/02/25, 12:09
Updated 11/10/26, 18:48
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 13

#104540 Module-Menu and Page-Tree: some arrows point into the wrong direction for rtl-languages

Current state: RTL vs. LTR

Author Ayke Halder
Created 08/02/24, 13:14
Updated 11/10/26, 17:13
Bug
New Fresh TYPO3 CMS 14

#111397 ObjectAccess::isPropertyGettable(): Argument #1 ($object) must be of type object|array, null given

Hey,

i use the new file upload attribute within a model. The form, where it is integrated has some obligatory fields and the upload self. If one of the obligatory fields is not filled out, i get this error because the value of the argument is null but the function “isPropertyGettable” expects an array or object.

May to cath the null earlier in “FileHandlingService”?

Thank you

Author Andreas Pfeiffer
Created 11/10/26, 16:07
Updated 11/10/26, 16:07
Feature
New Fresh Backend API

#104672 (Deployable) Permission presets for extensions

Add option to define permission presets for extensions and apply them in UI of backend user group.

Gist wit example preset and a broken (syntax error) preset example:
Example permission preset: https://gist.github.com/sbuerk/14a7a8f8a1c05b99ff7c999a23fd988e

Author Tomek W
Created 08/20/24, 14:29
Updated 11/10/26, 13:35
Bug
Under Review Fresh TYPO3 CMS 10

#92353 TypoScript ObjectBrowser and TemplateAnalyzer include hidden records

The typoscript object browser module displays typoscript from hidden typoscript records.
If you override e.g. page.10.value with “test” in an hidden typoscript record, the object browser would display it as if the value is set.
In FE this override will be correctly ignored.

In the template analyzer module all hidden typoscript templates are displayed, even the hidden ones.
Maybe this is wanted, but the hidden typoscript templates are not marked as hidden.
If the templates should not be listed here, it is the same problem as in the object browser. If they should be listed but marked as hidden, it most likely is an other issue.

The templates are listed and parsed since $queryBuilder->setRestrictions($this->queryBuilderRestrictions); in web/typo3/sysext/core/Classes/TypoScript/TemplateService.php is set to ignore hidden check (backend visibility context).

This problem occurs in TYPO3 9 and 10.

Author Sebastian Müller
Created 09/21/20, 10:04
Updated 11/10/26, 13:03
Task
Under Review Fresh TYPO3 CMS 15

#110991 Register default frontend JavaScript directly

Protected email links and JavaScript window links register the default
frontend JavaScript. Exporting it to typo3temp reads the source and
hashes its contents on every registration, even when the exported file
already exists.

Register the packaged asset directly and let the existing resource
publisher generate its URL and apply modification-time cache busting.
This removes the source reads, content hashing and temporary export.
Disabling default JavaScript and merging asset attributes and options
continue to work as before.

Registration costs decrease as follows:

Registrations   Source reads      Time before / after
1 1 -> 0 37.73 / 0.48 us
20 20 -> 0 581.32 / 7.08 us
100 100 -> 0 2985.30 / 34.82 us

These timings cover registration, not the complete frontend request.
Peak allocations for repeated registration fall from 13,848 to 1,680
bytes. Rendering still checks file metadata for cache busting.

Author Wouter Wolters
Assigned to Wouter Wolters
Created 10/09/26, 16:40
Updated 11/10/26, 12:27
Feature
Author Benjamin Kott
Created 04/22/26, 19:06
Updated 11/10/26, 11:31
Feature
Under Review Fresh Backend User Interface

#111079 Add device preview with zoom and pan to the preview module

Problem

The module “Content > Preview” shows a page in a box of the chosen screen size, at 100 %:

  • A screen wider than the module, such as a desktop of 1440 or 1920 pixels on a laptop, does not fit. The box overflows, and the page cannot be seen as a whole at the width its breakpoints are made for.
  • The size changes with handles and number fields only; there is no zoom.
  • Without a preview (no page selected, no access, a folder, no site), the module shows one generic message for every reason.

Proposal

  • Show the page at the size of a device screen, zoomed to fit the module or at a fixed factor, so a wide screen keeps its breakpoints.
  • Navigate as in a design tool: Ctrl/Cmd with the wheel or a pinch zooms around the pointer, + and – step through the zoom levels, Ctrl/Cmd with 0 or 1 fits or shows 100 % over the preview; Space with a drag or the middle mouse button pans.
  • A toolbar with the screen sizes, the current size and the zoom. The custom size gets handles at both sides and at the bottom, by pointer and with the arrow keys.
  • A screen without a height shows the page in its full height. For this, a frontend middleware adds a small script to the page in the module, for a signed parameter that it removes before the site is resolved (no cHash, no page cache). The script sends its messages only to the backend origin that signed the parameter.
  • Without a preview, say why in place of the page and lead to the module that helps (Records, or the site configuration for administrators). The buttons of the document header stay, disabled.
  • The chosen size and zoom are stored per user.

Presets of mod.web_view.previewFrameWidths without a height show the page in its full height; the desktop presets the core ships no longer set one.

Related

  • Supersedes the resizing of #106197 (change 88260).
  • Builds on #111075 and #111078 for the disabled QR code button.
Author Benjamin Kott
Created 10/15/26, 11:35
Updated 11/10/26, 10:22
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 14

#110871 Visibility toggle reports wrong state for live records in a workspace

Problem

In a workspace other than LIVE, hiding a content element in the page module saves correctly, but the page module does not show it: the button stays on “Hide”, no hidden overlay appears. Only a reload shows the hidden state.

This only affects records that exist in LIVE and have no workspace version yet. Records created in the workspace and all records in LIVE update immediately.

Independently of workspaces, the icon in the element header is replaced by the generic default icon of the table (mimetypes-x-content-text for tt_content) and loses its title after every toggle, until the next reload.

Steps to reproduce

  1. Create a workspace and switch to it.
  2. Open the page module on a page with an existing content element (for example of type “Text & Images”) that has no workspace version.
  3. Click the “Hide” button of the element.

Expected: the element gets the hidden overlay, the button switches to “Unhide”.
Actual: nothing changes in the page module. The database contains a new workspace version with hidden=1, the live record stays hidden=0. After a reload the element is shown as hidden.

Additionally, in any workspace including LIVE: the element icon switches from mimetypes-x-content-text-picture to mimetypes-x-content-text and loses its title.

Cause

RecordListController::toggleRecordVisibilityAction() (AJAX route record_toggle_visibility) re-reads the record after the DataHandler run with

$row = BackendUtility::getRecord($table, $uid, $selectFields);
  1. getRecord() applies no workspace overlay. In a workspace, the DataHandler creates a new version for the live uid, but the re-read returns the unchanged live row. The response says "isVisible": true, and page-layout.js keeps the element visible.
  2. $selectFields only contains uid, pid and the hidden field (plus a few page fields for pages). The type field (ctrl.typeicon_column, CType for tt_content), the enable columns and the version fields are missing, so IconFactory::getIconForRecord() falls back to the default icon and the overlay is computed from incomplete data. The rendered icon also carries no title, unlike the icon the page module renders in GridColumnItem.

The page module calls this endpoint since #109498 (change 93551, “Avoid reloading on visibility-toggle of content element”). Before that, the toggle triggered a full reload through tce_db, which rendered the workspace state correctly and hid the wrong response. The same endpoint is used by recordlist.js (Records module) and inline-control-container.js (FormEngine inline records), so both are affected the same way.

Proposed fix

$row = BackendUtility::getRecordWSOL($table, $uid);
if ($row !== null) {
    $recordIcon = $this->iconFactory->getIconForRecord($table, $row, IconSize::SMALL)
        ->setTitle(BackendUtility::getRecordIconAltText($row, $table, false));

    $response['icon'] = $recordIcon->render();
    $response['isVisible'] = (int)$row[$hiddenField] === 0;
}

This replaces the $selectFields block. Reading the full row is a single record lookup, and the title matches what GridColumnItem and DatabaseRecordList set.

Verified on 14.3.7 with functional tests. Without the change, “hide a live record in a workspace” reports isVisible: true and “icon keeps type and title” gets mimetypes-x-content-text; with the change both pass. “Show it again” and “hide in LIVE” pass in both cases and guard against regressions. A patch against main with a functional test will follow on Gerrit (Releases: main, 14.3).

Author Georg Tiefenbrunn
Created 10/01/26, 11:04
Updated 11/10/26, 09:48
Task
Under Review Fresh Performance TYPO3 CMS 15

#111392 Resolve the site of a site root page without loading its rootline

Problem

SiteFinder::getSiteByPageId() loads the full rootline of the given page, even if the page itself is the root page of a site. The nearest site in the rootline of a site root is always the page itself, so the lookup is unnecessary.

This is expensive on installations with many sites: PageSlugCandidateProvider::getPagesFromDatabaseForCandidates() calls getSiteByPageId() for every candidate page, and each site root has the slug “/”. With a few hundred sites, a rootline is loaded for each of them on every frontend request.

SiteFinder::getSiteByPage() (added in #100378) still loads the rootline of the parent page for site roots below another page, e.g. nested sites.

Proposal

  • Return the site directly if the page is the root page of a valid site and neither a rootline nor a mount point parameter is given.
  • Skip the parent rootline in getSiteByPage() for site root pages.
  • Invalid sites, mount points and given rootlines keep their behaviour.

Note: a deleted page that is configured as site root is now resolved to its site, where RootlineUtility failed with a PageNotFoundException before.

Related to the large-site collection #93547 and #95690.

Author Alexander Schnitzler
Created 11/10/26, 07:38
Updated 11/10/26, 08:40
Task
Under Review Fresh Backend User Interface TYPO3 CMS 11

#93242 Remove language information in page + list module if no multilanguage site

If a site uses only 1 language, there is no benefit from displaying the language for every record. Removing flag + label leads to a cleaner backend

Author Georg Ringer
Assigned to Georg Ringer
Created 01/08/21, 09:03
Updated 11/09/26, 21:37
Bug
New Fresh Backend JavaScript TYPO3 CMS 13

#108611 Drag & Drop of folders not working in Filelist

This issue occurs in firefox. I tested it in chrome and it worked perfectly fine.
I could reproduce this in mutliple TYPO3v13.4 instances

Author Bastien Lutz
Created 01/09/26, 14:31
Updated 11/09/26, 20:33
Feature
Under Review Fresh scheduler

#83933 TableGarbageCollectionTask should have the option to check for > 0 in expirePeriod mode

Currently the TableGarbageCollectionTask correctly checks if the relevant time field is greater than zero in the expireField mode.

It should do this check also for the expirePeriod mode. We have several cases where we currently can not use the task because of this missing check. We have rows that should be deleted, for example, 30 days after the last hit, but not if it was never hit (last_hit = 0).
Using expireField is not possible here because we need to wait some time before deletion and using expirePeriod is also not possible because zero-values are not allowed to be deleted in our business-logic.

Best solution would IMHO be a setting in the task configuration of both modes, like deleteZeroValuedRows => {true, false} (each mode with the default of the current behaviour to not introduce a breaking change).

Author S P
Created 02/16/18, 09:07
Updated 11/09/26, 20:27
Bug
Under Review Fresh Frontend TYPO3 CMS 12

#106180 Building the local rootline fails to detect root systemplate if page has multiple template records

Situation:
For historical reasons there is a central “page” which is the parent of all web site roots in the installation.

"TYPO3 root" <- contains root sys_template record
 +- "Site 1" <- contains root sys_template record
 |  +- page 1
 +- "Site 2" <- contains root sys_template record

If “Site 1” contains a sys_template record with the “root” property set and one or more sys_template records without the “root” property set, building the local rootline may fail to detect the “root” property.
First an array is created with the “pid” as key and the sys_template as value. With multiple sys_template records in a page the second (and third) record will overwrite the first one. If only the first one has the “root” option set the page will not be recognized as root page.

One effect is that HMENU will not use that page as the root of the menu.

This happens in v12 in \TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::getFromCache(), in v13 in \TYPO3\CMS\Frontend\Page\PageInformationFactory::setLocalRootLine() (haven’t checked v14 yet)

The solution is to build $sysTemplateRowsIndexedByPid with an array of systemplateRows and loop through them to check $sysTemplateRowsIndexedByPid[$pageId]['root'] for each of the sys template rows.

Note: the pagetree structure is a bit non-standard but has been working since v 4.x. The multiple sys_template records per page are in this situation caused by virtual TS templates which are added by a AfterTemplatesHaveBeenDeterminedEvent listener

Author Jigal van Hemert
Created 02/14/25, 18:48
Updated 11/09/26, 20:12
Bug
New Fresh FormEngine aka TCEforms TYPO3 CMS 11

#96626 In TCA group fields the suggest wizard shows records in all languages

on searching I find records in all languages without a hint which record is in which language.

by setting the searchcondition

'myfield' => array(
        'config' => [
            'type' => 'group',
            'allowed' => 'tx_xyz',
            'foreign_table' => 'tx_xyz',
            'MM' => 'tx_mymm',
            'suggestOptions' => [
                'default' => [
                    'searchCondition' => '(type = 0) AND sys_language_uid = 0'
                ],
            ]
        ],
    ),

I can limit it to the default language. However there seems to be no way to limit the records to the language of the language of the current record. That would have to be something akin to `sys_language_uid = ###REC_FIELD_sys_language_uid###` however this marker is not available in the suggest wizard.

Furthermore it would be important to display the language of records in the suggest wizard.

You currently cannot see which language a record is from if the title is the same:

Author Lina Wolf
Created 01/24/22, 11:04
Updated 11/09/26, 11:30
Feature
New Fresh Backend User Interface

#94617 Introduce generic record preview / listing

Ideas by Benni Mack:

TYPO3 Backend uses various places where records are shown, in different ways. There are lots of issues with the rendering, as it is completely re-built on most places of TYPO3 Backend.

Some current places:

  1. Content Elements in Page Module
    • There is a standard renderer, and a possibility to also use custom renderers
    • Everybody needs to built their own renderer to e.g. resolve connected File References
    • Somehow it allows to link to the FormEngine, but only if the user has access to
  2. Record Listing
    • As known from the List module, this enables to show a record with flexible column view, but is not useful for e.g. tt_content because it does not respect the CType and relevant fields for each type. Same goes for pages and fields like “shortcut_mode” or “url” which are only relevant for a specific type
  3. Element Browser
    • The list is also used in a limited rendering in the Element Browser, but for e.g. tt_content records, it shows the infamous “[no title]” when dealing with e.g. plugins. It is not possible to modify the listing properly, especially for specific types.
  4. Workspaces Module
    • The list module shows sub-records (e.g. Inline Element), which DB list does not show, but at the same is not configurable at all.
  5. BE Users / Redirects
    • A custom listing is added, where functionality like listing / grouping needs to be re-implemented over and over again.
  6. Files
    • The DB list is sometimes used, but on the Filelist module it is not always in use.

This approach aims to unify the different renderings in various ways, allowing to standardize the output while starting to use Web Components / Custom Elements, which could / should be re-defined on a per-record and per-record-subtype basis.

Registration:

$GLOBALS['TCA']['tt_content']['types']['textpic']['display'] = [
    'small' => ['header'],
    'medium' => ['header', 'bodytext', 'asset']
    'large' => ['header', 'bodytext', 'asset'],
    'full' => ?
    'renderer' => MyRenderer::class
];

class RecordDisplayInterface {
    public function resolveColumns(string $table, array $row, string $displayMode): array
    // @todo: deal with JS includes
    public function render(string $table, array $row, string $displayMode): string
}

Display Modes:

  • small
  • medium
  • large
  • list

Actions:

  • select checkbox (Multiselection)
  • delete/hide
  • link to edit
Author Oliver Hader
Created 07/22/21, 13:29
Updated 11/09/26, 11:29
Bug
New Fresh Extbase TYPO3 CMS 11

#92777 TCA l10n_mode exclude (as well as allow language syncronisation bahviour) and bidirectional MM relations cause Extbase to use uidLocalized instead of UID from foreign side

in TYPO3 v10.4.9 when I use the following tx_csdummy_domain_model_product.php TCA

'items' => [
        'l10n_mode' => 'exclude',
        'config' => [
            'type' => 'select',
            'renderType' => 'selectMultipleSideBySide',
            'foreign_table' => 'tx_csdummy_domain_model_item',
            'foreign_table_where' => ' AND (tx_csdummy_domain_model_item.sys_language_uid IN (0,-1)) ORDER BY title ASC',
            'MM' => 'tx_csdummy_product_item_mm',
            ]
        ],

    ],

and in the tx_csdummy_domain_model_item.php TCA

'products' => [
        'l10n_mode' => 'exclude',
        'config' => [
            'type' => 'select',
            'renderType' => 'selectMultipleSideBySide',
            'foreign_table' => 'tx_csdummy_domain_model_product',
            'foreign_table_where' => ' AND (tx_csdummy_domain_model_product.sys_language_uid IN (0,-1)) ORDER BY title ASC',
            'MM' => 'tx_csdummy_product_item_mm',
            'MM_opposite_field' => 'items',
            ]
        ],  
    ],

it works in the default language as it should. But when I have both sites translated, something goes wrong.

For example I have porduct default (uid=1), product translated (uid=2), item default (uid=5) and item translated (uid=6).

A) If I save the product, then the uid of the translated product points to the default language uid of the item.

tx_csdummy_product_item_mm
uid_local  uid_foreign
1          5
2          5

B) If I save the item, then the uid of the translated item points to the default language uid of the product.

tx_csdummy_product_item_mm
uid_local  uid_foreign
1          5
1          6

With A I can’t see the related product in the english version of the item in frontend. With B I can’t see the related item in the english version of the product.

https://stackoverflow.com/questions/64678793/typo3-tca-l10n-mode-exclude-and-mm-relations

Author Marc Hirdes
Created 11/05/20, 11:11
Updated 11/09/26, 11:27
Task
New Fresh Backend API TYPO3 CMS 14

#109878 Add beuser session identifier to form protection

In case php is a long running process (FrankenPHP, RoadRunner…) the following flashmessage shows up:
“Validating the security token of this form has failed”

The session leaks to another user in this case. That’s why the message above is thrown.

For more details see:
https://github.com/ochorocho/typo3-frankenphp/blob/main/Patches/cms-core-form-protection-factory-session-aware-cache.patch

Author Jochen Roth
Created 05/26/26, 18:28
Updated 11/09/26, 11:21
Bug
New Fresh Backend User Interface TYPO3 CMS 12

#104072 The override modal table is not accessible.

The image preview is focusable via AT, but does not contain a label. Since it is mainly decorative, it could be hidden from AT.

Description

The image preview is focusable via AT, but does not contain an alternative text. Since it is mainly decorative, it could be hidden from AT.

Reproduction steps

Navigate to file List
Replace an image, which is already listed
Focus on first cell in table, where image is placed

Impact

Target group

visual

Severity

medium

Frequency

common

Definition of Done

WHEN I focus on first table cell the Image does not get announced AND there is no empty cell announced
Recommended solution

add image to cell, remove from focus with empty alt-text

References / WCAG 2.2 Reference

1.1.1. If non-text content is pure decoration, then it is implemented in a way that it can be ignored by assistive technology.

Prioritizing the removal of the issues found

must have

Screencast or Screenshot

Author Christian Rath-Ulrich
Created 06/12/24, 13:32
Updated 11/09/26, 10:59
Task
New Fresh Localization TYPO3 CMS 14

#109515 Semantic of labels in Constant Editor

During our Huddle this morning with the localization team, and while going through pending approvals for French translations on Crowdin, I found what I consider wrong translations, namely that constant editor labels such as:

EXT:backend/Resources/Private/Language/locallang.xlf:config.loginLogo

Logo: Replace the TYPO3 logo above the login form (e.g. fileadmin/images/login-logo.png, EXT:my_theme/Resources/Public/Images/login-logo.png, or //domain.tld/login-logo.png).

EXT:backend/Resources/Private/Language/locallang.xlf:config.loginLogoAlt

Logo Alt-Text: Define the alternative text used as the alt attribute for the custom login logo image.

were suggested in French as a call-to-action or an imperative verb rather than a description of what the constant is used for.

So to make it clear, it was -translated-/suggested in a way that it means “[Please] replace the TYPO3 logo…” and “[Please] define the alternative text”. My understanding with all my years working with TYPO3 is that a constant is defined as a <label>: <description> value.

the screenshot in the documentation sounds like a description, rather than a call-to-action:

Problems in the Core

First problem I found while reviewing the French suggestions was with

EXT:backend/Resources/Private/Language/locallang.xlf:config.loginFootnote

Footnote: Enter the text displayed on the login screen, for example to provide copyright information for the background image (e.g. background image © 2017 by John Doe) or a short description.

=> Clearly “enter” is a call-to-action, we cannot say as in the first two examples above that it’s some kind of description of the constant. Suggestion to rephrase to something like “Text to be displayed on the login screen, …” or “If set, this text will be displayed…”

Problems/conventions to be discussed

1. Do we agree on the meaning of the description text?
2. Should English verbs such as “Define […]” or “Replace […]” better be in the 3rd form? (Defines, Replaces)?
3. Shall we suggest to end the description with a period? (all the examples from EXT:backend have it, but the screenshot in the documentation does not).
4. Possibly more rules/clean-up to be thought of

I understand this will require time and effort to adapt, but it would help to have a consensus on those little tiny details so that translation work is easier and TYPO3 is even more polished.

If so, I would suggest to go through the various constant editor-related labels of EXT:backend first, and use this ticket as an umbrella ticket for future work.

Author Xavier Perseguers
Created 04/08/26, 13:14
Updated 11/07/26, 16:06
Feature
Under Review Fresh

#111050 Provide MCP server based on Action API

AI clients and agents use the Model Context Protocol (MCP) to discover and call tools of external systems. TYPO3 has no MCP server, so every functionality would have to be wrapped manually for AI clients.

Provide an MCP server in TYPO3 Core that exposes the actions of the Action API (#111046) as MCP tools, based on the internal AI tool provider (#111049):

  • JSON-RPC dispatching for the MCP methods initialize, tools/list and tools/call, extensible via tagged request and notification handlers
  • tools are listed with title, description, input and output schema and read-only, destructive and idempotent hints, filtered by the scopes granted to the caller
  • the server itself is implemented as an action (POST /typo3/api/mcp), so it is reachable over HTTP with the authentication of the Action API, including app tokens and OAuth provided by EXT:hub (#111047)
  • a CLI command mcp:serve serves MCP over stdio for local clients
  • a new scope mcp grants access to the MCP server

This way, any functionality provided as action becomes available to MCP clients without additional integration code

Author Benjamin Franzke
Created 10/14/26, 11:31
Updated 11/06/26, 16:49
Feature
Under Review Fresh

#111047 Provide authenticated access to the Action API for external applications

The Action API (#111046) is currently only reachable from within a logged-in backend session. External applications (scripts, integrations, MCP clients, AI agents) have no way to authenticate against it.

Introduce a new system extension EXT:hub that provides API access for external applications (“apps”), managed as sys_app records:

  • Static apps: An administrator creates an app bound to a backend user to impersonate and generates a static bearer token in the backend. The token stays valid until the app is disabled or its secret is changed.
  • OAuth apps: OAuth 2.0 authorization code flow (via league/oauth2-server) with refresh tokens. Backend users grant an app access to selected scopes on a consent screen at /typo3/oauth/authorize; tokens are issued at /typo3/oauth/token.
  • Authorization server metadata (RFC 8414) at /.well-known/oauth-authorization-server, allowing clients like MCP to discover the endpoints and supported scopes.
  • Requests to the Action API endpoints without a backend session are authenticated with the app’s token, and the action is executed in the context of the associated backend user.
  • A backend module “Integrations > Hub” lists and manages apps
Author Benjamin Franzke
Created 10/14/26, 11:08
Updated 11/06/26, 10:12
Bug
Under Review Fresh Database API (Doctrine DBAL) TYPO3 CMS 14

#111356 DriverResult::fetchOne() returns a stream for blob columns on pdo_pgsql

On PostgreSQL with pdo_pgsql, fetchOne() on a blob column (bytea) returns a PHP stream resource, while fetchAssociative() and the other array fetches return a string. On MySQL/MariaDB both return a string, so code that reads a single blob value behaves differently per database.

Steps to reproduce

  1. TYPO3 14.3 on PostgreSQL with the default pdo_pgsql driver (observed on 14.3.10 with PostgreSQL 16; DriverResult is identical on 13.4 and main).
  2. Store any value in sys_registry, e.g. GeneralUtility::makeInstance(Registry::class)->set('test', 'key', 'value').
  3. Read the column with fetchOne():
$qb->select('entry_value')->from('sys_registry')->where(...)->executeQuery()->fetchOne();
  1. Result: a stream resource. ->fetchAssociative()['entry_value'] on the same row returns the serialized string.

Expected

fetchOne() returns a string, like the array fetches and like on MySQL.

Cause

CustomPdoDriverResultMiddleware wraps pdo_* results in DriverResult. DriverResult::fetchOne() passes its value through mapResourceToString(), but that method only converts resources inside an array, so the single value of fetchOne() is returned unchanged. The middleware has no functional test for the conversion.

Proposed fix

Let mapResourceToString() also convert a resource passed as the record itself, and add a functional test that reads a blob column with fetchOne() and the array fetches. A patch follows on Gerrit.

Found while adding PostgreSQL support to an extension: https://github.com/netresearch/t3x-nr-vault/pull/495

Author Sebastian Mendel
Created 11/06/26, 07:23
Updated 11/06/26, 10:09
Bug
New Fresh Site Handling, Site Sets & Routing TYPO3 CMS 13

#106669 Route aspect fallback value gets removed if set to null

If you have added a route enhancer with an aspect that has a fallbackValue of null to your site configuration, it will be removed when you save the configuration in the backend later.

So, e.g. this:

routeEnhancers:
  Address:
    type: Extbase
    extension: TtAddress
    plugin: ListView
    routes:
      -
        routePath: '/{address-title}'
        _controller: 'Address::show'
        _arguments:
          address-title: address
    defaultController: 'Address::list'
    aspects:
      address-title:
        type: PersistedAliasMapper
        tableName: tt_address
        routeFieldName: slug
        fallbackValue: null

becomes to:

routeEnhancers:
  Address:
    type: Extbase
    extension: TtAddress
    plugin: ListView
    routes:
      -
        routePath: '/{address-title}'
        _controller: 'Address::show'
        _arguments:
          address-title: address
    defaultController: 'Address::list'
    aspects:
      address-title:
        type: PersistedAliasMapper
        tableName: tt_address
        routeFieldName: slug

And this of course leads to a completely different error handling…

Author Uwe Wiebach
Assigned to Oliver Bartsch
Created 05/08/25, 09:45
Updated 11/06/26, 10:04

Showing results 176 to 200 of 1561