Showing results 301 to 325 of 1561

Bug
Needs Feedback Stale Backend User Interface TYPO3 CMS 13

#108443 Modal alert for required fields doesn’t name the affected field or tab

*Description*
The modal alert shown for missing required fields is too generic: it does not mention the specific field nor its tab. With multiple errors, neither the count nor an overview is provided, making corrections cumbersome.

Reproduction Steps
  1. Open a backend form with at least one required field.
  2. Leave at least one required field empty.
  3. Trigger “Save.”
  4. Observe the modal alert: message is generic, without field/tab names.
Impact
  • Increased time to fix, as users must search for the failing field.
  • Risk of incomplete or incorrect data remaining.
  • Poor UX, especially in forms with many tabs/fields.
Recommended Solution
  • Extend the validation collector to gather context: for each failing required field, determine field label and tab label.
  • Message logic:
    > * Exactly one error → include field and tab by name in the modal.
    > * Multiple errors → include the error count n and optionally provide a list/link to an error overview.
Definition of Done
  • For a single error, the modal names the exact field label and tab.
  • For multiple errors, the count n is shown; optionally provide a list or navigation hint.
Acceptance Criteria
  • Saving with exactly one empty required field shows: “Please correct the required field ‘{FieldLabel}’ in tab ‘{TabName}’.”
  • Saving with multiple empty required fields shows: “There are n required fields incomplete.
Author Christian Jung
Created 12/09/25, 14:42
Updated 06/17/26, 11:45
Bug
Under Review Stale Workspaces TYPO3 CMS 13

#110062 l10n_mode exlude fields are not synced to translations if changed within workspace

Changing the backend-layout of a page within a workspace creates a new workspace-version of that page.
All translations also get their workspace-version. All those workspace versions get the right backend-layout.

Changing the backend-layout again now of the default language, does not sync the selected layout to the translations.

The reason is a missing lookup within the Core, that does not consider workspace-versions correctly, when determining the records that need updates.

Author Markus Klein
Created 06/16/26, 13:31
Updated 06/16/26, 13:33
Task
Under Review Stale Extbase TYPO3 CMS 14

#109101 Mark AbstractDomainObject as not-internal

Author Oliver Klee
Assigned to Oliver Klee
Created 02/25/26, 18:07
Updated 06/10/26, 15:06
Feature
Under Review Stale Security

#109911 Require explicit inheritAccessFromModule declaration for AJAX routes

Aim for having inheritAccessFromModule either set to a module name (string) or false (bool).
This shall make it more explicit, when a particular AJAX route is allowed to be used.

In addition, there should be a new check in the reports module, that list AJAX routes that did not define these settings explicitly.

Optional:
  • Consider adding a feature flag, to enforce inheritAccessFromModule (which is a breaking change and should be enabled explicitly).
  • Consider back-porting this feature flag to older TYPO3 versions as well (v14, v13)

—-

inheritAccessFromModule was introduced with https://review.typo3.org/c/Packages/TYPO3.CMS/+/90631

Author Oliver Hader
Created 05/29/26, 09:17
Updated 05/29/26, 12:56
Bug
Needs Feedback Stale Fluid TYPO3 CMS 14

#109899 The f:image.srcset VH wrongly requires the srcset attribute (instead of defaulting to "1x"), the official HTML spec has it as optional (defaulting to "1x")

See https://html.spec.whatwg.org/#srcset-attribute – zero or one

> Zero or one of the following:
> # A width descriptor, consisting of: ASCII whitespace, a valid non-negative integer giving a number greater than zero representing the width descriptor value, and a U+0077 LATIN SMALL LETTER W character.
> # A pixel density descriptor, consisting of: ASCII whitespace, a valid floating-point number giving a number greater than zero representing the pixel density descriptor value, and a U+0078 LATIN SMALL LETTER X character.

And Mozilla says explicitly this, https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/source#srcset

> If the descriptors are not specified, the default value used is 1x

However, the f:image.srcset ViewHelper has this:

$this->registerArgument(‘srcset’, ‘string’, ‘Comma-separated list of width descriptors (e. g. 200w) or pixel density descriptors (e. g. 2x).’, true);

So, the required flag set to true for the srcset argument. This is HTML-spec-violating.

Correct would be $required = false and $defaultValue = '1x'.

Of course, we could adjust hundreds of places by explcitly passing “1x” – but this is super-tedious and basically renders this VH useless (in the sense of comfort-gain). Much better would be if the VH behaves just fully compliant to the HTML-spec oob.

