Showing results 276 to 300 of 1561

Bug
Under Review Stale File Abstraction Layer (FAL) TYPO3 CMS 13

#109630 Predefined value options for `sys_file_metadata.color_space` are wrong and incomplete

The accepted values for sys_file_metadata.color_space are defined as:

[
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.RGB', 'value' => 'RGB'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.sRGB', 'value' => 'sRGB'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.CMYK', 'value' => 'CMYK'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.CMY', 'value' => 'CMY'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.YUV', 'value' => 'YUV'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.grey', 'value' => 'grey'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.indx', 'value' => 'indx'],
]

They date back to https://github.com/TYPO3/typo3/commit/df73316a942141418285df633c2f0f18dfb59d7b#diff-9351198f2961db2960ea6ffd6589c2317efdb0768cc3ae360e6d0929c74dfe79R361-R366, which was reviewed and approved in https://review.typo3.org/c/Packages/TYPO3.CMS/+/24715/1 on 2013-10-15.

Some of these values are incorrect, and many options are missing.

The incorrect list was carried over from DAM (https://extensions.typo3.org/extension/dam), which defined:

        'color_space' => array(
            'label' => 'LLL:EXT:dam/locallang_db.xml:tx_dam_item.color_space',
            'l10n_mode' => 'exclude',
            'l10n_display' => 'defaultAsReadonly',
            'exclude' => '0',
            'config' => array(
                'type' => 'select',
                'items' => array(
                    array('', ''),
                    array('RGB', 'RGB'),
// This is not a colorspace but a color profile                    array('sRGB', 'sRGB'),
                    array('CMYK', 'CMYK'),
                    array('CMY', 'CMY'),
                    array('YUV', 'YUV'),
                    array('Grey', 'grey'),
                    array('indexed', 'indx'),
                ),
                'default' => ''
            )
        ),

Note that DAM already incorrectly defines 'grey' rather than the canonical 'GRAY', and it incorrectly defines 'YUV' rather than the canonical 'YCbr'.

But DAM correctly excludes sRGB, as sRGB is not a valid ICC color space data signature. (The ICC spec uses ‘RGB ‘ as the signature for any RGB-encoded image, regardless of whether the specific encoding is sRGB, Adobe RGB, ProPhoto, etc. Which specific RGB encoding is in use is conveyed by the attached ICC profile, not by the ColorSpaceData field.)

The conflation of the two was mistakenly introduced in https://github.com/TYPO3/typo3/commit/294a837b2222d1ebdb54337cba2fe6cbebede4ae (reviewed in https://review.typo3.org/c/Packages/TYPO3.CMS/+/44220), resolving https://forge.typo3.org/issues/70946, which was already based on the same incorrect premise.

The incorrect addition of sRGB to the color space list had worked as a band-aid to incorrect assumptions in EXT:extractor, but it must be removed, and metadata extraction fixed by no longer conflating color mode (fixed: https://github.com/xperseguers/t3ext-extractor/issues/89), color profile (unfixed) and color space.

The TYPO3 core’s incorrect color space list has also surfaced as https://github.com/xperseguers/t3ext-extractor/issues/83, although the actual bug is in TYPO3 EXT:filemetadata:

The ColorSpaceData value "GRAY", as observed in EXT:extractor#83, is in fact canonical, while 'grey' defined in https://github.com/TYPO3/typo3/blob/aa737bfbafc09cfd532d93582e5dcd693d5795a9/typo3/sysext/filemetadata/Configuration/TCA/Overrides/sys_file_metadata.php#L413-L419 is incorrect.

Aligning sys_file_metadata.color_space with the canonical ICC definition:

The set of correct values is defined in https://www.color.org/specification/ICC.1-2022-05.pdf in Table 19 — Data colour space signatures, in section 7.2.6 Data colour space field (bytes 16 to 20) on numbered page 21, which maps to physical PDF page 35.

Table 19 — Data colour space signatures

_.Colour space type _.Signature _.Hex encoding
nCIEXYZ or PCSXYZ ‘XYZ ’ 58595A20h
CIELAB or PCSLAB ‘Lab ’ 4C616220h
CIELUV ‘Luv ’ 4C757620h
YCbCr ‘YCbr’ 59436272h
CIEYxy ‘Yxy ’ 59787920h
RGB ‘RGB ’ 52474220h
Gray ‘GRAY’ 47524159h
HSV ‘HSV ’ 48535620h
HLS ‘HLS ’ 484C5320h
CMYK ‘CMYK’ 434D594Bh
CMY ‘CMY ’ 434D5920h
2 colour ‘2CLR’ 32434C52h
3 colour (other than those listed above) ‘3CLR’ 33434C52h
4 colour (other than CMYK) ‘4CLR’ 34434C52h
5 colour ‘5CLR’ 35434C52h
6 colour ‘6CLR’ 36434C52h
7 colour ‘7CLR’ 37434C52h
8 colour ‘8CLR’ 38434C52h
9 colour ‘9CLR’ 39434C52h
10 colour ‘ACLR’ 41434C52h
11 colour ‘BCLR’ 42434C52h
12 colour ‘CCLR’ 43434C52h
13 colour ‘DCLR’ 44434C52h
14 colour ‘ECLR’ 45434C52h
15 colour ‘FCLR’ 46434C52h

ICC.1:2022 © ICC 2022 – All rights reserved

ICC.1:2022 is the current version: https://www.color.org/icc_specs2.xalter

“Signature” is the value which must be saved to sys_file_metadata.color_space. (Trimming avoids roundtrip issues with VARCHAR columns which are auto-trimmed by some databases in some collations.)

The correct values for sys_file_metadata.color_space must therefore be defined as:

[
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.XYZ',  'value' => 'XYZ'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.Lab',  'value' => 'Lab'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.Luv',  'value' => 'Luv'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.YCbr', 'value' => 'YCbr'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.Yxy',  'value' => 'Yxy'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.RGB',  'value' => 'RGB'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.GRAY', 'value' => 'GRAY'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.HSV',  'value' => 'HSV'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.HLS',  'value' => 'HLS'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.CMYK', 'value' => 'CMYK'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.CMY',  'value' => 'CMY'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.2CLR', 'value' => '2CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.3CLR', 'value' => '3CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.4CLR', 'value' => '4CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.5CLR', 'value' => '5CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.6CLR', 'value' => '6CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.7CLR', 'value' => '7CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.8CLR', 'value' => '8CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.9CLR', 'value' => '9CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.ACLR', 'value' => 'ACLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.BCLR', 'value' => 'BCLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.CCLR', 'value' => 'CCLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.DCLR', 'value' => 'DCLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.ECLR', 'value' => 'ECLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.FCLR', 'value' => 'FCLR'],
]

dbFieldLength remains unchanged at 4.

The corresponding language labels must be:

  <trans-unit id="sys_file_metadata.color_space.XYZ">
    <source>nCIEXYZ or PCSXYZ</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.Lab">
    <source>CIELAB or PCSLAB</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.Luv">
    <source>CIELUV</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.YCbr">
    <source>YCbCr</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.Yxy">
    <source>CIEYxy</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.RGB">
    <source>RGB</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.GRAY">
    <source>Gray</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.HSV">
    <source>HSV</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.HLS">
    <source>HLS</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.CMYK">
    <source>CMYK</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.CMY">
    <source>CMY</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.2CLR">
    <source>2 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.3CLR">
    <source>3 colour (other than those listed above)</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.4CLR">
    <source>4 colour (other than CMYK)</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.5CLR">
    <source>5 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.6CLR">
    <source>6 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.7CLR">
    <source>7 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.8CLR">
    <source>8 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.9CLR">
    <source>9 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.ACLR">
    <source>10 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.BCLR">
    <source>11 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.CCLR">
    <source>12 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.DCLR">
    <source>13 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.ECLR">
    <source>14 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.FCLR">
    <source>15 colour</source>
  </trans-unit>

Migrations:

- grey is migrated to the correct GRAY.
- YUV is migrated to the correct YCbr.
- indx (indexed color) is removed, as it is a storage encoding, not an ICC color space signature. This was a misconception in DAM, conflating color mode/encoding and color space.
- sRGB equally is not an ICC color space signature; it was introduced to work around incorrect assumptions in EXT:extractor and must be fixed there.

Side note regarding indx and color mode conflation:

A separate sys_file_metadata.color_mode could be introduced, but that is out of scope of this bug report, which only aims at cleaning up the cargo cult of incorrect color space definitions, and finally allowing clean mapping from image files’ ColorSpaceData field to sys_file_metadata.color_space, without conflation of concepts.

Side note regarding sRGB:

The legacy and mostly obsolete EXIF ColorSpace tag describes either ICC RGB (tagged “sRGB”, “Adobe RGB”, “Wide Gamut RGB”) or none (tagged “Uncalibrated”). The tag has been superseded by ICC profile embeddings.
Notably, extracting the ICC profile description tag, such as “sRGB IEC61966-2.1” or “Adobe RGB (1998)” is out of scope. If it were in scope, then the obsolete EXIF ColorSpace tag would translate into that additional image file metadata field.

Author Leonie Philine
Created 04/17/26, 12:55
Updated 08/06/26, 20:30
Task
Under Review Stale Backend User Interface TYPO3 CMS 13

#104048 Merge Acces module into the Backend Users module

The Access module (which will be renamed to Permissions in TYPO3 13) should be merged into Backend Users to have a single and central place where integrators manage permissions.

Author Marcin Sągol
Assigned to Marcin Sągol
Created 06/11/24, 11:27
Updated 08/06/26, 17:04
Task
New Stale Backend User Interface TYPO3 CMS 12

#91203 Deleting a page with subpage(s) doesn't mention subpages in modal confirm box

Problem/Description

The modal does not show the proper information, that subpages are also deleted (if your editor user has recursive delete option activated).

Author Josef Glatz
Created 04/27/20, 09:55
Updated 08/06/26, 16:04
Bug
New Stale Backend User Interface TYPO3 CMS 10

#92909 Page Translation list is not orderable, but is rendered always in first position

In the list view for translated pages the “Page Translation” list is always on top.

In the daily work of content editors this list will hardly ever be the most important one, but there is no possbility to reorder it, because mod.web_list.tableDisplayOrder doesn’t have any effect on it.

The fact that you also can’t really collapse it (#92907) makes the situation worse.

Author Sebastian Michaelsen
Created 11/23/20, 15:24
Updated 08/06/26, 16:03
Bug
New Stale Workspaces TYPO3 CMS 13

#108958 user sees custom stages despite no stage permissions - disable or hide those stages in the dropdown

We want to use CUSTOM workspaces with several users and each user has either the permissions for one or more stages.

An example would be the following user:

The user has the permission only for CUSTOM STAGE 3 but not for Bearbeiten, CUSTOM STAGE 1/2 or Bereit zum Veröffentlichen (see screenshot)

Now, the changed record is in the stage CUSTOM STAGE 1 and the user sees every stage the record can be send to.
When he chooses for example one of the stages Bearbeiten, CUSTOM STAGE 1/2/3 or Bereit zum Veröffentlichung, the modal with the email selection appears and after clicking the “OK” button, the modal disappears and the record stays in CUSTOM STAGE 1 because the user has no permission for CUSTOM STAGE 1. So this is correct but also confusing for the user.

Why show every step when he has only the permission for CUSTOM STAGE 3.

I would suggest to disable all stages in the dropdown menu, when the permission don’t allow it that the selected record can be sent to a certain stage, so it’s clear for the user what he can do or not. If multiple records are selected, one in CUSTOM STAGE 1 and one in CUSTOM3 STAGE 3 then the dropdown should still disable all options because it’s not possible for this user to send all selected records to the choosen custom stage.

I also noticed the filter dropdown, where users can filter the records for certain stages. Maybe it’s possible to pre-select the filters based on the stages the user has permission for (multiple options have to be possible) so that the user only sees the records in the stages he has permission for from the beginning.

Author David Menzel
Created 02/12/26, 12:38
Updated 08/06/26, 16:02
Bug
New Stale Backend User Interface TYPO3 CMS 14

#108900 messages.xlf files are ignored by the new label syntax with domains

Test to reproduce the issue:

the labels defined in sysext/scheduler/Resources/Private/Language/messages.xlf

Are used in

sysext/scheduler/Resources/Private/Partials/GroupUnusedList.fluid.html
sysext/scheduler/Resources/Private/Partials/TaskList.fluid.html

as the body message of the modals triggered when you delete a task or a group, but they are ignored and the modal writes a generic “Are you sure?” that looks
like a fallback…

Please note that if you rename the messages.xlf file into whatever.xlf, then change the domain accordingly in the partials, it works.

Author Riccardo De Contardi
Created 02/08/26, 10:08
Updated 08/06/26, 16:02
Bug
New Stale Workspaces TYPO3 CMS 13

#108614 Workspace preview does not shrink down to mobile sizes

Under certain circumstances (e.g. with new pages), there is a notice displayed “The previewed page has been created in a workspace and has no live counterpart.”

This notice is very wide and disallowed by CSS from wrapping, thus the whole page including the preview iframes is wider than the viewport if you shrink down to mobile sizes (300-400px wide). See attached screenshot for an example.

Author Andreas Wolf
Created 01/09/26, 15:56
Updated 08/06/26, 16:02
Bug
New Stale Backend User Interface TYPO3 CMS 13

#108238 Deleting a record with translation does not mention the deletion of translations

TYPO3 13.4 actual situation

  1. you select multiple / all records
  2. visually only the source records are stated als “selected”
  3. pressing delete does not mention the not selected translations
  4. all selected source records and translations were removed correctly
  5. however, an editor without that deep knowledge should be informed about what is happening with translations too

What to do?

I think this is kind of UX improvement task to transport such information before deleting records.

Author Josef Glatz
Created 11/21/25, 08:38
Updated 08/06/26, 16:02
Bug
New Stale Backend API TYPO3 CMS 12

#106807 Warning "Unused elements detected on this page" not displayed in "Language comparison" "All languages"

Steps to reproduce

1. Create problematic state, e.g. by changing the colpos of a (translated) container child to invalid colpos
2. Now jump to “Language comparison” and select “All languages”

Result: The warning will not be displayed, the warning will only be displayed if the language of problematic element is selected.

If someone always works in “All languages” mode, they will never see the problem. The problematic elements (with missing colpose) are also not displayed in this mode.

The warning is displayed if problematic language is selected:

> Unused elements detected on this page
> These elements don’t belong to any of the available columns of this page. You should either delete them or move them to existing columns. We highlighted the problematic records for you.

Versions:

  • 12.4.21
Author Sybille Peters
Created 06/02/25, 10:58
Updated 08/06/26, 16:02
Task
Accepted Stale Mailer API TYPO3 CMS 12

#102335 TransportFactory should instantiate custom transports via DI container

Currently, when using $GLOBALS['TYPO3_CONF_VARS']['MAIL']['transport'] = '<classname>'; and/or $GLOBALS['TYPO3_CONF_VARS']['MAIL']['transport_spool_type'] = '<classname>';, the class in question is instantiated via makeInstance() along with constructor arguments, which does not allow to use a configured service here which itself allows for DI. this also blocks extending AbstractTransport which does a lot of useful logic already you don’t want to reimplement.

The core should use a signaling interface here like MailSettingsAware which passes the mail settings to the service (if needed) instead of passing those along as constructor arguments, especially since those are available through $GLOBALS anyway…

Author Alexander Schnitzler
Created 11/07/23, 10:04
Updated 08/06/26, 16:02
Feature
Accepted Stale Workspaces

#103639 Record Info: Show workspace in reference list

An editor wants to delete a file, but couldn’t, because it shows a reference. In the referencing element the file reference is not visible – it’s only visible in a workspace.

In the list of record references the workspace name/number would be a nice addition. The record edit link then could also contain the workspace (don’t know if possible)

Author Christoph Lehmann
Created 04/16/24, 11:54
Updated 08/06/26, 15:51
Bug
Accepted Stale Backend User Interface TYPO3 CMS 7

#75890 editor with only read access to page - some interface improvements

Steps to reproduce the issue

1) set up a page where an “editor” BE user has ONLY the “show” permission.
2) translate also the page on an alternative language
3) enter as the editor, go to the page and do the following:

3.1) Switch to “languages” view

RESULT:

see attached file schermata1.png
– the “edit” pencil icons are still present
3.1.1) if you click on the pencil > see attached file schermata2.png
- the error is not much evident (maybe a Bootstrap alert panel would be better)
– the name of the user should be used instead of/altogether with the id
– the name of the page should be used instead of/altogether with the id
– the error number “1437679336” should not be shown – for the editor, it means nothing
– last but not the least, it should be better to not show the pencil at all, I guess.

3.2) Switch to “quickedit” view

RESULT:

see attached schermata3.png

- the error is not much evident (maybe a Bootstrap alert panel would be better)
– if you click on the arrows, nothing happens; again I guess it should be better to not show them at all

Hope I made myself clear enough. have a nice day.

Author Riccardo De Contardi
Created 04/24/16, 10:02
Updated 08/06/26, 15:50
Bug
Under Review Stale Backend User Interface TYPO3 CMS 13

#106846 Char counter partally hidden

In inline record, the char counter (typo3-backend-formengine-char-counter) of last input is partally hidden

Author Davide Alghi
Created 06/07/25, 13:28
Updated 08/06/26, 15:49
Feature
Accepted Stale FormEngine aka TCEforms

#100184 Add possibility to modify inline record title for TCA type file

The introduced TCA type file does not support any method to modify the title of the rendered inline records in the backend.
Previously it was possible to set a formattedLabel_userfunc in the TCA of the sys_file_reference table.
This method still gets called but the generated recordTitle will be ignored by the FileReferenceContainer::getRecordTitle() method.

