Showing results 1 to 25 of 1561

Bug
Under Review Quiet CLI TYPO3 CMS 15

#109968 Command application loads all commands with incomplete Container

In some edge cases the \TYPO3\CMS\Core\Console\CommandApplication will try to load all registered commands, even if only the minimal fallback container has been initialized.

The issue can be reproduced by executing bin/typo3 dump in a Composer installation.

Observed errors

I’ve seen 3 different error messages during my tests:

> Too few arguments to function TYPO3\CMS\Core\Schema\TcaSchemaFactory::__construct(), 0 passed in typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 2884

> Uncaught TYPO3 Exception Too few arguments to function TYPO3\CMS\Core\Registry::__construct(), 0 passed in typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 2489 and exactly 2 expected thrown in file typo3/sysext/core/Classes/Registry.php in line 45

Both are caused by \TYPO3\CMS\Impexp\Import::fetchStorages() which is called in the constructor.

> No TCA schema exists for the name “sys_redirect”.

This one is caused by the \TYPO3\CMS\Redirects\Command\CleanupRedirectsCommand which depends on the \TYPO3\CMS\Redirects\Repository\RedirectRepository which tries to fetch the sys_redirect TCA schema in its contructor.

The hidden error

Both errors mask the actual error message that should be displayed because the command is disabled in a Composer environment.

> The command “dumpautoload” does not exist.

This happens due to the alias resolution in the Command Application and Symfony Console’s error handling:

  • First it checks, if a full boot is needed, since the alias is not known, it assumes it is
  • In a later check the real command dumpautoload has been resolved and a full boot is no longer required. This means the TCA will not be initialized
  • The dumpautoload command is not enabled in Composer environments. Therefore Symfony will fail with a \Symfony\Component\Console\Exception\CommandNotFoundException
  • During the Failure, Symfony will load all commands to show more information to the user
  • This will crash for commands of which the constructor depends on a fully available Container / TCA

Possible solutions

  • Make sure the container is fully initialized, if the command is not available (current Patch)
  • Alternative 1: Fix the underlying issues by making the Command Constructors more robust and not rely on TCA functions
  • Alternative 2: Remove fallback logic that boots the container without loading TCA -> uses can not rely on aliases, the full command must be used
Author Alexander Stehlik
Created 06/02/26, 22:53
Updated 10/02/26, 07:01
Task
Under Review Stale Content Security Policy TYPO3 CMS 13

#108396 Auto remove CSP directive upgrade-insecure-requests in report header

Set the upgrade-insecure-requests directive for a site and have the CSP reporting feature active, then you get an error in the browser console:

The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.

CSP Config config/sites/<my-site>/csp.yml</my-site>

inheritDefault: true
mutations:
  - mode: set
    directive: upgrade-insecure-requests

Enable both CSP Headers:

    'SYS' => [
        'features' => [
            'security.frontend.enforceContentSecurityPolicy' => true,
            'security.frontend.reportContentSecurityPolicy' => true,
        ],
    ],

I propose to automatically remove this directive for the report-only CSP header.

Author André Buchmann
Created 12/04/25, 10:58
Updated 09/14/26, 08:47
Bug
Under Review Quiet Linkvalidator TYPO3 CMS 13

#100933 Checking internal links to current page with missing anchor is not reported as broken link

