Showing results 901 to 925 of 1561

Bug
New Orphaned Workspaces TYPO3 CMS 13

#109297 Incorrect PID resolution for translated pages in workspace preview with identical slugs

*Description*
In TYPO3 workspace preview, slug resolution for translated (non-default language) pages is inconsistent when identical slugs exist across workspace and live records.

*Scenario (anonymized)*
Two language variants (default + translation) exist in both live and workspace, sharing the same slugs:
Live default: /example-path/environment (ID: LIVE_DEFAULT_ID)
Live translated: /translated-path/environment (ID: LIVE_TRANSLATED_ID)
Workspace default: /example-path/environment (ID: WS_DEFAULT_ID)
Workspace translated: /translated-path/environment (ID: WS_TRANSLATED_ID)

*Actual behavior*
Default language request resolves correctly to LIVE_DEFAULT_ID.
Translated request resolves to the workspace default page (WS_DEFAULT_ID) due to fallback to default language.

*Expected behavior*
Translated requests should resolve consistently to the live default page (LIVE_DEFAULT_ID), not the workspace default page.

*Notes*
The issue appears to stem from fallback logic preferring workspace records for translated pages while preferring live records for default language pages.

*References*
vendor/typo3/cms-core/Classes/Routing/PageRouter.php:560ff
vendor/typo3/cms-core/Classes/Routing/PageSlugCandidateProvider.php:206ff

Temporary fix

--- a/Classes/Routing/PageSlugCandidateProvider.php
+++ b/Classes/Routing/PageSlugCandidateProvider.php
@@ -206,7 +206,7 @@ class PageSlugCandidateProvider
             // Exact match will be first, that's important
             ->orderBy('slug', 'desc')
             // versioned records should be rendered before the live records
-            ->addOrderBy('t3ver_wsid', 'desc')
+            ->addOrderBy('t3ver_wsid', (($workspaceId > 0 && $languageId > 0) ? 'asc' :'desc'))
             // Sort pages that are not MountPoint pages before mount points
             ->addOrderBy('mount_pid_ol', 'asc')
             ->addOrderBy('mount_pid', 'asc')
--
Author Benjamin T.
Created 03/20/26, 08:21
Updated 03/20/26, 08:21
Feature
Under Review Orphaned Dashboard

#108628 Dashboard widget for largest unused files

To help TYPO3 users keep their file mounts organized, we could add a dashboard widget that lists files that that are not referenced.

Author Ulrich Mathes
Created 01/14/26, 11:17
Updated 03/18/26, 13:26
Task
New Orphaned Content Security Policy TYPO3 CMS 12

#100906 Handle CSP violations in browser extensions

General

Payloads

{"blocked-uri":"inline","column-number":9,"disposition":"enforce","document-uri":"https:\/\/indiemusik-festival.de\/events\/festival-2023","effective-directive":"script-src-elem","line-number":33,"original-policy":"frame-src 'self' https:\/\/*.youtube-nocookie.com https:\/\/*.youtube.com https:\/\/*.vimeo.com https:\/\/instagram.com https:\/\/*.instagram.com; img-src 'self' https:\/\/*.ytimg.com https:\/\/*.vimeocdn.com data: https:\/\/instagram.com https:\/\/*.instagram.com; default-src 'self'; script-src 'self' 'nonce-XnDPuvTcc38QsmBT2aH5OLzK1Vv1G9l_HZZ-sioaqjJmVB2lpp7RXg' 'report-sample'; style-src-attr 'unsafe-inline' 'report-sample'; object-src 'none'; base-uri 'none'; style-src 'self' 'report-sample'; connect-src 'self' https:\/\/analytics.in-die-musik.de; script-src-elem 'self' 'nonce-XnDPuvTcc38QsmBT2aH5OLzK1Vv1G9l_HZZ-sioaqjJmVB2lpp7RXg' https:\/\/analytics.in-die-musik.de 'report-sample'; font-src 'self' data:; media-src 'self' https:\/\/cloud.in-die-musik.de; report-uri https:\/\/indiemusik-festival.de\/@http-reporting?csp=report&requestTime=1684526938506325","referrer":"","script-sample":"(function (NAVIGATOR, OBJECT) {\n\n    if \u2026","source-file":"moz-extension","status-code":200,"violated-directive":"script-src-elem"}

