Showing results 951 to 975 of 1561

Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#108668 Sysfolders in Page Tree below minimum contrast

Description In the TYPO3 backend page tree, sysfolders currently show insufficient color contrast against the background (measured approx. 1.4:1 and 1.3:1), failing WCAG 2.2 Success Criterion 1.4.3 “Contrast (Minimum)” Level AA (≥ 4.5:1). Increase sysfolder contrast to at least 4.5:1. A target of 7:1 is recommended to further enhance readability.

Reproduction Steps

  1. Log in to the TYPO3 backend.
  2. Open the Page module to display the page tree.
  3. Identify a sysfolder entry (default theme, normal state, not active/hover).
  4. Measure color contrast between the sysfolder icon/label and the background using a contrast checker.
  5. Observe the value is below 4.5:1 (e.g., ~1.3:1–1.4:1).

Impact

Non-compliance with WCAG 2.2 SC 1.4.3 (AA); accessibility compliance risk.
Reduced recognizability for users with visual impairments; potential misnavigation in the page tree.
Negative effect on usability and QA.

Recommended Solution

Adjust CSS/theme for sysfolders in the page tree:
Update icon and, if applicable, label colors to achieve ≥ 4.5:1 contrast (target 7:1).
Prefer existing TYPO3 backend design tokens/CSS variables; avoid hard-coded values.
Cover all states: normal, hover, active/selected, focus, disabled.
Test in light and dark mode and under various zoom/DPI settings.
If icons (SVG) are affected: ensure fill/stroke is CSS-controllable or provide alternative color variants.

Definition of Done

Contrast between sysfolder icon/label and background is ≥ 4.5:1 in all relevant states; target 7:1 achieved or limitations documented.
Verified with a recognized contrast checker in light and dark mode and at 100%/125%/150% zoom.
No regressions for other page types/icons in the page tree.
Code adheres to TYPO3 theme/CSS guidelines, reviewed by Development, approved by QA.

Acceptance Criteria

Measured contrast ≥ 4.5:1 for sysfolders in normal, hover, active, and focus states.
Consistent rendering in light and dark mode.
No degradation of readability for other page types/icons.
Documentation of selected color tokens/variables in the PR.

Author Christian Jung
Created 01/19/26, 08:41
Updated 01/19/26, 08:41
Bug
Accepted Orphaned File Abstraction Layer (FAL) TYPO3 CMS 12

#105671 youtube shorts width/height landscape, portrait needed (after backend upload)