This is reported as broken link (assuming CE #999999999 does not exist on page 27):

<p><a href="t3://page?uid=27#999999999">link to another page with missing anchor</a></p>

This is not reported as broken link (assuming CE #999999999 does not exist on current page):

<p><a href="t3://page?uid=current#99999999">link to current page with missing anchor</a></p>

Reproduce

  1. Create a content element (e.g. textmedia) with a link to the following url: t3://page?uid=current#99999999 (add a number of a ce which does not exist)
  2. in Linkvalidator module: Perform link checking
  3. look at the list of broken links: the link should be reported as broken

Versions

  • reproducible with latest main (14.0.0-dev, Apr 6, 2025)
  • 11.5 (latest)

More context

Another issue has been created for the more general problem in the softref parser: #100934

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

So it looks like not an error in linkvalidator, but an error in the link parser.

code:

} elseif ($linkDetails['type'] === LinkService::TYPE_PAGE && preg_match('/page\?uid=(\d+)#?(\d+)?/', $matches[1], $pageAndAnchorMatches)) {

https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/DataHandling/SoftReference/TypolinkSoftReferenceParser.php

Author Sybille Peters
Created 05/31/23, 06:20
Updated 10/02/26, 11:56
Bug
Under Review Quiet Backend User Interface TYPO3 CMS 14

#110118 Layout module language comparison: horizontal scrollbar is unreachable on tall grids

In the Layout module Languages → Language comparison view, the grid (.t3-grid-container) scrolls horizontally via overflow-x: auto, so the scrollbar sits at the bottom of the grid element. When a page has many languages (grid wider than the viewport) and enough content that the grid is taller than the viewport, the horizontal scrollbar ends up far below the fold.

To scroll the comparison to the right, a user has to scroll all the way down to reach the scrollbar, scroll right, then scroll back up to read the content.
Shift + mouse wheel works but is not discoverable.

Steps to reproduce

1. Configure a site with more than ~4 languages.
2. Open a page with several translations and several content elements in the Page module.
3. Switch to Language comparison and select All languages, so the grid is both wider and taller than the viewport.
4. Try to scroll the comparison horizontally.

Expected: horizontal scrolling should be possible without leaving the current vertical position. The scrollbar should stay reachable (e.g. pinned near the bottom of the viewport).

Author Amir Arends
Created 06/29/26, 07:58
Updated 10/02/26, 13:20
Task
Under Review Quiet TYPO3 CMS 13

#110900 Incorporate TYPO3 Association recommendation for commit sign-off

See
https://news.typo3.com/article/typo3-association-board-meeting-protocol-8-july-2026/board-statement-on-gpl-and-ai-code

> Official Board Recommendation
> The Board does, however, recommend that the responsible teams evaluate
> a lightweight per-commit sign-off in the form of a Developer
> Certificate of Origin. This sign-off is distinct from the author’s name
> and email that Git records in every commit. The author field is an
> identity attribution and carries no legal representation, whereas a
> Developer Certificate of Origin sign-off is a deliberate Signed-off-by
> line that affirms the published text of the certificate, by which the
> contributor certifies the right to submit the contribution under the
> project’s license. A sign-off therefore makes the contributor’s
> provenance representation explicit and auditable, which is of
> particular value in exactly the cases the Best Practices Team raises,
> where contaminated third-party material may have entered a contribution
> unnoticed. This is a recommendation to consider, not a precondition
> for the position stated here.
>
> This allocation applies equally to the Core and to extensions. Where a
> contributor cannot or will not stand behind the provenance of a
> contribution, that contribution should not be merged.

Author Benjamin Franzke
Created 10/02/26, 18:14
Updated 10/02/26, 18:30
Task
Under Review Quiet Backend User Interface TYPO3 CMS 13

#108748 Distinct actions for checkbox and dropdown

As a backend user I’d expect clicking the “select all” checkbox to select all (toggles) records immediately while the dropdown opens the options. Compare this with Gmail where the checkbox selects all emails and the dropdown icon opens the options.

Author Simon Schaufelberger
Created 01/23/26, 15:25
Updated 10/22/26, 15:47
Bug
Under Review Quiet TYPO3 CMS 13

#107434 TcaSchemaFactory::has(): Argument #1 ($schemaName) must be of type string, int given in EditDocumentController

TYPO3\CMS\Core\Schema\TcaSchemaFactory::has(): Argument #1 ($schemaName) must be of type string, int given, called in /www/htdocs/xxxx/my-domain.de/typo3_src-13.4.18/typo3/sysext/backend/Classes/Controller/EditDocumentController.php on line 2108

Author Nikita Hovratov
Created 09/11/25, 11:08
Updated 10/22/26, 16:32
Feature
Under Review Fresh

#111102 Introduce enums and content detection for image formats

Problem

Image formats, their file extensions and their media types are passed around as strings. Every place that maps one to the other keeps a list of its own, for example GraphicsCanvas (GIFBUILDER, install tool) and the FileContentParser of Indexed Search, which handles jpg, jpeg and tif by hand.

The format of a file is taken from its name, so an image with a misleading file extension is handed to the wrong decoder.

Proposal

  • Introduce the enums Format, FileExtension and MediaType in TYPO3\CMS\Core\Imaging. Each creates the others, ignoring case and a leading dot; Format::isLossy() tells whether a format is written with a quality.
  • Introduce FormatDetector, which tells the format of a file from its content, without ImageMagick and without ext-fileinfo.
  • Use them in GraphicsCanvas, which then loads images by their content, and in the FileContentParser of Indexed Search, which tells JPEG and TIFF images by their format.
Author Benjamin Kott
Created 10/17/26, 00:43
Updated 11/09/26, 00:31
Feature
Under Review Fresh FormEngine aka TCEforms

#102239 Set default values for FlexForm fields

Hi,

I’m trying to set a default value for a flexform field, but I don’t think it is currently possible, is it?

I tried using TCAdefaults with the syntax described here: https://docs.typo3.org/m/typo3/reference-tsconfig/main/en-us/PageTsconfig/TceForm.html but I think this only applies to TCEFORM and not TCAdefaults?
If this would work with TCAdefaults, how would it work with flexform sections? I tried to change a label for a field in a flexform section via TCEFORM but didn’t succeed.

Best regards
David

Author David Mellen
Created 10/24/23, 07:54
Updated 11/09/26, 10:56
Bug
Under Review Fresh Locking / Session Handling TYPO3 CMS 8

#72074 FileLockStrategy fails on NFS folders

FileLockStrategy assumes it can always lock exclusively but fails on NFS mounts (example: vagrant environment). There should be a check that exclusive lock is possible before the capability is reported.

The result of the error is the exception:

#1294586098: Could not acquire access lock for "pagesection""

RuntimeException thrown in file
/home/***/vendor/typo3/cms/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php in line 4921.

7 TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::acquireLock("pagesection", "1::")

/home/***/vendor/typo3/cms/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php:
02357:             // but we protect the access again with a global exclusive lock to avoid race conditions
02358: 
02359:             $this->acquireLock('pagesection', $this->id . '::' . $this->MP);
02360:             //
02361:             // from this point on we're the only one working on that page ($key)
Author Dmitry Dulepov
Created 12/06/15, 12:56
Updated 11/11/26, 08:59
Bug
Under Review Fresh Extbase + l10n TYPO3 CMS 10

#65859 Support l10n_mode in extbase

Intro

Currently extbase lacks support for l10n_mode.

See #62921 for a lengthy discussion of the background. From my point of view support for l10n_mode must explicitly be enabled/added in extbase, that’s why I duplicated #62921 here.

Use Case

As Developer I want to be able to assign a relation on a record in the default translation that must not be changed in the translation of the record.
When I set l10n_mode=exclude in $TCA
When I use the \TYPO3\CMS\Extbase\Persistence\QueryInterface to lookup records by a category
Then I expect to find translated records in the Frontend

//$TCA
'faculty' => array(
            'exclude' => 0,
            'l10n_mode' => 'exclude',
            'l10n_display' => 'hideDiff,defaultAsReadonly',
            'label' => 'LLL:EXT:luhjobs/Resources/Private/Language/locallang_db.xlf:tx_luhjobs_domain_model_vacancy.faculty',
            'config' => array(
                'type' => 'select',
                'foreign_table' => 'tx_luhjobs_domain_model_faculty',
                'foreign_table_where' => 'AND tx_luhjobs_domain_model_faculty.sys_language_uid IN (-1,0)',
                'items' => array(
                    array('',''),
                ),
                'minitems' => 1,
                'maxitems' => 1,
            ),
        ),
// QueryInterface
$constraints[] = $query->equals('faculty', $uid);
// resulting SQL(relevant parts only) in case of Frontend with ?L=1
tx_luhjobs_domain_model_vacancy.type = '19' AND tx_luhjobs_domain_model_vacancy.intern = 0
)
AND
(
    tx_luhjobs_domain_model_vacancy.sys_language_uid IN (1,-1)
    OR
    (
        tx_luhjobs_domain_model_vacancy.sys_language_uid=0 AND tx_luhjobs_domain_model_vacancy.uid NOT IN
            (
                SELECT tx_luhjobs_domain_model_vacancy.l10n_parent FROM tx_luhjobs_domain_model_vacancy WHERE tx_luhjobs_domain_model_vacancy.l10n_parent>0 AND tx_luhjobs_domain_model_vacancy.sys_language_uid=1 AND tx_luhjobs_domain_model_vacancy.deleted=0
            )
    )
)

This does miss the translated records as they have faculty=0 due to the l10n_mode=exclude setting in $TCA

Author Peter Niederlag
Created 03/20/15, 09:41
Updated 11/11/26, 09:13
Task
Under Review Fresh Backend User Interface TYPO3 CMS 15

#108358 Display warning for orphaned CEs when l10n_parent refers to a record with sys_language_uid = -1

When a default language record that has translations is switched to “All Languages” (sys_language_uid = -1), its translated records remain in the database but lose a valid parent reference.

Since records with sys_language_uid = -1 cannot serve as translation parents, the related translations become orphaned. TYPO3 currently does not warn about this inconsistent state, and the language “All” record is shown instead of the translation in the frontend.

TYPO3 should detect and mark such orphaned translations with a clear warning, similar to how mixed-mode inconsistencies are highlighted when l10n_parent is invalid.

Steps to reproduce:

  1. Create a content element in the default language.
  2. Translate it into another language.
  3. Change the default record’s sys_language_uid to -1 (“All Languages”).
  4. The translation remains in the database but references an invalid l10n_parent.

Expected result:
TYPO3 should display a backend warning or visual indicator for these orphaned translation records, as their parent is no longer valid.

Author Eric Harrer
Assigned to Eric Harrer
Created 11/28/25, 12:16
Updated 11/11/26, 10:33
Bug
Under Review Fresh Fluid TYPO3 CMS 12

#107347 pageType can't be reset with UriBuilder and link viewhelpers

f:link.action and f:uri.action ignore any pageType=0 argument.
This leads to core using the current page type.

This is a problem for instance in RSS feeds, like the one from TER
https://git.typo3.org/services/t3o-sites/extensions.typo3.org/ter/-/blob/develop/extensions/ter_fe2/Resources/Private/Templates/Extension/ListLatest.html?ref_type=heads

The RSS feed shall contain links to the default pageType, but all links are generated using the current pageType (the one for the RSS feed).

Author Markus Klein
Assigned to Markus Klein
Created 08/28/25, 20:45
Updated 11/11/26, 10:34
Task
Under Review Fresh TYPO3 CMS 14

#108712 Avoid deprecated xlink:href namespace in svg use tags

<use xlink:href="…"> is deprecated and <use href="…"> shall
be used instead, see:
https://developer.mozilla.org/en-US/docs/Web/SVG/Reference/Attribute/xlink:href

Author Benjamin Franzke
Created 01/21/26, 12:17
Updated 11/11/26, 11:05
Bug
Author Ayke Halder
Created 11/10/25, 23:47
Updated 11/11/26, 13:10
Task
Under Review Fresh Backend User Interface TYPO3 CMS 14

#106144 Improve accessibility of record-list by adding row-headers

Author Ayke Halder
Created 02/10/25, 15:43
Updated 11/11/26, 13:40
Task
Under Review Fresh Backend User Interface TYPO3 CMS 14

#110117 Layout module "All languages" comparison selection is lost when the available languages change (navigation / creating a translation)

Selecting “All languages” in the page-module language comparison is saved as a fixed list of language IDs instead of an “all” intent, so the selection is lost (shrinks) when navigating to a page with more translations, or when creating a new translation.

Expected: “All languages” should keep meaning all languages of the current page.

Author Amir Arends
Created 06/29/26, 06:26
Updated 11/11/26, 14:46
Task
Under Review Fresh Localization TYPO3 CMS 14

#108145 Consolidate Clipboard labels

Clipboards are being used in the Content > List module and the Media > Filelist module.

Their labels are found in core.core with the `cm.`, messages in with the `mess.` prefix, but not all messages are clipboard related. Some labels have the `cliptabs-` prefix.

Author Lina Wolf
Assigned to Lina Wolf
Created 11/16/25, 06:28
Updated 11/11/26, 16:16
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 14

#107770 Improve positioning code of page modules page-column-header actions

Author Ayke Halder
Created 10/17/25, 16:11
Updated 10/17/25, 16:41
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 13

#107769 Improve accessibility of the view module menubar

The menubar is missing aria role attributes for itself and its items.

Also the menus keyboard interactions should be implemented via JS.

See https://www.w3.org/WAI/ARIA/apg/patterns/menubar/#keyboardinteraction

Author Ayke Halder
Created 10/17/25, 15:43
Updated 10/17/25, 15:44
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 11

#92684 Form input fields in the search detail page have insufficient color contrast and focus style

Pages/Tasks
  • Search
Affected WCAG 2.1 Success criterions
  • 1.4.11 Non-Text Contrast (WCAG 2.1) AA
  • 2.4.7 Focus Visible AA
Affected components
  • Text input
  • Select

Description
The form inputs and selects at the search detail page (choose “Show all” in search or activate search fields on page view) have an insufficient contrast ratio of 1.8:1 (border color: #BABBBA, background color #F9FAF9), see WebAIM Color Contrast Checker.

When focussed, the elements get a subtle box-shadow and the border-color changes from #BABBBA to #AAAAAA, which is an insufficient contrast change from 1.2:1, see WebAIM Color Contrast Checker.

Recommendation
To fulfill the minimum contrast ratio for form inputs, implement the following:

  • increase the contrast ratio of the border color for the form inputs and selects to a minimum value of 3:1.
  • increase the contrast ratio of the border color for the focussed form inputs and selects to a minimum value of 3:1

#tas2020

Author Jakob Widhalm
Created 10/22/20, 18:22
Updated 10/13/25, 15:10
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 11

#92671 Form elements have insufficient color contrast and insufficient focus style

The form inputs and selects in the Edit section have an insufficient contrast ratio of 2.37:1 (border color: #6DAAE0, background color #FAFAFA), see WebAIM Color Contrast Checker

The elements get a subtle box-shadow and the border-color changes from #6DAAE0 to #4392D7, which is an insufficient contrast change from 1.33:1, see WebAIM Color Contrast Checker

.has-change .form-control {
  border: 1px solid #6daae0;
}

.has-change .form-control:focus {
  border-color: #4392d7;
}

*Recommendation:*
To fulfill the minimum contrast ratio for form elements, implement the following:

  • Increase the contrast ratio of the border color for the form elements to a minimum value of 3:1.
  • Increase the contrast ratio of the border color for the focussed form to a minimum value of 3:1.
Author Mylene Kreiger
Created 10/22/20, 13:32
Updated 10/13/25, 15:10
Feature
New Orphaned Security

#107582 Reduce need to enter MFA using trusted devices

One of my client suggests that it should be possible to reduce the number of times MFA is asked [when doing Backend authentication] by only asking it something like once every 30 days on devices/browsers that have been authenticated once.

Rationale is that Microsoft 365 is doing that and that must certainly be fine security-wise.

What do you think of this? Has it already been considered? Is there possibly a solution I’m not aware of?

me: created the ticket in TYPO3 on behalf of that client, aware of the fact that a password manager usually makes MFA transparent

Author Xavier Perseguers
Assigned to Oliver Hader
Created 10/01/25, 16:06
Updated 10/01/25, 16:06
Bug
New Orphaned Caching TYPO3 CMS 13

#107564 Cache is not emptied for scheduled records other than tt_content

If I use e.g. a news record which should show up at 16:00, and the page(s) where the news is shown is rendered with a 7 day cache lifetime, the cache is not refreshed at 16:00 today.

Consider this news might be shown on multiple pages, or it is an address record scheduled for tomorrow. The news post will not show up naturally but only if an editor or somebody else actively invalidates the cache.

The PSR-14 event ModifyCacheLifetimeForPageEvent does not cut it, because when doing a SQL query, you never know which records you DON’T get from the DB query.

Author Benni Mack
Created 09/30/25, 05:58
Updated 09/30/25, 05:58
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 12

#100515 Ensure table contents are vertically centered

Author Benjamin Kott
Created 04/06/23, 13:13
Updated 09/26/25, 10:59

Showing results 1 to 25 of 1561