Author S P
Created 05/28/26, 09:37
Updated 05/29/26, 05:31
Feature
Under Review Orphaned Fluid Styled Content

#99316 Move all Fluid Styled Content specific components to EXT:fluid_styled_content

Current state

The default CTypes and their rendering definition are shipped by Fluid Styled Content. But templating and configurations are spread across three system extensions:

  • EXT:fluid_styled_content:
    • TypoScript base rendering definition (lib.contentElement)
    • TypoScript rendering definition (per CType)
    • CType templates, layouts and partials
  • EXT:frontend:
    • Necessary tt_content fields (SQL)
    • CType definitions in TCA
    • TypoScript (tt_content = CASE)
  • EXT:backend:
    • Backend preview

As described in the big vision #98134, all components related to Fluid Styled Content, should be moved to EXT:fluid_styled_content, so that it can be deprecated and moved to FriendsOfTYPO3 as an independent package later on.

Author Lidia Demin
Created 12/08/22, 14:32
Updated 05/21/26, 19:53
Feature
Needs Feedback Orphaned Extbase

#107116 Validate extbase domain model properties against DB schema limits

When you have an extbase application, which persists data, it is currently easily possible to crash the application when saving data to the persistence layer using extbase domain models and repositories. When the domain model for example has a field named title, which is defined in TCA as type input, TYPO3 will automatically create a varchar(255) DB field. When the extbase application however provides an input field to modify the title field, it is not checked, if the given data exceeds the defined DB field size. Instead, a hard Data too long for column 'title' at row 1 exception is thrown, if the provided data is too long for the database field.

Using the TcaSchemaFactory and the SchemaManager, it should be possible to determine possible DB schema field limits for domain model properties. A possible new feature (e.g. validator which is automatically applied to domain model validation) could check, if the given data with exceed DB schema field limits and add a validation error instead.

Example Validator code:

    public function __construct(private readonly DataMapFactory $dataMapFactory) {}

    public function isValid(mixed $value): void
    {
        if (!($value instanceof AbstractDomainObject)) {
            return;
        }

        /** @var TcaSchemaFactory $tcaSchemaFactory */
        $tcaSchemaFactory = GeneralUtility::makeInstance(TcaSchemaFactory::class);

        $dataMap = $this->dataMapFactory->buildDataMap(get_class($value));
        $schema = $tcaSchemaFactory->get($dataMap->getTableName());
        $schemaManager = GeneralUtility::makeInstance(ConnectionPool::class)
            ->getConnectionForTable($dataMap->tableName)
            ->createSchemaManager();
        $columns = $schemaManager->listTableColumns($dataMap->tableName);

        foreach ($schema->getFields() as $field) {
            if (!$field->isType(TableColumnType::INPUT)) {
                continue;
            }

            $fieldValue = $value->_getProperty($field->getName());
            $schemaColumn = $columns[$field->getName()] ?? null;

            if ($schemaColumn && strlen($fieldValue) > $schemaColumn->getLength()) {
                $this->addError('Field too long', 1753032690);
            }
        }
    }
Author Torben Hansen
Created 07/20/25, 17:50
Updated 05/12/26, 07:58
Bug
Under Review Orphaned TYPO3 CMS 14

#109669 Executing `typo3 extension:setup` after upgrade fails with exception due to missing `be_users.user_settings` field

Executing vendor/bin/typo3 extension:setup -vvv right after upgrading
the core composer packages throws following exception:

$ vendor/bin/typo3 extension:setup -vvv./

In ExceptionConverter.php line 63:

  [Doctrine\DBAL\Exception\InvalidFieldNameException (1054)]                                     
  An exception occurred while executing a query: Unknown column 'user_settings' in 'field list'  

