Showing results 926 to 950 of 1561

Bug
New Orphaned Workspaces TYPO3 CMS 13

#108961 Workspaces: custom stages are skipped when they shouldn't

We want to use multiple custom stages and have multiple users who have permissions for one or more stages.

During testing I noticed that custom stages can be skipped.

For example you have the following stages:

1 Bearbeiten (default) – just for editors
2 CUSTOM STAGE 1 – check 1 by information security officer
3 CUSTOM STAGE 2 – check 2 by quality management
4 CUSTOM STAGE 3 – check 3 by individual person
5 Bereit zum veröffentlichen (default)

CUSTOM STAGE 1 and 2 are mandatory and it shouldn’t be possible to skip them.

Now a user has permission for the stages Bearbeiten and CUSTOM STAGE 3

A record in stage Bearbeiten can now be send to the stage CUSTOM STAGE 2 , therefor skipping CUSTOM STAGE 1 .
It’s also possible to send it directly to the stage Bereit zum veröffentlichen and skip the custom stages alltogether, probably because the user has permissions for the stage CUSTOM STAGE 3 too?

CUSTOM stages shouldn’t be allowed to be skipped. Maybe it’s possible to implement an option that a record can only be send to the next stage, so skipping stages is impossible?

Author David Menzel
Created 02/12/26, 13:42
Updated 02/12/26, 13:42
Bug
New Orphaned Workspaces TYPO3 CMS 13

#108954 Workspace History not in LIVE after publish (again)

I noticed that the history from a CUSTOM workspace is not available in the LIVE workspace:
I think this is the same issue like here: https://forge.typo3.org/issues/102381

When changes are published I only get the final change with the tag “veröffentlicht” in the LIVE worspace history but the individual steps, like when a record was send to another stage or were edited are missing. This information is only available in the CUSTOM workspace.

Is this the correct behaviour or should the individual steps als be available in the LIVE Workspace?

Author David Menzel
Created 02/12/26, 09:54
Updated 02/12/26, 09:54
Bug
New Orphaned Backend User Interface TYPO3 CMS 12

#108945 Sorting with duplicate sorting values not possible

Given the following database content of tt_content:

+-------+---------+
| uid   | sorting |
+-------+---------+
| 11467 |       2 |
| 12326 |    1153 |
| 12233 |    1217 |
| 12343 |    1426 |
| 12298 |    1539 |
| 12230 |    3868 |
|  6950 |    3876 |
| 12008 |    3876 |
| 12346 |    4132 |
| 12334 |    4400 |

Now, in the backend GUI a user wants to move the content element with uid 12346 directly before 12008. This is not possible, the sorting stays at 4132.

I assume, this is because uid 6950 and uid 12008 have the same sorting.

Setting the sorting of uid 12008 to, for example, 4000 manually in the database, then 12346 can be moved via GUI before 12008 again.

Author Chris Müller
Created 02/11/26, 14:05
Updated 02/11/26, 14:09
Task
New Orphaned DataHandler aka TCEmain TYPO3 CMS 14

#107862 Remove mirror from SimpleDataHandlerController and EditDocumentController

The mirror is rarely used. To streamline the internal state of the DataHandler, the function will be removed.

Author Daniel Windloff
Assigned to Daniel Windloff
Created 10/27/25, 16:30
Updated 02/07/26, 17:24
Feature
Accepted Orphaned Fluid Styled Content

#93780 New File Icons for Uploads

The icon set we’re using is around since at least v4. They now are too small, and they should be SVG instead of GIF. Oh, and extensions are missing.
I’d be happy to work on that issue.

(Actually, I believe the extension-icon should be provided as a background-image via CSS, but that is a different issue.)

Related: [1]

Author Nils Hodyas
Assigned to Benjamin Kott
Created 03/19/21, 09:33
Updated 02/07/26, 08:58
Epic
New Orphaned Backend User Interface

#108657 Support `maxitems: 1`

While a full definition of “maxitems: XXX” might not be needed, it would be nice to be able to define that a colPos should only have ONE instance of a content element type.

For example a “hero” colPos should only be able to contain exactly one “textmedia” element.

Currently, as soon as a content element type is allowed, any amount of instances could be added, leading to a wrongly built frontend.