I’d suggest to introduce a new event instead of re-implementing the userfunc functionality. This would add up the to already existing ModifyFileReferenceEnabledControlsEvent and ModifyFileReferenceControlsEvent.

Maybe something named ModifyFileReferenceLabelEvent.

Author Willi Wehmeier
Created 03/16/23, 10:50
Updated 08/06/26, 15:48
Feature
New Stale

#95907 Wizard to recalculate image sizes

In case crop variants (TCA) are adjusted, currently all images need to be recalculated manually. This should be improved by adding e.g. a wizard for this task.

Imported from t3mc session "Zap the gremlins"
Author Oliver Bartsch
Created 11/08/21, 11:38
Updated 08/06/26, 15:48
Feature
Under Review Stale Dashboard

#105594 Workspaces Overview Dashboard Widget

As a chief editor I want to have an overview over the workspaces we have, their state, owners etc.

Author Sebastian Michaelsen
Assigned to Sebastian Michaelsen
Created 11/14/24, 08:19
Updated 08/06/26, 15:46
Feature
Under Review Stale CLI

#110229 Provide a `messenger:setup-transports` console command

Symfony Messenger ships a “messenger:setup-transports” command that prepares the
infrastructure (e.g. the database table) of the configured transports, but TYPO3
does not expose it.

