Showing results 1001 to 1025 of 1561

Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 14

#102530 Mandatory fields only recognisable visually and after validation errors

Description

Required fields, e.g., page title, are marked visually as required but not recognized by AT.

Reproduction steps

- open an existing page
- Remove the entered page title
- The field is marked, but this has no effect because the icon (!) cannot be reached.

Impact

Target group

Screen reader

Severity

high

Frequency

common

Definition of Done

As a user, when I enter the field, I receive a message indicating that it is a required field.

Recommended solution

The symbol should be output as an SVG with a title and be part of the input label or connected via aria-describedby.
References / WCAG 2.2 Reference

1.3.1,
4.3.1,
3.3.2

Prioritizing the removal of the issues found

medium

Screencast or Screenshot

—-

Original ticket text:

Mandatory fields can only be recognized visually and only after an error has occurred. These are marked with an exclamation mark, which has no structural alternative. To make matters worse, the exclamation mark displays two different pieces of information (affected tab and affected field).

Author Christian Rath-Ulrich
Created 11/27/23, 15:18
Updated 10/16/25, 15:09
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 14

#92625 Form elements have insufficient color contrast and focus style

The form elements do not have sufficient contrast for users with a visual impairment. A contrast of 3:1 for input fields and buttons is required, as long as there is no sufficiently contrasted icon (3:1) or text (4,5:1) element placed inside. The contrast can be measured border and fill or border and background.

Reproduction steps

- Use colour contrast analyser
- Measure contrast (between border/fill or border/background)

Impact

Target group

visual

Severity

high

Frequency

very common

Definition of Done

WHEN I measure contrast of input field or button (without text or icon inside) against background or fill, the contrast is at least 3:1 or more

Recommended solution

enhance contrast of border

References / WCAG 2.2 Reference

1.4.11

Prioritizing the removal of the issues found

must have

Screencast or Screenshot

—-

Original Ticket Text:

The form elements in the Edit section have the border color #bbb. When the form elements receive focus, the border color is #aaa. Both of those colors surrounded by the background color #ededed have an insufficient contrast ratio of 1.98:1, see WebAIM Color Contrast Checker

When the form elements receive focus, the elements get a subtle box-shadow and the border-color changes from #bbb to #aaa, which is an insufficient contrast change from 1.21:1, see WebAIM Color Contrast Checker

Author Mylene Kreiger
Created 10/21/20, 11:52
Updated 10/16/25, 14:11
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 14

#92648 Multiple edit icon (hover button) is not contrast sufficient

Description

The button to edit mulitple elements is not color contrast sufficient. Users with a vision impairment cannot see this button.

Reproduction steps

- Open Page
- Try to edit multiple elements within one section

Impact

Target group

visual

Severity

high

Frequency

very common

Expected solution / Acceptance Criteria / Definition of Done

WHEN I measure the contrast on the icon against its background or the button area against its background, the color contrast should be at least 3:1.

Recommended solution

Enhance contrast

References / WCAG 2.2 Reference

1.4.1.1.

Prioritizing the removal of the issues found

must have

Screencast or Screenshot

—-

Original Ticket text:

Page column header has insufficient color contrast and no

-tag, the icon has no discernible text