Author Garvin Hicking
Created 01/16/26, 13:12
Updated 02/06/26, 19:38
Task
Accepted Orphaned Database API (Doctrine DBAL) TYPO3 CMS 13

#101985 Deal with leftover sql definitions from type=group

If a group field is defined as maxitems = 1 and has only one table in the allowed parameter, the resulting value is an integer. After #101908 these would be converted to text, so the sql definition was kept in place.
Deal with this exception from the rule and find a clean way to get rid of the sql definition and have those fields as integers

possible solutions:
- introduce a new TCA type for this exact configuration
- rewrite those definitions to selectSingle
- something else

Author Anja Leichsenring
Assigned to Anja Leichsenring
Created 09/21/23, 04:29
Updated 02/06/26, 18:13
Bug
Accepted Orphaned File Abstraction Layer (FAL) TYPO3 CMS 11

#99548 files of file collection uploaded from folder are not referenced in backend fileList Module

when I select a folder in the “File collection“
the reference to these files is missing in the filelist backend module.

!clipboard-202301161222-t1dnk.png!

Author Collab Team
Created 01/16/23, 11:27
Updated 02/06/26, 12:49
Task
New Orphaned Backend User Interface TYPO3 CMS 13

#108883 Content > Layout (formerly Web > Page) should be more Dark-Mode friendly

Latest version of EXT:theodia on TER and Packagist provides a dark-mode compatible extension icon which is used as the icon for the two plugins provided by the extension.

When the Backend is set to Dark Mode, the icon is hardly visible as it’s black on Dark. But if the module would incorporate the icon using this (“icon-color” class is actually not needed in my test but is the same markup as the edit pencil icon), this would work:

<span class="icon-markup">
   <svg class="icon-color"><use xlink:href="/_assets/880a1153de7de6fea22ae83da382980a/Icons/Extension.svg?1770312065"></use></svg>
</span>

instead of:

<span class="icon-markup">
   <img src="/_assets/880a1153de7de6fea22ae83da382980a/Icons/Extension.svg?1770312065" width="16" height="16" alt="">
</span>

Problem actually exists since TYPO3 v13, but since the markup changes a bit, possibly I could get this gets only fixed with upcoming v14.

Note: Extension Manager shows the same issue with extension icon.

Author Xavier Perseguers
Created 02/06/26, 08:50
Updated 02/06/26, 08:50
Bug
Under Review Orphaned Backend JavaScript TYPO3 CMS 12

#101210 PageView: Jump to the element currently being edited

As an editor, I would be happy if after editing (and closing) an element and returning to the PageView, I would be back at the place where I just started editing.
Especially with longer pages, which are edited from top to bottom, this saves unnecessary scrolling time, and I can continue with the next one right away.

TYPO3 offers 3 ways to start editing a CE:
1. edit icon
2. click into the preview
3. via menu

For 1 &2 this works.
For 3 unfortunately not – you always end up at the top of the page.

(Screen is taken in TYPO3 v11, behaviour in v12 is the same)

Author Julian Hofmann
Created 06/30/23, 11:56
Updated 02/05/26, 06:07
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#108835 Sorting option dropdown in the file list not labeled reliably

Description

In the TYPO3 backend filelist, the sorting icon in the column header (e.g. column “Name”) is currently labelled only by the visible column title “Name”. For screen reader users, it is therefore not clear that this icon / button is an interactive control for sorting. The function of the graphical element (sorting / opening sorting options) is not clearly exposed programmatically.

Reproduction steps

  1. Open the TYPO3 backend and navigate to the Filelist.
  2. In the filelist, locate the column header “Name” (or another sortable column) that contains the sorting icon.
  3. Inspect the sorting icon or its associated button/link using the browser DevTools.
  4. Check how the accessible name is implemented:
  5. There is no explicit accessible name that describes the sorting function (e.g. no aria-label like “Sorting: open options”).
  6. The label effectively comes only from the column title “Name”.
  7. Test with a screen reader (e.g. NVDA, JAWS, VoiceOver) how the element is announced and whether it is clearly conveyed as a sorting control.

