Showing results 726 to 750 of 1561

Feature
New Stale Backend User Interface

#102390 Make date/time format configurable on a per-user basis

The date/time format shown in the TYPO3 backend can be configured as a global configuration:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['ddmmyy'] = 'd-m-y';
$GLOBALS['TYPO3_CONF_VARS']['SYS']['hhmm'] = 'H:i';

However, different BE users prefer different formats. This in particular applies to TYPO3 installations for large enterprises or organizations across the globe. A BE user located in the US likely prefers a different format than a user in Europe. Therefore, a global configuration is not appropriate.

I’d like to have the date/time format configurable on a per-user basis (for example: User -> User Settings -> Backend appearance).

Author Michael Schams
Created 11/16/23, 22:29
Updated 08/06/26, 15:48
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 Mailer API

#96285 SVG in loginLogo is also used in the default email-template. Problem in Outlook.

In the Typo3 default email template (SystemEmail.html) the login.loginLogo is used.
We often use SVGs for the logo. It works fine in Typo3.
But in default email-template the same logo is used, but it is not visible in Outlook, because Outlook doesn’t supports SVG very well.

SystemEmail.html

 <f:image src="{typo3.systemConfiguration.backend.loginLogo}" ... />

Why not add an additional Field login.emailLogo for use of jpg or png only for the email?

OK, I can make my own copy but in the most purposes the default email-template is good. Only with this small issue.

Author Mario Wilhelm
Created 12/08/21, 09:29
Updated 08/06/26, 15:48
Feature
New Stale Backend User Interface

#98953 "Go to list module" hint in not folder pages

Make it possible to configure a page that’s not a sysfolder to display the “Go to list module” hint in Page module.

The hint description should be a bit different:
“The current page could contain records only visible in List module.”

Author Christian Toffolo
Assigned to Yasmin Haustein
Created 10/29/22, 09:40
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
New Stale Import/Export (T3D)

#94941 Exports via export tools sometimes contain previous exports

When I used the export tool to make an export the exported data was saved at public/fileadmin/user_upload/_temp_/importexport

On the next export all files from public/fileadmin/user_upload/_temp_ and their sys_file entries also got exported. Therefore the export contained the previous export as files and grew bigger and bigger…

Author Lina Wolf
Created 08/20/21, 08:21
Updated 08/06/26, 15:48
Feature
New Stale Linkvalidator

#92542 Linkvalidator should check shortcut pages

We repeatedly have errors in the log due to inaccessible shortcut pages, e.g. from solr crawling.

Unfortunately, the linkvalidator does not check the shortcuts, and they can not be simply added to the PageTS config since the target page also depends on the shortcut_mode field.
It would be awesome to have this functionality added to the linkvalidator!

Author Andreas Kießling
Created 10/12/20, 12:06
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
Task
Accepted Stale TYPO3 CMS 14

#108784 Migrate dropdowns to popover API

Author Oliver Bartsch
Created 01/27/26, 08:08
Updated 08/06/26, 15:46
Bug
Accepted Stale TYPO3 CMS 12

#106200 IconFactory returns modified icons

I as an API user would expect a proper Icon instance from the IconFactory.
But the IconFactory does not return the pure icon. It keeps an internal cache with references. The returned icons can be modified later through their setter. This might be useful if one would add an title or re use an icon but make it spinning.
The issue is that those are setters. Instead, a clone should be returned. Maybe `with` instead of `set` methods should exist.

This can also happen when using <core:icon title="Open actions menu" identifier="actions-menu" />. That way also integrators might run into those issues. As it is not clear that the `title` attribute will modify the system state of the used icon.

Steps to reproduce:

  1. Fetch an icon by its identifier in context a and render it
  2. Fetch an icon by the same identifier as in step 1, modify the returned icon, e.g. make it spinning or set a title and render it
  3. Fetch an icon by the same identifier as in step 1. It will be rendered with modifications from 2nd step.

The issue occurs in v12 and v13.

Author Daniel Siepmann
Created 02/18/25, 13:28
Updated 08/06/26, 15:46
Feature
Accepted Stale Linkvalidator

#106487 Improve linkvalidator report mail template