Text must have a color contrast ratio of 4.5:1, icons a color contrast ratio of 3:1. The headline in .t3-page-column-header has insufficient color contrast of 2.84 (foreground color: #999999, background color: #ffffff), see WebAIM Color Contrast Checker.

Since this is a heading, a

-tag should be used.

A screenreader doesn’t know the purpose of the link because the link and icon have no discernible text.

#tas2020 TYPO3-60

Author Mark Leutl
Created 10/21/20, 16:26
Updated 10/16/25, 13:34
Bug
Under Review Orphaned FormEngine aka TCEforms TYPO3 CMS 12

#103532 Using TSconfig TCEFORM to change existing flexform field configuration does not work

You can use TSconfig TCEFORM to change attributes of flexform fields via:

TCEFORM.tx_styleguide_flex.flex_file_1.default.sDEF.input_1.label = Override Label

However, you can not change the “config” section of a field, for example to add a enableRichtext attribute, or change the rows/cols of an input. This is currently only possible to change for main-level fields like “tt_content.header”, but not for flexform fields:

TCEFORM.tx_styleguide_flex.flex_file_1.default.sDEF.input_1.config.max = 30
TCEFORM.tx_styleguide_flex.flex_file_1.default.sDEF.input_1.config.size = 5

You can already use PSR-14 events (AfterFlexFormDataStructureParsedEvent) to modify a flexform, but this is a bit more complicated than just using TSconfig. So I’d argue that setting it via TSconfig should be possible.

Author Garvin Hicking
Created 04/04/24, 11:10
Updated 10/16/25, 10:34
Epic
Accepted Orphaned Backend User Interface

#91518 Keyboard usage in the TYPO3 backend

This epic collects all issues related to keyboard usage in the backend.

When improving the keyboard interactivity, accessibility of the usage and patterns should be considered, too.

Frontend tests for the keyboard interactivity improvements need to be added to ensure they keep working.

The goal is to get the backend WCAG compatible. Keyboard interactivity not only improves accessibility, but also the usability for every user.

All fixes need to compatible with all browsers supported by TYPO3 and work with common screen readers.

Author Michael Telgkamp
Assigned to Michael Telgkamp
Created 05/29/20, 10:40
Updated 10/14/25, 12:13
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 11

#92684 Form input fields in the search detail page have insufficient color contrast and focus style

Pages/Tasks
  • Search
Affected WCAG 2.1 Success criterions
  • 1.4.11 Non-Text Contrast (WCAG 2.1) AA
  • 2.4.7 Focus Visible AA
Affected components
  • Text input
  • Select

Description
The form inputs and selects at the search detail page (choose “Show all” in search or activate search fields on page view) have an insufficient contrast ratio of 1.8:1 (border color: #BABBBA, background color #F9FAF9), see WebAIM Color Contrast Checker.

When focussed, the elements get a subtle box-shadow and the border-color changes from #BABBBA to #AAAAAA, which is an insufficient contrast change from 1.2:1, see WebAIM Color Contrast Checker.

Recommendation
To fulfill the minimum contrast ratio for form inputs, implement the following:

  • increase the contrast ratio of the border color for the form inputs and selects to a minimum value of 3:1.
  • increase the contrast ratio of the border color for the focussed form inputs and selects to a minimum value of 3:1

#tas2020

Author Jakob Widhalm
Created 10/22/20, 18:22
Updated 10/13/25, 15:10
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 11

#92671 Form elements have insufficient color contrast and insufficient focus style

The form inputs and selects in the Edit section have an insufficient contrast ratio of 2.37:1 (border color: #6DAAE0, background color #FAFAFA), see WebAIM Color Contrast Checker

The elements get a subtle box-shadow and the border-color changes from #6DAAE0 to #4392D7, which is an insufficient contrast change from 1.33:1, see WebAIM Color Contrast Checker

.has-change .form-control {
  border: 1px solid #6daae0;
}

.has-change .form-control:focus {
  border-color: #4392d7;
}

*Recommendation:*
To fulfill the minimum contrast ratio for form elements, implement the following:

  • Increase the contrast ratio of the border color for the form elements to a minimum value of 3:1.
  • Increase the contrast ratio of the border color for the focussed form to a minimum value of 3:1.
Author Mylene Kreiger
Created 10/22/20, 13:32
Updated 10/13/25, 15:10
Task
Under Review Orphaned Database API (Doctrine DBAL) TYPO3 CMS 13

#107612 Warmup database cache listening to `CacheWarmupEvent`

Author Stefan Bürk
Assigned to Stefan Bürk
Created 10/06/25, 14:26
Updated 10/10/25, 09:47
Bug
New Orphaned TYPO3 CMS 12

#106179 ContentContentObject conf select.languageField = 0 does not disable language overlay

The configuration “languageField = 0” in the following TypoScript code does not work as described in the documentation, since it is not possible to fetch a record without translating it.

lib.title = CONTENT
lib.title {
    table = tx_mywachau_domain_model_company
    select {
            pidInList = {$plugin.tx_mywachau.persistence.storagePid}
            where.data = GP:tx_mywachau_mywachaucompanyshow|company
            where.intval = 1
            where.wrap = tx_mywachau_domain_model_company.uid = |
            languageField = 0
            max = 1
        }
}
From the documentation:
> By default all records that have language-relevant information in the TCA “ctrl”-section are translated on translated pages.
>
> This behaviour can be disabled by setting languageField = 0.
Reference:

The ContentContentObject->render() method calls ContentObjectRenderer->getRecords() ($this->cObj->getRecords($conf['table'], $conf['select.']);).
The method ContentObjectRenderer->getRecords() calls $tsfe->sys_page->getLanguageOverlay($tableName, $row) unconditional while iterating over the result. Therefore, I can not see how this could work.
However, I need to fetch values from specific records with specific languages without translating them.

Author Sebastian Mazza
Created 02/14/25, 16:34
Updated 10/07/25, 15:38
Bug
New Orphaned Extbase TYPO3 CMS 14

#92514 SELECT DISTINCT and ORDER BY in Extbase query lead to database error when using PostgreSQL

Model Lorem has a property $ipsum for a 1:1 relation to Model Ipsum, which has a property $name.
Model Lorem has a property $dolors for a n:1 relation to Model Dolor, which has a property $lorem and a property $code

The query

class LoremRepository extends \TYPO3\CMS\Extbase\Persistence\Repository {
public function findLoremFilteredByDolorsOrderedByIpsum()
  $query = $this->createQuery();
  return $query
    ->matching($query->in('dolors.code', ['A', 'B']))
    ->setOrderings(['ipsum.name' => 'ASC'])
    ->execute();
  }
}

is translated by Extbase to the following SQL query

SELECT DISTINCT tx_my_lorem.*
FROM tx_my_lorem
LEFT JOIN tx_my_dolor ON tx_my_lorem.uid = tx_my_dolor.lorem
LEFT JOIN tx_my_ipsum ON tx_my_lorem.ipsum = tx_my_ipsum.uid
WHERE tx_my_dolor.code IN ('A','B')
ORDER BY tx_my_ipsum.name;

This query works on MySQL but fails on PostgreSQL (and probably SQLite, MSSQL as well) with a Doctrine\DBAL\Exception\DriverException: ORDER BY items must appear in the select list if SELECT DISTINCT is specified.

This happens because the DISTINCT result is sorted by tx_my_ipsum.name, a column which is not retrieved in SELECT.

In
@extbase/Classes/Persistence/Generic/Storage/Typo3DbQueryParser.php@
for $columnMap->getTypeOfRelation() = ColumnMap::RELATION_HAS_MANY)@ and @$columnMap->getTypeOfRelation() = ColumnMap::RELATION_HAS_AND_BELONGS_TO_MANY)
the property $this->suggestDistinctQuery = true; is set.
This is used in the method getObjectDataByQuery() of extbase/Classes/Persistence/Generic/Storage/Typo3DbBackend.php
by checking isDistinctQuerySuggested()
to add DISTINCT to the query: $selectParts[0] = 'DISTINCT ' . $selectParts[0];