Impact

  • Screen reader users cannot reliably recognize the sorting icon as a sorting control and may perceive it only as a column header.
  • The function “Sorting: open/change options” is not clearly communicated, which can lead to uncertainty or non-use of the sorting feature.
  • The usability and accessibility of the filelist are reduced for users relying on assistive technologies.

Target group

  • Screen reader users
  • Users with visual impairments or blindness
  • TYPO3 backend editors relying on assistive technologies

Severity

Medium (an important interaction option in the filelist is not clearly exposed as a control for screen reader users).

Frequency

Occurs for every sortable column header in the filelist (100 % of the affected columns).

Definition of Done

  • The sorting icon and its associated button/link in the filelist column header have a clear, programmatically determinable accessible name that describes the sorting function (e.g. “Sorting: open options”).
  • Screen readers announce the element as a control with a sorting function, not just as a plain column header.
  • Manual tests with at least one screen reader (e.g. NVDA, JAWS, VoiceOver) have been performed and confirm that purpose and function of the control are understandable.
  • The visual appearance (icon, “Name” text, hover and focus styles) remains unchanged.

Suggestion

Add a clear accessible name to the button/link of the sorting icon, for example using aria-label=“Sortierung: Optionen öffnen” or in English aria-label=“Sorting: open options”.

Recommended solution

Add a descriptive aria-label to the interactive element (button or link) controlling the sorting icon in the filelist, for example:

Optionally, adapt the aria-label dynamically to reflect different sort states (e.g. “Sort ascending by name” / “Sort descending by name”).
Ensure that the visible text “Name” remains correctly exposed as the column header and that the aria-label is used solely to describe the interactive sorting function.

References / WCAG 2.2 Reference

  • WCAG 2.2 – 2.5.3 Label in Name: The accessible name should reflect the purpose and function of the control (e.g. “Sorting: open options”).
  • WCAG 2.2 – 4.1.2 Name, Role, Value: Interactive elements require a programmatically determinable name that clearly describes their function.
  • WCAG 2.2 – 1.3.1 Info and Relationships: Relationships and functions of controls (e.g. sorting a column) must be programmatically determinable.
Author Jennifer Geiß
Created 02/03/26, 08:44
Updated 02/04/26, 08:33
Epic
Author Elias Häußler
Assigned to Elias Häußler
Created 10/27/25, 20:27
Updated 02/03/26, 20:52
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 13

#108686 Unsaved-Changes Dialog: Clear Button Hierarchy and Labeling

In the “Close without saving” dialog, action labels are not clear and the visual/functional hierarchy of buttons is ambiguous. Users must quickly understand the prompt and distinguish primary from secondary/neutral actions. Accessibility (e.g., clear labels, logical focus order, sufficient contrast) must be ensured.

Reproduction Steps

  1. Edit a page/record.
  2. Attempt to close without saving (e.g., “Close”, browser back/navigation).
  3. “Close without saving” dialog appears.
  4. Observe: Button labels and order are unclear; hierarchy is hard to recognize.

Impact

  • Increased risk of errors (e.g., unintended discard).
  • Lower efficiency and higher frustration, especially for keyboard and screen reader users.
  • Violations of UX/a11y principles (contrast, no color-only communication; clear naming).

Recommended Solution

  • Primary action as a clearly highlighted primary button (e.g., “Save & close” or “Discard changes”) on the right; secondary/Cancel on the left.
  • Clear, consistent labels; no icon-only actions. Use aria-label for icon controls.
  • Logical focus order: title → body text → primary → secondary → cancel; tested with keyboard and screen readers per WCAG.
  • Sufficient color contrast; do not rely on color alone to convey meaning.

Definition of Done

  • New dialog structure and button order implemented and visually validated.
  • Accessibility check: contrast, focus order, screen reader announcements (aria-label/role) passed.
  • UX review approved; copy finalized.
  • QA: Manual tests across key viewports; keyboard-only operation works reliably.

Acceptance Criteria

  • Buttons have clear, unambiguous labels.
  • Each action’s function is immediately recognizable (text + hierarchy).
  • Visual and functional hierarchy is clear: Primary > Secondary > Cancel.
  • Pop-up is clearly structured: meaningful title, short explanatory text, logically ordered actions.
  • Keyboard navigation and screen reader output are correct;
  • no color-only communication;
  • sufficient contrast.