one of my editors has added a youtube short to his user_upload and the with/height gets wromg: it’s landscape, not portrait. when manually I changed width and height of this video in sys_file_metadata, frontend renders perfect (I render with aspect-ratio in the news single template:

  <f:variable name="videowidth">{mediaElement.originalResource.properties.width}</f:variable>
  <f:variable name="videoheight">{mediaElement.originalResource.properties.height}</f:variable>
  <!-- width:{videowidth},height:{videoheight}-->
  <div class="mediaelement-video" style="--aspect-ratio: {videowidth}/{videoheight};">
        <f:media file="{mediaElement}" style="max-width:100%;"/>
    </div>

Could somebody have a look?

Author Sabine Deeken
Created 11/21/24, 15:52
Updated 01/16/26, 16:19
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
Bug
New Orphaned TYPO3 CMS 13

#108485 Moving pages in page tree using BEFORE method inserts page into last visible node instead of sibling

When moving pages in the page tree using the BEFORE positioning method, the page is inserted inside the last visible (expanded) node, instead of being placed before the selected target page as a sibling.

This behavior breaks the expected hierarchy logic of the page tree and can easily lead to pages being moved into the wrong parent without the editor noticing immediately.

—-

Steps to Reproduce

1. Create the following page tree structure:

  • Page 1
  • Page 2
  * Page 3
  • Page 4

2. Ensure that:

  • Page 2 is expanded
  • Page 3 is visible
  • Page 4 is visible

3. Page 1 is currently a sibling of Page 2 and Page 4, positioned before Page 2.

4. Move Page 1 using drag & drop, targeting Page 4.

—-

Expected Result

Page 1 should be placed before Page 4, resulting in:

  • Page 2
  • Page 3
  • Page 1
  • Page 4

(Page 1 remains on the same level as Page 4)

—-

Actual Result

Page 1 is incorrectly moved inside Page 3 (the last visible expanded node), resulting in:

  • Page 2
  • Page 3
* Page 1
  • Page 4

Impact

  • Editors may unintentionally move pages into incorrect parent pages
  • Hard to detect in large or deeply nested page trees
  • Can cause structural and navigation issues
Author Stefan Hilhorst
Created 12/15/25, 11:47
Updated 12/15/25, 11:48
Bug
New Orphaned TYPO3 CMS 13

#108480 Navigation workspace tables causes excessive and hierarchically incorrect screenreader output

Description

The workspaces table contains a global head-section (-Element), and multiple sub section with header cells (-elements) that span all columns.

Using the NVDA screenreader paired with Google Chrome, all of the header cells are announced for every cell upon navigation. The attached screenshot demonstrates the announcement for the single cell with content “Testredaktuer” [sic]. The problem grows exponentially with the number of children.

Note: The many slashes are part of the output with default punctuation verbosity, resulting in the rather lengthy word “Schrägstrich” in German.

Reproduction steps

  1. Use the NVDA screenreader and Google Chrome.
  2. Select “Einfacher Freigabeprozess” from the Workspace menu in the top bar (this label remains German when I change the user interface language to English).
  3. Select “Workspaces” from the module side bar.
  4. In the page tree, select a node with multiple nested children.
  5. Navigate the table in the main area; for every header or content cell, all header cells in the table are announced.

Impact

Due to the excessive auditory announcements, the functionality is extremely hard to understand and use with the affected environment. Besides the verbosity, the relational structure is wrong. To make matters worse, it is not even possible to interrupt the redundant information, because the content comes last.

Target group

Screenreader users

Severity

high

Frequency

common

Definition of Done

Only relevant header cells are announced during table navigation for any selected cell.

Recommended solution

Unfortunately, this looks like a hard problem to solve without a major overhaul of the UX.

The general recommendation for this problem area is to split complex tables with multiple sections and header cells into multiple simple tables. Problems in this case would be:

  • The complexity of the multi-selection checkbox increases.
  • The visual presentation is cluttered for sighted users by repeating the section. (That might be a solvable problem by visually hiding them, but would require extensive testing with browser/screenreader pairings to ensure it doesn’t introduce new problems.)

Note: It is not sufficient to add explicit relations with headers/id-Attributes. This works fine in Firefox paired with NVDA, but not in Google Chrome. Please refer to chromium bug report in the next section. I verified this long standing bug hasn’t been solved at the time of writing with NVDA 2025.3.2 and Chrome 143.

References / WCAG 2.2 Reference

In terms of the WCAG, the current table structure is not accessibility supported and success criterion 1.3.1 (9.1.3.1 in the EN 301 549) is not satisfied.

Existing issues in the NVDA and Google Chrome trackers:

Author Anonymous
Created 12/12/25, 16:16
Updated 12/12/25, 16:16
Bug
New Orphaned DataHandler aka TCEmain TYPO3 CMS 13

#108397 After switching page translation from strict to free mode, FAL (sys_file_references) keeps the connection. Leads to wrong file deletion, when on default language elements are deleted

The error also exists in version 12 as well.

Environment:
  • Basic TYPO3 system without third-party extensions.
  • At least two languages in the system
Reproduction:
  1. Create a new page or use an existing one where no element has been created yet.
  2. Create a text/media or text/image element.
  3. Insert an image into it.
  4. Translate the content into the second language using the Translate (connected mode) option.(If necessary, create the translation for the page first)
  5. Switch to free mode.
  6. To do so, open the translated content element. Under the language tab, set Transl.Orig to empty. Save and close.
  7. Now “Free Mode” should be displayed in the second language.
  8. Go to the element in the default language and delete the image from the element. (Alternatively, the entire element can be deleted. The behavior is the same)
  9. After saving, the image will also be deleted in the translation. If the entire element is deleted in the default language, still only the image in the element of the second language will be deleted.

The reason, when I disconnect the parent tt_content element (Transl.Orig) from the default language, in sys_file_reference the l10n_parent remains set. I diden’t go deep on this, but i assume DataHandler will check l10n_parent fields, when the “original” sys_file_reference will be deleted and delete the matches as well.

Within the normal irre setup, i can disconnect the individual irre records. In the context of FAL (sys_file_reference), an editor cannot do this, because the language tab is not available by default. In this case, when removing the connection via Transl.Orig, the DataHandler should also remove the corresponding sys_file_reference connections.

Big thanks to all the people that do work for this nice project :).

