Showing results 801 to 825 of 1561

Story
Under Review Orphaned TYPO3 CMS 15

#98134 Future of Content Elements in TYPO3

This epic describes, how CTypes (Content Elements) should be offered in future TYPO3 versions, what should be shipped by default, and how to ensure backwards compatibility.

Current state

The default CTypes and their rendering definition are shipped by EXT:fluid_styled_content:

  • 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

Problems

  • Template and configuration are split into 3 extensions!
  • Some tt_content fields are rarely used
  • If not explicitly configured editors (meaning also admins) see a lot of information in the editing interface, that is unnecessary and confusing
  • This leads to discussions like this: https://decisions.typo3.org/t/remove-outdated-ctypes-and-fields/745
  • Not all CTypes are really usable by default with FSC (e.g. textpic is not responsive)
  • FSC specific fields for frontend representation are (mis-)used by TYPO3 for backend features like live search, backend preview, list module, my open records
  • A good backend preview is only partially possible with custom tt_content fields
  • No future strategy

Vision

“Defining ‘Content Elements’ in TYPO3 can be hard and the learning curve is steep. You need to learn PHP, TCA, TypoScript and Fluid and maybe even other languages.”
_The Structured Content Initiative_

Therefore, the goal is to:
  • Empower integrators/ developers with limited TYPO3 knowledge (e.g. beginners, frontend-only developers) to easily define CTypes
    • via a configuration file
    • via a GUI
  • Have only really necessary fields in tt_content:
    • system fields (e.g. uid, pid, …)
    • fields defined by integrator
  • Enable integrators to define the backend preview
An integrator shall be able to decide if he/she wants to install
  • only selected (custom) CTypes or
  • a distribution/ meta package (e.g. FSC for all CTypes, minimal, menu, …, bootstrap-package)
So there will be two major changes:

Implementation blocks and roadmap

Phase 1:

TYPO3 Content Blocks:
  • Identify content block for a composer package
  • Define field types
  • Documentation
  • GUI for creation of content blocks via backend Module
  • Refactoring vue to LitElements in the backend module
Extract FSC from core:

Phase 2

Extract FSC from core:
  • Resolve dependencies of other system extensions to FSC (e.g. lib.contentElement, plugins)
  • Move all FSC-specific stuff from other system extensions to FSC

Phase 3

TYPO3 Content Blocks:
  • Improve UX
  • Mask / CB to Core Component Converter
  • CLI-Support (with strong defaults, like symphony does, or ruby on rails)
Extract FSC from core:
  • Extract FSC from core to FriendsOfTYPO3
  • Migration from FSC to Content Blocks
  • Migrate-Button for CType-Switches with CType Mapping → no mapping, no switching
Author Lidia Demin
Created 08/12/22, 13:33
Updated 05/22/26, 06:58
Task
New Orphaned Form Framework TYPO3 CMS 15

#109861 Decouple frontend templates from backend preview rendering

EXT:form currently uses a single shared set of Fluid templates for both frontend rendering (the actual form in the browser) and backend preview rendering (the form editor preview in the TYPO3 backend). This coupling creates an undesired dependency on frontend CSS in the backend.
Because the form editor preview reuses the frontend template stack, individual partials already contain previewMode conditionals like:

<f:if condition="{element.rootForm.renderingOptions.previewMode}">...</f:if>
This means:
  • Frontend templates carry backend-specific branching logic that does not belong there.
  • The backend preview depends on the frontend CSS framework being loaded in the backend.
  • Customizing frontend templates may unintentionally affect the backend preview (and vice versa).

Proposed Solution

New Fluid templates in EXT:form/Resources/Private/FormEditor/BackendPreview/ and a new configuration option:

renderingOptions:
  backendPreviewTemplateRootPaths:
    10: 'EXT:form/Resources/Private/FormEditor/BackendPreview/Templates/'
  backendPreviewPartialRootPaths:
    10: 'EXT:form/Resources/Private/FormEditor/BackendPreview/Partials/'
  backendPreviewLayoutRootPaths:
    10: 'EXT:form/Resources/Private/FormEditor/BackendPreview/Layouts/'