Author Christian Jung
Created 01/19/26, 10:28
Updated 02/02/26, 11:12
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#108824 File upload - Heading structure inconsistent

Description

In the “Upload file” area, a heading is implemented inside a switch/button. The switch/button contains a level 3 heading. Using a heading element inside an interactive control (switch/button) is semantically incorrect and may lead to confusing output for assistive technologies.

Reproduction steps

  1. Open the TYPO3 backend and navigate to the module/record containing the “Upload file” section.
  2. Use the browser DevTools to inspect the HTML structure of the switch/button in the upload area.
  3. Check whether a heading element (

    –

    , specifically

    ) is nested inside the switch/button.

  4. Confirm that the button label is implemented as a level 3 heading.

Impact

  • Screen reader users may perceive the heading inside the button as a structural heading, although it is actually just the label of an interactive control.
  • The semantic document structure is weakened, because headings should describe sections of content and not be part of a control itself.
  • This can cause confusing or redundant announcements in screen readers.

Target group

  • Screen reader users
  • Users who rely strongly on clear semantic structure (e.g. cognitive impairments)
  • TYPO3 backend editors using assistive technologies

Severity

Medium (semantic issue affecting understandability of structure for assistive technologies, but limited to a specific area/control).

Frequency

Occurs every time the affected “Upload file” area is opened (100%).

Definition of Done

  • There is no heading inside a switch/button in the affected “Upload file” area anymore.
  • The former heading used as button label is implemented as a regular label.
  • Screen readers announce the control with a clear role and accessible name, without treating it as a heading.
  • The page’s heading outline is not distorted by a heading nested in a button.
  • Manual tests with at least one screen reader (e.g. NVDA/JAWS/VoiceOver) have been performed.

Recommended solution

Remove the current h3 element and replace it with an element marked up as label.

References / WCAG 2.2 Reference

  • WCAG 2.2 – 1.3.1 Info and Relationships: Headings are meant for structuring content; button semantics must not distort this structure.
  • WCAG 2.2 – 2.4.6 Headings and Labels: Labels should clearly describe the purpose of controls; headings and labels serve different roles.
  • WCAG 2.2 – 4.1.2 Name, Role, Value: Interactive elements like buttons must have a clear role and accessible name; mixing heading and button semantics can confuse assistive technologies.
Author Jennifer Geiß
Created 02/02/26, 09:10
Updated 02/02/26, 09:10
Bug
New Orphaned Link Handling & Redirect Handling TYPO3 CMS 11

#102901 Automatically created redirects can point to the same URL as the source

If you update a slug, typo3 will create a redirect that removes all additional query params (“Keep GET Parameters” = off).

It may happen, that – through changing of slugs – a redirect is created, that effectively looks this way:

curl -I ‘https://my.site/path/to/page?type=200&cHash=someCacheHash’

HTTP/2 307 
content-type: text/html; charset=UTF-8
x-redirect-by: TYPO3 Redirect 101
location: https://my.site/path/to/page

So when generating those links in your fluid template you will never receive the content you want to load, you will always load page type 0.

This affects all required query parameters.

My suggestion:
If the source and the generated target url are the same:

1) dont send the redirect
2) if not protected, delete the obsolete redirect

Author Philipp Wrann
Assigned to Stefan Bürk
Created 01/23/24, 15:03
Updated 01/30/26, 09:59
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#108804 Redirects: SourceHostProvider doesn't find sites configured on child pages of webmount

When a non-admin backend user has a webmount set to a page that doesn’t have a site configuration directly, but child pages of that webmount do have site configurations, no domains are shown in the source host dropdown when creating/editing redirects.

Steps to reproduce:

  1. Create a page structure like:
    📁 Parent Page (uid: 100) ← no site config
    📁 Site A (uid: 101) ← site config with domain-a.com
    📁 Site B (uid: 102) ← site config with domain-b.com
  2. Create a backend user with webmount set to page 100
  3. Log in as that user and open the Redirects module
  4. Try to create a new redirect
  5. The source host dropdown shows no domains (only * if allowed)
Author Sascha Friedl
Created 01/29/26, 13:38
Updated 01/29/26, 13:45
Bug
New Orphaned Import/Export (T3D) TYPO3 CMS 13