Exception trace:
  at ./vendor/doctrine/dbal/src/Driver/API/MySQL/ExceptionConverter.php:63
 Doctrine\DBAL\Driver\API\MySQL\ExceptionConverter->convert() at ./vendor/doctrine/dbal/src/Connection.php:1460
 Doctrine\DBAL\Connection->handleDriverException() at ./vendor/doctrine/dbal/src/Connection.php:1396
 Doctrine\DBAL\Connection->convertExceptionDuringQuery() at ./vendor/doctrine/dbal/src/Connection.php:911
 Doctrine\DBAL\Connection->executeStatement() at ./vendor/doctrine/dbal/src/Connection.php:483
 Doctrine\DBAL\Connection->update() at ./typo3/sysext/core/Classes/Database/Connection.php:289
 TYPO3\CMS\Core\Database\Connection->update() at ./typo3/sysext/core/Classes/Authentication/BackendUserAuthentication.php:2017
 TYPO3\CMS\Core\Authentication\BackendUserAuthentication->writeUC() at ./typo3/sysext/core/Classes/Authentication/BackendUserAuthentication.php:1965
 TYPO3\CMS\Core\Authentication\BackendUserAuthentication->backendSetUC() at ./typo3/sysext/core/Classes/Authentication/CommandLineUserAuthentication.php:110
 TYPO3\CMS\Core\Authentication\CommandLineUserAuthentication->authenticate() at ./typo3/sysext/core/Classes/Authentication/CommandLineUserAuthentication.php:118
 TYPO3\CMS\Core\Authentication\CommandLineUserAuthentication->backendCheckLogin() at ./typo3/sysext/core/Classes/Core/Bootstrap.php:523
 TYPO3\CMS\Core\Core\Bootstrap::initializeBackendAuthentication() at ./typo3/sysext/core/Classes/Command/SetupExtensionsCommand.php:79
 TYPO3\CMS\Core\Command\SetupExtensionsCommand->execute() at ./vendor/symfony/console/Command/Command.php:341
 Symfony\Component\Console\Command\Command->run() at ./vendor/symfony/console/Application.php:1117
 Symfony\Component\Console\Application->doRunCommand() at ./vendor/symfony/console/Application.php:356
 Symfony\Component\Console\Application->doRun() at ./vendor/symfony/console/Application.php:195
 Symfony\Component\Console\Application->run() at ./typo3/sysext/core/Classes/Console/CommandApplication.php:113
 TYPO3\CMS\Core\Console\CommandApplication->run() at ./vendor/typo3/cms-cli/typo3:23
 {closure}() at ./vendor/typo3/cms-cli/typo3:24
 include() at ./bin/typo3:119

In ConnectionError.php line 24:

  [Doctrine\DBAL\Driver\Mysqli\Exception\ConnectionError (1054)]  
  Unknown column 'user_settings' in 'field list'                  

Exception trace:
  at ./vendor/doctrine/dbal/src/Driver/Mysqli/Exception/ConnectionError.php:24
 Doctrine\DBAL\Driver\Mysqli\Exception\ConnectionError::upcast() at ./vendor/doctrine/dbal/src/Driver/Mysqli/Connection.php:35
 Doctrine\DBAL\Driver\Mysqli\Connection->prepare() at ./vendor/doctrine/dbal/src/Driver/Middleware/AbstractConnectionMiddleware.php:19
 Doctrine\DBAL\Driver\Middleware\AbstractConnectionMiddleware->prepare() at ./typo3/sysext/adminpanel/Classes/Log/LoggingConnection.php:43
 TYPO3\CMS\Adminpanel\Log\LoggingConnection->prepare() at ./vendor/doctrine/dbal/src/Connection.php:901
 Doctrine\DBAL\Connection->executeStatement() at ./vendor/doctrine/dbal/src/Connection.php:483
 Doctrine\DBAL\Connection->update() at ./typo3/sysext/core/Classes/Database/Connection.php:289
 TYPO3\CMS\Core\Database\Connection->update() at ./typo3/sysext/core/Classes/Authentication/BackendUserAuthentication.php:2017
 TYPO3\CMS\Core\Authentication\BackendUserAuthentication->writeUC() at ./typo3/sysext/core/Classes/Authentication/BackendUserAuthentication.php:1965
 TYPO3\CMS\Core\Authentication\BackendUserAuthentication->backendSetUC() at ./typo3/sysext/core/Classes/Authentication/CommandLineUserAuthentication.php:110
 TYPO3\CMS\Core\Authentication\CommandLineUserAuthentication->authenticate() at ./typo3/sysext/core/Classes/Authentication/CommandLineUserAuthentication.php:118
 TYPO3\CMS\Core\Authentication\CommandLineUserAuthentication->backendCheckLogin() at ./typo3/sysext/core/Classes/Core/Bootstrap.php:523
 TYPO3\CMS\Core\Core\Bootstrap::initializeBackendAuthentication() at ./typo3/sysext/core/Classes/Command/SetupExtensionsCommand.php:79
 TYPO3\CMS\Core\Command\SetupExtensionsCommand->execute() at ./vendor/symfony/console/Command/Command.php:341
 Symfony\Component\Console\Command\Command->run() at ./vendor/symfony/console/Application.php:1117
 Symfony\Component\Console\Application->doRunCommand() at ./vendor/symfony/console/Application.php:356
 Symfony\Component\Console\Application->doRun() at ./vendor/symfony/console/Application.php:195
 Symfony\Component\Console\Application->run() at ./typo3/sysext/core/Classes/Console/CommandApplication.php:113
 TYPO3\CMS\Core\Console\CommandApplication->run() at ./vendor/typo3/cms-cli/typo3:23
 {closure}() at ./vendor/typo3/cms-cli/typo3:24
 include() at ./bin/typo3:119