→ "source-file":"moz-extension"
→ payload (function (NAVIGATOR, OBJECT) { if
→ trigger https://github.com/EFForg/privacybadger/blob/ef6a2b38b2550e8805076b072645367c4e044a79/src/js/contentscripts/dnt.js#L23

—-

…

Author Oliver Hader
Created 05/20/23, 11:55
Updated 03/17/26, 09:26
Task
Under Review Orphaned Security TYPO3 CMS 12

#100903 Add Facebook In-App Handler

The Facebook App in mobile devices is using an In-App-Browser Handler which seems to inject JavaScript, spotted on https://indiemusik-festival.de/events/festival-2023

Potential Actions:

  • either add handler to allow these requests,
  • or add information/analyzer that describes what was going on

Sources:

CSP Violations:

  • {"document-uri":"https://indiemusik-festival.de/events/festival-2023/act/aetna","referrer":"https://indiemusik-festival.de/events/festival-2023","violated-directive":"script-src-elem","effective-directive":"script-src-elem","original-policy":"frame-src 'self' *.youtube-nocookie.com *.youtube.com *.vimeo.com https://instagram.com https://*.instagram.com; img-src 'self' *.ytimg.com *.vimeocdn.com data: https://instagram.com https://*.instagram.com; default-src 'self'; script-src 'self' 'nonce-MPX1bdMnopM_utJ_FmTCFFHZ9KHhyCmdRfse0-UqvO4QjSq5g6wn7A' 'report-sample'; style-src-attr 'unsafe-inline' 'report-sample'; object-src 'none'; base-uri 'none'; style-src 'self' 'report-sample'; connect-src 'self' https://analytics.in-die-musik.de; script-src-elem 'self' 'nonce-MPX1bdMnopM_utJ_FmTCFFHZ9KHhyCmdRfse0-UqvO4QjSq5g6wn7A' https://analytics.in-die-musik.de 'report-sample'; font-src 'self' data:; media-src 'self' https://cloud.in-die-musik.de; report-uri https://indiemusik-festival.de/@http-reporting?csp=report&requestTime=1684531784834120","blocked-uri":"https://connect.facebook.net/en_US/pcm.js","status-code":0,"source-file":"https://indiemusik-festival.de/events/festival-2023/act/aetna","line-number":1,"column-number":339}
  • {"document-uri":"https://indiemusik-festival.de/events/festival-2023","referrer":"https://l.facebook.com/","violated-directive":"script-src-elem","effective-directive":"script-src-elem","original-policy":"frame-src 'self' *.youtube-nocookie.com *.youtube.com *.vimeo.com https://instagram.com https://*.instagram.com; img-src 'self' *.ytimg.com *.vimeocdn.com data: https://instagram.com https://*.instagram.com; default-src 'self'; script-src 'self' 'nonce-EC5M1XDTyK9jsgUvmXkk5NgpMA9SWP0Y9tfQ4vbQoOiIXgyNXn10zg' 'report-sample'; style-src-attr 'unsafe-inline' 'report-sample'; connect-src 'self' https://analytics.in-die-musik.de; script-src-elem 'self' 'nonce-EC5M1XDTyK9jsgUvmXkk5NgpMA9SWP0Y9tfQ4vbQoOiIXgyNXn10zg' https://analytics.in-die-musik.de 'report-sample'; font-src 'self' data:; media-src 'self' https://cloud.in-die-musik.de; report-uri https://indiemusik-festival.de/@http-reporting?csp=report&requestTime=1684427112240721","disposition":"enforce","blocked-uri":"https://connect.facebook.net/en_US/iab.autofill.enhanced.js","line-number":1,"column-number":259,"status-code":200,"script-sample":""}

Meta-Data:

  • {"addr":"2003:6:53df:b973::","agent":"Mozilla/5.0 (iPhone; CPU iPhone OS 16_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/20E252 [FBAN/FBIOS;FBDV/iPhone11,8;FBMD/iPhone;FBSN/iOS;FBSV/16.4.1;FBSS/2;FBID/phone;FBLC/de_DE;FBOP/5]"}
  • {"addr":"2003:d5:8721:f000::","agent":"Mozilla/5.0 (iPhone; CPU iPhone OS 16_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 Instagram 283.0.0.16.103 (iPhone11,2; iOS 16_4_1; de_DE; de-DE; scale=3.00; 1125x2436; 474411477)"}
  • {"addr":"2003:eb:d747:f4bf::","agent":"Mozilla/5.0 (Linux; Android 12; SM-G973F Build/SP1A.210812.016; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/112.0.5615.136 Mobile Safari/537.36 [FB_IAB/FB4A;FBAV/414.0.0.30.113;]"}
  • {"addr":"2003:e7:a707:6171::","agent":"Mozilla/5.0 (Linux; Android 10; MAR-LX1A Build/HUAWEIMAR-L21A; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/113.0.5672.77 Mobile Safari/537.36 [FB_IAB/FB4A;FBAV/414.0.0.30.113;]"}

→ User-Agent containing FB* indicated the In-App-Browser

Author Oliver Hader
Assigned to Oliver Hader
Created 05/20/23, 11:17
Updated 03/17/26, 09:25
Task
Author Oliver Hader
Assigned to Oliver Hader
Created 04/03/23, 15:51
Updated 03/17/26, 09:25
Bug
Under Review Orphaned Frontend TYPO3 CMS 14

#106343 403 and misleading error in FE when NOT logged in if page is descendant of hidden=1 and extendToSubpages=1

Reproduce

prerequisites:
  • we are not logged in the BE
  • there is no access restriction on the page (e.g. FE user)

1. Create a page test with hidden=1 and extendToSubpages=1
2. Create a not hidden subpage test2
3. Load the page test2 in the frontend (not logged in the backend)

We expect to get a 404 (like for hidden pages), but we get a 403:

Error message

> 403
> Page Not Found
> The page did not exist or was inaccessible. Reason: Subsection was found and not accessible

Also, the error message is misleading and non-intuitive.

(I tried to find existing issue but found lots of issues with preview. This is about not being logged in the BE and there is no FE user or access restriction).

Versions

  • reproduced with latest main (14.0.0-dev)
  • also reproduced with latest v12 (12.4.28-dev)
Author Sybille Peters
Created 03/08/25, 09:46
Updated 03/12/26, 14:19
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#109218 Change required by Heading implementation

In the edit mode of the backend the heading hierarchy is not correctly structured. The H2 in the tap bar is marked as a Heading which is not correct, the tap bar is not a navigation section.
Recommended: The H2 in the tap bar should be removed, as the tap bar shouldn´t be implemented as a heading.
Then the right order should be H1 followed by h2, so the H3 Heading should be changed to be H2. otherwise the screen reader users would see an inconsistent heading hierarchy, which violates common accessibility best practices (proper consecutive heading levels).

Expected result:

  • No heading in the Tap bar
  • Correct order of the Heading after modifying the H3s
Author Christian Jung
Created 03/12/26, 11:09
Updated 03/12/26, 13:47
Bug
Accepted Orphaned Backend User Interface TYPO3 CMS 12

#107024 Translated starttime and endtime fields not editable [regression]

In translated records the Publish Date (starttime) and Expiration Date (endtime) are no longer editable and issue a JS error.

A video to reproduce the problem.

Also in T3v13

Author Davide Alghi
Created 07/03/25, 06:03
Updated 03/11/26, 16:26
Bug
New Orphaned TYPO3 CMS 14

#109205 Context Editing Panel, does not catch links

When clicking the edit button for references, the Frame changes contents and the control stop working.
It’s not possible anymore to close the overlay anymore with the ESC key and also the top bar of the context changes.

!clipboard-202603111053-gzmkt.png!

Author Benjamin Kott
Created 03/11/26, 09:55
Updated 03/11/26, 09:55
Bug
New Orphaned TypoScript TYPO3 CMS 12

#109203 ContentObjectRenderer getRecords does not properly respect default language hidden value when overlays are disabled

Given the following setup:

A TYPO3 installation with single site but two languages:
1. Language is default language
2. Language is configured as:

   title: 'Französisch (fr-FR)'
   enabled: true
   base: '/fr-FR/'
   typo3Language: 'fr'
   locale: 'fr_FR.utf8'
   iso-639-1: 'fr'
   websiteTitle: ''
   navigationTitle: 'Französisch in Frankreich'
   hreflang: 'fr-FR'
   direction: ''
   fallbackType: 'free'
   fallbacks: '8'
   flag: 'fr'
   languageId: 9

Overlays are off for this language.

Now execute a query like this:

page.10.dataProcessing {
   10 = TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor
   10 {
         table = pages
         # The field is an enum with string values, so quote the value
         where = {#tx_e2core_highlight} = '1'
         pidInList = 14101
         recursive = 3
         max = 5
         orderBy = lastUpdated DESC
         as = articles
   }
}

The important part is to query pages.

Now one of the possible pages is hidden in default language, but enabled in foreign
language. l18n_cfg is set to 0.

The expectation is: The page is not fetched, as hiding default language always should
hide the page in all languages, also if overlays are off.

Actual result: The page is fetched in foreign language, failing to build links to the
page, as the expected behaviour is working while building links to the page.

This affects in general everything using the ContentObjectRenderer->getRecords() method:
- cObject CONTENT (to my understanding, not tested)
- cObject RECORDS (to my understanding, not tested)
- data processor TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor (tested)
- … maybe more, maybe also everything using the underlying exec_getQuery() and getQuery() and getQueryConstraints()

This might be related, at least to some degree, to:
- #69022
- #85284
- #88071

Author Daniel Siepmann
Created 03/11/26, 07:17
Updated 03/11/26, 07:17
Bug
New Orphaned Reports TYPO3 CMS 12

#109105 Website down if sys_log is full

It would be very nice and useful if TYPO3 can detect and warn before the sys_log reaches 4294967295 entries (INT) and not show an error 403 in this situation to the website user. We have changed the column type to BIGINT at this installation. Maybe this is a workaround in general.
We have a big and old multi domain website and of course tidy up our sys_log, but don’t touch the auto increment value.
Thank you.

Author Stefan Maischner
Created 02/26/26, 10:56
Updated 03/09/26, 07:34
Feature
Under Review Orphaned Frontend

#93610 Add video platform name to iframe title for youtube and vimeo

To ease use for a screen reader user prefix the video title with “Youtube video” or “Vimeo video”, so she knows in advance what is inside the iframe.

Author Martin Kutschker
Assigned to Martin Kutschker
Created 02/28/21, 10:07
Updated 03/08/26, 19:55
Feature
Under Review Orphaned Frontend

#92200 Allow Subtitle files for Media content Videos

The VideoTagRenderer does not allow to add Subtitle files (file extension vtt) to be added. To allow having subtitles for videos this would be required.

Author Michael Telgkamp
Created 09/04/20, 17:13
Updated 03/07/26, 19:50
Feature
Under Review Orphaned Form Framework

#109143 Inspector Editor Registry for the Form Framework

The TYPO3 form framework’s backend editor uses “inspector editors” — configurable UI widgets that allow editors to modify form element properties (text fields, select lists, property grids, etc.). The behavior of these editors is currently defined implicitly through YAML `templateName` values, with the corresponding PHP logic hard-coded across multiple extractor classes.

This creates two key problems:

  1. Extension developers cannot create custom inspector editors with multi-value property support.** The framework only recognizes a fixed list of five `templateName` values as multi-value capable. Any custom editor that handles arrays, key/value pairs, or dynamic option sets is rejected by the form definition validation — there is no way to register new multi-value editors.
  2. Editor behavior is scattered and duplicated.** Whether an editor supports multi-value properties, rich text, or collection scoping is determined by `if/else` chains checking `templateName` strings in at least six different PHP files. Adding or changing editor behavior requires modifications in multiple unrelated locations.

Proposed Solution

Introduce a PHP-based inspector editor registry that allows each inspector editor to be represented as a PHP class declaring its own capabilities. The registry replaces all hard-coded `templateName` checks with a single lookup mechanism.

Core Concepts

  • PHP attribute for registration: A new `#[AsFormInspectorEditor]` attribute marks a class as an inspector editor. The Symfony DI container discovers and collects these classes automatically at compile time — no manual `Services.yaml` wiring needed.
  • `InspectorEditorInterface`: Each editor class implements a contract that describes its behavior: * Which property paths have multi-value semantics * Whether multi-value properties are scoped to validator/finisher collections * Whether the editor supports CKEditor rich text * How property paths with placeholders are expanded to concrete paths * How select option paths are resolved * Which Fluid partial renders the editor’s HTML
  • `AbstractInspectorEditor` base class: Provides sensible defaults so that simple editors only need to implement `getFluidPartialName()`. Complex editors override specific methods to declare their behavior.
  • `InspectorEditorRegistry`: A central, immutable registry populated at container compile time. All extractors and services query this registry instead of checking `templateName` strings directly.

What Changes for Existing Code

  • All existing extractor classes (`MultiValuePropertiesExtractor`, `SelectOptionsExtractor`, `IsCreatablePropertyCollectionElementExtractor`, `PropertyPathsExtractor`, etc.) are refactored to use the registry instead of hard-coded conditionals.
  • The `FormDefinitionConversionService` and `FormEditorEnrichmentService` use the registry for rich text detection and partial resolution.
  • All 17 built-in inspector editors are migrated to PHP classes.

What Changes for Extension Developers

  • Custom inspector editors can now fully participate in multi-value property validation, rich text enrichment, and property path processing by implementing the interface.
  • The `formEditorPartials` YAML key becomes unnecessary for inspector editors — the Fluid partial path is resolved from the PHP class. Existing YAML entries still work but are deprecated.
  • The existing YAML-based `templateName` configuration remains the way editors are referenced in form definitions. The PHP class is purely additive metadata.

Backward Compatibility

  • All existing YAML form configurations continue to work without changes.
  • Editors not found in the registry fall back to the previous behavior (property path used as-is, no multi-value support). This ensures third-party editors that have not yet migrated to the new mechanism remain functional.
  • `Inspector-*` entries in `formEditorPartials` trigger a deprecation log and will be removed in v15. Non-inspector entries (`FormElement-*`, `Modal-*`) are unaffected.
Author Josua Vogel
Created 03/03/26, 19:04
Updated 03/04/26, 16:28
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#108400 Wrong backendlocked modal is shown if TYPO3 backend is not available (httpstatus 403)

Problem/Description

  1. a TYPO3 website where the backend slug (e.g. /typo3) is only available if you are in a specific ip range (e.g. VPN)
  2. keep the backend opened
  3. change your client IP/network/logout from VPN
  4. the webserver (in this case a NGiNX reverse proxy) answer with HTTP status 403
  5. The backendlocked modal is active but informs the editor about “a locked TYPO3 backend for maintenance” – which is wrong in this scenario

!clipboard-202512050656-tr5ev.png!

> The TYPO3 backend is currently locked for maintenance. Leave this browser window open and the backend will automatically become available again once maintenance is complete.

Acceptance Criteria

  • A clear indication that the backend is currently unavailable (status 403) and information that this may be a security precaution would be perfect.
  • It would also be good if an active maintenance lock of the TYPO3 backend could be reliably read from the system.
Author Josef Glatz
Created 12/05/25, 06:00
Updated 03/04/26, 07:38
Feature
New Orphaned Authentication

#109132 Automatically unblock TOTP MFA provider after some time

When entering the wrong TOTP code 3x upon login, the TOTP MFA provider gets locked. The user gets the following message:

> This provider is temporarily locked!
>
> The maximum attempts for this provider are exceeded. Please use another provider or contact your administrator.

This is not temporarily because it requires an admin to reset/unlock the provider for this specific user.

The provider should be unlocked automatically after some hours or a day, so that Admins don’t have so much to do and the “temporarily” message is correct.

(This is with TYPO3v12, but I believe it’s the same in TYPO3 v13)

Author Christian Weiske
Created 03/03/26, 08:50
Updated 03/03/26, 08:50
Task
Under Review Orphaned Link Handling & Redirect Handling TYPO3 CMS 14

#107886 Smarter Auto-Redirects

It would be good that redirects for pages are NOT automatically created if the page
has never been published (= created + hidden by default) otherwise you end up with a lot of unnecessary redirects for editors.

Author Benni Mack
Assigned to Benni Mack
Created 10/28/25, 12:34
Updated 02/27/26, 17:20
Bug
New Orphaned Authentication TYPO3 CMS 13

#108995 Anonymous Fe Session on Redis vs. DB

anonymous fe sessions are handeled differently on redis vs. db backend. the following snippet works fine on \TYPO3\CMS\Core\Session\Backend\DatabaseSessionBackend::class (default), but failes if \TYPO3\CMS\Core\Session\Backend\RedisSessionBackend::class in $GLOBALS[‘TYPO3_CONF_VARS’][‘SYS’][‘session’][‘FE’][‘backend’] is used:

$userSessionManager = \TYPO3\CMS\Core\Session\UserSessionManager::create('FE');
$session = $userSessionManager->createFromRequestOrAnonymous(
    $GLOBALS['TYPO3_REQUEST'],
    'mysession',
);
$session->set('mykey', serialize(123));
$userSessionManager->updateSession($session);

this is because redis backend throws an error if no session is found (https://github.com/TYPO3/typo3/blob/13.4/typo3/sysext/core/Classes/Session/Backend/RedisSessionBackend.php#L190)
but db backend is okay with missing sessions (https://github.com/TYPO3/typo3/blob/13.4/typo3/sysext/core/Classes/Session/Backend/DatabaseSessionBackend.php#L169).

Author Pascal Hofmair
Created 02/17/26, 09:51
Updated 02/26/26, 14:38
Feature
Under Review Orphaned Site Handling, Site Sets & Routing

#105819 Allow TYPO3 contextual configuration for site sets

Currently, site set configurations cannot be set contextually for a specific TYPO3 context.
It would be nice if this were possible. Symfony does this with extra files or with a special “when@” directive.
https://symfony.com/doc/current/configuration.html#configuration-environments

Currently, environment variables or TypoScript constants can be used as a workaround.

Author Timo Webler
Created 12/13/24, 08:00
Updated 02/23/26, 13:23
Bug
New Orphaned Extbase TYPO3 CMS 10

#91560 ActionController::forward() not work with different target controller - Needs better error description

I use a forward in one action to an action in another controller. With version <= 9.5 it worked without any problems. But with 10.4 the controller class cannot be found.

TYPO3\CMS\Extbase\Mvc::controllerAliasToClassNameMapping has only the mapping of the controller for the first action.

The error was that the action in the flexform was not allowed. There would be a better error message here if the controller could not be found or a fallback with a warning.

Author Markus Pircher
Created 06/03/20, 11:40
Updated 02/22/26, 17:15
Feature
New Orphaned Backend User Interface

#109041 Backend field validation in closed IRRE elements

*Situation:*
TYPO3 v13LTS

I’ve elements with related irre elements in two sub-levels.
When I edit such an element, the backend view is long and gets sometimes confusing.
Therefore I want to close the irre elements to get a better overview.

But when I save such an element, all previous closed “children” will be opened again.

The reason I think is, because of the mandatory-field-validation, which does not work in closed irre-children.

Expected behaviour:
  • all elements will stay in the state I left them
  • the validation for mandatory field works
  • if there is a validation error, the related element is marked (like it works with the tabs!)
  • perfect would be, if all irre elements are closed when I open an existing element – this would give a good overview and fast possibility to find, what I want to edit.
Author Wolfgang Twaroch
Created 02/20/26, 14:26
Updated 02/20/26, 14:26
Bug
Accepted Orphaned Themes TYPO3 CMS 14

#108669 Camino: Menu not accessible

The current implementation is not accessible:

- users are unable to navigate to the sub entries via keyboard
- the sub menu opens on hover and cannot be opened via keyboard
- the sub menu opener needs to be a dedicated action
- keyboard navigation pattern for menus need to be implemented.

Author Benjamin Kott
Created 01/19/26, 09:10
Updated 02/17/26, 11:24
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 10

#96461 itemsProcFunc is not able to add itemGroups

Before itemGroups was introduced, it was possible to add a [‘Some Label’, ‘—div—’] option to add grouped items from itemsProcFunc. This is not fully supported anymore because you dont have access to the itemGroups configuration.

You can still add groups but have no possibility of adding labels.

Lets assume you have an “itemsProcFunc” method which takes one parameter called $config:

1) You cant manipulate $config[‘itemGroups’] because ItemProcessingService has no support for it
2) You can not manipulate $config[‘config’][‘itemGroups’] because it is not passed as reference
3) You can not use ExtensionManagementUtility::addTcaSelectItemGroup, it modifies the TCA as expected but TcaSelectItems::addData already works with a local copy of the field config

Current possible workarounds:

1) keep using [‘LLL:label’, ‘—div—’]

con: will be deprecated, no future-proof solution

2) Dont use ‘LLL:label’ for the itemGroup Key, use the translated label