#108801 export / import does not respect IRRE-relations in TCA columnsOverrides

Exporting and importing Elements with inline-relations, defined only in columnsOverrides, get not respected on export.
On Import the counting relation-field is taken as uid of foreign_table!
The foreign_field of the falsely selected foreign record gets set to the new created uid.
This is results in unpredictable scrambled relations on larger Imports!

A minimal example including TCA, used cli-commands and SQL-Results before and after Import is following:
This example should reproduce the error for testing.

TCA relation

Configuration/TCA/tx_test_relation.php

<?php

defined('TYPO3') or die();

return call_user_func(function (): array {
    $tableName = 'tx_test_relation';

    return [
        'ctrl' => [
            'title' => $tableName,
            'label' => 'label',
            'tstamp' => 'tstamp',
            'crdate' => 'crdate',
            'hideTable' => false,
            'default_sortby' => 'ORDER BY cruser_id DESC',
            'delete' => 'deleted',
            'sortby' => 'sorting',
            'enablecolumns' => [
                'disabled' => 'hidden',
                'starttime' => 'starttime',
                'endtime' => 'endtime',
            ],
            'searchFields' => '',
            'security' => [
                'ignorePageTypeRestriction' => true,
            ],
        ],
        'types' => [
            '0' => [
                'showitem' => 'label, tt_content',
            ],
        ],
        'columns' => [

            'label' => [
                'exclude' => true,
                'label' => $tableName . 'label',
                'config' => [
                    'type' => 'input',
                    'size' => 60,
                    'eval' => 'trim',
                ],
            ],

            'tt_content' => [
                'label' => 'tt_content',
                'config' => [
                    'type' => 'passthrough',
                    // same result with backward relation
                    //'type' => 'inline',
                    //'foreign_table' => 'tt_content',
                    //'foreign_field' => 'tx_test_relation', 
                ],
            ],
        ],
    ];
});

TCA tt_content

Configuration/TCA/Overrides/tt_content.php

<?php

defined('TYPO3') or die();

\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addTCAcolumns(
    'tt_content',
    [
        'tx_test_relation' => [
            'label' => 'tx_test_relation',
            'exclude' => 1,
            'config' => [
                'type' => 'passthrough',
                /* impexp works with direct inclusion of relation
                'type' => 'inline',
                'foreign_table' => 'tx_test_relation',
                'foreign_field' => 'tt_content',
                'minitems' => 1,
                */
            ]
        ],
    ]
);
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addToAllTCAtypes(
    'tt_content',
    'tx_test_relation',
);

// if inline is defined via columnsOverrides, impexp produces error
$GLOBALS['TCA']['tt_content']['types']['header']['columnsOverrides']['tx_test_relation']['config'] = [
    'type' => 'inline',
    'foreign_table' => 'tx_test_relation',
    'foreign_field' => 'tt_content',
    'minitems' => 1,
];

Before import:

SELECT uid, pid, CType, header, tx_test_relation FROM tt_content WHERE pid IN (758,759);
+------+-----+--------+------------+------------------+
| uid  | pid | CType  | header     | tx_test_relation |
+------+-----+--------+------------+------------------+
| 1653 | 758 | header | testexport |                3 | <- holds 3 items
| 1654 | 759 | header | exportme   |                2 | <- holds 2 items, should be exported
+------+-----+--------+------------+------------------+
SELECT uid,pid,label,tt_content FROM tx_test_relation;
+-----+-----+------------+------------+
| uid | pid | label      | tt_content |
+-----+-----+------------+------------+
|   1 | 758 | Uid 1      |       1653 |
|   2 | 758 | Uid 2      |       1653 |
|   3 | 758 | Uid 3      |       1653 |
|   4 | 759 | exportme 1 |       1654 |
|   5 | 759 | exportme 2 |       1654 |
+-----+-----+------------+------------+

Commands for export and import: (Same results for --type=t3d)

bin/typo3 impexp:export --type=xml --pid 759 --levels 3 --table=tt_content --table=tx_test_relation --exclude-disabled-records -- TestExport
> [OK] Exporting to fileadmin/user_upload/_temp_/importexport/TestExport.xml succeeded. 
bin/typo3 impexp:import -- fileadmin/user_upload/_temp_/importexport/TestExport.xml -759
> [OK] Importing fileadmin/user_upload/_temp_/importexport/TestExport.xml to page -759 succeeded.