An improvement for the template of the LinkValidator report will be:
1) on a multi-site setup, there will be many different reports for different receipients and different sites. Therefore it would be helpful, if there is some differentation in the mail reports.
E.g. the site name or the text out of the scheduler task or another free text field which I can fill in at the scheduler configuration.

2) another helpful feature will be a direct linking out of the report mail to the backend to edit the broken records. Now we’ve the direct links to backend views, so it should be possible to link to the affected entries directly.

Author Wolfgang Twaroch
Created 04/02/25, 09:32
Updated 08/06/26, 15:46
Bug
New Stale FormEngine aka TCEforms TYPO3 CMS 13

#109375 ExtensionManagementUtility::addToAllTCAtypes is broken with auto-created system TCA columns

An arbitrary field cannot be properly inserted wherever we like if the position is “before” or “after” an auto-created system TCA column such as “starttime”, “hidden” or “fe_group”.

Works fine:

  • Up to TYPO3 v12

Broken in:

  • TYPO3 v13
  • TYPO3 v14.2.0-dev

This seems related to the introduction of auto-created system TCA columns in #104311.

Sample code to reproduce

Taken from EXT:mfa_protect, use features/TYPO3v14 branch to have sample code to play with in v13 and v14.

From that extension, content of Configuration/TCA/Overrides/tt_content.php (stripped to minimum):

$tempColumns = [
    'tx_mfaprotect_enable' => [
        'label' => 'LLL:EXT:mfa_protect/Resources/Private/Language/locallang_db.xlf:tt_content.tx_mfaprotect_enable',
        'config' => [
            'type' => 'check',
            'renderType' => 'checkboxToggle',
        ]
    ],
];

\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addTCAcolumns('tt_content', $tempColumns);
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addToAllTCAtypes(
    'tt_content',
    'tx_mfaprotect_enable',
    '',
    'before:starttime'
);

Up to TYPO3 v12, the field is properly inserted between “hidden” and the palette containing “starttime”:

Since TYPO3 v13, the field is inserted at “random position” at the end of another tab.

Further analysis

Inserted position containing an auto-created system column seems to cause the issue. Inserting before/after any other field (such as “linkToTop” or “pi_flexform”) doesn’t cause this issue.

Adding to a palette seems to work with those system columns:

\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addFieldsToPalette(
    'tt_content',
    'hidden',
    '--linebreak--,tx_mfaprotect_enable',
    'after:hidden'
);

This effectively inserts my field within the hidden auto-created palette and is visually similar, although not 100% identical:

Author Xavier Perseguers
Created 03/26/26, 08:46
Updated 08/06/26, 09:26
Task
Author Simon Praetorius
Assigned to Simon Praetorius
Created 08/05/26, 13:46
Updated 08/05/26, 22:18
Epic
New Stale Database API (Doctrine DBAL)

#110253 Prepare database abstraction layer for Doctrine DBAL 5.x

doctrine/dbal 4.3 and 4.4 deprecated a large part of the schema object and
schema manager API that TYPO3 builds upon. main, 14.3 and 13.4 all use
doctrine/dbal ~4.4.3, so the deprecation surface is identical on all three
branches.

Nothing is currently visible: doctrine/deprecations defaults to “none” and
TYPO3 never enables it. This is forward-compatibility work for DBAL 5.x, not
an active defect.

An audit identified three items that are not part of the upstream deprecation
list but dominate the effort:

1. The new introspect*() API bypasses the protected _getPortable*() hooks
entirely. Introspection now runs through IntrospectingSchemaProvider and the
per-platform MetadataProvider implementations, both final/internal. TYPO3
carries six _getPortable* overrides (Doctrine type from column comment,
MySQL default value unescaping, MySQL index prefix lengths). Migrating
naively drops that behaviour silently and persists wrong column metadata in
the “database_schema” cache.

2. TYPO3\CMS\Core\Database\Schema\TableDiff extends the Doctrine class but
deliberately does not call parent::__construct(). The inherited
getDroppedForeignKeyConstraintNames() reads Doctrine’s uninitialised private
property and raises an Error. Dormant today, but it is the method DBAL 5
switches to.