TYPO3 should provide a native “messenger:setup-transports” console command that
prepares the infrastructure of the configured messenger transports, while NOT
touching transports whose schema is managed by TYPO3 itself.

Expected

  • ./bin/typo3 messenger:setup-transports sets up every transport that needs it.
  • ./bin/typo3 messenger:setup-transports <name> sets up only the given
    transport.

Managed transports must be skipped

The shipped Doctrine transport (“doctrine”) stores its messages in the
“sys_messenger_messages” table, whose schema is created and updated by the TYPO3
schema management (ext_tables.sql), not by the transport. Running the transport
self-setup against it would reconcile the table to Symfony’s expected shape
(“id” INT vs BIGINT, single-column indexes vs one composite index) and fight
TYPO3’s schema management.

Such a transport must therefore be skipped. It is flagged via a new marker
interface TYPO3\CMS\Core\Messenger\SchemaManagedTransportInterface; the shipped
Doctrine transport is created as schema-managed whenever automatic setup is
disabled (which TYPO3 does for “sys_messenger_messages”). The synchronous
“default” transport is not a receiver and does not support setup either.

On a standard installation the command therefore reports that there is nothing
to set up; it becomes relevant once an additional Doctrine transport with its
own table (and auto_setup enabled) is configured.

Details

  • The command is not offered as an EXT:scheduler task (one-off,
    deployment-time operation, not a recurring background job).
  • Sibling of the “messenger:stats” command (#110228).
Author Stefan Bürk
Assigned to Stefan Bürk
Created 07/19/26, 20:26
Updated 08/01/26, 20:36
Bug
Under Review Stale Extension Manager TYPO3 CMS 14

#110292 Dependency on system extension removed from core cannot be resolved

Problem

System extensions removed from the core and merged into another system extension
are declared as replacements in the composer manifest of the absorbing extension.
EXT:setup was removed in v14, and the composer manifest of EXT:backend lists
typo3/cms-setup in its replace section.

Extension releases made for older core versions still declare the extension key
setup in their ext_emconf.php constraints, and carry it in their TER dependency
data. Resolving such a dependency fails, because the replacement is only known by
composer name, never by extension key.

PackageManager::registerPackage() builds the alias map from
Package::getPackageReplacementKeys(), which returns the replace section of the
composer manifest. That map is therefore keyed by composer names, and
PackageManager::getPackageKeyFromComposerName() – used by
PackageManager::isPackageActive() – only ever hits it with a composer name.
Passing the extension key misses the map and is returned unchanged.

Verified at runtime in a functional test on main:

bc. isLoaded with setup results in false
isLoaded with backend results in true
getPackageKeyFromComposerName with setup results in setup
getPackageKeyFromComposerName with typo3/cms-setup results in backend
isPackageActive with typo3/cms-setup results in true

Impact

DependencyUtility::checkExtensionDependency() receives the extension key setup.
isDependentExtensionLoaded() is false, isDependentExtensionAvailable() is false,
and downloadExtensionFromRemote() therefore raises:

bc. The extension setup is not available from TER.

In the Extension Manager of a classic, non composer installation the extension
can be downloaded, but not activated – the activation button stays disabled and
the dependency check reports the missing extension setup. Composer mode is not
affected, because composer resolves the replace section itself.

Reported for the TER extensions deepltranslate_core and deepltranslate_glossary
on TYPO3 14.3, whose shared base extension deepl_base declares setup in the
release line built for v12 and v13.

Affected versions

main and 14.3. In 13.4 EXT:setup still exists as a system extension, so the
dependency resolves there.

Author Stefan Bürk
Assigned to Stefan Bürk
Created 07/24/26, 22:04
Updated 07/26/26, 10:07
Bug
Needs Feedback Stale File Abstraction Layer (FAL) TYPO3 CMS 13

#110137 Image processing stores a 0-byte / invalid result as a successful ProcessedFile

Summary

When the image processor (GraphicsMagick/ImageMagick) does not produce a valid output but leaves a 0-byte file behind, TYPO3 treats the run as successful — it only checks `file_exists()`, never the file’s validity/size — creates a `sys_file_processedfile` record for it, and then serves that 0-byte file on every subsequent request.

A single transient processing failure therefore turns into a permanently cached, broken image until the processed-files cache is cleared or the original file changes. This is why it typically shows up as “images are sometimes broken, sometimes not”.

Trigger

The output is empty whenever the underlying CLI run fails after (partially) creating the target file. GM/IM does exactly this on a WebP encode error: it leaves a 0-byte target file.

A reliable, deterministic trigger is a WebP output whose width or height exceeds libwebp’s hard limit of 16383 px — GM/IM aborts with `width or height exceeds limit` but leaves a 0-byte file. In production the same empty output also occurs from transient failures under load (resource contention), which is the “sometimes” case.

Steps to reproduce

1. Put a source image wider than 16383 px into a storage, e.g. `fileadmin/wide.png` (17000×1000):

gm convert -size 17000x1000 xc:teal fileadmin/wide.png

2. Process it to WebP at original size (so the result is 17000 px wide → exceeds the libwebp limit):

   $file = $storage->getFile('/wide.png');
   $processed = $file->process(
       \TYPO3\CMS\Core\Resource\ProcessedFile::CONTEXT_IMAGECROPSCALEMASK,
       ['width' => '', 'height' => '', 'fileExtension' => 'webp']
   );

Actual result (TYPO3 13.4)

isProcessed       = 1
usesOriginalFile  = 0
name              = csm_wide_<hash>.webp
exists            = 1
size              = 0          <-- empty file
width / height    = 0 / 0

- A `sys_file_processedfile` row is created (width=0, height=0).
- A second `process()` call returns the same cached 0-byte file (no reprocessing) → the failure is sticky.
- The rendered `` points to a 0-byte `.webp` → broken image, permanently, until the processed-files cache is cleared.

Expected result

A run that did not produce a valid image must not be treated as successful and must not be persisted as a ProcessedFile. The invalid result should be discarded (so the next request reprocesses) and/or the original file used as fallback — a 0-byte file should never be cached and served.

Root cause

`TYPO3\CMS\Core\Resource\Processing\LocalImageProcessor::processTaskWithLocalFile()` decides success purely on file existence (TYPO3 13.4, ~line 69):

} elseif (!empty($result['filePath']) && file_exists($result['filePath'])) {
    $task->setExecuted(true);
    $imageInformation = GeneralUtility::makeInstance(ImageInfo::class, $result['filePath']);
    // ...
    $task->getTargetFile()->updateProperties([
        'width'  => $imageInformation->getWidth(),   // 0 for an empty file
        'height' => $imageInformation->getHeight(),  // 0
        'size'   => $imageInformation->getSize(),     // 0
        'checksum' => $task->getConfigurationChecksum(),
    ]);
    $task->getTargetFile()->updateWithLocalFile($result['filePath']);
}