After import:

SELECT uid, pid, CType, header, tx_test_relation FROM tt_content WHERE pid IN (758,759,778);
+------+-----+--------+------------+------------------+
| uid  | pid | CType  | header     | tx_test_relation |
+------+-----+--------+------------+------------------+
| 1653 | 758 | header | testexport |                2 |
| 1654 | 759 | header | exportme   |                4 |
| 1667 | 778 | header | exportme   |                1 | <- new imported
+------+-----+--------+------------+------------------+

SELECT uid,pid,label,tt_content FROM tx_test_relation;
+-----+-----+------------+------------+
| uid | pid | label      | tt_content |
+-----+-----+------------+------------+
|   1 | 758 | Uid 1      |       1653 |
|   2 | 758 | Uid 2      |       1667 | <- uid 2 taken from tt_content[uid=1654].tx_test_relation = 2
|   3 | 758 | Uid 3      |       1653 |
|   4 | 759 | exportme 1 |       1654 |
|   5 | 759 | exportme 2 |       1654 |
|   6 | 778 | exportme 2 |       1654 | <- new imported
|   7 | 778 | exportme 1 |       1654 | <- new imported
+-----+-----+------------+------------+

exported XML (shortend)

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<T3RecordDocument>
    <header type="array">
        <XMLversion>1.0</XMLversion>
        <meta type="array">
            <title></title>
            <description></description>
            <notes></notes>
            <packager_username>_cli_</packager_username>
            <packager_name></packager_name>
            <packager_email></packager_email>
            <TYPO3_version>13.4.23</TYPO3_version>
            <created>Thu 29. January 2026</created>
        </meta>
        <static_tables index="relStaticTables" type="array"></static_tables>
        <excludeMap type="array"></excludeMap>
        <softrefCfg type="array"></softrefCfg>
        <extensionDependencies type="array"></extensionDependencies>
        <charset>utf-8</charset>
        <pagetree type="array">
            <node index="759" type="array">
                <uid>759</uid>
            </node>
        </pagetree>
        <records type="array">
            <table index="pages" type="array">
                <rec index="759" type="array">
                    <uid>759</uid>
                    <pid>1</pid>
                    <title>exportme</title>
                    <relations index="rels" type="array"></relations>
                    <softrefs type="array"></softrefs>
                </rec>
            </table>
            <table index="tt_content" type="array">
                <rec index="1654" type="array">
                    <uid>1654</uid>
                    <pid>759</pid>
                    <title>exportme</title>
                    <relations index="rels" type="array"></relations>
                    <softrefs type="array"></softrefs>
                </rec>
            </table>
            <table index="tx_test_relation" type="array">
                <rec index="4" type="array">
                    <uid>4</uid>
                    <pid>759</pid>
                    <title>exportme 1</title>
                    <relations index="rels" type="array"></relations>
                    <softrefs type="array"></softrefs>
                </rec>
                <rec index="5" type="array">
                    <uid>5</uid>
                    <pid>759</pid>
                    <title>exportme 2</title>
                    <relations index="rels" type="array"></relations>
                    <softrefs type="array"></softrefs>
                </rec>
            </table>
        </records>
        <pid_lookup type="array">
            <page_contents index="1" type="array">
                <table index="pages" type="array">
                    <item index="759">1</item>
                </table>
            </page_contents>
            <page_contents index="759" type="array">
                <table index="tt_content" type="array">
                    <item index="1654">1</item>
                </table>
                <table index="tx_test_relation" type="array">
                    <item index="4">1</item>
                    <item index="5">1</item>
                </table>
            </page_contents>
        </pid_lookup>
    </header>
    <records type="array">
        <tablerow index="pages:759" type="array">
            <fieldlist index="data" type="array">
                <field index="uid" type="integer">759</field>
                <field index="pid" type="integer">1</field>
                <field index="tstamp" type="integer">1769598933</field>
                <field index="crdate" type="integer">1769598509</field>
                <field index="deleted" type="integer">0</field>
                <field index="hidden" type="integer">0</field>
                <field index="starttime" type="integer">0</field>
                <field index="endtime" type="integer">0</field>
                <field index="title">exportme</field>
                <field index="slug">/exportme</field>
                <field index="doktype" type="integer">1</field>
                <field index="TSconfig" type="NULL"></field>
                <field index="is_siteroot" type="integer">0</field>
                [...]
            </fieldlist>
            <related index="rels" type="array"></related>
        </tablerow>
        <tablerow index="tt_content:1654" type="array">
            <fieldlist index="data" type="array">
                <field index="uid" type="integer">1654</field>
                <field index="pid" type="integer">759</field>
                <field index="tstamp" type="integer">1769675355</field>
                <field index="crdate" type="integer">1769607299</field>
                <field index="sorting" type="integer">1</field>
                <field index="CType">header</field>
                <field index="header">exportme</field>
                <field index="colPos" type="integer">0</field>
                [...]
                <field index="tx_test_relation" type="integer">2</field>
            </fieldlist>
            <related index="rels" type="array"></related>
        </tablerow>
        <tablerow index="tx_test_relation:4" type="array">
            <fieldlist index="data" type="array">
                <field index="uid" type="integer">4</field>
                <field index="pid" type="integer">759</field>
                <field index="tstamp" type="integer">1769675355</field>
                <field index="crdate" type="integer">1769675355</field>
                <field index="deleted" type="integer">0</field>
                <field index="hidden" type="integer">0</field>
                <field index="starttime" type="integer">0</field>
                <field index="endtime" type="integer">0</field>
                <field index="sorting" type="integer">1</field>
                <field index="label">exportme 1</field>
                <field index="tt_content" type="integer">1654</field>
            </fieldlist>
            <related index="rels" type="array"></related>
        </tablerow>
        <tablerow index="tx_test_relation:5" type="array">
            <fieldlist index="data" type="array">
                <field index="uid" type="integer">5</field>
                <field index="pid" type="integer">759</field>
                <field index="tstamp" type="integer">1769675355</field>
                <field index="crdate" type="integer">1769675355</field>
                <field index="deleted" type="integer">0</field>
                <field index="hidden" type="integer">0</field>
                <field index="starttime" type="integer">0</field>
                <field index="endtime" type="integer">0</field>
                <field index="sorting" type="integer">2</field>
                <field index="label">exportme 2</field>
                <field index="tt_content" type="integer">1654</field>
            </fieldlist>
            <related index="rels" type="array"></related>
        </tablerow>
    </records>
