Showing results 201 to 225 of 1561

Feature
New Quiet FormEngine aka TCEforms

#111352 Allow integer columns like pid for foreign_table_item_group

Use case

Records of one kind are often stored in several places that mean something to editors, for example pages of a custom doktype below different parent pages:

Section
├── Category A    → pages of the custom doktype
├── Category B    → pages of the custom doktype
└── Category C    → pages of the custom doktype

A content element offers these pages in a selectMultipleSideBySide field (foreign_table => pages, restricted to the doktype). With dozens of items, the list of available items is much easier to use when it is grouped the way editors know it from the page tree: by parent page.

foreign_table_item_group (Feature #95808) looks like the perfect fit: 'foreign_table_item_group' => 'pid', plus itemGroups mapping the parent uids to labels. The same applies to any other integer column that groups records naturally, e.g. a storage folder, a select field stored as integer or sys_language_uid.

Current behaviour

Opening the record fails:

TypeError: TYPO3\CMS\Core\Schema\Struct\SelectItem::__construct(): Argument #5 ($group) must be of type ?string, int given

The database returns pid as integer, AbstractItemProvider::addItemsFromForeignTable() sets it as the item’s group, and SelectItem::fromTcaItemArray() passes it to the constructor unchanged. An itemsProcFunc does not help either, the items are converted to SelectItem before it runs.

This matches the documentation: the group key is defined as string (group (string) in the TCA reference, and the changelog of Feature #95808 says “this needs to be a string”). So this is a feature request rather than a bug. Today it takes a custom itemsProcessor that rebuilds the groups.

Proposal

Accept integer group identifiers by casting them to string, the same way #108989 did for integer labels:

--- a/typo3/sysext/core/Classes/Schema/Struct/SelectItem.php
+++ b/typo3/sysext/core/Classes/Schema/Struct/SelectItem.php
@@ public static function fromTcaItemArray(array $item, string $type = 'select'): SelectItem
     {
+        $group = $item['group'] ?? $item[3] ?? null;
         return new self(
             type: $type,
             label: (string)($item['label'] ?? $item[0]),
             value: $item['value'] ?? $item[1] ?? null,
             icon: $item['icon'] ?? $item[2] ?? null,
-            group: $item['group'] ?? $item[3] ?? null,
+            group: $group !== null ? (string)$group : null,

Tested on 14.3.10 with the configuration below: the available items render in one optgroup per parent page, labelled via itemGroups (numeric keys work as they are). The TCA reference of foreign_table_item_group could then state that integer columns are supported.

'related_pages' => [
    'label' => 'Pages',
    'config' => [
        'type' => 'select',
        'renderType' => 'selectMultipleSideBySide',
        'foreign_table' => 'pages',
        'foreign_table_where' => 'AND {#pages}.{#doktype} = 116 AND {#pages}.{#sys_language_uid} IN (0,-1) ORDER BY pages.sorting',
        'foreign_table_item_group' => 'pid',
        'itemGroups' => [
            10 => 'Category A',
            11 => 'Category B',
            12 => 'Category C',
        ],
    ],
],
Author Tim Bäcker
Created 11/05/26, 12:51
Updated 11/05/26, 12:51
Feature
Author Alexander Schnitzler
Assigned to Alexander Schnitzler
Created 12/02/20, 14:31
Updated 11/04/26, 09:21
Feature
Under Review Quiet Dashboard

#109859 Provide more dashboard widget types

Make it easier by providing more widget types in ext:dashboard

Author Georg Ringer
Assigned to Georg Ringer
Created 05/20/26, 13:46
Updated 11/03/26, 20:45
Feature
Under Review Quiet SEO

#107013 RecordsXmlSitemapDataProvider / Sitemap: Add config for selectFields

By default, all fields in a table are read with * in https://github.com/TYPO3/typo3/blob/main/typo3/sysext/seo/Classes/XmlSitemap/RecordsXmlSitemapDataProvider.php#L101. This caused performance issues for us because we used a large number of fields (attributes). PHP did not need them in the logic at all.

Therefore, it would be ideal if we could add a ‘selectFields’ option to the existing configuration that can override this * default value.

Author Guido Schmechel
Created 07/01/25, 10:44
Updated 11/03/26, 19:59
Bug
Under Review Quiet Extbase TYPO3 CMS 9

#91029 Validation fails if nested properties of same type are present

I recently stumbled upon an issue regarding the validation process and after some debugging I was able to track down the problem to be exactly the same problem that has already been fixed years ago in the FLOW framework:

https://forge.typo3.org/issues/50585

Long story short:

The validate() methods in
  • TYPO3\CMS\Extbase\Validation\Validator\AbstractValidator
  • TYPO3\CMS\Extbase\Validation\Validator\CollectionValidator
  • TYPO3\CMS\Extbase\Validation\Validator\GenericObjectValidator
    will override $this->result every time they are called not preserving previous error results that might eventually already exist.

In the FLOW framework this is being handled by pushing the previous error result on a stack before the isValid() method is being processed and then popped backed out again afterwards.

See here as an example:
https://github.com/neos/flow/blob/master/Classes/Validation/Validator/AbstractValidator.php#L150

It also looks like this problem still exists in TYPO3 10.x as the validators mentioned above still look the same as in TYPO3 9.5

Author Daniel Schultheis
Created 04/14/20, 15:22
Updated 11/03/26, 19:50
Feature
New Quiet Extbase

#111293 Extbase controller action argument mapping should respect persistence.storagePid restrictions

When Extbase automatically resolves a domain object from a controller action argument, the configured persistence.storagePid restriction is ignored. For example:

public function showAction(Post $post): ResponseInterface

A record can be resolved by its UID even if it is stored outside the configured storage PIDs. While this behavior appears to be intentional and is documented, it may not be the best default.

Why this matters

Regular Extbase repository queries generally respect persistence.storagePid by default, with exceptions such as findByUid(). However, automatic controller argument mapping does not respect this restriction. This inconsistency is easy to overlook and may lead to unintended access to records outside the current plugin’s scope, particularly in multi-site setups or installations with separate data storage areas.

Suggested improvement

Automatic controller argument mapping should respect the configured persistence.storagePid restrictions by default, while providing an explicit way to opt out when necessary. Since changing the existing behavior could affect backward compatibility, a configurable solution or a change in a future major version might be appropriate.

Author Jan Kornblum
Created 10/30/26, 14:57
Updated 10/30/26, 14:57
Feature
New Quiet Localization

#111281 Allow a site language with a locale the Core does not list

Problem

TYPO3\CMS\Core\Localization\Locales::$languages is the list of languages the backend interface can be switched to, and the list TYPO3 fetches translations from Crowdin for. It is also, as a side effect, the list of locales a frontend site can resolve labels in.

So a site in Zulu, Amharic, Hausa, Yoruba, or any of around thirty further languages that have an ISO 639-1 code, needs a user-defined locale in $GLOBALS['TYPO3_CONF_VARS']['SYS']['localization']['locales']['user'] before a single label of its own sitepackage is read. Those labels are in the site’s own XLF files. Nothing about them depends on the Core knowing the language.

The registration is installation-wide rather than per site, so a multi-site installation declares the language globally for the sake of one site.

OfficialLanguages::$rawData already carries all of these codes, and the site configuration module offers them as site languages. TYPO3 offers the language, accepts translated content in it, and then renders the labels in English.

What this asks for

Which languages the backend interface offers is properly limited: you can only switch to a language a language pack exists for. Which locale a site language resolves labels in should not be limited the same way. Accept any well-formed locale, derive its dependency chain the way a listed language’s is derived, and resolve <locale>.locallang.xlf from the extensions that ship it.

To settle before a patch:

  • whether the gate moves out of Locales::createLocale(), or the frontend path stops going through it
  • what Locales::getLocales() and the backend language dropdown return afterwards, since UserSettingsItemsProcFunc and the language pack management read the same list
  • whether a site language’s locale still has to exist as a system locale. #110967 is already removing the per-request setlocale() dependency, which was one of the reasons the gate was defensible

Related, and not the same

  1. asks for separate label files where several site languages share one listed locale, en_GB for Germany and en_GB for Hungary. This issue is the other half: a language the Core does not list at all. A fix for either does not give the other.
  1. is the silent English fallback that makes the present behaviour hard to diagnose.

Out of scope

Translations of the Core itself. Those are maintained on Crowdin by the translation teams and are not part of this repository.

Author Lina Wolf
Created 10/29/26, 18:07
Updated 10/29/26, 18:07
Feature
Under Review Quiet FormEngine aka TCEforms

#111275 Provide easy integration of enums into TCA select fields

A common use case of TCA columns is the representation of enum cases. This currently works either by constructing the items manually or by using a dedicated items processor. A core-native EnumItemsProcessor would ease such an integration.

Author Elias Häußler
Assigned to Elias Häußler
Created 10/29/26, 09:22
Updated 10/29/26, 10:12
Task
Under Review Quiet Backend User Interface TYPO3 CMS 15

#111269 Use searchable selects in backend modules

  1. introduces <typo3-backend-searchable-select> and uses it for FormEngine selectSingle and country fields. Several other backend selects regularly list many entries (users, groups, tables, languages, hosts, types) and benefit from the same search.

This task wraps those single selects. Multiple selects and listboxes (size > 1) stay native. On touch devices without hover the native select UI is kept. With seven or more options the search field shows on opening; with fewer options typing reveals it.

The element is additionally loaded in the backend main frame, as modals render there and not in the module iframe.

How to test

For every location below: open the select, type a part of an option, pick an entry with Enter or a click and check that the module reacts as before (filter applied, form value saved, navigation done).

  1. Site configuration: Site Management > Sites > edit a site > tab “Languages”. The selects “Choose a preset…” and “Use Language from existing site…” next to “Create new language”. Picking an entry still adds the language.
  2. Access: Users > Access, select a page, edit its permissions. Selects “Owner” and “Group”. Also in the list: click the owner or group name of a page; the inline selector loaded via AJAX is searchable, saving still works.
  3. Form editor: Forms > open a form > add/select a “Country select” element > inspector field “Default value” (~250 countries). Inspector “Validators > Add validator” of any field and “Finishers > Add finisher” on form level. The multi selects “Prioritized/Only/Exclude countries” stay native.
  4. Advanced query: System > Database > “Advanced query”. Selects “Table”, the field selects of each condition row and the stored queries in “Load/Save query”.
  5. Inline relation with foreign_selector: Styleguide > Manage page trees > “Create styleguide page tree with data”. Page “styleguide TCA demo > inline usecombination”, open the “Form engine – inline use combination” record. Field inline_1: the select next to “Create new”. Field inline_2 uses autoSizeMax and stays a native listbox.
  6. Log: System > Log, filter “Users” (grouped by groups and users) and “Workspace” (only with workspaces installed).
  7. Backend users: Users > Backend users, filter “Group”.
  8. Redirects, QR codes, Short URLs: Link Management > Redirects, filters “Source host” and “Created by”; QR codes and Short URLs, filter “Source host”. The filters only show when records exist.
  9. Info module: Status > Pagetree Overview and Localization Overview, select a page. Selects “Language”, “Depth” and “Pages”.
  10. Webhooks: Integrations > Webhooks, filter “Type” (needs at least one webhook).
  11. Reactions: Integrations > Reactions, filter “Impersonate user” (needs at least one reaction).
  12. Workspaces: switch to a workspace, Content > Workspaces. Filters “Language” (with flag icon) and “Stage”.
  13. Import/Export: page tree context menu > More options > Import: select “File”. Export: tab “File & Preset”, select “Preset” (needs a saved export preset).
  14. Bookmarks: toolbar > Bookmarks > Manage bookmarks, edit a bookmark, select “Group”.
  15. Record download: needs download presets, e.g. Page TSconfig:
mod.web_list.downloadPresets {
    tt_content {
        10 {
            label = Quick overview
            columns = uid, pid, CType, header, colPos
        }
        20 {
            label = UID and headers only
            columns = uid, header
        }
    }
}

Content > Records, page with content elements, table “Page Content” > “Download”. The select “Preset” in the modal is searchable and the chosen preset is used for the download.

Not included

  • “Create multiple pages” (page type select): new rows are cloned via innerHTML, which would duplicate the rendered trigger.
  • FormEngine value picker: it sits next to a text input and would need a special case.
  • Fixed short lists (depth, status, log level and similar) in other modules.
Author Matthias Vogel
Created 10/28/26, 14:24
Updated 10/29/26, 09:22
Task
Under Review Quiet Form Framework TYPO3 CMS 15

#110656 Throw exception if yaml file does not exist

Author Simon Schaufelberger
Assigned to Simon Schaufelberger
Created 09/08/26, 13:44
Updated 10/29/26, 07:05
Bug
New Quiet TYPO3 CMS 14

#111247 Missing possibility to extend file selectors

With the change https://review.typo3.org/c/Packages/TYPO3.CMS/+/92693 the ElementBrowserParameters DTO misses opportunity to store additional information needed for own file selectors. It should be possible to extend the dto or at least have some data-additional property.

Currently one is forced to reuse or misuse an unused property to be able to pass additional information to the (own) browser.

Author Nicole Hummel
Created 10/26/26, 12:28
Updated 10/26/26, 12:28
Bug
Under Review Quiet Backend User Interface TYPO3 CMS 9

#87328 "Make new translation of this page" can create invalid page translations

Since #81345 the Make new translation of this page feature within the page module directly creates localizations instead of opening the edit view for page translations.

This can lead to invalid page translations if e.g. the title has been configured to be empty in translations (unset l10n_mode) and thus must be filled by editors explicitly. In this case the edit view is shown correctly with errors after localization but one can simply close the view without additional prompt or action. After this the translation exists without title which in itself can lead to further issues. When trying to save instead a proper dialog is shown mentioning the invalid fields.

Author Mathias Brodala
Created 01/04/19, 14:05
Updated 10/26/26, 10:33
Bug
Under Review Quiet Backend User Interface TYPO3 CMS 13

#109751 Text spacing in “+ Add content” modal is not fully applied

In the Backend “Page” module, the “+ Add content” button opens a modal dialog to add new content elements to a page.
When user-defined text spacing is enabled (e.g. via the BITV test bookmarklet “Textabstände” or a browser extension for WCAG text spacing), only the modal heading reflects the changed text spacing, whereas the remaining text (descriptions, categories, buttons, labels, etc.) does not update accordingly.
This violates BITV 2.0 – Check 9.1.4.12 “Textabstände anpassbar” (WCAG 2.1 Success Criterion 1.4.12 “Text Spacing”), as text spacing adjustments are not consistently applied throughout the modal.

Context:

  • Area: TYPO3 Backend, Page module
  • UI Element: “+ Add content” modal
  • Affected texts: All text blocks inside the modal (except the title)

3. Reproduction Steps

  1. Log in to the TYPO3 backend.
  2. Navigate to the Page module.
  3. Select any page that can be edited.
  4. Click on the “+ Add content” button to open the modal for creating a new content element.
  5. Now adjust text spacing, e.g.:
  6. Either run the BITV test bookmarklet “Textabstände” in the browser (see link in the reference section).
  7. Or use a browser extension that applies the WCAG 1.4.12 test values for text spacing (e.g. adjusting line-height, letter-spacing, word-spacing and spacing between paragraphs).
  8. Observe the behavior in the open modal.

Expected result:

  • All text within the modal (heading, descriptions, categories, labels, buttons, help texts, etc.) fully reflects the changed text spacing.
  • With increased text spacing, no content is cut off or overlapping, and horizontal scrolling is not required.
  • Actual result:
  • The modal heading reacts to the changed text spacing.
  • Other texts (descriptions, labels, buttons, etc.) do not reflect the changed text spacing or only partially.
  • With increased text spacing, some content can become overlapping, cut off or harder to read.

4. Impact

  • Makes the modal hard or impossible to use for users depending on custom text spacing.
  • At risk of failing BITV/WCAG accessibility audits for the backend.

Link:
https://bitvtest.de/pruefschritt/bitv-20-web/bitv-20-web-9-1-4-12-textabstaende-anpassbar

Author Christian Jung
Created 05/04/26, 09:25
Updated 10/26/26, 09:58
Bug
New Quiet Workspaces TYPO3 CMS 14

#111216 Workspaces: "Send to stage" modal can be submitted multiple times, causing duplicate publish requests and errors

If a users klicks the “OK” Button in the “Send to stage” modal in the Workspaces module mulitple times it leads to e.g. “Element sys_file_reference:… does not exist” errors, since mulitple request are sent. The publishing process is still successfull, but it would be better if only one request is sent, or the button is disabled after the first click.

Steps to reproduce:
  1. Open the Workspaces module.
  2. Click “Send to next stage” on the record.
  3. In the modal, click “OK” several times quickly.
Author Lisa Kreitz
Created 10/23/26, 13:18
Updated 10/26/26, 07:12
Task
Under Review Quiet Backend API TYPO3 CMS 15

#111034 Clarify the override options for the TCA column configuration

Based on the TCA configuration of the column type, a wide range of configurations are derived, such as the generation of the database’s default schema, the mapping to global configuration objects (TcaSchemaApi), the display of backend forms (FormEngine), the persistence layer (DataHandler) and the mapping of values in Extbase’s ORM.

Changes to the ‘column config type’ specification therefore have potentially far-reaching consequences.
TYPO3 offers a wide range of options for overriding TCA, primarily by extension authors in `Configuration/TCA/Overrides`, as well as in `columnOverrides` depending on the record type, or in `overrideChildTca` depending on the child table.

As all overrides are stored in the same database field, the values must be compatible.
Other functions based on the TCA also rely on this data structure.

Restrictions on overrides were recommended depending on the area of application, but were not technically enforced.

For the purpose of clarification, the following is now ensured:
column > config > type must not be overridden or modified by any override option.

Author Daniel Windloff
Assigned to Daniel Windloff
Created 10/13/26, 01:14
Updated 10/26/26, 04:17
Bug
Under Review Quiet DataHandler aka TCEmain TYPO3 CMS 15

#110901 Validation and transformation for column type "color"

The column type “color” should save colors in a uniform way.
It depends on the option `opacity`.
The `DataHandler->checkValueForColor` know transforms and validate colors.

Only long hex colors with a leading # are saved as colors now.

Author Daniel Windloff
Assigned to Daniel Windloff
Created 10/03/26, 04:04
Updated 10/26/26, 03:49
Task
Under Review Quiet TYPO3 CMS 15

#110373 Apply PHP code simplifications

- Return expressions directly instead of assigning single-use variables.
- Use foreach values instead of repeated keyed array lookups.
- Pass variadic arguments directly instead of unpacking temporary arrays.
- Replace conditional bounds checks with min() and max().
- Use native string helpers such as str_starts_with().
- Remove redundant assignments, continue statements, concatenations, and PHPDoc.
- Simplify boolean expressions and test helpers.
- Apply equivalent cleanups across 110 files in Core and system extensions.

Author Wouter Wolters
Assigned to Wouter Wolters
Created 08/04/26, 20:38
Updated 10/24/26, 19:14
Bug
Needs Feedback Quiet TYPO3 CMS 13

#108272 Changing the case of folder names does not work

Steps to reproduce

Open the backend module Filelist.
Rename a folder from “name” to “NAME”.

Current behaviour

Before rename: “name“
After rename: “name” (case change not applied)

Expected behaviour

Before rename: “name“
After rename: “NAME” (case change applied)

Author Dennis Purisevic
Created 11/23/25, 10:53
Updated 10/24/26, 07:13
Feature
Under Review Quiet Backend User Interface

#110101 Add skip links for keyboard users in TYPO3 backend

Steps to reproduce

Log in to the TYPO3 backend.
Use only the keyboard (Tab / Shift+Tab, arrow keys) to navigate the backend interface.
Start from the very top of the page (browser address bar → page content).
Try to quickly reach:

  • The main navigation / page menu,
  • The site tree (if available in the current module),
  • The main content area (e.g. language selector and content form).

Current result

There are no skip links at the beginning of the backend page.
Keyboard users must tab through multiple controls and interface elements before reaching the main areas they want to interact with (e.g. main menu, site tree, main content).
There are no intermediate skip links before the page menu or before the site tree to jump directly to the next major section.
As a result, navigating the backend using only a keyboard is time‑consuming, repetitive, and hard to orient in, especially for frequent users and screen reader users.

Expected result

The TYPO3 backend provides skip links to allow keyboard users to jump quickly between main regions of the interface.
At the top of the page, a skip link (or a small group of skip links) is available and focusable, allowing quick navigation to:

  • The page/menu navigation,
  • The site tree (if present),
  • The main content area (e.g. top language selector / content).

Impact

Affects keyboard‑only users, screen reader users, and many users with motor or cognitive impairments who rely on efficient keyboard navigation.
Without skip links, users must repeatedly tab through the same interface elements on every page, which:

Reduces efficiency and increases fatigue,
Makes it harder to orient within the backend,
Can discourage or effectively block some users from managing content.
This impacts compliance with WCAG / BITV criteria related to keyboard accessibility and bypassing blocks of content, in particular WCAG 2.4.1 (Bypass Blocks).

Recommended solution (for context / implementation guidance)

Example: https://design-system.service.gov.uk/components/skip-link/

Add a skip link container at the very beginning of the <body> that becomes visible on keyboard focus.<br>Provide skip links to:</body>

The page/menu navigation,
The site tree (if present in the current view),
The main content area (e.g. language selector / main form).
Ensure these targets have corresponding landmarks or IDs to receive focus.

Use a common, visually recognizable style for skip links when they receive focus (e.g. visible outline, contrast, simple positioning).
Ensure skip links are implemented in a way that works consistently across major browsers and screen readers.

Definition of done

At the top of the backend page, focusable skip links exist that allow jumping to:

Page/menu navigation,
Site tree (if present),
Main content area.

Skip links are:

  • Reachable via keyboard,
  • Clearly visible on focus,
  • Correctly associated with their target sections (via IDs / landmarks).
  • Screen reader and keyboard testing confirm that the skip links work reliably and significantly improve navigation.
  • No visual regressions in the backend layout for mouse users.

Acceptance criteria

At the beginning of the <body>, there is a set of skip links that, when focused and activated, move focus to:</body>

Page/menu navigation,
Site tree (when available),
Main content area.
Skip links near main sections

Skip links are visible when focused and hidden otherwise (using a standard accessible pattern).
Targets of skip links (menu, site tree, main content) are focusable or handle focus correctly.
Keyboard‑only navigation is significantly simplified; users can quickly reach main sections without excessive tabbing.

Tested with at least one screen reader (e.g. NVDA + Chrome) and pure keyboard navigation to confirm that:

Skip links are announced,
They move focus to the intended sections,
They improve orientation and navigation.
Compliance

Accessibility review confirms that skip links contribute to meeting WCAG 2.4.1 (Bypass Blocks) and improve overall keyboard usability of the TYPO3 backend.

Author Aphisit Chanathale
Created 06/25/26, 07:40
Updated 10/23/26, 20:30
Task
Needs Feedback Quiet Backend User Interface TYPO3 CMS 13

#102695 Revise taborder of the pagetree area

When navigating through the backend with the tab key, the order of the focused elements isn’t intuitive at all.

Author Willi Wehmeier
Created 12/19/23, 08:33
Updated 10/23/26, 08:04
Epic
Author Tymoteusz Motylewski
Created 09/19/18, 00:33
Updated 10/23/26, 06:23
Bug
Under Review Quiet Backend User Interface TYPO3 CMS 13

#108011 Fix DarkMode browser-default-BG-color:white flicker

it does take too much time [ms] (for the browser) to parse the html{background-color} resulting in white-flicker @ dark-mode

my idea was ..

+++ vendor/typo3/cms-backend/Classes/Template/PageRendererBackendSetupTrait.php    2025-11-07 19:27:45.406969057 +0100
@@ -54,6 +54,8 @@
     ): void {
         $pageRenderer->setLanguage($languageService->getLocale());
         $pageRenderer->setMetaTag('name', 'viewport', 'width=device-width, initial-scale=1');
+        $pageRenderer->setMetaTag('name', 'theme-color', '#f5f5f5', ['media' => '(prefers-color-scheme:light)']);
+        $pageRenderer->setMetaTag('name', 'theme-color', '#171717', ['media' => '(prefers-color-scheme:dark)']);
         $pageRenderer->setFavIcon($this->getBackendFavicon($extensionConfiguration, $request));
         $nonce = $request->getAttribute('nonce');
         if ($nonce !== null) {

output is broken ..

<meta name="generator" content="TYPO3 CMS">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="theme-color" content="#f5f5f5">
<meta name="theme-color:media" content="(prefers-color-scheme:light)">
<meta name="theme-color" content="#171717">
<meta name="theme-color:media" content="(prefers-color-scheme:dark)">

it should be this ..

<meta name="generator" content="TYPO3 CMS">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="theme-color" content="#f5f5f5" media="(prefers-color-scheme:light)">
<meta name="theme-color" content="#171717" media="(prefers-color-scheme:dark)">

=> you might also have to fix `\TYPO3\CMS\Core\MetaTag\*MetaTagManager`

Author Marcus Förster
Created 11/07/25, 18:38
Updated 10/22/26, 10:28
Bug
Under Review Quiet TYPO3 CMS 15

#110645 Ensure RootlineUtility respects the full visibility aspect

RootlineUtility does not consistently consider the full visibility aspect when resolving related records and generating cache identifiers. This can cause hidden relations to be incorrectly included or omitted, or cached results to be reused across different visibility settings.

Relation resolution and cache identifiers should account for all relevant visibility settings. Extend the sys_refindex.lookup_rec index with ref_table to keep queries filtering by the referenced table efficient.

Author Matthias Vogel
Created 09/07/26, 09:13
Updated 10/19/26, 12:42
Bug
Under Review Quiet SEO TYPO3 CMS 13

#111143 HrefLangGenerator renders alternates for mount point URLs while the canonical points to the mounted page

Prerequisites

Two sites with English and German:

  • the main site example.com
  • a product site product.example.com with a translated start page

Steps to reproduce

  1. On example.com, create a translated page “Product” of type “Mount Point”. Mount the start page of product.example.com and enable “Show content of mounted page”. Set the same page type on the translation.
  2. Open example.com/product and look at the head.

Actual result

<link rel="canonical" href="https://product.example.com/">
<link rel="alternate" hreflang="en" href="https://www.example.com/product">
<link rel="alternate" hreflang="de" href="https://www.example.com/de/produkt">

The canonical says “the real page is on product.example.com”, the hreflang tags say “the language versions are on example.com”. Search engines ignore hreflang that points to non-canonical URLs.

Expected result

Canonical and hreflang point to the same site.

Additional information

  • Reproduced on 13.4.35 for the mount point page with “Show content of mounted page”. Per #93300 subpages below a mount point are affected as well. Same code in 14.3 and main.
  • CanonicalGenerator::checkDefaultCanonical() removes the mount point before building the URL (since #93300), HrefLangGenerator::__invoke() does not.
  • Possible fix: skip hreflang when the page is rendered through a mount point, like the existing skip for an explicit canonical_link. Alternatively, build the alternates for the product site, which needs its languages and URLs.

Related: #93300

Author Alexander Hahn
Created 10/19/26, 08:37
Updated 10/19/26, 08:58
Task
Author Oliver Bartsch
Assigned to Oliver Bartsch
Created 10/09/26, 21:52
Updated 10/19/26, 07:27

Showing results 201 to 225 of 1561