A 0-byte file “exists”, so the task is marked executed/successful and the (zero) dimensions are stored without being validated. `FileProcessingService::processFile()` then persists it because the task reports success (TYPO3 13.4, ~line 78):

if ($task->isExecuted() && $task->isSuccessful() && $processedFile->isProcessed()) {
    $this->processedFileRepository->add($processedFile);
}

(`GraphicalFunctions::imageMagickConvert()` likewise returns the target as a result based on `file_exists()`, so the empty file reaches the processor as a “result” in the first place.)

Proposed fix

Validate the produced file before marking the task successful — the needed data (`ImageInfo`) is already available at that spot. In `LocalImageProcessor::processTaskWithLocalFile()`:

} elseif (
    !empty($result['filePath'])
    && file_exists($result['filePath'])
    && filesize($result['filePath']) > 0
) {
    $task->setExecuted(true);
    $imageInformation = GeneralUtility::makeInstance(ImageInfo::class, $result['filePath']);
    if ($imageInformation->getWidth() === 0 || $imageInformation->getHeight() === 0) {
        // produced file is not a valid image -> do not cache, retry next time
        $task->setExecuted(false);
        return;
    }
    // ... existing success handling ...
} else {
    // no valid processing result
    $task->setExecuted(false);
}

With `setExecuted(false)` the result is not persisted; the next request reprocesses and no broken file is ever served.

Author Benjamin Blanck
Created 07/01/26, 13:45
Updated 07/02/26, 09:09
Bug
Under Review Stale Backend API TYPO3 CMS 14

#110059 Redirection to deleted pages should be visible to contributors

Hello,

Actually the module “redirect” is not showing redirections linked to deleted pages to a contributor. Which doesn’t make much sense.

If the target is an hidden page or a non-existent one, the system will show the redirect to the user, but if the page is flagged as “deleted=1” no. Which then leads to the user thinking the redirect doesn’t exist, he create a new one, but the old one is still in place and it leads to a 404 in the frontend (page deleted, normal behavior)

First one is a disabled page, the contributor can see it, no issue.
Second one, is a page that doesn’t exist, the user can see it again, no issue.

If I log in as an admin, their is a third redirect, at the top, the one with a deleted page as a target:

If the user is a contributor, their is some access check compared to an admin. In this file: TYPO3\CMS\Redirects\Security\RedirectPermissionGuard:113:

We simply needs to set the third parameter “$useDeleteClause = true” to false.

I don’t see any issue to do that, since the system will still check if the user can see the page or not.
The bug is present at least since TYPO3 10, but it’s not a security issue, so it should be fix for TYPO3 13 and up? If I have time I’ll send a patch.

Author Ludovic Nogueira
Created 06/16/26, 05:45
Updated 06/30/26, 13:49
Task
Under Review Stale Backend JavaScript TYPO3 CMS 14

#109062 Deprecate inline language labels (TYPO3.lang)

Author Benjamin Franzke
Created 02/22/26, 14:10
Updated 06/29/26, 08:25
Bug
New Stale Database API (Doctrine DBAL) TYPO3 CMS 13

#110091 Database schema is changed once an extension regfisters a page tsconfig file via ExtensionManagementUtility::registerPageTSConfigFile()

The database schema for tsconfig_includes changes from StringType (e.g. varchar(255)) to TextType, when at least one
item has been added to the select list via ExtensionManagementUtility::registerPageTSConfigFile().

That means the installations of extension like bootstrap_package that configure select items as in https://github.com/benjaminkott/bootstrap_package/blob/15.0.4/Configuration/TCA/Overrides/100_pages.php#L15 trigger a column change.

This is unfortunate, especially in sqlite environments, as it requires the entire table to be recreated via the sqlite table recreation pattern: https://github.com/doctrine/dbal/blob/73653de42d9836e4a00350afc697c5e7e31706f2/src/Platforms/SQLitePlatform.php#L693-L709

Ideally we should try to enforce a stable schema for core fields, where we know upfront, that the column type shall be TEXT.

See screenshot:

For sake of completeness, this is the full SQL that is presented to the integrator:

CREATE TEMPORARY TABLE __temp__pages AS SELECT uid, pid, tstamp, crdate, deleted, hidden, starttime, endtime, fe_group, sorting, rowDescription, editlock, sys_language_uid, l10n_parent, l10n_source, l10n_state, l10n_diffsource, t3ver_oid, t3ver_wsid, t3ver_state, t3ver_stage, perms_userid, perms_groupid, perms_user, perms_group, perms_everybody, SYS_LASTCHANGED, shortcut, content_from_pid, mount_pid, tx_impexp_origuid, sitemap_priority, doktype, title, slug, TSconfig, php_tree_stop, categories, layout, extendToSubpages, nav_title, nav_hide, subtitle, target, url, lastUpdated, newUntil, cache_timeout, cache_tags, no_search, shortcut_mode, keywords, description, abstract, author, author_email, media, is_siteroot, mount_pid_ol, module, l18n_cfg, backend_layout, backend_layout_next_level, tsconfig_includes, seo_title, no_index, no_follow, sitemap_changefreq, canonical_link, og_title, og_description, og_image, twitter_title, twitter_description, twitter_image, twitter_card FROM "pages"
Current value: "tsconfig_includes" VARCHAR(255) DEFAULT ''

DROP TABLE "pages"
Current value: "tsconfig_includes" VARCHAR(255) DEFAULT ''