</T3RecordDocument>
Author Andreas Häfner
Created 01/29/26, 09:30
Updated 01/29/26, 09:30
Bug
New Orphaned Extbase TYPO3 CMS 7

#69818 ExtensionService - getPluginNamespace should have signalSlot to build (not only set via TypoScript) own pluginnamespace

Sometimes it would be good to be able to override the pluginnamespace more dynamically then just using the TypoScript setting allows.
For instance appending a Input-Fieldnmae of the content element or the UID.

The reason is if you intend to create a plugin that can/should be used multiple times on the same site the pluginNamespace defines which plugin is actually involved.
As the ExtensionService itself is injected in quite a lot of classes it is a bit complicated to get the change to work everywhere.

The easist solution would add a signalSlot that allows to modify the default pluginnamespace.

Author Andreas Allacher
Created 09/15/15, 12:33
Updated 01/25/26, 12:58
Feature
New Orphaned AdminPanel

#94504 Make queries backtrace limit configurable

In TYPO3 10.4 it’s fixed to 7, where only 4 steps are displayed.

Would be nice to be able to increase the limit by configuration. Queries may occur multiple times and the important “step” may be missing.

See \TYPO3\CMS\Adminpanel\Log\DoctrineSqlLogger::startQuery()

Author Christoph Lehmann
Created 07/08/21, 09:27
Updated 01/24/26, 11:22
Feature
New Orphaned Backend User Interface

#108754 show categories as tags with different colors in the record column

Here is an optimization idea for backend editors.

We use the ext:blog extension and noticed that the Artikel modul has listed all articles with there categories and tags. Those are not simply words, they are shown as “tags” with color. They are easy to see because they are not just a list of words.

Furthermore you can filter by category and tag using the dropdown in the table header – which is really nice if you want to have every article with a certain category.