con: Does not “feel” right/consistant but works

3) Add the itemGroup via TCA Overrides

con: not as much straight-forward as it could be, more boilerplate code…

Possible solution:

A) pass the global TCA-config value to TcaSelectItems::groupAndSortItems

pro: Could alter itemGroups via ExtensionManagementUtility::addTcaSelectItemGroup
con: unpredictable side-effects possible

B) pass whole field config as reference

pretty much the same cons than A but the Utility method ExtensionManagementUtility::addTcaSelectItemGroup would not work

C) add itemGroups, sortItems and everything necessary to $processorParameters in AbstractItemProvider::resolveItemProcessorFunction

pro: you can alter itemGroups without any side-effects
con: The Utility method ExtensionManagementUtility::addTcaSelectItemGroup would not work

I would suggest Option C as a solution because it does only add some new options without changing anything else.

Author Philipp Wrann
Created 01/05/22, 09:31
Updated 02/15/26, 10:22
Feature
New Orphaned Extbase

#101125 Ability to convert Domain Models to Array

In the same context with this https://forge.typo3.org/issues/101124, it would be very practical if there was a function in the AbstractEntity , which converts the Model to array.

Technology is moving fast, and headless and communication between systems are made mostly with json strings. Currently, one has to create a method in the domain model which return the values as arrays, but this also could be PITA if an extension has 10+ models and relations. Specially now that with TYPO3 12, we have Webhooks and Reactions , which makes the communication between systems very easy.