Extbase adds the DISTINCT because requesting a Lorem filtered by multiple Dolors could lead to the same Lorem being returned multiple times which is not wanted in Extbase context when constituting objects.

The sorting by tx_my_ipsum.name is the wanted and correct behaviour.

In case Extbase adds the DISTINCT to the query it must also SELECT the ORDER BY columns, even if it does not use them (as a random column name?).
When selecting the ORDER BY columns care must be taken this random column name does not interfere with the columns of lorem

SELECT DISTINCT tx_my_lorem.*, tx_my_ipsum.name AS some_random_string_which_does_not_interfere_with_lorem_columns
FROM tx_my_lorem
LEFT JOIN tx_my_dolor ON tx_my_lorem.uid = tx_my_dolor.lorem
LEFT JOIN tx_my_ipsum ON tx_my_lorem.ipsum = tx_my_ipsum.uid
WHERE tx_my_dolor.code IN ('A','B')
ORDER BY tx_my_ipsum.name;

This query works on PostgreSQL as well.

Author Stephan Großberndt
Created 10/08/20, 10:08
Updated 10/07/25, 12:18
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 11

#91390 Page translation of a shortcut does not respect type changed to standard

If you translate a page that has the type “Shortcut” in the main language, and change it to “Standard” in the translation, it will still behave like a shortcut in the frontend.