In Connection.php line 33:

  [mysqli_sql_exception (1054)]                   
  Unknown column 'user_settings' in 'field list'  

Exception trace:
  at ./vendor/doctrine/dbal/src/Driver/Mysqli/Connection.php:33
 mysqli->prepare() at ./vendor/doctrine/dbal/src/Driver/Mysqli/Connection.php:33
 Doctrine\DBAL\Driver\Mysqli\Connection->prepare() at ./vendor/doctrine/dbal/src/Driver/Middleware/AbstractConnectionMiddleware.php:19
 Doctrine\DBAL\Driver\Middleware\AbstractConnectionMiddleware->prepare() at ./typo3/sysext/adminpanel/Classes/Log/LoggingConnection.php:43
 TYPO3\CMS\Adminpanel\Log\LoggingConnection->prepare() at ./vendor/doctrine/dbal/src/Connection.php:901
 Doctrine\DBAL\Connection->executeStatement() at ./vendor/doctrine/dbal/src/Connection.php:483
 Doctrine\DBAL\Connection->update() at ./typo3/sysext/core/Classes/Database/Connection.php:289
 TYPO3\CMS\Core\Database\Connection->update() at ./typo3/sysext/core/Classes/Authentication/BackendUserAuthentication.php:2017
 TYPO3\CMS\Core\Authentication\BackendUserAuthentication->writeUC() at ./typo3/sysext/core/Classes/Authentication/BackendUserAuthentication.php:1965
 TYPO3\CMS\Core\Authentication\BackendUserAuthentication->backendSetUC() at ./typo3/sysext/core/Classes/Authentication/CommandLineUserAuthentication.php:110
 TYPO3\CMS\Core\Authentication\CommandLineUserAuthentication->authenticate() at ./typo3/sysext/core/Classes/Authentication/CommandLineUserAuthentication.php:118
 TYPO3\CMS\Core\Authentication\CommandLineUserAuthentication->backendCheckLogin() at ./typo3/sysext/core/Classes/Core/Bootstrap.php:523
 TYPO3\CMS\Core\Core\Bootstrap::initializeBackendAuthentication() at ./typo3/sysext/core/Classes/Command/SetupExtensionsCommand.php:79
 TYPO3\CMS\Core\Command\SetupExtensionsCommand->execute() at ./vendor/symfony/console/Command/Command.php:341
 Symfony\Component\Console\Command\Command->run() at ./vendor/symfony/console/Application.php:1117
 Symfony\Component\Console\Application->doRunCommand() at ./vendor/symfony/console/Application.php:356
 Symfony\Component\Console\Application->doRun() at ./vendor/symfony/console/Application.php:195
 Symfony\Component\Console\Application->run() at ./typo3/sysext/core/Classes/Console/CommandApplication.php:113
 TYPO3\CMS\Core\Console\CommandApplication->run() at ./vendor/typo3/cms-cli/typo3:23
 {closure}() at ./vendor/typo3/cms-cli/typo3:24
 include() at ./bin/typo3:119

extension:setup [-e|--extension EXTENSION]

It seems that @::authenticate()@ calls "$this->backendSetUC()", which is
@BackendUserAuthentication::backendSetUC()@ and trying to write to the
not yet existing `user_settings` field during the cli bootstrap before
the field can be added to the database.

Not tested, but could be that this is also an issue for backend/install
in case the field is missing.
Author Stefan Bürk
Assigned to Stefan Bürk
Created 04/21/26, 11:49
Updated 05/11/26, 14:53
Bug
Under Review Orphaned Content Security Policy TYPO3 CMS 13

#109814 Add nonce to JavaScript modules

