Showing results 326 to 350 of 1561

Feature
Under Review Orphaned File Abstraction Layer (FAL)

#107120 Why should we keep real files for online media?

TYPO3 could actually just remove the need to store physical stub files for youtube or vimeo files?

Author Benni Mack
Assigned to Benni Mack
Created 07/21/25, 16:44
Updated 04/21/26, 11:23
Bug
Accepted Orphaned Backend User Interface TYPO3 CMS 13

#108288 The heading hierarchy in the create folder modal in filelist is incorrect.

In the “Create new folder” dialog, the main heading is marked as H1. Immediately below, the entry “Fileadmin/(auto-created)…” is marked as H4. This skips levels and violates the expected, programmatically discernible hierarchy.

Per WCAG, the number of headings at the same level is not limited; multiple H4s under an H3 are allowed if the hierarchy is consistent and semantically correct. Here, the heading structure must be adjusted so no levels are skipped (e.g., H1 → H2 → H3 …).

The goal is a semantically correct structure that works well with assistive technologies, without changing the visual appearance.

Current issue: H1 “Create new folder” followed by H4 “Fileadmin/(auto-created)…”.
Expected: No H4 right after an H1; use H2 (or H3) instead, depending on the logical structure.
Multiple same-level headings are allowed if properly nested in the hierarchy.
Optionally recommended structure in the modal:

H1: Dialog title (or—if the backend already provides a page-level H1—start with H2 in the modal)
H2: Section heading (e.g., “Location” / “Storage”)
H3/H4: Sub-items within that section (e.g., “fileadmin/(auto-created)…”)

Author Christian Jung
Created 11/24/25, 09:53
Updated 04/14/26, 09:41
Bug
New Orphaned Extbase TYPO3 CMS 13

#109524 $this->redirect() in an Extbase Controller should accept a Plugin Name

If after getting rid of Switchable Controller Actions you split up your formerly one plugin into several plugin it becomes neccessary to redirect beetween differnt Plugins, as those will be contained in the generated URL parameters.

Currently you have to override $this->redirect() in the controller or return a cutom RedirectResponse.

Author Lina Wolf
Created 04/09/26, 07:18
Updated 04/11/26, 10:13
Bug
New Orphaned Backend User Interface TYPO3 CMS 14

#108993 context menu: lost focus after ESC

In the TYPO3 backend, when opening the context menu from a tree structure (e.g. page tree) and closing it via the ESC key, the keyboard focus jumps to the top of the page (or another item before) instead of returning to the triggering tree item.
This breaks efficient keyboard usage and is problematic from an accessibility perspective.

Steps to Reproduce

  1. Log into the TYPO3 backend.
  2. Navigate to the page tree (or any tree structure that provides a context menu).
  3. Focus a tree item
  4. Open the context menu for this item
  5. Press ESC to close the context menu.
  6. Check where the keyboard focus is now located (press TAB once).

Current Behavior

After pressing ESC, the context menu closes, but the focus moves to the top of the page or is no longer on the previously focused tree item.

Expected Behavior

After pressing ESC, the context menu is closed and the keyboard focus returns to the triggering tree item (or, more generally, to the triggering UI element).

Impact

  • Keyboard and screen reader users lose their position in the backend tree and have to re-navigate to the desired node.
  • Increased navigation time and frustration for heavy keyboard users.
  • Violates common accessibility and focus management patterns (incl. WCAG 2.1 focus order recommendations).
Author Christian Jung
Created 02/17/26, 07:41
Updated 04/21/26, 11:23
Bug
New Orphaned TYPO3 CMS 14

#89916 Shortcut to a disabled page with redirect fails

When disabling a page and setting a redirect for that old url to a new/other page, the redirect works.
When setting a page shortcut to the old url, this error shows up:

Page not found: Reason: ID was not an accessible page

Which is obvious because the shortcut functionality checks the availability of the target page.
But maybe it’s wanted/expected behaviour to get redirected if there is a redirect for the page available.

To reproduce:
- Create old-page and set hidden
- Create new-page and set visible
- Create redirect from /old-page to /new-page => this works
- Create shortcut to old-page -> shortcut fails

Author Riny van Tiggelen
Created 12/11/19, 11:09
Updated 04/21/26, 11:23
Task
New Orphaned TYPO3 CMS 14

#109333 Use alternative markup for icons in ModifyButtonBarEvent

I’m using a ModifyButtonBarEvent event listener to add a button. This button has an svg icon (not sprite). It does not seem possible to set an alternative markup in this context.

I need the inline context because the icon uses currentColor to match the dark mode option.

My workaround is to set the markup to the alternative markup:

$button = $this->componentFactory->createGenericButton();
$icon = $this->iconFactory->getIcon('page-feedback-thumbs-up-regular');
$icon->setMarkup($icon->getAlternativeMarkup(SvgIconProvider::MARKUP_IDENTIFIER_INLINE));
$button->setIcon($icon)