In my opinion, this individual setting should work, but if this is not possible or desired, then the type dropdown for translations is superfluous, isn’t it?

Author Benjamin Robinson
Created 05/13/20, 22:31
Updated 10/02/25, 11:16
Feature
New Orphaned Security

#107582 Reduce need to enter MFA using trusted devices

One of my client suggests that it should be possible to reduce the number of times MFA is asked [when doing Backend authentication] by only asking it something like once every 30 days on devices/browsers that have been authenticated once.

Rationale is that Microsoft 365 is doing that and that must certainly be fine security-wise.

What do you think of this? Has it already been considered? Is there possibly a solution I’m not aware of?

me: created the ticket in TYPO3 on behalf of that client, aware of the fact that a password manager usually makes MFA transparent

Author Xavier Perseguers
Assigned to Oliver Hader
Created 10/01/25, 16:06
Updated 10/01/25, 16:06
Feature
Author Alexander Schnitzler
Assigned to Alexander Schnitzler
Created 09/25/23, 06:04
Updated 10/01/25, 12:02
Task
Under Review Orphaned Backend JavaScript TYPO3 CMS 13

#107573 Generate TypeScript declarations (d.ts)

Export TypeScript declarations (d.ts) for each system extension.

Author Oliver Hader
Created 10/01/25, 07:29
Updated 10/01/25, 08:16
Bug
New Orphaned Caching TYPO3 CMS 13

#107564 Cache is not emptied for scheduled records other than tt_content

If I use e.g. a news record which should show up at 16:00, and the page(s) where the news is shown is rendered with a 7 day cache lifetime, the cache is not refreshed at 16:00 today.

Consider this news might be shown on multiple pages, or it is an address record scheduled for tomorrow. The news post will not show up naturally but only if an editor or somebody else actively invalidates the cache.

The PSR-14 event ModifyCacheLifetimeForPageEvent does not cut it, because when doing a SQL query, you never know which records you DON’T get from the DB query.

Author Benni Mack
Created 09/30/25, 05:58
Updated 09/30/25, 05:58
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 12

#100515 Ensure table contents are vertically centered

Author Benjamin Kott
Created 04/06/23, 13:13
Updated 09/26/25, 10:59
Feature
New Orphaned Backend User Interface

#107525 Support recordsOverview wizard in TCA select fields

The “groups” TCA field type supports the “recordsOverview” field wizard that shows icons + titles for selected records, and allows us to invoke actions on the items: https://docs.typo3.org/m/typo3/reference-tca/12.4/en-us/ColumnsConfig/Type/Group/Index.html#confval-group-recordsoverview

It would be nice to have this wizard available in “select” fields, especially the “selectMultipleSideBySide” render type when foreign_table is used to fetch records from database tables.

Author Christian Weiske
Created 09/23/25, 10:48
Updated 09/23/25, 10:48
Bug
Needs Feedback Orphaned TypoScript TYPO3 CMS 13

#107378 sys_template TS-Setup won't get parsed when containing TS-Conditions

We are just migrating vom LTS 11 to 13, so the new Typoscript parsing becomes active… In some places, however, a behavior occurs that can only be explained by a bug.

For several extensions we have sys_templates containing the following setup:

plugin.tx_myextension {
  settings {
    someKeys = someValue
  }
  persistence {
    storagePid = 123
  }
  view { 
      templateRootPaths { 
        10 = fileadmin/templates/{$global.project_path}/extensions/myextension/Templates
      }
      partialRootPaths { 
        10 = fileadmin/templates/{$global.project_path}/extensions/myextension/Partials
      }
      layoutRootPaths { 
        10 = fileadmin/templates/{$global.project_path}/extensions/myextension/Layouts 
      }
  }
}

It is parsed as expected and all values are readable in the active TS.

But as soon as adding any Condition to the setup like