Currently, using JavaScript modules via the
@AssetCollector->addJavaScriptModule@ does not add nonces.

This usually works because the default Content Security Policy (CSP)
settings set the "self" source list keyword .

However, if the website wants the CSP to only allow nonces,
then none of the JavaScript modules will load.

First reported at: https://github.com/FriendsOfTYPO3/visual_editor/issues/78

Author Matthias Vogel
Created 05/11/26, 12:21
Updated 05/11/26, 12:31
Bug
New Orphaned Backend User Interface TYPO3 CMS 15

#109752 "Error undefined" while editing a content element with insufficient permissions

Originally reported in Content Blocks package: https://github.com/FriendsOfTYPO3/content-blocks/issues/514

> I made a FAQ content block (migrated from a EXT:mask element) where an editor can add content elements of different CTypes inside a collection.
> A regular editor doesn’t have the permission to edit one of the listed CTypes (e.g. html, which is reserved for admin users). So when a admin or superuser adds a content element with the CType html to the FAQ element, an editor gets an error message when trying to open the content element inside the collection element in the backend.
>
> This behaviour is expected and the error justified, but it should be more helpful than “error undefined”.
>
> Steps to reproduce the behavior:
>
> Use the attached config.yaml as an example for a new content type
> Create a new FAQ content block as an admin and add a content element (CType html) inside the collection (tx_mask_faq_ce)
> Switch to an editor who, unlike the admin, doesn’t have the permission to edit html content elements
> Edit the FAQ content block as an editor and open the collection with the html element
> “Error undefined“
>

TYPO3 Version
13.4.28

Author Nikita Hovratov
Created 05/04/26, 09:27
Updated 05/04/26, 09:27
Bug
Under Review Orphaned Localization TYPO3 CMS 14

#104816 Duplicate referenced inline items when triggering translation for multiple languages at the same time

Happend in the list module. We have objects with multiple inline references. Translations were triggered in the list module over the ‘localize to’ option. If only one translation is triggered at once, everything translates like it should. However, as the buttons for the different language are right beside each other, some users will click multiple flag-buttons at once and thus trigger multiple translations at once. If that happends the inline references inside the triggered translation will be messed up. There will be multiple duplicated translated inline references and the l10n_parent will be faulty too. In our instance it happend that they all referenced each other and were hard to clean up that way.
E.g. Main object A has inline object B. Translation for A is triggered for multiple languages at once. The translation will look like: translated Object A has now multiple translations of object B (we call them B1, B2, B3). B1 will point at B in the original language for l10n_parent, while B2 will point at B1, and B3 will point at B2 as l10n_parent. This makes it hard to clean them up via the database, but wouldn’t be nessesary if there weren’t any duplicates to begin with.

The easiest solution would be to maybe disable the other language buttons once one translation is triggered or check if there is already a translation process running and prevent the system from doing multiple translations at once. After a few seconds the translation dialouge will open, but by then an impatient user will already have clicked multiple translation buttons.

Author Jennifer Hauß
Created 09/04/24, 13:23
Updated 04/24/26, 06:55
Bug
Under Review Orphaned DataHandler aka TCEmain TYPO3 CMS 9

#92093 Sorting of records in frontend with sys_language all (-1) and normal

Using a multilanguage setup, we experience problems regarding sorting of normal language records mixed with “all” language records.

The sorting seems to be done in the DataHandler Class.

We patch the DataHandler to get the in our opinion better order.

Can someone please help to get this into the core.

Might be nearby 70154

Author Markus Gerdes
Created 08/25/20, 09:46
Updated 04/22/26, 06:55
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 13

#104566 Closing notification message has movement on close animation

The content of notifaction messages ‘moves’ while the notification is closed.

Moving objects are also recognized by peripheral vision. There is no need to recognize a closing notification.

Author Ayke Halder
Created 08/07/24, 14:55
Updated 04/22/26, 06:54
Bug
Under Review Orphaned DataHandler aka TCEmain TYPO3 CMS 13

#107375 DataHandler->isTableAllowedForThisPage() no longer checks doktype of correct page

This seems to be introduced via https://git.typo3.org/typo3/typo3/-/commit/9490df3 #106382.
The old code fetched the doktype of target page and passed that one down the chain.
The new code uses the doktype of the page record to insert, which seems to be the wrong logic.

https://git.typo3.org/typo3/typo3/-/commit/9490df3#2e113d50d07e048063e4879bbf366c06ea2235ac_7278_7224