Now, in the listview module you can change the columns and in a sysfolder with news articles, if you add the category column, you see just a simple comma separated string of the used categories. If you have two categories with the same name but for different use-cases, you see the category twice and you don’t know which category is for what use case.

In our example in the screenshot we have the “Museum” category listed twice. One time for the website, where the news should be shown and a second category (same name but different ID) is for a category name when imported into the intranet. This category can either be checked or not, depending if the news should have the tag in the intranet.

Optimizations:
1. use the dropdown filter for the categories column for easy filtering (or make it configurable via TypoScript: activate filter or not)
2. add a field for color to the category, so that you can assign a color to each category
3. use a tag-style with a colored background – the color can be set in the category (see 2.)

Advantage:
Now, when looking at the category column you can see right away which categories are used for a certain record.

Author David Menzel
Created 01/23/26, 20:27
Updated 01/23/26, 20:27
Bug
New Orphaned Content Security Policy TYPO3 CMS 12

#103640 CSP: default-src: 'none' is inherited to other directives

Using this configuration:

inheritDefault: false

mutations:
  - mode: set
    directive: 'default-src'
    sources:
      - "'none'"

  - mode: extend
    directive: "child-src"
    sources:
      - "'self'"

results in this output:

default-src 'none'; child-src 'none' 'self'

The ‘none’ in “child-src” is obviously wrong.

Author Chris Müller
Assigned to Oliver Hader
Created 04/16/24, 16:44
Updated 01/23/26, 11:21
Bug
New Orphaned Backend User Interface TYPO3 CMS 8

#14858 extended clipboard: setCopyMode can`t be set to copy by default

Hi,

I couldn`t find any TCAdefaults or other TSconfig option to switch the copy mode of the extended clipboard to copy by default.

At the moment the default is “move” which can be very annoying.

Please add the possibility to choose the default behaviour of the “setCopyMode” button.

Thanks,
Sacha

(issue imported from #M1277)

Author Sacha Vorbeck
Created 07/11/05, 23:31
Updated 01/23/26, 08:30
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 13

#108739 Using "filter" in TCA type "group" is not applied in element browser using columnOverrides

When using the filter property in the TCA type “group” the filter is applied by DataHandler on saving (records not matching the filter criteria are removed). But the filter is not applied in the element browser: other records not matching the filter criteria are also displayed and can be selected.

According to the documentation this should work: “The values are filtered in the Element Browser as well as during processing in DataHandler.“
https://docs.typo3.org/permalink/t3tca:confval-group-filter

I am using columnOverrides to adjust the behaviour of the records group field for a custom shortcut content element (only certain content elements are allowed to be selected):

'columnsOverrides' => [
    'records' => [
        'config' => [
            'type' => 'group',
            'allowed' => 'tt_content',
            'maxitems' => 200,
            'size' => 5,
            'filter' => [
                [
                    'userFunc' => RecordsFilter::class . '->filter',
                ],
            ],
        ],
    ],
],

I am using TYPO3 v13.4.24

Edit: If I apply the filter to the records field of the original shortcut element (directly, without columnOverrides), the filter works also in element browser.

Author Chris Müller
Created 01/23/26, 08:17
Updated 01/23/26, 08:26
Bug
Accepted Orphaned Workspaces TYPO3 CMS 13

#96778 Workspace Preview Links not working when [starttime] in future

When a page has a Publish Date [starttime] in the future, generating preview links with the workspaces module “Generate Preview Links”-Button doesn’t seem to work correctly.

The preview link either can’t be generated at all or it cuts a significant part of the URL.

I tested and reproduced the problem in Version 10 and 11.

Author Claus-Peter Eberwein
Created 02/08/22, 07:48
Updated 01/22/26, 08:45
Feature
Under Review Orphaned Pagetree

#103253 Pagetree filter should support doktype/module lookup

Currently it’s possible to filter the pagetree by strings and single uids.
In case a user was interested in all “news” folders searching for “news” might not include all relevant pages of the pagetree.

For such a scenario being able to search for pages of a certain module or doktype would come in handy:

_.Module _.Doktype
Author Philipp Kitzberger
Created 03/02/24, 15:57
Updated 01/22/26, 06:53

Showing results 926 to 950 of 1561