[10465 in tree.rootLineIds || 10616 in tree.rootLineIds || 10669 in tree.rootLineIds]
plugin.tx_myextension {
  settings {
    someKeys = someOverride
  }
  persistence {
    storagePid = 987
  }
}
[global]

The whole setup of this sys_template record is not present anymore. We read all the changelogs like https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Breaking-97816-TypoScriptSyntaxChanges.html but there is no note that conditions are not supported anymore. Also we have other sys_templates where it is working as expected.

Even any empty condition seems to break the whole parsing:

[10465 in tree.rootLineIds || 10616 in tree.rootLineIds || 10669 in tree.rootLineIds]

[global]

We also tried [END], same behaviour.

Only when removing or commenting out the condition lines […] and [global], the record is parsed again.

Author Webadmin no-lastname-given
Created 09/03/25, 09:26
Updated 09/22/25, 15:05
Feature
Under Review Orphaned

#107035 Introduce System Settings API

Provide a unified System settings API similar to site settings for * “System-wide” settings / global settings (Install tool via DefaultConfiguration.yaml), not extendible * Extension Configuration API (“cryptic syntax”)

The API should replace the internal DefaultDescription.yaml
and extension ext_conf_template APIs.

Also system settings should be definable by Setting objects
via PHP attributes, allowing to implicitly define settings
and inject them in consuming code.

Author Benjamin Franzke
Assigned to Benjamin Franzke
Created 07/04/25, 11:41
Updated 09/22/25, 09:19
Bug
New Orphaned Extbase TYPO3 CMS 10

#94899 Exbase: Expression #1 of ORDER BY clause is not in SELECT list

TYPO3 10.4.19
MySQL 5.7.35

When I do an individual Query in my Repository with an order_by to a related table field, an error like:

Expression #1 of ORDER BY clause is not in SELECT list, references column 'typo3.tx_lux_domain_model_pagevisit.tstamp' which is not in SELECT list; this is incompatible with DISTINCT

came up

Example function in a Repository:

    public function findSomething(): QueryResultInterface
    {
        $query = $this->createQuery();
        $query->setOrderings(['relatedTable.tstamp' => QueryInterface::ORDER_DESCENDING]);
        return $query->execute();
    }

When I do a “select SQL_MODE;” – this is the definition:

ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
Author Alex Kellner
Created 08/16/21, 11:00
Updated 09/18/25, 08:41
Bug
New Orphaned Authentication TYPO3 CMS 13

#107472 FE-Login in second Browser-Tab yield inconsistent Userstate and Login-Error

Steps to reproduce:
  • fe_user are located on any sys_folder
  • $GLOBALS[‘TYPO3_CONF_VARS’][‘FE’][‘checkFeUserPid’] = true
  • Page with fe-login-Plugin
  • Login page opened in two browser tabs
  • in first browser tab do a login with username and password
  • do the same login in second tab afterward
  • Login-Error is displayed

If $GLOBALS[‘TYPO3_CONF_VARS’][‘FE’][‘checkFeUserPid’] = false is used,
no error is displayed
In this case even wrong password or inexistend user yield same result

Reason for Login-Error:
@AbstractUserAuthentication::fetchValidUserFromSessionOrDestroySession();@, which relys on $checkPid_value, is executed before
@BeforeRequestTokenProcessedEvent@ has been dispatched.
@\TYPO3\CMS\FrontendLogin\Event\ProcessRequestTokenListener@ sets `$checkPid_value` to late.

Deeper in middleware-stack the frontend-user is not logged in, while its session has a user id:
@frontendUser->getSession()->getUserId() !== $frontendUser->getUserId()@

It would be nice , if both configuration variants yield same behavior.

Users getting this type of login error, try to change password and run in same problem again.
How could it be possible, to detect and handle the “new login while already authenticated”-condition and inform the user about the mistake?

Author Andreas Häfner
Created 09/17/25, 12:36
Updated 09/17/25, 12:36
Feature
New Orphaned Link Handling & Redirect Handling

#106338 No automatically redirects for never ever before published pages

Also for completely new pages, that have never been published ever before, a redirect is created automatically, if the slug is renamed again during editing.
Yes, you can undo it via the Revert Updates Button, but from Editor POV you always need to revert it and sometimes you miss it or its annoying if you create always new pages and its kind of normal that slugs are changed during content creation of new pages.