Steps to reproduce:
  1. Create a custom page type.
  2. Prevent pages on the new custom page type.
  3. Create a page of custom page type.
  4. Copy the new page.
  5. Paste the copy onto a normal page.

Expected Behaviour:
The page is inserted, page tree is reloaded

Actual Behaviour:
An error is shown: 1: Attempt to insert record "pages:8854" on a page (34) that can't store record type

Normal pages should allow all new page types. But the system will respond with an error that the page is not allowed.

I suggest to keep the old logic to fetch the doktype from target page.

Author Daniel Siepmann
Created 09/03/25, 05:38
Updated 04/22/26, 06:51
Bug
Under Review Orphaned Logging TYPO3 CMS 12

#105514 Append requested URL to formatted log message in ErrorHandler

In the AbstractExceptionHandler, the requested URL is appended within the web context.
This is highly advantageous when an error is thrown, as the provided URL helps locate the error more quickly.
However, if only an ErrorHandler is triggered, no URL is appended.

Author Amir Arends
Created 10/29/24, 14:26
Updated 04/22/26, 06:49
Bug
Under Review Orphaned Localization TYPO3 CMS 9

#92488 Default language does not support fallback language ids

Problematic

I have a multi-site install where the default language can be semantically any of English, French, German or Italian.

Some pages are shared and mounted from a common shared “subsite” (in the context of TYPO3 v9, for the sake of being able to properly create slugs but conceptually, just a bunch of pages in an outside page tree). Those shared pages have arbitrarily their default language in English and are then translated (=overlaid) into French, German and Italian.

In the database we have pages and content with sys_language_uid=0..4 since:

  • sys_language_uid=0 is any semantic default language
  • sys_language_uid=1 is German
  • sys_language_uid=2 is French
  • sys_language_uid=3 is Italian
  • sys_language_uid=4 is English

E.g., when sys_language_uid=0 represents English, then sys_language_uid=4 is not used.

Up to TYPO3 v8 inclusive, the trick to have everything work properly was to never configure a Frontend website to use sys_language_uid=0 but only 1 to 4 and rely on fallback chain to read 0 if the corresponding language is undefined. This way, content from a website in any default language (and translated) can use a common set of shared pages where the default language is semantically English (thus possibly another one).

TYPO3 v9

To do that in TYPO3 v9, the language configuration for a German-first website needs to be this one:

languages:
  -
    title: Deutsch
    enabled: true
    base: /de/
    typo3Language: de
    locale: 'de_CH.utf8,de_CH.UTF-8'
    iso-639-1: de
    websiteTitle: ''
    navigationTitle: Deutsch
    hreflang: de-CH
    direction: ''
    fallbackType: fallback
    fallbacks: '0'
    flag: de
    languageId: '1'
  -
    title: Français
    enabled: true
    base: /fr/
    typo3Language: fr
    locale: 'fr_CH.utf8,fr_CH.UTF-8'
    iso-639-1: fr
    websiteTitle: ''
    navigationTitle: Français
    hreflang: fr-CH
    direction: ''
    fallbackType: fallback
    fallbacks: '0'
    flag: fr
    languageId: '2'
  -
    title: Italiano
    enabled: true
    base: /it/
    typo3Language: it
    locale: 'it_CH.utf8,it_CH.UTF-8'
    iso-639-1: it
    websiteTitle: ''
    navigationTitle: Italiano
    hreflang: it-CH
    direction: ''
    fallbackType: fallback
    fallbacks: '0'
    flag: it
    languageId: '3'
  -
    title: English
    enabled: true
    base: /en/
    typo3Language: default
    locale: 'en_GB.utf8,en_GB.UTF-8'
    iso-639-1: en
    websiteTitle: ''
    navigationTitle: English
    hreflang: en-GB
    direction: ''
    fallbackType: fallback
    fallbacks: '0'
    flag: en-us-gb
    languageId: '4'

but the problem we face is that asking for generating a link for sys_language_uid=0 (in whichever context, for instance an API) leads to an internal catched exception when invoking typolink_URL(). It throws InvalidArgumentException 1522960188 which is “Language 0 does not exist on site xyz.”.

What is expected

In such context, logically speaking the default language (thus the first one in the definition) should be checked for “fallbacks”, something that is normally not expected to happen because TYPO3 wrongly thinks the default language is always 0.

Suggestion