CREATE TABLE "pages" (uid INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, pid INTEGER UNSIGNED DEFAULT 0 NOT NULL, tstamp INTEGER UNSIGNED DEFAULT 0 NOT NULL, crdate INTEGER UNSIGNED DEFAULT 0 NOT NULL, deleted SMALLINT UNSIGNED DEFAULT 0 NOT NULL, hidden SMALLINT UNSIGNED DEFAULT 0 NOT NULL, starttime INTEGER UNSIGNED DEFAULT 0 NOT NULL, endtime INTEGER UNSIGNED DEFAULT 0 NOT NULL, fe_group VARCHAR(255) DEFAULT '0' NOT NULL, sorting INTEGER DEFAULT 0 NOT NULL, rowDescription CLOB DEFAULT NULL, editlock SMALLINT UNSIGNED DEFAULT 0 NOT NULL, sys_language_uid INTEGER DEFAULT 0 NOT NULL, l10n_parent INTEGER UNSIGNED DEFAULT 0 NOT NULL, l10n_source INTEGER UNSIGNED DEFAULT 0 NOT NULL, l10n_state CLOB DEFAULT NULL, l10n_diffsource BLOB DEFAULT NULL, t3ver_oid INTEGER UNSIGNED DEFAULT 0 NOT NULL, t3ver_wsid INTEGER UNSIGNED DEFAULT 0 NOT NULL, t3ver_state SMALLINT DEFAULT 0 NOT NULL, t3ver_stage INTEGER DEFAULT 0 NOT NULL, perms_userid INTEGER UNSIGNED DEFAULT 0 NOT NULL, perms_groupid INTEGER UNSIGNED DEFAULT 0 NOT NULL, perms_user SMALLINT UNSIGNED DEFAULT 0 NOT NULL, perms_group SMALLINT UNSIGNED DEFAULT 0 NOT NULL, perms_everybody SMALLINT UNSIGNED DEFAULT 0 NOT NULL, SYS_LASTCHANGED INTEGER UNSIGNED DEFAULT 0 NOT NULL, shortcut INTEGER UNSIGNED DEFAULT 0 NOT NULL, content_from_pid INTEGER UNSIGNED DEFAULT 0 NOT NULL, mount_pid INTEGER UNSIGNED DEFAULT 0 NOT NULL, tx_impexp_origuid INTEGER DEFAULT 0 NOT NULL, sitemap_priority NUMERIC(2, 1) DEFAULT '0.5' NOT NULL, doktype INTEGER UNSIGNED DEFAULT 0 NOT NULL, title VARCHAR(255) DEFAULT '' NOT NULL, slug CLOB DEFAULT NULL, TSconfig CLOB DEFAULT NULL, php_tree_stop SMALLINT UNSIGNED DEFAULT 0 NOT NULL, categories INTEGER UNSIGNED DEFAULT 0 NOT NULL, layout INTEGER UNSIGNED DEFAULT 0 NOT NULL, extendToSubpages SMALLINT UNSIGNED DEFAULT 0 NOT NULL, nav_title VARCHAR(255) DEFAULT '' NOT NULL, nav_hide SMALLINT UNSIGNED DEFAULT 0 NOT NULL, subtitle VARCHAR(255) DEFAULT '' NOT NULL, target VARCHAR(80) DEFAULT '' NOT NULL, url VARCHAR(255) DEFAULT '' NOT NULL, lastUpdated BIGINT DEFAULT 0 NOT NULL, newUntil BIGINT DEFAULT 0 NOT NULL, cache_timeout INTEGER UNSIGNED DEFAULT 0 NOT NULL, cache_tags VARCHAR(255) DEFAULT '' NOT NULL, no_search SMALLINT UNSIGNED DEFAULT 0 NOT NULL, shortcut_mode INTEGER UNSIGNED DEFAULT 0 NOT NULL, keywords CLOB DEFAULT NULL, description CLOB DEFAULT NULL, abstract CLOB DEFAULT NULL, author VARCHAR(255) DEFAULT '' NOT NULL, author_email VARCHAR(255) DEFAULT '' NOT NULL, media INTEGER UNSIGNED DEFAULT 0 NOT NULL, is_siteroot SMALLINT UNSIGNED DEFAULT 0 NOT NULL, mount_pid_ol SMALLINT DEFAULT 0 NOT NULL, module VARCHAR(255) DEFAULT '' NOT NULL, l18n_cfg SMALLINT UNSIGNED DEFAULT 0 NOT NULL, backend_layout VARCHAR(64) DEFAULT '' NOT NULL, backend_layout_next_level VARCHAR(64) DEFAULT '' NOT NULL, "tsconfig_includes" CLOB DEFAULT NULL, seo_title VARCHAR(255) DEFAULT '' NOT NULL, no_index SMALLINT UNSIGNED DEFAULT 0 NOT NULL, no_follow SMALLINT UNSIGNED DEFAULT 0 NOT NULL, sitemap_changefreq VARCHAR(10) DEFAULT '' NOT NULL, canonical_link CLOB DEFAULT '' NOT NULL, og_title VARCHAR(255) DEFAULT '' NOT NULL, og_description CLOB DEFAULT NULL, og_image INTEGER UNSIGNED DEFAULT 0 NOT NULL, twitter_title VARCHAR(255) DEFAULT '' NOT NULL, twitter_description CLOB DEFAULT NULL, twitter_image INTEGER UNSIGNED DEFAULT 0 NOT NULL, twitter_card VARCHAR(255) DEFAULT '' NOT NULL)
Current value: "tsconfig_includes" VARCHAR(255) DEFAULT ''

INSERT INTO "pages" (uid, pid, tstamp, crdate, deleted, hidden, starttime, endtime, fe_group, sorting, rowDescription, editlock, sys_language_uid, l10n_parent, l10n_source, l10n_state, l10n_diffsource, t3ver_oid, t3ver_wsid, t3ver_state, t3ver_stage, perms_userid, perms_groupid, perms_user, perms_group, perms_everybody, SYS_LASTCHANGED, shortcut, content_from_pid, mount_pid, tx_impexp_origuid, sitemap_priority, doktype, title, slug, TSconfig, php_tree_stop, categories, layout, extendToSubpages, nav_title, nav_hide, subtitle, target, url, lastUpdated, newUntil, cache_timeout, cache_tags, no_search, shortcut_mode, keywords, description, abstract, author, author_email, media, is_siteroot, mount_pid_ol, module, l18n_cfg, backend_layout, backend_layout_next_level, "tsconfig_includes", seo_title, no_index, no_follow, sitemap_changefreq, canonical_link, og_title, og_description, og_image, twitter_title, twitter_description, twitter_image, twitter_card) SELECT uid, pid, tstamp, crdate, deleted, hidden, starttime, endtime, fe_group, sorting, rowDescription, editlock, sys_language_uid, l10n_parent, l10n_source, l10n_state, l10n_diffsource, t3ver_oid, t3ver_wsid, t3ver_state, t3ver_stage, perms_userid, perms_groupid, perms_user, perms_group, perms_everybody, SYS_LASTCHANGED, shortcut, content_from_pid, mount_pid, tx_impexp_origuid, sitemap_priority, doktype, title, slug, TSconfig, php_tree_stop, categories, layout, extendToSubpages, nav_title, nav_hide, subtitle, target, url, lastUpdated, newUntil, cache_timeout, cache_tags, no_search, shortcut_mode, keywords, description, abstract, author, author_email, media, is_siteroot, mount_pid_ol, module, l18n_cfg, backend_layout, backend_layout_next_level, tsconfig_includes, seo_title, no_index, no_follow, sitemap_changefreq, canonical_link, og_title, og_description, og_image, twitter_title, twitter_description, twitter_image, twitter_card FROM __temp__pages
Current value: "tsconfig_includes" VARCHAR(255) DEFAULT ''
Author Benjamin Franzke
Created 06/24/26, 07:21
Updated 06/24/26, 19:53
Bug
New Stale FormEngine aka TCEforms TYPO3 CMS 14

#110095 TcaColumnsRemoveEmptyRelations behavior is too disruptive

The default behavior of the newly introduced feature to completely hide select fields (and others) in the backend form in case not selectable items can be shown is too disruptive. In case the debug-mode is not active, an expected field is simply missing in the backend form, leaving the user clueless and confused what actually happened.