Author Josua Vogel
Assigned to Josua Vogel
Created 05/21/26, 20:30
Updated 05/21/26, 20:30
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
Bug
New Orphaned Backend User Interface TYPO3 CMS 14

#109833 UX - translation wizard on empty pages

Premise:

Since version 14 the translation wizard has been reworked to offer a more streamlined experience: Let’s consider this scenario:

Scenario 1.

1) Create a page in the default (main) language
2) Add some content elements to it
3) Use the dropdown to Create a New Translation to the secondary language
4) Now the wizard is opened and lets you

- choose which element to translate
- select the translation mode ( Translation or Copy )

At the end of the process, the user has created a new translated page and the translated content elements, in one single passage (GOOD).

But here’s the issue: consider this scenario:

Scenario 2.

5) Create a page in the default (main) language and leave it empty*
6) Use the dropdown to *Create a New Translation
to the secondary language
7) now the wizards still pops up and still asks you to choose between Translation or Copy mode, even though it makes no sense without content :(

This behavior is confusing for the user, because it asks the user to operate a choice that…should not be taken at page level.

There is a third scenario possible:

Scenario 3.

8) Create a page in the default (main) language
9) Add some content elements to it
10) Use the dropdown to Create a New Translation to the secondary language
11) In the wizard, deselect all content elements and click “Next“
12) The wizard still asks you to choose between Translation or Copy mode, even though there is nothing to translate or copy.

Conclusion

- When the page is empty it should be better to remove the wizard at all, I think
- When no content element is selected, maybe the passage to choose between translation or copy mode could be skipped?

Additional

Another source of potential confusion is the stepper in the translation wizard: when it is just opened (step 3)) it already reads “Step 3 of 7”… where are the first two steps?

BTW: in the other scenario (empty page, no initial content) it reads “Step 4 of 7”)

Author Riccardo De Contardi
Created 05/14/26, 09:01
Updated 05/14/26, 09:01
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
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 13

#109810 Merge settings.definitions from siteset dependencies

Follow up to #109809

The settings from a site sets dependencies settings.definitions.yaml seems to not be taken into account when create SettingDefinition.

This makes it “not possible” to override a single setting of a site set dependencies settings, without defining the whole settings

So, instead being able to write

settings:
felogin.Pid:
hidden: true

I must write the full definition with all known properties

settings:
felogin.Pid:
type: Page
hidden: true

Suggestion goes towards merging the settings.definitions of dependencies

Author Soren Malling
Created 05/11/26, 08:32
Updated 05/12/26, 07:51
Feature
Author Oliver Hader
Assigned to Oliver Hader
Created 05/08/26, 07:17
Updated 05/12/26, 06:30
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
New Orphaned Workspaces TYPO3 CMS 11

#92458 Creating the "same" record in live and draft workspace led to misbehaviour in recordlist

Given you have two site languages (Default L=0 and Translation L=1) and the page is translated in L=1.

  1. Create a new content element in L=0
  2. Switch in Workspace Draft and translate the newly created record (1.) in L=1 (Don’t publish)
  3. Switch back to Live and translate the newly created record (1.) in L=1
  4. recordlist now displays the created live record (3.)
  5. Switch back in Workspace Draft and publish the translated record (2.)
  6. Switch back to Live
  7. Now the record (2.) is displayed in recordlist although we created the translation already (3.)
  8. Switch back in Workspace Draft and remove the record from (2.)
  9. Live record (3.) is displayed again

Doing the same in page module results in having two translations for the default record in connected mode.

Author Oliver Bartsch
Created 10/01/20, 12:06
Updated 05/11/26, 14:23
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
Accepted Orphaned Frontend TYPO3 CMS 6.2

#62699 Page contains the same id multiple times when inserting the same Content Element with Insert Records more often