3. Two places rely on the array keys of Table::getIndexes() and
Table::getForeignKeys() being names. Those become lists in DBAL 5, turning
an overwrite into an append (duplicate indexes and foreign keys).

Related to #106495, which deferred exactly this scope.

Work is split into child issues. Behaviour-preserving changes are backported to
14.3 and 13.4; anything that changes generated DDL, diff content or public API
stays on main.

There are possible more to come in the future.

[1] https://github.com/doctrine/dbal/blob/4.4.x/UPGRADE.md

Author Stefan Bürk
Assigned to Stefan Bürk
Created 07/21/26, 18:00
Updated 08/02/26, 12:15
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
Feature
Under Review Stale CLI

#110228 Provide a `messenger:stats` console command

Symfony Messenger ships a “messenger:stats” command that reports the number of
queued messages per transport, but TYPO3 does not expose it.

TYPO3 should provide a native “messenger:stats” console command that reports the
message count for the configured messenger transports, so the queue fill level
can be monitored from the command line.

Expected

  • ./bin/typo3 messenger:stats prints a table of transport name and message
    count for every countable transport.
  • ./bin/typo3 messenger:stats <name> [<name> ...] limits the output to the
    given transports.
  • --format=txt (default, table) and --format=json (machine readable) are
    supported.

Details

  • Countable transports are receivers implementing
    Symfony\Component\Messenger\Transport\Receiver\MessageCountAwareInterface.
    The shipped Doctrine transport (“doctrine”) qualifies; the synchronous
    “default” transport is not a receiver and is not listed.
  • A transport that exists but cannot report a count is reported as uncountable
    rather than silently omitted.
  • The command is read-only and does not modify any transport.

Scope

This is the first, self-contained part of bringing TYPO3 to parity with the
Symfony Messenger tooling. The related “messenger:setup-transports” command and
the failure-transport / retry / “messenger:failed:*” tooling are handled in
separate, dedicated issues, because “setup-transports” must account for the
DBMS-managed “sys_messenger_messages” table (TYPO3 manages its schema, so it
must be excluded from the transport self-setup).

Author Stefan Bürk
Assigned to Stefan Bürk
Created 07/19/26, 19:23
Updated 08/01/26, 20:36
Bug
Under Review Stale Backend User Interface TYPO3 CMS 15

#110330 Translation wizard offers Translate mode for Free Mode source languages

Problem

When Free Mode content from a non-default language is selected as the source in the translation wizard, the wizard still offers both Translate and Copy as localization modes.

A Free Mode source record has no relation to a default-language record through l18n_parent. The wizard therefore cannot derive a connected translation from that source record.

Nevertheless, the wizard allows the editor to select Translate, which represents the connected localization mode. Completing the wizard still creates a target-language record with an empty l18n_parent. The resulting record is therefore Free Mode content, regardless of the selected localization mode.

The Translate option consequently suggests that a connected localization can be created, although the selected mode has no corresponding effect on the resulting record structure.

Prerequisites

  • TYPO3 v14 or TYPO3 15.0.0-dev
  • A site with a default language
  • At least two additional languages
  • A page translated into both additional languages
  • At least one Free Mode content element in the first additional language
  • Default localization wizard configuration

Steps to reproduce

  1. Create a page in the default language.
  2. Create page translations for two additional languages, for example German and Spanish.
  3. Create a content element in the first additional language in Free Mode, either independently or by using the Copy localization mode.
  4. Verify that the Free Mode content element has an empty l18n_parent.
  5. Open the language column of the second additional language in Content > Layout.
  6. Start the translation wizard.
  7. Select the first additional language as the source language.
  8. Select the Free Mode content element.
  9. Continue to the localization-mode step.
  10. Select Translate as the connected localization mode.
  11. Complete the wizard.
  12. Inspect the content element created in the target language.

Actual behavior

The localization-mode step offers both Translate and Copy.

Selecting Translate creates a target-language content element with an empty l18n_parent. The created record is therefore in Free Mode and is not connected to a default-language record.

The resulting data structure is equivalent to the structure created through Copy. Selecting the connected localization mode does not create a connected translation and has no meaningful effect on the result.

An attached video demonstrates the complete workflow using the following languages:

  • English as the default language
  • German as the source language containing Free Mode content
  • Spanish as the target language

