Showing results 576 to 600 of 1561

Bug
Under Review Fresh DataHandler aka TCEmain TYPO3 CMS 11

#99980 DataHandler "processRemapStack" fails settings correct values for e.g. passthrough fields like "l10n_parent" (sets values from "remapAction" before)

I think we found a major bug in the DataHandlers `processRemapStack` function that needs to be fixed urgently.

            $newValue = null;
            foreach ($this->remapStack as $remapAction) {....}

The “newValue” which gets set as replacement value in the database is defined outside of the loop.

This leads to the case that a remapAction will get the value from the remapAction before.

                // Process the arguments with the defined function:
                if (!empty($remapAction['func'])) {
                    $callable = [$this, $remapAction['func']];
                    if (is_callable($callable)) {
                        $newValue = $callable(...$remapAction['args']);
                    }
                }
                // If array is returned, check for maxitems condition, if string is returned this was already done:
                if (is_array($newValue)) {
                    $newValue = implode(',', $this->checkValue_checkMax($tcaFieldConf, $newValue));
                    // The reference casting is only required if
                    // checkValue_group_select_processDBdata() returns an array
                    $newValue = $this->castReferenceValue($newValue, $tcaFieldConf, $isNew);
                }

This can happen when both of the conditions above evaluate to false. E.g. for passthrough fields there is no “$remapAction[‘func’]”.

This breaks for example the creation of inline records when “allowLanguageSynchronization” is enabled. In this case the “l10n_parent” field which is defined as passthrough gets the count of inline items set instead of the correct parent uid.

Author Denis Mir
Created 02/17/23, 12:44
Updated 11/09/26, 20:55
Feature
New Fresh Form Framework

#97491 Allow disabling / enabling of elements

As an editor I want to disable/ enable elements of a form. This should be possible for the following elements:

  • finisher
  • step
  • form element
  • validator
Disabling such an element:
  • hides the element in the FE, i.e. the element is not shown/ not executed anymore
  • marks the element as disabled in the BE, i.e. the element is still visible, can be edited and enabled

Some of those elements can only be added once (e.g. finisher and validators). Disabling such elements does not allow the editor to add a new instance of this element. For example:

  • The “email to receiver” finisher can only be added once.
  • Disabling this finisher does not allow the editor to add a second finisher of type “email to receiver”.

The following image shows a possible finisher design:

Author Björn Jacob
Created 04/27/22, 16:07
Updated 11/09/26, 19:59
Bug
New Fresh Backend User Interface TYPO3 CMS 11

#92661 Menus and the select input field in search detail view get clipped off when zoomed

On search detail view: when you zoom the font size to 200% in the browser (only font size), the select input field gets clipped off and the value is not readable anymore.

#tas2020

Author Markus Süss
Created 10/22/20, 09:58
Updated 11/09/26, 16:49
Task
New Fresh Backend User Interface TYPO3 CMS 11

#95246 New users can’t guess they can click on the icon of a content to get the context menu

For a better overview, A new button for the content element context menu is added in the content element header right button bar.

Author Rachel Foucard
Created 09/16/21, 10:31
Updated 11/09/26, 11:29
Feature
New Fresh Linkvalidator

#92822 Ignore button for link targets

As already mentioned the problem of “false positives” can make working with linkvalidator difficult and tedious.

False positives can be the case because:

  • sometimes a URL is checked as false even if it is not (domains with cookies, login restrictions, etc.)
  • in spite of bug fixing – there may still be problems with external URLs which cannot be checked correctly.

The ignore list has 2 advantages:

1. give editors the possibility to get rid of the false positives
2. collect these problem cases. Admins can then sift through them and use this for bug reporting.

How this works

  • A link target can be ignored with an ignore button

  • The ignore criteria can either be edited (or just use exact match by default?)
  • From usability point of view, it would probably be preferable to just create the ignore record and possibly edit it later

  • The ignored urls will then not be shown in the list, but can be edited separately
  • Ignore lists could be maintained in a central place (pid=0) or per site