Using Insert Records (IR) multiple times on the same page and each IR-CE insert the same content, the id (which comprises of c + content.uid) is rendered multiple times on the page.
This allows a user to invalidate the generated HTML code.

Author Markus Klein
Created 11/04/14, 16:58
Updated 05/11/26, 08:54
Task
Under Review Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 13

#109809 Hide site settings

When a site depends on another site set, all “settings.definitions.yaml” get included in the “site settings” of that site.

We don’t have a way to hide any settings. This could be settings that get a default value via “settings.yaml” or settings that makes no sense.

Similar to how we can hide a full site set from the selection, i propose a similar “hidden: true” setting on both categories and settings level.

This is purely a UI/visual thing and does not have effect on any code

Author Soren Malling
Created 05/11/26, 07:57
Updated 05/11/26, 08:27
Epic
New Orphaned Backend API

#90050 Translation wizard improvements and issues

Epic grouping translation wizard issues

Author Tymoteusz Motylewski
Created 01/03/20, 13:25
Updated 05/08/26, 14:13
Bug
Accepted Orphaned composer / dependencies / third-party TYPO3 CMS 14

#109666 Composer class loader errors during upgrade from v13.4.28 to v14.3.0

composer update

 [snip]

  - Upgrading typo3/cms-info (v13.4.28 => v14.3.0): Extracting archive
  - Upgrading typo3/cms-install (v13.4.28 => v14.3.0): Extracting archive
  - Upgrading typo3/cms-lowlevel (v13.4.28 => v14.3.0): Extracting archive
  - Upgrading typo3/cms-reports (v13.4.28 => v14.3.0): Extracting archive
  - Upgrading typo3/cms-rte-ckeditor (v13.4.28 => v14.3.0): Extracting archive
  - Upgrading typo3/cms-tstemplate (v13.4.28 => v14.3.0): Extracting archive
  - Upgrading typo3/cms-viewpage (v13.4.28 => v14.3.0): Extracting archive
Generating autoload files

In ClassAliasMapGenerator.php line 139:

  [Error]                                                                  
  Class "TYPO3\ClassAliasLoader\IncludeFile\CaseSensitiveToken" not found  

Exception trace:
  at […]/vendor/typo3/class-alias-loader/src/ClassAliasMapGenerator.php:139
 TYPO3\ClassAliasLoader\ClassAliasMapGenerator->generateAliasMapFiles() at /usr/share/composer
Author Benjamin Franzke
Created 04/21/26, 10:28
Updated 05/07/26, 10:08
Task
Under Review Orphaned WebHooks - Incoming = Reactions + Outgoing TYPO3 CMS 14

#109747 Let reaction verify request based on other header

Basis for verifying a request handled by a “reaction” is to require a header named “x-api-key”.

To really open EXT:reactions for external systems, we must let a reaction verify a request it self.

For example: Stripe

https://docs.stripe.com/webhooks/signature

Stripe sends a Stripe-Signature header. EXT:reactions will not be able to handle such incoming request.

Instead, we will build own custom middlewares.

Goal here, is to extend the functionality of verifying a request and opening up for receiving request from systems such as WMS, Payment, CRM and much more. And having a single point of entry for this.

Author Soren Malling
Created 05/03/26, 20:00
Updated 05/06/26, 10:30
Bug
Needs Feedback Orphaned Frontend TYPO3 CMS 12

#105555 TypoScript caching locks other page calls exklusive

The TypoScript frontend controller locks complete website on each call exclusivly.

We have the following setup:
- Load Balancer + Varnish
- 3 Webserver with TYPO3 on each Node
- NFS Share for shared files
- Redis Server