Author Oliver Pfaff
Created 12/04/25, 13:59
Updated 12/04/25, 13:59
Task
New Orphaned Backend API TYPO3 CMS 14

#108391 Read default backend_layout from tsconfig if key is present

I propose a change to the DefaultDataProvider for backend layouts.

Having a default backend layout for a project that is different from a single colPos, require you to either * create a backend_layout database entry * create a page.tsconfig with a key
and select that afterwards in “Page properties”.

This is due to the “DefaultDataProvider” looking if the key is “default” – and then fallback to a default tsconfig.

I suggest that the default provider can look at the tsconfig of the pageId given to “getBackendLayout” and can see if the “default” key is set. This could have been done via a configured site set.

And if set, use that configuration.

Author Soren Malling
Created 12/03/25, 15:03
Updated 12/04/25, 08:56
Task
Under Review Orphaned Extbase TYPO3 CMS 13

#106462 Improve default Extbase error message

When the validation of a parameter fails, usually caused by the visitor entering wrong data into a form, The following error message is displayed by default:

```
An error occurred while trying to call MyVendor\MyController\Controller\AccountController->updateAccountAction()
```

This message is shown to website visitors , however. We should provide a better default like “check the data you entered” and create a log entry with the controller name instead if desired.

Author Lina Wolf
Created 03/31/25, 08:38
Updated 12/03/25, 08:05
Bug
New Orphaned Backend User Interface TYPO3 CMS 12

#105795 Paste behavior not consistent in page module for all webbrowsers

When a content element is pasted in the page module, the paste behavior is different depending on the webbrowser used.

Assume you open a page in TYPO3 backend, which has e.g. 10 content elements with lorem ipsom text. The page module content is longer than the webbrowsers viewport, so you can scroll down to the bottom. Now copy the first content element with the context menu, scroll down and paste it on the same page after the last content element.

  • Behavior in Firefox: Element is pasted as expected and the scroll position is the same as before the paste operation.
  • Behavior in Chrome, Edge, Safari and Opera: Element is pasted as expected and the scoll position jumps up to the top of the page (page seems reloaded). Editor has to scroll down again in order to edit the pasted element.

Then behavior of Firefox is best from a UX perspective. If possible, paste behavior should be the same for all browsers.

Author Torben Hansen
Created 12/09/24, 12:53
Updated 11/27/25, 16:21
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 14

#108314 Dashboard Widget row-height

In my setup the content of a “small dashboard widget” has a vertically scrolling bar:

This solves the issue:

.dashboard-grid {
  --row-height: 202px; /* slightly increased from 200px */
}
“small dashboard widget” consists of:
  • Header bar
  • 3 lines of text
  • Action button
Author Ayke Halder
Created 11/25/25, 14:58
Updated 11/26/25, 20:45
Task
New Orphaned Content Security Policy TYPO3 CMS 14

#108324 CSP Resolution

Currently, the CSP module has the ability to fix fixable CSP violations. The entries are then stored in the CSP resolution. However, there is currently no way to revoke or view a stored exception via the existing UI.