Author Sybille Peters
Created 11/11/20, 17:22
Updated 11/09/26, 11:27
Task
New Fresh Content Rendering TYPO3 CMS 10

#88627 Unify DataProcessing properties

Hi,

I’m currently working with DataProcessors, and I can see some incoherence (or maybe I’m missing something). For each DataProcessor except LanguageMenu and Menu, parameter ‘as’ is required. LanguageMenu and Menu DataProcessor provides $menuDefaults, which provides default values for e.g. ‘as’ property, but for LanguageMenu, property $menuDefaults is protected, and for Menu, property is set to public.

I think we should set LanguageMenu $menuDefaults to public, and add property $menuDefaults with default values for required field e.g. ‘as’ (and maybe other) for other DataProcessors.

In other DataProcessors, default value is hardcoded in parameter for stdWrapValue.

Let me know what do you think, and I will create patch if necessary.

Author Łukasz Uznański
Assigned to Jo Hasenau
Created 06/25/19, 15:28
Updated 11/09/26, 11:24
Feature
Under Review Fresh CLI

#111375 Browse the Configuration module data interactively with lowlevel:inspect

Problem

lowlevel:inspect (see the issue “Show the data of the Configuration module on the command line”) shows the data of the System > Configuration backend module, but only for keys you already know: every further level is another call. Exploring an unknown provider, finding where a value sits in the TCA or comparing raw and translated labels means many calls and a lot of scrolling.

Proposal

An option --interactive, short -i, that browses the same data in the terminal.

  • One level per screen: its keys on the left, the selected entry on the right as a small tree or as the complete value, the path as a breadcrumb on top.
  • Arrow keys move and go in and out, also with the keys known from less and vim; ? lists all keys.
  • / searches keys and values below the current level like the search of the backend module; n and N go to the next and previous hit.
  • L switches between raw label references and translated labels, starting with the state of --resolve-labels.
  • Without arguments it starts on the provider list; path arguments set the level to start on.
  • Leaving with q prints the lowlevel:inspect call for the selected entry to stdout, while the browser draws on stderr, so path=$(bin/typo3 lowlevel:inspect -i tca) captures it.
  • Without a terminal, and together with --format, --depth, --no-size-limit or --no-interaction, the command exits with code 2.

No new dependency: the browser is built on Symfony Console.

Author Matthias Vogel
Created 11/09/26, 10:29
Updated 11/09/26, 11:22
Feature
New Fresh Extbase

#108379 Provide a $this->logger property in Extbase ActionController.

Currently, developers must use LoggerAwareInterface and LoggerAwareTrait to access a logger. Because method injection is not supported and constructor injection is difficult due to ActionController inheritance, getting a logger is more complicated than it should be. This often discourages especially newer developers from using logging at all.

Providing a preconfigured $this->logger (similar to eventDispatcher, uriBuilder, and flash message helpers) would make logging easier and more consistent in Extbase controllers.