Maybe svg icons should be rendered generally inline in that context?

Author Tobias Jungmann
Created 03/24/26, 08:24
Updated 03/24/26, 08:24
Task
New Orphaned Backend User Interface TYPO3 CMS 14

#109303 Improve Wizard steps with a "Quick Finish" / "Fast Forward" / "Accept defaults" / ... methodology

The new form, page and localization wizards can be very verbose.

The second-to-last-step is only a “summary” of all actions, the last step contains the success messages. And then the modal also needs to be closed.

That means there are three steps (that can be ENTER-multitapped) that are kind of unneeded.

For the page creation wizard (especially the drag-drop variant that starts in step 3), it would be very helpful to have the ability to skip through the form very quickly, to create stubs of pages to be filled later.

In the current implementation, the missing focus of the first field with a required field (page title) also slows down the process, and missing validation. Both will be adressed as part of the feature.

For future reworks of the modal process it would be great to have a functionality that “skips all steps that have no mandatory input, and auto-close the modal if there are no errors”.

This functionality must be available on a case-by-case basis. People may want to quickly step through the page wizard, but not the form wizard, localization or other custom wizards. This means, it should not be a user-specific option. Also it should not be an option that would persist for the same kinds of wizards, because in some cases you may want to fill out fields/steps that are optional, or to specifically check the summary for correctness.

Author Garvin Hicking
Created 03/20/26, 12:22
Updated 03/20/26, 12:22
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
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
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
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 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
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
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
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 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 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

#108529 Modernize FormEngine node type registration

Custom FormEngine node types are currently registered via $GLOBALS['TYPO3_CONF_VARS']['SYS']['formEngine']['nodeRegistry']. This could be easily migrated to an attribute-based approach.

Author Elias Häußler
Assigned to Elias Häußler
Created 12/18/25, 21:55
Updated 01/13/26, 14:09
Bug
New Orphaned DataHandler aka TCEmain TYPO3 CMS 13

#106152 Restoring records does not check for valid slugs

Problem/Description

> TL;DR: Restoring pages can result in pages with duplicate url slugs

TYPO3 does not check for any resulting inconsistencies of record slugs. The datahandler is is used to undo / restore records but is NOT using \TYPO3\CMS\Core\DataHandling\DataHandler::fixUniqueInSiteForSubpages method to verify and update restored slugs.

how to reproduce (simple example)

1. Create a pagetree

site/subpage/subpage

2. delete subpage in first level

site/subpage and childrens

3. create a new page with slug site/subpage

4. restore the previously deleted pages

with activated recursive restore checkbox

5. you have now to pages with the same slug site/subpage

ToDo(s)

  • Restored records (just pages or also any record with a defined slug field??) must have a consistent unique (site or whole TYPO3 instance wide) slug.
  • The backend user needs to be informed about the slug inconsistence and the changed records

Acceptance Criteria

A restored records must not have a conflicting slug in general

Author Josef Glatz
Created 02/11/25, 11:36
Updated 01/03/26, 06:58
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 14

#108582 Wrong border radius for big input fields

The border radius is given in em units instead of rem

The combination of input fields and buttons with different font-sizes looks not so good.

For other components .75em is no issue as these comnponents do not have a font-size set and thereby are already use :root font-size of 16px.
So chainging this to .75rem will just work.

——

On the somehow not ideal design decision to use em instead of rem for border-radius

For most elements the border-radius must visually fit to other outer components:
—> Use rem so all components have identical border-radius.

Only for some graphical elements like “badge-pill”, “checkbox” etc. the border-radius must fit to the font-size of the element itself:
—> Use em so the border-radius changes with font-size.
—> Or: Use rem so the border-radius visually fits with all outer components.

Author Ayke Halder
Created 12/30/25, 10:53
Updated 12/30/25, 15:59
Feature
Accepted Orphaned Linkvalidator

#107983 Make Link Validator (linkvalidator) accessible for Preview-Workspace users

Scenario:

- I have a large corporate multi site with many users with limited user (role) rights.
- Editors only have access to “Preview Workspace”.

Problem:

Since the module “Link Validator” is only accessible for users with the right to “Edit live”, there is no possibility for Editors to check for broken links.

Solution:

Make the module “Link Validator” accessible for all workspaces.

Author Thomas Mock
Created 11/05/25, 09:54
Updated 11/10/25, 19:49
Feature
Under Review Orphaned Frontend

#104529 Missing hook to enhance the page cache data content

Currently the TypoScriptFrontendController does not offer the option of manipulating the content of the page cache data set before it is send to the cache backend. For example, to extend the page cache data with additional data. Extending the data set is useful, for example, for content that is otherwise only calculated or loaded in the event of a cache miss. Examples of this are the inlineLanguageLabels or the inlineSettings in the PageRenderer.

Author Tim Weisenberger
Created 08/01/24, 20:40
Updated 11/08/25, 19:36

Showing results 326 to 350 of 1561