In the video, German is selected as the source language and Translate is selected as the connected localization mode. The resulting Spanish content element is nevertheless created in Free Mode with an empty l18n_parent.

The video confirms that the offered localization-mode choice does not correspond to the localization structure that the wizard can actually create.

Expected behavior

Translate must not be offered when the selected source records are Free Mode records from a non-default language and no default-language translation parent can be derived.

When all selected source records meet this condition, Copy is the only structurally valid Core localization mode.

With the default wizard configuration, the wizard should therefore apply the copy behavior directly and skip the localization-mode step because no meaningful choice remains.

When the selected records from a non-default source language are connected to default-language records, both Translate and Copy must remain available.

Reproducibility

  • Reproducible: Yes
  • Initially observed: Translation Handling Initiative meeting on 2026-07-24
  • Confirmed affected version: TYPO3 v14
  • Confirmed affected version: TYPO3 15.0.0-dev
  • Earlier versions: Not verified
  • Regression: Not verified
  • Demonstration: Reproduction video attached

Technical analysis

A connected localization requires a default-language origin that can be assigned to the target record through l18n_parent.

A Free Mode source record from a non-default language does not have such a relation. The translation wizard therefore cannot derive a default-language origin for the new target-language record.

As a result, selecting Translate cannot produce the connected record structure represented by that mode. The wizard instead creates the same Free Mode structure that is expected from Copy.

The availability of Translate should therefore depend not only on the selected source language, but also on whether the selected source records provide valid relations to default-language records.

Forge issue #95909 established the general behavior that the localization-mode step should be skipped when only one localization mode is available. The missing condition here is detecting that Translate is not applicable when the selected source records are Free Mode records from a non-default language.

Scope

  • In scope: Selections consisting entirely of Free Mode records from a non-default source language
  • In scope: Removing the structurally unavailable Translate option
  • In scope: Skipping the localization-mode step when Copy is the only remaining Core mode
  • Out of scope: Selections containing both connected and Free Mode records
  • Out of scope: Third-party translation or machine-translation integrations
  • Out of scope: Changing the handling of connected records from a non-default source language

Additional information

A reproduction video is attached. The demonstration uses English as the default language, German as the Free Mode source language, and Spanish as the target language.

It shows that selecting German Free Mode content as the source and choosing Translate still creates Spanish Free Mode content. This demonstrates that the offered localization-mode choice does not affect the resulting relation structure.

Forge #95909 implemented skipping the localization-mode step when only one mode is available. It does not detect that Translate is unavailable for Free Mode records from a non-default source language.

Forge #109833 concerns another unnecessary localization-mode step in the new wizard, but only for empty pages or an empty record selection.

Forge #86231 documents the structural limitation of deriving translations from a Free Mode localization, but does not address the corresponding localization-mode selection in the current wizard.

Author Eric Harrer
Assigned to Eric Harrer
Created 07/30/26, 09:45
Updated 07/31/26, 22:58
Bug
Under Review Stale Localization TYPO3 CMS 15

#110328 Transl.Orig selector offers records already translated into the target language

Problem

When editing a connected translation of a content element, the Transl.Orig [l18n_parent] selector offers default-language records that are already used as the translation parent of another active record in the same target language.

Assigning such a record and saving the form creates multiple translated content elements with the same combination of:

  • target language (sys_language_uid)
  • translation parent (l18n_parent)

The regular record-editing workflow therefore allows an inconsistent localization state to be created.

This inconsistency also causes different backend modules to resolve and display different translations for the same default-language content element.

Prerequisites

  • TYPO3 v14 or TYPO3 15.0.0-dev
  • A site with a default language and at least one additional language
  • A page translated into the additional language
  • Two content elements in the default language

Steps to reproduce

  1. Create two default-language content elements, referred to as content element 1 and content element 2.
  2. Use the translation wizard in Content > Layout to create connected translations of both records in the same target language.
  3. Open the translated record of content element 2.
  4. Open the Language tab.
  5. Change Transl.Orig from content element 2 to content element 1, although content element 1 is already assigned as the translation parent of the translated content element 1.
  6. Save the record.
  7. Compare the translated page in the Page module and the List module.