Step to reproduce

  • new TYPO3 v14/v15 instance (not having filemounts or be_groups at all)
  • TYPO3_CONF_VARS/BE/debug is disabled (false)
  • create a new be_groups record
  • the fields “subgroup” or “filemounts” are simply not shown (the “filemounts” has wizard actions for creating new file mounts

Expectation

  • at least show a hint, why the field is not shown (like it’s done when having debuggin enabled)

Suggested Change

Instead of enforcing the disruptive change and that affected fields have to opt out (which also is a breaking change), I’d suggest to apply the opposite behavior:
Fields must actively opt in, in case the want to use that TYPO3 v14.2 feature.

Docs Reference

Author Oliver Hader
Created 06/24/26, 10:30
Updated 06/24/26, 10:44
Epic
Under Review Stale

#97387 Configurable Password Policies

In order to provide strong defaults in regards to password security, TYPO3 will be able to validate user passwords against configurable password policies. This feature will increase the general security for TYPO3 users by providing a default password policy. Also TYPO3 as a CMS would be inline with recommendations on password security from the german BSI.

  • TYPO3 will ships with a default password policy
  • TYPO3 uses the default password policy for all scopes (backend and frontend user passwords)
  • The default password policy can be extended
  • It is possible to define custom password policies
  • TYPO3 will by default only support 2 scopes (BE and FE user passwords), but can be extended to support user defined scopes (e.g. in order to validate custom password fields for tables other than be_users and fe_users)

Technical implementation

A password policy is defined by a set of validators (not Extbase validators). If a password policy consists of multiple validators, they are chained. A Password checked within a password policy must match all configured and active validators.

The PasswordPolicyValidator class will provides a function to validate a given password based on the current password policy for the current scope. The validation result (true/@false@) will be returned and potential validation error messages can be retrieved from the PasswordPolicyValidator instance.

Validators

Validators for usage in a password policy must implement the PasswordValidatorInterface or extend the AbstractPasswordValidator class. Besides validation logic, a validator must also be able to return an array of strings with password requirements (e.g. “minimun length x chars”) in order to provide human readable password requirements. In case of a failed validation a validation error message can be definied.

Validators can be excluded for certain actions (e.g. no current password check for password of new users). Available actions are definied globally in the class PasswordPolicyAction.

Password Policy Configuration

Password Policy configuration is located in LocalConfiguration.php as shown below:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['passwordPolicies'] = [
    'default' => [
        'validators' => [
            \TYPO3\CMS\Core\PasswordPolicy\Validator\CorePasswordValidator::class => [
                'options' => [
                    'minimumLength' => 8,
                    'upperCaseCharacterRequired' => true,
                    'lowerCaseCharacterRequired' => true,
                    'digitCharacterRequired' => true,
                    'specialCharacterRequired' => true,
                ],
                'excludeActions' => [],
            ],
            \TYPO3\CMS\Core\PasswordPolicy\Validator\NotCurrentPasswordValidator::class => [
                'options' => [],
                'excludeActions' => [
                    \TYPO3\CMS\Core\PasswordPolicy\PasswordPolicyAction::NEW_USER_PASSWORD,
                ],
            ],
        ],
    ],
];

$GLOBALS['TYPO3_CONF_VARS']['BE']['passwordPolicy'] = 'default';
$GLOBALS['TYPO3_CONF_VARS']['FE']['passwordPolicy'] = 'default';

Password Policies can globally be disabled (e.g. for development environment) by setting the BE/FE password policy to an empty value in AdditionalConfiguration.php

→ see https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Feature-97388-ConfigurablePasswordPolicies.html

JavaScript module and API (TYPO3 backend only)

In order to provide instant feedback for users entering a password, a general JavaScript module needs to be developed, which validates a password when it is entered into a password field. The JavaScript module can be used for either password fields in FormEngine or regular password input fields (e.g. setup module or install tool) if possible.

Example:

A new backend route (similar to the slug suggest route) will use the configured password policy based on the given scope. Since custom password validators may use backend logic (e.g. check password against a deny-list), a client/server integration as described is required and has to be discussed.

Where can password policies be used in TYPO3?

  • Backend and frontend user password change using DataHandler (TCA type=password)
  • Backend user password (setup module)
  • Password reset for backend user
  • Password reset for frontend user
  • Install tool – Create Administrative User
  • Install tool – Install tool password
  • Install tool – Initial admin user
Author Torben Hansen
Assigned to Torben Hansen
Created 04/15/22, 05:49
Updated 06/21/26, 09:14
Bug
New Stale TYPO3 CMS 12

#106507 invalidateAllSessionsByUserId method in SessionManager runs out of memory when fe_sessions table has 300k+ entries

In TYPO3\CMS\Core\Session\SessionManager class method invalidateAllSessionsByUserId is called for an example when fe_user password is changed in backend.

If fe_sessions table has 300k+ entries getting all sessions runs out of memory. Increasing memory to 2GB helps but only to a point.

It would be better if only sessions specific for fe_user are fetched instead of $backend->getAll().

foreach ($backend->getAll() as $session) {
            if ($userAuthentication !== null) {
                if ($session['ses_id'] === $sessionToRenew || $session['ses_id'] === $hashedSessionToRenew) {
                    $userAuthentication->enforceNewSessionId();
                    continue;
                }
            }
            if ((int)$session['ses_userid'] === $userId) {
                $backend->remove($session['ses_id']);
            }
        }

This might also be a problem by password recovery, but I did not test that.

Number of sessions in fe_sessions needed for memory issue depends on ses_data size. My issue was with 300k+ entries.

Author B Novak
Created 04/03/25, 14:04
Updated 06/19/26, 13:52

Showing results 276 to 300 of 1561