My suggestion is to also include the resolved entries in the CSP list and to offer a “fixed” attribute analogous to “fixable” and a way to remove the solution.

In addition, I would suggest another filter to hide the fixed entries from the list or to display only these, similar to the existing filter dropdown.

Author Christian Rath-Ulrich
Created 11/26/25, 13:23
Updated 11/26/25, 13:41
Task
New Orphaned Backend User Interface TYPO3 CMS 14

#108316 Separate visual connection of page-tree-header and doc-header

The page-tree and doc-header/content-area are visually completley connected by the horizontal lines.
But they do not belong together.

Current state

Suggestion – shortened lines

.tree-toolbar__menu {
  padding: var(--tree-toolbar-padding-y) 0;
  padding-inline-start: 0;
  margin-inline-start: var(--tree-toolbar-padding-x);
  padding-inline-end: 30px;
  margin-inline-end: var(--tree-toolbar-padding-x);
}
.module-docheader-navigation {
  padding: var(--module-docheader-padding-y) 0;
  margin: 0 var(--module-docheader-padding-x);
}

Suggestion – no middle line with reduced height

Suggestion – complete pagetree header overhaul without horizontal lines

Author Ayke Halder
Created 11/25/25, 15:34
Updated 11/25/25, 17:20
Task
New Orphaned Backend User Interface TYPO3 CMS 14

#108315 Breadcrumb with multi-level module and multi-level tree-path needs fine-tuning

The breadcrumb with multi-level module and multi-level tree-path needs fine-tuning:
  • Visually separate module part and tree-path part
  • Only use one module icon instead of two

Current state

Suggestion

.breadcrumb, .breadcrumb-measurement {
  --typo3-breadcrumb-divider-content: ">"; /* replaces "/" */
}

/* And an additional extra divider like pipe "|" to divide the module from the tree-path like: */
.breadcrumb-item.breadcrumb-divider::after {
  content: "|";
  width: 1em;
  display: inline-block;
  text-align: center;
}
Author Ayke Halder
Created 11/25/25, 15:12
Updated 11/25/25, 15:12
Story
New Orphaned TYPO3 CMS 14

#108298 Improve TYPO3 login and session handling

When working with external SSO systems (e.g. OAuth, OpenID Connect, SAML), TYPO3 allows the implementation of custom authentication services for both frontend and backend users. While initial login works well, the current session expiration and re-authentication process is problematic for SSO-based users (especially for Backend Users).

Current problems:
  • After session expiration in TYPO3 backend, a modal is shown requesting the users password (usually unknown for SSO users)
  • Session timeout is global and cannot be set dynamically per user/provider
  • Backend session expiration warning only appears as a modal (no browser notifications if tab inactive)
Proposed improvements:
  • Skip TYPO3 password request for backend users after session has expired. Instead redirect browser to backend login
  • Allow dynamic session lifetime per user / auth provider
  • Use Browser Notification API before session expires in addition to modal countdown
Author Torben Hansen
Created 11/24/25, 18:08
Updated 11/24/25, 18:08
Task
Under Review Orphaned Authentication TYPO3 CMS 14

#97059 Removal of re-login popup functionality

The re-login popup dialog has conceptual drawbacks, and I opt for removing it as its usefulness has been decreased in the past years.

The re-login works as this: An AJAX request is done every 60 seconds. If the session timeout is less than 60 seconds, then a popup is shown to re-enter their credentials to stay logged in. This is useful when writing longer texts and unsaved changes should be kept.

However, the following issues exist:
  • When using an external login provider (OAuth, SSO, OpenID connect) is used, the re-login concept does not work (that’s why there is a global ! option to disable the popup)
  • When working with multiple tabs, and the editor jumps back to the tab when the session timeout is over, the new session does not keep the existing values either
  • Custom login providers cannot be used in conjunction with this dialog
  • The AJAX polling of 60 seconds is rather a bummer, as we should rather use “push” functionality when the login is about to expire
  • Various places in TYPO3 Backend code try to allow such “AJAX polling” calls and build up the form without any useful rendering of such a dialog