Actual behavior

The record is saved successfully.

Both translated records now have the same target language and reference content element 1 through tt_content.l18n_parent.

The Transl.Orig selector neither prevents the duplicate assignment nor indicates that content element 1 is already used by another active translation in the current target language.

The resulting inconsistent state is handled differently by backend modules:

  • The Page module only displays the translated content element 2.
  • The List module only displays the translated content element 1.

A video demonstrating the complete workflow and the differing results in both modules is attached.

Expected behavior

The Transl.Orig selector must not offer a default-language record that is already assigned as the translation parent of another active record in the current target language.

The following records must remain selectable:

  • The translation parent currently assigned to the edited record
  • Default-language records that do not yet have an active connected translation in the current target language

The regular record-editing workflow must not allow multiple active records to acquire the same combination of target language and translation parent.

The Page and List modules must consequently operate on an unambiguous translation relation and display the same connected translation.

Reproducibility

  • Reproducible: Yes
  • Initially observed: Translation Handling Initiative meeting on 2026-07-24
  • Confirmed affected versions: TYPO3 v14 and TYPO3 15.0.0-dev
  • Earlier versions: Not verified
  • Regression: Not verified

Technical analysis

For tt_content, the TCA transOrigPointerField is configured as l18n_parent.

For connected translations, the combination of the target language and the translation parent is expected to identify a single active translated record. The record-editing form currently does not enforce this invariant when manually changing l18n_parent.

Filtering the Transl.Orig selector should therefore account for:

  • the target language of the record being edited
  • existing active translations using each possible parent
  • the UID of the record currently being edited, so that its existing parent remains selectable
  • applicable enable fields and record-state restrictions

The inconsistent Page- and List-module results indicate that different record-retrieval paths resolve the ambiguous translation relation differently. Preventing the duplicate assignment would avoid creating this ambiguous data state through the regular editing workflow.

Scope

  • In scope: Preventing duplicate translation-parent assignments through the regular record-editing form
  • In scope: Filtering default-language records that are already used by another active translation in the current target language
  • In scope: Preserving the current record’s existing parent as a selectable option
  • Out of scope: Repairing existing inconsistent database records
  • Out of scope: Restoring deleted records
  • Out of scope: Conflicts introduced through Workspace publication

Additional information

Forge #97094 covers an incorrect translation status after manually changing Transl.Orig. It does not request that already occupied translation parents be excluded from the selector.

Forge #107071 describes the same duplicate target-language and translation-parent data structure being created through Workspace publication. The issue described here concerns the regular record-editing workflow.

Author Eric Harrer
Assigned to Eric Harrer
Created 07/30/26, 09:23
Updated 07/31/26, 22:58
Task
Under Review Stale TYPO3 CMS 15

#110342 Followup on output buffering removal

With #110250 output buffering was removed but
some leftovers kept in place: AbstractApplication,
DebugUtility and EidHandler

Author Benjamin Franzke
Created 07/31/26, 09:19
Updated 07/31/26, 09:19
Task
Under Review Stale File Abstraction Layer (FAL) TYPO3 CMS 15

#110336 Remove unserialize in sys_file_processedfile

Author Benni Mack
Assigned to Benni Mack
Created 07/30/26, 16:59
Updated 07/30/26, 17:57
Bug
Under Review Stale File Abstraction Layer (FAL) TYPO3 CMS 12

#101928 f:image(.uri) and other FAL/File ViewHelpers should never raise an Exception for missing files!

For some reason the Core-Team still thinks it’s a “good practice” to break the whole site if there’s just a simple problem about a missing file for an image or file-ViewHelper.

I did’t care about that by overriding that with my custom ViewHelper catching such issues and handling them in a more useful and end-user friendly way. But this isn’t possible anymore as those ViewHelpers are now final class and the logic inside isn’t outsourced into a PHP-Trait that could be re-used by other developers that want to take care of this more senseful.

So please implement:
- possibility to render an optional fallback (placeholder?!) image.
- possibility to disable raising an exception (this should be the default if the site is even without f.e. file/image is useable)
- possibility to send a Signal/Event for FAL/Files missing with data for the file/fal object to give users the ability to handle such behavour.