Due to NFS share we cannot use file locking strategy – we use Redis locking strategy (https://github.com/b13/distributed-locks).
We have approximately 7-10 Requests per second and 1.3 million pages in TYPO3. Many of them are not cached, so the page cache, especially the TypoScript cache has to be generated new on different calls.

The aquire lock is on 3 different places in the code:
- https://github.com/TYPO3/typo3/blob/v12.4.22/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php#L1402
- https://github.com/TYPO3/typo3/blob/v12.4.22/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php#L1428
- https://github.com/TYPO3/typo3/blob/v12.4.22/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php#L1432

The locking here causes the complete T3 to wait for the lock to be release (the lock name is ‘pages’). So if there are 7 calls per second and for 10 seconds -> 70 calls has to be handled. The locking part takes for example 1 second to lock/unlock -> after 10 seconds only 10 requests of 70 are handled and the PHP FPM process starts to spawn until the limit is reached.

In the ResourcesMutex an exclusive and non-block lock is done for the key ‘pages’ (https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/Locking/ResourceMutex.php#L87-L89) which causes all other pages to wait until a random page is finished.

I would expect that only this specific page is locked instead of all pages are locked (with the hash included).

What if the the code is adapted to:

$this->lock->acquireLock('pages_' . $this->newHash, $this->newHash);

Then the lock is acquired only per specific page instead that everything is locked.

The same ResourceMutex is used in T3 v13 – so the problem should be the same.

How to reproduce?

1. Add a sleep(40); before line 90 (https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/Locking/ResourceMutex.php#L90)
2. Call one random page without cache.
3. Now call another page without cache and the second call will wait until the first call ist finished :)

If you need further information let me now!

Thanks Andi

Author Andreas Hager
Created 11/07/24, 12:17
Updated 05/04/26, 15:14
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
New Orphaned RTE (rtehtmlarea + ckeditor) TYPO3 CMS 13

#109733 CKEditor 5: Contextual Link Dialog cannot be focused via keyboard (Cmd+F10 / Alt+F10)

In TYPO3 v13.4, keyboard navigation and accessibility fail when trying to edit an existing link in the CKEditor 5.
When the cursor is placed on an existing link, pressing the documented keyboard shortcut Cmd+F10 (Mac) or Alt+F10 (Windows/Linux) fails to move the keyboard focus into the contextual link balloon/dialog. The user has no way to reach the link input fields or the edit/unlink buttons without using a mouse.

Note: In standard vanilla CKEditor 5 builds (e.g., https://ckeditor.com/ckeditor-5/demo/feature-rich/), pressing Cmd+F10 correctly jumps directly into the floating link dialog. This points to an issue with TYPO3’s backend integration, specifically how it handles floating UI elements or focus trapping.

Steps to Reproduce:

  1. Open a backend record with a Rich Text Editor (CKEditor 5).
  2. Type some text, select it, and create a link (either via mouse or Cmd+K ).
  3. Place the text cursor inside the newly created or any existing link.
  4. Try to focus the contextual link dialog/balloon using the keyboard shortcut Cmd+F10 (or Alt+F10 ).
  5. Try using Arrow Keys to see if the focus moves into the floating dialog.

*Expected Behavior:*
Pressing Cmd+F10 / Alt+F10 when a link is selected should move the focus directly into the CKEditor link balloon panel, allowing the user to use Arrow Keys to navigate to the “Edit link” button or directly edit the URL.

*Actual Behavior:*
The shortcut is either ignored, swallowed by the TYPO3 backend, or the focus gets trapped/lost. The contextual link dialog cannot be reached via keyboard at all.

*Possible Causes (Technical Hypothesis):*
This seems to be a focus-trapping conflict. CKEditor 5 renders the link dialog as a floating “Balloon Panel” outside the normal editor DOM flow. TYPO3’s global event listeners (FormEngine, Lit components, or backend overlay management) likely intercept the focus shift or trap the focus within the main editor wrapper, preventing the CKEditor FocusTracker from successfully shifting focus to the floating balloon.

Environment:

  • TYPO3 version: 13.4.27
  • Browser: Chrome v147.0.7727.116, Firefox v149.0, Edge v147.0.3912.86
  • OS: macOS
Author Marco Luig
Created 04/30/26, 06:38
Updated 04/30/26, 06:38
Bug
New Orphaned Backend JavaScript TYPO3 CMS 14

#109581 Cannot close content edit modal with click outside when an exception occurs

When editing a content element in the new v14 backend a click outside the modal that opens the content element closes it.
When an exception occurs a click outside the modal does not close the modal.

Author Philipp Edwell
Created 04/14/26, 21:44
Updated 04/29/26, 12:47
Bug
New Orphaned RTE (rtehtmlarea + ckeditor) TYPO3 CMS 13

#109722 CKEditor 5: Keyboard navigation broken in "Styles" dropdown grid (a11y)

In TYPO3 v13.4, accessibility/keyboard navigation fails within the CKEditor 5 “Styles” dropdown (the one containing “Text styles” and “Block styles”).
While navigating the main toolbar works fine (via Alt+F10), it is not possible to navigate through the actual grid of styles inside the dropdown using the Arrow keys or the Tab key. The focus gets stuck, jumps out of the editor context entirely, or is simply swallowed by the backend.

Note: This works perfectly fine in the vanilla CKEditor 5 builds outside of TYPO3 (see CKEditor docs: https://ckeditor.com/docs/ckeditor5/latest/examples/builds-custom/full-featured-editor.html). Therefore, this seems to be a TYPO3 backend integration issue rather than an upstream CKEditor bug.

Steps to Reproduce:

  1. Open any backend record containing a Rich Text Editor (CKEditor 5) with the “Styles” plugin enabled.
  1. Focus the editor text area.
  1. Press Alt + F10 (or Option + F10 on Mac) to focus the CKEditor toolbar.
  1. Use the arrow keys to navigate to the “Styles” dropdown button and press Enter or Space to open it.
  1. Try to navigate through the opened styles grid (Text styles / Block styles) using the Arrow keys or the Tab key.

*Expected Behavior:*
The user should be able to navigate through the grid of styles using the arrow keys and select a style with Enter, as seen in vanilla CKEditor 5 examples.

*Actual Behavior:*
The focus fails to move properly between the style items. The user cannot select specific text or block styles using the keyboard.

*Possible Causes (Technical Hypothesis):*
The issue likely stems from a conflict between TYPO3’s global backend event listeners (FormEngine, Lit components) and the CKEditor’s internal FocusTracker.
Since the “Styles” dropdown renders as a more complex grouped UI panel (unlike the simpler paragraph/headings dropdown), TYPO3’s event interception (e.g., handling Tab/Arrow keys for global form navigation) might intercept the keystrokes before CKEditor can process them for its internal grid navigation. Shadow DOM boundaries might also cause the CKEditor FocusTracker to lose context.

Environment:

TYPO3 version: 13.4.27

Browser: Chrome v147.0.7727.116, Firefox v149.0, Edge v147.0.3912.86

OS: macOS

Author Marco Luig
Created 04/28/26, 08:50
Updated 04/28/26, 08:50
Feature
New Orphaned

#109721 Allow to preview hidden records via GET-Parameter

TYPO3 already has a centralized logic to add necessary simulation parameters to URLs within TYPO3\CMS\Backend\Routing\PreviewUriBuilder->getAdditionalQueryParametersForAccessRestrictedPages().

Despite its name, this also works well for records, see: https://github.com/georgringer/news/issues/2796

One thing does not work though, that is preview of hidden records. There is no parameter yet to trigger preview of hidden records, as the implementation currently only targets pages.
The current logic to preview hidden pages is done within TYPO3\CMS\Frontend\Middleware\PreviewSimulator.

It would be cool to open the logic for other records as well and to attach a ?ADMCMD_simHidden=1 parameter or alike to trigger preview of hidden records on demand.

Author Daniel Siepmann
Created 04/28/26, 05:37
Updated 04/28/26, 05:38
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 15

#109627 Moving content with translation(s) to a free-mode target language leaves orphaned translations

Description

When a default-language tt_content record that already has translations is moved into a non-default target language that is handled in free mode, TYPO3 can leave existing translations behind in an invalid state.

In the observed scenario, the moved record changes its sys_language_uid to the non-default target language, while existing translations remain unchanged in the database. Their l18n_parent relation then no longer points to a default-language record, so they become orphaned translation records. In addition, these orphaned records are no longer visible in the Layout module.

The move operation must not silently create this inconsistent state.

Steps to reproduce

  1. Create a default-language tt_content record.
  2. Create at least one existing translation of that record.
  3. Ensure that the target language is handled in free mode.
  4. Move the default-language record into that non-default target language using the backend page module workflow.
  5. Inspect the remaining translations in the backend and in the database.

Actual behavior

  • The moved record receives the target sys_language_uid.
  • Existing translations remain in the database.
  • Their l18n_parent relation is no longer valid because it no longer points to a default-language record.
  • The remaining translation records become orphaned and are no longer visible in the Layout module.

Expected behavior

  • The move operation must not silently create orphaned translation records.
  • TYPO3 should either block the move or require an explicit destructive confirmation before proceeding.
  • If the destructive path is chosen, TYPO3 should handle the affected translations explicitly and consistently, for example by soft-deleting them and informing the editor.
  • If the editor does not confirm, the move must be cancelled.

Impact / rationale

The current behavior compromises data consistency and can hide affected records from editors while keeping them in the database.

A silent orphaning of translation records is not acceptable. At the same time, a destructive cleanup without explicit confirmation would also be too risky.

Related issues / patches

  • #108358 / 93063 is related but narrower: it focuses on a warning for already orphaned content elements in a specific constellation. The scope of this report is the move operation itself and the requirement that TYPO3 must not silently create orphaned translation records.
  • #102345 is broader historical context around orphaned translation records during problematic copy/move operations across different language setups, but it is primarily page-focused and does not cover this exact tt_content move-to-free-mode scenario.
Author Eric Harrer
Created 04/17/26, 11:24
Updated 04/24/26, 06:23
Bug
Under Review Orphaned Localization TYPO3 CMS 15

#108925 Prevent copying free-mode records to unsupported languages

When copying records using the TYPO3 DataHandler, language restrictions are currently only enforced for connected-mode translations (records linked to a default-language record via the translation origin pointer).

Free-mode records, defined as records with a language UID greater than zero that are not connected to a default-language record, bypass these checks during copy operations.

As a result, records can be copied into a target site or target page where the corresponding language is not available, leading to orphaned language records.

This also affects related IRRE child records (e.g. sys_file_reference), which are copied as part of the same operation.

Author Eric Harrer
Created 02/10/26, 12:16
Updated 04/24/26, 06:22
Bug
New Orphaned Backend User Interface TYPO3 CMS 12

#102034 The treeConfig.startingPoints parameter does not work correctly in TYPO3 v 12 (Related to https://forge.typo3.org/issues/102015)

Scenario:
1) A fresh TYPO3 v 12 installation
2) A page tree with 2 website root pages and a sysfolder (as in screenshot “Page_Tree.png”)
3) A Category Tree in the sysfolder (as in screenshot “Category_Tree.png”)
4) A backend usergroup named “Website A & B usergroup” that can manage both sites and has “Main Category 1” in Category Mounts (as in screenshot “Backend_Group.png”)
5) On “Website A” page -> Resources this TSConfig: TCEFORM.sys_category.parent.config.treeConfig.startingPoints=3 (where “3” is the uid of the first subcategory of “Main Category 1”

if the backend user associated with the backend usergroup tries to create a new category on the “Website A” page he should be able to see in the “parent” field the sub-category “Sub Category Root for Website A” and its subcategories thanks to the parameter TCEFORM.sys_category.parent.config.treeConfig.startingPoints=3 Instead he just sees only “Sub Category Root for Website A” (as in screenshot “New_Category_Creation.png”.

This is related to bug [102015]

Author Robert von Hackwitz
Created 09/25/23, 13:51
Updated 04/22/26, 13:43

Showing results 801 to 825 of 1561