In the past years, we also mitigated this issue by setting the session lifetime of backend users from 2h to 8h (= 1 workday) so editors should not see this dialog that often anymore.

Author Benni Mack
Created 02/28/22, 09:41
Updated 11/24/25, 15:53
Bug
New Orphaned Extbase TYPO3 CMS 12

#102529 Properly support HTTP Status Code 201 within extbase

Sources regarding HTTP Status Code 201:

The 201 status code can contain a location header, like the 3xx redirect status codes.
This is currently not possible via Extbase, as Extbase has hard checks regarding >= 300 within the Bootstrap class after internal dispatching of the request. Returning a redirect with 201 and a url is therefore not working as expected.

Browsers (tested with Firefox) probably do not support this, but APIs might need to conform to this.

The corresponding checks regarding >=300 could be adjusted to also check for 201 status code.

Author Daniel Siepmann
Created 11/27/23, 14:53
Updated 11/24/25, 15:38
Bug
Author Christian Kuhn
Created 11/22/25, 13:36
Updated 11/22/25, 13:48
Bug
New Orphaned System/Bootstrap/Configuration TYPO3 CMS 12

#108170 DI-cache can not be configured, because hardcoded

In the Bootstrap-Class, the configuration for DI-caches are hardcoded and ‘options’ are empty.
https://github.com/TYPO3/typo3/blob/80c54568a4fc1246fad59b7e0b99f6d7d0d52266/typo3/sysext/core/Classes/Core/Bootstrap.php#L353

I have to move the var/cache dir to another location, because of a Multi-Pod Environment to avoid cache-crashes during cache-flushes.
For all cache types with “File/SimpleFilebackend” there is a option “cacheDirectory” that worked fine so far.

The DI cache (/var/www/html/releases/417/var/cache/code/di/DependencyInjectionContainer_310013f5e81206c365af99087e70c5038efb75c5.php) still in var/cache folder and with high traffic and a cache-flush some requests get a 500-error:

Failed opening required ‘/var/www/html/releases/417/var/cache/code/di/DependencyInjectionContainer_310013f5e81206c365af99087e70c5038efb75c5.php’

It should be able to configure the “cacheDirectory” for DI-Cache, is this possible?

Author Ralf Hübner
Created 11/18/25, 11:28
Updated 11/21/25, 09:12
Feature
Under Review Orphaned

#107870 Modernize backend login provider registration

Backend login providers are currently registered via $GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['backend']['loginProviders']. This could be easily migrated to an attribute-based approach.

Author Elias Häußler
Assigned to Elias Häußler
Created 10/27/25, 20:04
Updated 11/20/25, 17:32
Feature
New Orphaned Backend User Interface

#108211 Clear Labeling and Accessibility for Language Select in Filelist (Edit Dialog)

Description

In the Filelist file edit dialog, the language select is currently not clearly labeled. To improve clarity and accessibility:

  • Add a clear, visible label (e.g., “Language”).
  • Since select elements don’t support true placeholders, add a first, non-valid default option “Please select a language” with an empty value.
  • Display a short helper text (below the field), e.g., “This setting controls the display language.”
  • For screen readers, ensure proper label-for/aria-label and, if a helper text exists, aria-describedby linkage.
  • Existing save behavior remains unchanged; the placeholder option must not be stored as a valid selection.
  • Note: If a language is already set, it should be preselected; the placeholder option must not appear as the active selection.