diff --git a/typo3/sysext/core/Classes/Site/Entity/Site.php b/typo3/sysext/core/Classes/Site/Entity/Site.php
index 3d20c20f2a..ea7748b533 100644
--- a/typo3/sysext/core/Classes/Site/Entity/Site.php
+++ b/typo3/sysext/core/Classes/Site/Entity/Site.php
@@ -242,6 +242,11 @@ class Site implements SiteInterface
     {
         if (isset($this->languages[$languageId])) {
             return $this->languages[$languageId];
+        } else {
+            $defaultLanguage = $this->getDefaultLanguage();
+            if (in_array($languageId, $defaultLanguage->getFallbackLanguageIds(), true)) {
+                return $defaultLanguage;
+            }
         }
         throw new \InvalidArgumentException(
             'Language ' . $languageId . ' does not exist on site ' . $this->identifier . '.',
Author Xavier Perseguers
Created 10/06/20, 08:52
Updated 04/22/26, 06:48
Task
Under Review Orphaned TYPO3 CMS 14

#109451 Rate Limit: log warning on failed login attempt

In #93825 a rate limit was introduced for BE logins. Once exceeded, a user gets an error message telling him when he can try again.

However, there are no hints about the failed login attempts which led to exceeding the rate limit.

There are log entries but only for the DEBUG log level since #88230. The rationale behind this back then was that sensitive login data should not show up in logs by default.

However, this was tackled generally in #93925 afterwards thus login data is redacted before being logged.

Altogether the logging of failed login attempts should be reverted to the WARNING log level to have it logged by default. This improves auditing/tracing of login attempts and gives a clear explanation for exceeded rate limits.

Author Mathias Brodala
Assigned to Mathias Brodala
Created 04/01/26, 08:42
Updated 04/22/26, 06:47
Task
Under Review Orphaned TYPO3 CMS 13

#108812 Unneeded instanceof on xxx|null. Use a null check instead.

This is a pre-patch for #108652

Author Simon Schaufelberger
Created 01/30/26, 12:58
Updated 04/22/26, 06:45
Bug
Author Elias Häußler
Assigned to Elias Häußler
Created 03/12/26, 13:56
Updated 04/22/26, 06:43
Task
Author Simon Schaufelberger
Assigned to Simon Schaufelberger
Created 01/16/26, 09:57
Updated 04/22/26, 06:41
Bug
Under Review Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 12

#107283 PageTypeDecorator should add default slash suffix for unconfigured type

This configuration

PageTypeSuffix:
  type: PageType
  default: '/'
  index: ''
  map:
    'sitemap.xml': 1533906435

should result in URLs like this:

Current buggy result – trailing slash missing:
Author Ayke Halder
Created 08/14/25, 10:37
Updated 04/22/26, 06:32
Bug
Under Review Stale TYPO3 CMS 15

#110598 PAGEVIEW resolves the page layout identifier twice

Problem

PAGEVIEW determines the Fluid template of a page from the backend layout
identifier. It does not use the page layout that has already been
resolved for the request and is available from the page information.
Instead it asks PageLayoutResolver for the identifier a second time,
based on the page record and the root line.

The content areas that PAGEVIEW assigns to the view come from the
resolved page layout. Template name and content areas are therefore
taken from two independent resolutions of the same thing.

Effect

Both results can differ. A backend layout data provider decides which
layout an identifier resolves to, and it may return a layout carrying a
different identifier than the requested one. In that case PAGEVIEW
renders the template of the requested identifier while the content areas
belong to the layout that was actually resolved.

The duplicated resolution also hides the case where a layout identifier
is found but the layout definition for it can not be resolved: the
template is rendered as if the layout existed, while there are no
content areas at all.

Expected

The template is determined from the page layout that has been resolved
for the page, so template and content areas always describe the same
layout. If no page layout could be resolved, the previous behaviour is
kept as a fallback.

Affected code

typo3/sysext/frontend/Classes/ContentObject/PageViewContentObject.php

Related to the crash reported in issue #110596, which surfaces in the
same area.

Author Stefan Bürk
Created 09/02/26, 10:48
Updated 09/03/26, 09:39
Epic
In Progress Orphaned Backend User Interface

#108176 Rework Look & Feel of the TYPO3 Backend

Previous work from the Product Strategy Group and various interviews with end-users showed that it is important to give a facelift to the TYPO3 Backend.

The perception is that the TYPO3 Backend hasn’t adapted to new and modern tools people work with these days.

This can be
- Messaging apps (Slack, Microsoft Teams)
- Cloud-based Editing software (Google Docs)
- Developers Web Applications (such as GitHub/GitLab)
- Apps and even full Operating Systems (MacOS, Windows 11, iOS 26 etc)
- Other CMSes and DXPs

This is more than just changing colors, but also introduce new ways to make TYPO3 Backend more like a modern Web Application than keeping the same principles as 20 years ago.

Editors want to see that TYPO3 adapts how other systems look like nowadays.

This epic should summarize (maybe with sub-epics) essential changes for v14.

Author Benni Mack
Assigned to Benni Mack
Created 11/18/25, 16:22
Updated 04/21/26, 11:26
Epic
New Orphaned Backend User Interface

#108183 Modern simplified layering and fewer borders in TYPO3 v14/v15 backend

This epic refines the TYPO3 v14 backend by reducing unnecessary borders and visual layers in order to improve clarity, reduce visual noise and make complex screens easier to scan.

Over the years, the backend interface has gained many helpful structural elements: panels, cards, section headers, separators, etc. These were all added with the intention of clarifying structure and improving orientation. In very dense views, however, the accumulation of nested boxes, multiple borders and stacked layers can make it harder for editors to immediately see what is important and where the main working area begins and ends.

Research on visual perception and cognitive load shows that every additional frame, line and layer is one more element the eye has to parse before reaching the content. Clear hierarchy, consistent grouping and a limited number of strong structural containers help users understand complex layouts faster and with less effort. Spacing, alignment and background differences often provide enough grouping without needing extra borders.

The goal of this initiative is not to radically change the layout, but to simplify it: keep the borders and layers that genuinely support understanding, and remove or soften those that are redundant. This should make the backend feel calmer and more focused, while preserving the character of the existing design.

This epic will:

  • Review key backend views (dashboard, module overview, record lists, forms, sidebars) to identify redundant borders, nested panels and overlapping layers.
  • Reduce the number of stacked containers (panel inside panel inside card) by merging or simplifying them into a smaller set of clear structural regions.
  • Ensure that interactive elements (inputs, buttons, alerts) remain clearly identifiable and accessible, with affordances that do not rely solely on heavy borders.
  • Initiate simple guidelines for when to use borders and containers (e.g. top-level structure, interactive fields, critical messages) and when spacing, alignment or background changes are sufficient.
Author Rachel Foucard
Assigned to Benni Mack
Created 11/18/25, 21:59
Updated 04/21/26, 11:26
Task
Under Review Orphaned Dashboard TYPO3 CMS 14

#107918 New Widget: Activity Stream for Admins

Overview

Create a new dashboard widget that displays system activity logs specifically designed for administrator monitoring and oversight.

Purpose

This widget provides administrators with real-time visibility into system activities by displaying the latest entries from the `sys_log` table. It enables admins to monitor what’s happening in their TYPO3 installation, track user actions, identify errors, and maintain system oversight.

Access Control

**Admin-Only Widget**
- The widget must be visible ONLY to administrator users (`admin = 1`)
- Non-admin users should NOT see this widget in the widget selector at all

Configuration Options

The widget must provide the following configurable settings accessible through the configuration cog icon:

Setting 1: Number of Entries to Display
- **Type:
Dropdown/Select
- Options: 5, 10, 20, 50, 100
- Default: 10
- Label: “Number of entries to display“
- Behavior: Dynamically adjusts how many sys_log entries are fetched and displayed

Setting 2: Show Only Admin Users
- **Type:
Checkbox
- Default: Unchecked (show all users)
- Label: “Show only admin users“
- Behavior: When enabled, filters the activity stream to show only actions performed by administrator users

Setting 3: Show Only Errors and Warnings
- **Type:
Checkbox
- Default: Unchecked (show all statuses)
- Label: “Show only errors and warnings“
- Behavior: When enabled, filters to show only entries with error levels 1, 2, or 3 (warnings, errors, system errors), hiding successful operations

Setting 4: Compact View
- **Type:
Checkbox
- Default: Unchecked (normal view)
- Label: “Compact view (hide avatars, smaller text)“
- Behavior:
– When enabled: Hides user avatars, uses smaller table styling (`table-sm`), reduces padding
– When disabled: Shows full avatars, normal font sizes and spacing

Author Regis TEDONE
Created 10/29/25, 18:14
Updated 04/21/26, 11:25

Showing results 301 to 325 of 1561