*Solution*
Create a method in AbstractEntity which processes everything (FileReferences, Relations) and return everything as an array

Author Aristeidis Karavas
Created 06/20/23, 08:58
Updated 02/14/26, 08:37
Feature
Under Review Orphaned Site Handling, Site Sets & Routing

#107814 settings.yaml does not support context-specific configuration based on ApplicationContext

Hi,

Currently, TYPO3 supports baseVariants within the config.yaml file, allowing context-based configuration by evaluating conditions such as the ApplicationContext.

However, this concept does not extend to settings.yaml, site sets, or site definitions.

This limitation makes it impossible to define site settings that differ between environments (e.g. Development, Production, or sub-contexts like Development/dev-1) without duplicating or overriding configurations manually.

What about following structure:

Development/settings.yaml
Development/dev-1.settings.yaml
Production/settings.yaml

TYPO3 could automatically merge or override these configurations based on the current ApplicationContext.
This would align with TYPO3’s existing baseVariants concept but offer a cleaner and more maintainable approach, avoiding repetitive “condition” declarations for each setting.

Maybe that issue is something for EPIC: https://forge.typo3.org/issues/103034

Stefan

Author Stefan Froemken
Created 10/22/25, 20:05
Updated 02/13/26, 12:20

Showing results 901 to 925 of 1561