Author Marc Freitag
Created 03/07/25, 16:45
Updated 09/16/25, 11:45
Bug
New Orphaned TYPO3 CMS 13

#107450 WCAG: Module menu: Headings/hierarchies of the individual modules

The individual menu items and hierarchy levels within the module menu are not comprehensible to the user.

The burger menu does not have a clear label and is therefore not recognizable as such.
“I’m missing a structure that is navigable. There are no headings for the widgets, so I don’t understand the structure.”
Navigation of the menu tree is not immediately intuitive: Screen readers do not read the lowest level consistently (web in the test example);
Focusing does not work consistently with the cursor keys; the menu tree can be opened with the cursor (right), but cannot be closed with the left cursor key.

Solution idea
The menu items must be provided with headings. All menu items should be given an H1 so that they have the same level. The sub-items should then be given an H2.

Expected result
The menu items are provided with headings and separated from each other. Orientation is provided and output by the screen reader.
The menu can be opened and closed easily using the cursor keys.

Addition:
Minimize module menu is read incorrectly (miniminimieren), depending on the screen reader; it should be checked whether the button is necessary at all for visually impaired users.

Further information/comments
Organizing the dashboard or individual menu items by region is not effective due to the customizability.

Internal reference: ITZBUNDPHP-4976

Author Christian Rath-Ulrich
Created 09/12/25, 08:57
Updated 09/12/25, 08:57
Bug
New Orphaned TYPO3 CMS 13

#107449 WCAG: Navigation from module menu to workspace

Here using the example of “My Dashboard”

The user navigates through the module menu and has selected “My Dashboard.”

The corresponding workspace for My Dashboard opens to the right.

It is not clear to the user that a workspace has opened and how they can navigate to it.

It is not easy to navigate to the workspace using the tab key, as the focus does not automatically jump to the selected area. Using the tab key first jumps to the search field.

A structuring element is missing. It is not clear what the workspace belongs to and where it begins and ends.

Solution idea

In principle, the “workspace” could be marked as a region.

Idea: Mark the horizontal menu, module menu (left-aligned), and workspace as regions.

Expected result

A screen reader outputs where the user is located and that a workspace has opened, corresponding to the selected module menu item from the main menu on the left. This is automatically selected and the focus is set accordingly.

It should be clear where the workspace begins and where it ends.

Additional information/comments

As soon as an element (e.g., within the menu or when creating a new page) is selected/activated, the focus must move to a clearly named (X) area.

“It wasn’t entirely clear to me where I actually was.”

Internal reference: ITZBUNDPHP-4977

Author Christian Rath-Ulrich
Created 09/12/25, 08:54
Updated 09/12/25, 08:54
Bug
New Orphaned TYPO3 CMS 13

#107446 WCAG: Functionality of the “Numbering” button

Screenshot I

The user is in the workspace of their page and has already added content modules to the Top, Main, or Bottom areas.

There is a small icon in front of the title of the content module, which is output as “numbering” by the screen reader.

When selected (left mouse button), a context menu opens. When attempting to navigate through it, the focus jumps, for example, to the path (top right) or to the drop-down menu (layout/language comparison) at the top left, but the context menu remains open.

Screenshot II

The icon/functionality Numbering is also located in the path of an image selection, which is not understandable here. The number sign (blue image) is not displayed meaningfully at this point, as we can edit the module here à it is also included in the frame.

Screenshot III + IV:

Display of the Numbering icon also for image files and at the end of pages.

Display on screenshot is shown as a cross-reference – but is not one

Solution idea:

Find intuitive/understandable naming
Is the function necessary or already covered by the editing function? Remove the function?
Expected result:

Selecting the icon opens the context menu, which I can navigate using the tab key.
Make the icon label more intuitive.
Remove the function at this point.
Additional comments:

The numbering function/icon appears in several places and is not self-explanatory.

internal reference: ITZBUNDPHP-4987

Author Christian Rath-Ulrich
Created 09/12/25, 08:35
Updated 09/12/25, 08:35

Showing results 1001 to 1025 of 1561