This also supports the TYPO3 v14 roadmap goals of reducing complexity and lowering the entry barrier for developers. (https://news.typo3.com/archive/roadmap-for-typo3-v14-the-high-level-objectives-and-strategic-goals)

Author Lina Wolf
Assigned to Lina Wolf
Created 12/02/25, 13:30
Updated 11/09/26, 11:16
Feature
New Fresh Site Handling, Site Sets & Routing

#107296 PageTypeDecorator: type suffix mapping option limited to root url

Having this configuration:

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

Especially sitemaps must be accessible via the root-url only:

On sub-pages there is no need for the sitemap type to be used as suffix:

And therefore the url from above should not be resolved to type=1533906435, but either to type=0 or even better show error “page not found”.

Solution

Implement new mapping configuration option with prefix ^.

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

Url resolution result:

Corresponding link generation:

“Security” considerations

This solution would still allow urls like this to work:

If there is a kind of “blocking” necessary for a specific type on sub-pages, this must be additionally implemented as mentioned in comment:
https://forge.typo3.org/issues/105837#note-6

> – We introduce a TypoScript option “limitToPages = root” to allow PAGE objects [with a specific typeNum] to be accessible only for specific page IDs.

  pageSitemap = PAGE
  pageSitemap {
    typeNum = 1533906435
    limitToPages = root
  }
Author Ayke Halder
Created 08/15/25, 13:23
Updated 11/09/26, 11:06
Bug
New Fresh Localization TYPO3 CMS 13

#105343 Invalid selection of content elements given on translate or copy function when a content element has no relation

https://github.com/TYPO3/typo3/blob/main/typo3/sysext/backend/Classes/Domain/Repository/Localization/LocalizationRepository.php

Function `->getRecordsToCopyDatabaseResult()` should return all elements which are available for selection for translation or copy. However imagine you have default language (EN) and translation German (2). Where the there are 10 content elements in default and only 6 of them translated in German.

When 1 content element is set in german which does not have any relation (so l10n_source = 0) the while loop exits.
@
while ($origUid = $originalUidsStatement->fetchOne()) {
$originalUids[] = (int)$origUid;
}@

If this happens to be the 2nd element in the array all others are skipped and not taking into the next query to exclude them from listing. Resulting in a list of items which are available for translation or copy while there already is an content element with a translation.

Author Joey Bouten
Created 10/18/24, 08:43
Updated 11/09/26, 11:02
Task
Under Review Fresh DataHandler aka TCEmain TYPO3 CMS 15

#111368 Remove control from DataHandler

Pass null values via dataMap to DataHandler

Author Daniel Windloff
Assigned to Daniel Windloff
Created 11/07/26, 15:17
Updated 11/07/26, 16:52
Task
Under Review Fresh Backend User Interface TYPO3 CMS 15

#110831 Improve modal messages in ext:beuser feature

- Remove filling words like “Are you sure…” from the modal message
to avoid sounding patronizing
- start using the new language domain syntax for the button labels of the modals (other patches will follow)

Author Riccardo De Contardi
Created 09/29/26, 10:19
Updated 11/07/26, 16:20
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 13

#108571 BE user password field not storable in Password manager

I hope this is not a duplicate, else apologies.

If I create a BE user (TYPO3 13.4.22), my password manager (1password) correctly proposes to generate a new password, which is convenient, as it will then also store it directly. (Screenshot1)

But, alas, when checking the stored value in the password manager, it is always `*****`

Which is of course not the new password, but I guess some kind of double security layer, adding those ***?

Desired outcome: seamless integration of the new password box with password managers. As known from literally any other password field on the internets.

Happy Holidays btw and thanks for everything!

Author Urs Braem
Created 12/24/25, 12:57
Updated 11/07/26, 12:20
Epic
New Fresh

#106031 Rework clipboard

The clipboard is one of the oldest components in the TYPO3 backend and could benefit from refactoring.

Author Andreas Kienast
Created 01/30/25, 13:31
Updated 11/06/26, 09:30
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 11

#93540 It is not clear which options extendToSubpages in page properties aplies to

Problems

1. Not intuitive to see which fields are affected by extendToSubpages
2. additional problems, see comments

extendToSubpages applies to property hidden (among others).

It does not apply to nav_hide .

The way the options are grouped currently is misleading. It does not make it clear, what extendToSubpages apply to. One could assume it applys to all the options in the section (which would not include hidden) or all option in the row (which might include start and stop, depending on how the page is resized) or in the “Access” tab.

Ideally group the options differently.

Desired change

1. rethink which options should be overriden with extendToSubpages? currently: hidden, starttime, endtime, fe_group
2. change gui: Easy to see which fields are affected by extendToSubpages (e.g. group fields accordingly)
3. improve docs

see also questions and suggestions below in comments.

current state:

Author Sybille Peters
Created 02/18/21, 07:36
Updated 11/06/26, 08:48
Bug
New Quiet Workspaces TYPO3 CMS 14

#110530 Workspace publishing treats elements from other pages as dependencies

If a link field in a flexform references an unpublished content element or page, then that referenced record is considered a workspace dependency and is published automatically together with the referencing element (… which contains the flexform-link-field). This can lead to the unexpected behavior that a seemingly unrelated element from another page (or the page itself) still in the editing stage is published in the background without proper review.

Example:

  • Page A is in draft workspace and has never been published.
  • user adds a content element with a flexform that contains a link field to Page B
  • user references Page A in that link field
  • user publishes Page B

This leads to Page A being published as well in the background, without any information to the user.

Note that in our tests, this was also reproducible on TYPO3 v13, which didn’t use the new event, but seems to have a similar behavior.

Author Simon Praetorius
Created 08/24/26, 15:25
Updated 11/04/26, 17:21
Feature
Under Review Quiet Extbase

#111178 Dispatch Extbase actions through a configurable PSR-15 middleware stack

Extbase offers no way to wrap the dispatching of a controller action. BeforeActionCallEvent and AfterRequestDispatchedEvent allow code before and after, but not around it: no try/finally around the action, no timing across exceptions (e.g. tracing/APM such as Sentry spans), no short-circuit with an own response. Today this requires an own controller base class or XCLASS.

Proposal: Mvc\Dispatcher runs each action (once per pass of the forward loop) through a PSR-15 middleware stack named “extbase”. Middlewares are registered in Configuration/RequestMiddlewares.php like the “frontend”/“backend” stacks (before/after/disabled, ordered and cached by MiddlewareStackResolver) and executed by Core\Http\MiddlewareDispatcher. The kernel resolves the controller and calls processRequest(). Core registers no middleware in this stack, so behaviour without third-party middlewares is unchanged. No change to ActionController or ControllerInterface.

The inner stack around the action invocation (#[Authorize], #[RateLimit]) follows in a separate change, see the related issue.

Author Alexander Schnitzler
Created 10/20/26, 15:20
Updated 11/04/26, 10:01
Bug
Under Review Quiet Backend User Interface TYPO3 CMS 12

#108984 In TCAs selectMultipleSideBySide you can select an option by accident

If an option inside the available options list is highlighted you can select it by clicking with the mouse on the list border or by clicking on a group name.

How to get there:

  • Mark an option in the selected options list and click remove.
  • The option gets removed from selected and added to available and highlighted.
  • If you now click on the border or an any group of the available options list the highlighted option is again added to selected options.

What should happen:

  • Only the selected options form element should get highlighted/selected to work.
Author Alexander Opitz
Created 02/15/26, 00:50
Updated 11/03/26, 19:02
Task
Author Simon Schaufelberger
Assigned to Simon Schaufelberger
Created 10/14/26, 09:17
Updated 11/03/26, 11:24
Bug
New Quiet Fluid TYPO3 CMS 7

#72703 Flash message caching has changed in TYPO3 7.3

Flash messages rendered by EXT:fluid VH are cached and rendered from cache on page access. This was not the case before TYPO3 7.3 and is not the case when using TYPO3 6.2.

Example
User creates an object, a flash message is added and the user is redirected to the list view.
The flash message will be cached and displayed to any user until the cache of the page is flushed somehow.

Previously the page cache was disabled whenever the flash messages VH was used within a cached plugin.

Cause of this is a removed no cache config in the flash message VH, see marked line:

https://github.com/TYPO3/TYPO3.CMS/commit/70a7ed3a9a8e4462618c81a47122d6825ab7d70f#diff-c458c84cec13de48e7fabedab0c4e47aL114

This behavior change is undocumented and should be considered breaking.

Links
Author Felix Nagel
Created 01/14/16, 15:58
Updated 11/02/26, 14:54
Bug
New Quiet Site Handling, Site Sets & Routing TYPO3 CMS 14

#91751 Redirects are not tied to site configuation breaking referential integrity and making it impossible to test on/transfer from staging systems

The select box for the source domain in the redirects module is filled by using the site configurations and the matching baseVariant. The base variant is shown then.

When saving the redirect it is persisted using the actually shown domain, however (so a baseVariant gets persited, for example). Not – contrary to what one would expect – the site id or the base (from where baseVariants could be retrieved as well) to have proper referential integrity.

Why is this relevant? Because with this you can not test redirects on base variant systems. Nor can you have staging system for testing from where you transfer rows of sys_redirect to the live system.

Currently I’m sitting in front 1000+ redirects having a wrong source_host because a baseVariant was persisted instead of the site id or actual base…. It’s also not possible this way to write a SQL update that transforms the source_host to the one relevant for the current system, because you can not join on yaml files obviously.

It must be possible to save redirects in a form that data integrity to the site configurations is preserved. If this is technically not possible there should not be a dropdown letting you select from site configurations implicitly suggesting that this creates sys_redirect rows actually pointing to the selected site configuration (suggesting that redirects can be transferred between baseVariant setups without losing their functionality).

Author S P
Created 07/06/20, 13:17
Updated 11/01/26, 11:30
Bug
Accepted Quiet Database API (Doctrine DBAL) TYPO3 CMS 14

#105502 DB analyzer fails to add uid field to MM table

The DB analyzer adds a field ‘uid’ to a MM table. However this always fails with error messages
:

Database update failed.

Error: Incorrect table definition; there can be only one auto column and it must be defined as a key

Error: Key column “uid” does not exist in table

ALTER TABLE `tx_mbiproductscategories_mm` ADD `uid` INT UNSIGNED AUTO_INCREMENT NOT NULL

Solution: (by Garvin Hicking)

ALTER TABLE tx_mbiproductscategories_mm ADD COLUMN uid INT UNSIGNED AUTO_INCREMENT PRIMARY KEY;

Select Tree for tt_products category

Slack

Author Franz Holzinger
Created 10/28/24, 17:03
Updated 11/01/26, 07:17
Bug
Accepted Quiet DataHandler aka TCEmain TYPO3 CMS 8

#84618 Not possible to translate a record when allowLanguageSynchronization is set for relation field like 'image' in tt_content

Szenario:

tt_content record of type image in default language with one image (default language en)
translated tt_content record in one language with individual image(s) selected in this record (language dk)

Action:
translate the record in a third language with selecting the translated (dk) record as source.

Expectation:
A translated record is created with sync set to translation source

Actual:
exception is thrown and image(s) in dk record is multiplied

Author Helmut Hummel
Created 04/04/18, 17:13
Updated 10/30/26, 16:56
Bug
Under Review Quiet Database API (Doctrine DBAL) TYPO3 CMS 14

#111272 SQL parser fails to parse "decimal unsigned" correctly

The SQL parser for ext_tables.sql always omits the “unsigned” keyword for “decimal” or “numeric” fields.
The value is actually parsed correctly, but the datatype object does not persist this information correctly.

Code can be copied from the integer datatype.

Author Markus Klein
Assigned to Markus Klein
Created 10/28/26, 20:13
Updated 10/30/26, 07:43
Epic
In Progress Quiet Backend API

#111053 Action API: typed API for TYPO3 with OpenAPI, OAuth and MCP

TYPO3 lacks a uniform, self-describing way for remote systems – backend JavaScript, external integrations and AI agents – to interact with TYPO3. This epic groups the changes introducing such an API.

Service methods marked with #[AsAction] become actions. Their input and output JSON Schema is derived from the method signature, arguments and results are validated, and access is restricted by scopes. On this base, actions are exposed via HTTP, described via OpenAPI, made accessible to external applications via OAuth and provided as tools to AI clients via MCP – without wrapping every functionality manually.

Author Benjamin Franzke
Assigned to Benjamin Franzke
Created 10/14/26, 12:56
Updated 10/28/26, 11:40

Showing results 576 to 600 of 1561