When I’ve been reading about Fluid ViewHelpers will be declared final in v12 [https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/11.5/Important-95298-FluidViewhelpersWillBeDeclaredFinalInV12.html] I thought the core-team would to this by using best-practices like using an Abstract-Class or Trait implementing the main logic. But now it’s only possible to implement custom handling by doing a full-implementation or 1:1 copy if original core ViewHelpers which leads to none-upgradeable functionalities for core-changes.

Related to:
#101927

Author Gabriel Kaufmann TYPOworx GmbH | NewMedia
Created 09/15/23, 11:35
Updated 07/30/26, 04:47
Bug
Under Review Stale Backend API TYPO3 CMS 12

#101929 ViewHelperInvoker should catch Exceptions allow the Site-Developer to handle or supress exceptions

The ViewHelperInvoker (\TYPO3Fluid\Fluid\Core\ViewHelper\ViewHelperInvoker) should catch Exceptions allow the Site-Developer to handle or supress exceptions. This can be useful to supress exceptions for f.e. missing images, FAL, files (f:image etc.).

To archive that the ViewHelperInvoker should emit a Signal that developers can use to receive such Error-Events and giving them the ability to supress the actual Exception or implement custom rendering to replace the output of ViewHelpers.

So far I’ve extended/wrapped such core-viewhelpers to implement a more user-friendly handling of minor errors (like missing image or download files), replacing them with log-signal, user-friendly error-message, placeholder image and so on. This enshures the rest of the website works even if there is a stupid image missing.

This is not possible anymore due to the breaking change, that most of these ViewHelpers are now declared final class. Site-Developers would have to maintain their 1:1 copy of these core-classes (instead of simply extending the logic). This isn’t useful as this could also lead to core-fixes that won’t apply there anymore.

So I think there must be a better solution to give developers the ability to handle this themselfe — or keep the old Exception if they don’t care about it.

I think at least implementing a signal-event should be no brain-breaker!

Author Gabriel Kaufmann TYPOworx GmbH | NewMedia
Created 09/15/23, 11:57
Updated 07/29/26, 12:30
Feature
New Stale Backend User Interface

#110300 Multi-select content elements in Page module

Some times it’s necessary to use the Page module in backend when you want delete multiple content elements. Currently you have to delete every content element one after another or switch to the list view (which can be confusing when having many elements and/or elements wrapped in containers). Therefore it would be nice (and user friendly) to have the possibility of selecting multiple elements in the page module view as well.

Suggestion (as visualized in the screenshot attached): Add a checkbox for every single content element and a button for bulk delete action (e.g. a sticky button that appears after 1 or more content elements were selected)

Author Christoph Bolda
Created 07/27/26, 14:07
Updated 07/27/26, 14:07
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
Under Review Stale Extbase + l10n TYPO3 CMS 9

#90430 Language handling of bidirectional mm selects is not consitent.

I found a inconsistent behaviour in the new language handling of typo3 9.5. The situation is like this, I have a bidirectional mm relation with selects on both sides, which are excluded in non default languages. I adapted it to the blog example.
So lets say we have posts and tags which can be selected on both sides.

I reproduced this behaviour in blog_example:
https://github.com/undkonsorten/blog_example/commit/4bcdae43cf750c98f6f39fc4864430d202bf2891

Scenario:

I create a blog post (P) with uid 1
I create a tag (T) with uid 11
I create a translation P’ for P with uid 2
I create a translation T’ for T with uid 12

I open P (default language) and add T.

Database looks like this:

uid_local    uid_foreign
1            11
2            11
P <=> T
P' <=> T

I open T (default language) and save it.

Database looks like this:

uid_local    uid_foreign
1            11
1            12
P <=> T
P <=> T'

Save P’ or T’:

uid_local    uid_foreign
1            11
1            12
2            12
2            11
P <=> T
P <=> T'
P' <=> T
P' <=> T'

The problem is that when I save T the tag is no longer shown on that post in Frontend.

The modified extension can be found here:
https://github.com/undkonsorten/blog_example/

Author Eike Starkmann
Created 02/19/20, 12:54
Updated 07/24/26, 15:19

Showing results 726 to 750 of 1561