Acceptance Criteria

  • Visible label:
    > * A visible label “Language” is shown next to/above the select.
    > * The label is correctly associated with the select via for/id.
  • Placeholder option:
    > * The first option reads “Please select a language” and has an empty value.
    > * The placeholder option cannot be saved as a valid selection.
    > * If a language is already set, it is preselected; the placeholder is not selected.
  • Helper text:
    > * A short helper text is displayed below the field: “This setting controls the display language” (translatable/configurable).
    > * The helper text is linked to the select via aria-describedby.
  • Accessibility/screen readers:
    > * The select has the visible label (preferred) or, as a fallback, an aria-label “Language”.
    > * Screen readers announce the helper text via aria-describedby.
    > * Keyboard navigation (Tab, Arrow keys, Enter/Space) continues to work as before.
  • i18n/translations:
    > * Label, placeholder option, and helper text are translatable via XLF and appear in the backend user’s language.
  • UI/UX:
    > * Styling is consistent with TYPO3 backend (spacing, contrast, dark/light mode).
    > * No layout shifts or overlapping in the edit dialog.
  • Functionality/saving:
    > * Existing save/validation logic for the language selection is unchanged, except that the placeholder is not accepted as a valid value.
    > * If language is required (project-specific), validation prevents saving without a valid selection and shows a clear error message.
  • Regression:
    > * No impact on other fields or forms in Filelist.
    > * No effect on already stored language assignments.

Out of Scope

  • No changes to language inheritance or resolution logic outside the edit dialog.
  • No changes to permissions/roles.

Implementation Notes (for Devs)

  • Prefer a visible label for best accessibility; aria-label is a fallback only.
  • Add the placeholder option as the first select item with an empty value; enforce invalidity server-side and client-side.
  • Render the helper text as a field description and use its ID for aria-describedby.
  • Maintain all user-facing strings (label, placeholder, helper) in XLF for translation.
Author Christian Jung
Created 11/20/25, 10:25
Updated 11/20/25, 10:25
Task
New Orphaned TYPO3 CMS 13

#106489 Removing a site does not remove the site config directory

If a site configuration gets removed, only that specific config file is removed. An empty folder is preserved.

Author Andreas Kienast
Created 04/02/25, 10:07
Updated 11/19/25, 11:20
Bug
New Orphaned Caching TYPO3 CMS 12

#103805 Extbase response headers are not cached

When you have an extbase action which is cacheable (within TYPO3 cache) and which returns a response with custom headers, those custom headers are only sent when it’s not returned from cache.

Example Action:

<?php
public function indexAction(): ResponseInterface {
    return $this->htmlResponse()
        ->withHeader('Content-Type', 'application/json;charset=utf-8')
        ->withHeader('X-Custom-Header', 'test')
    ;
}

If this action is not part of the nonCacheableActions in TYPO3\CMS\Extbase\Utility\\ExtensionUtility::configurePlugin, the first call to this action will return the correct headers and the second call will return the string content from TYPO3 cache.

curl -o /dev/null -s -D - 'https://www.example.com'
HTTP/1.1 200 OK
...
Content-Type: application/json;charset=utf-8
X-Custom-Header: test
...

curl -o /dev/null -s -D - 'https://www.example.com'
HTTP/1.1 200 OK
...
Content-Type: application/json;charset=utf-8
...
(No X-Custom-Header)

The Content-Type header will be saved in the cache, but other headers won’t be saved.

The problem exists in Extbases Bootstrap or TypoScriptFrontendController:
https://github.com/TYPO3/typo3/blob/6199bdd0b0e29e54a1762c786c2344bfe24b0267/typo3/sysext/extbase/Classes/Core/Bootstrap.php#L137

Because the (string) result of Extbase is cached and the headers are only sent in Bootstrap::handleFrontendRequest which is not called when the content is restored from cache.

Author Robert Vock
Created 05/08/24, 12:05
Updated 11/18/25, 17:55
Task
New Orphaned Localization TYPO3 CMS 14

#108144 Consolidate general purpose action labels

There are general purpose action labels like “Edit”, “Delete” etc defined in multiple domains. Consolidate general purpose action labels into a single file

Author Lina Wolf
Assigned to Lina Wolf
Created 11/16/25, 05:50
Updated 11/16/25, 05:50

Showing results 951 to 975 of 1561