Showing results 226 to 250 of 1561

Task
New Quiet Extbase TYPO3 CMS 7

#70020 @transient properties should be ignored when checking if object is dirty

I am currently working on a REST Api for TYPO3-7 and i recognized, that i allways get TRUE when checking AbstractEntity::_isDirty()

The problem is, that @transient properties are checked also.

But by using the ObjectAccess::getProperties and stuff a @transient property will be loaded via get-method, that way an objects internal logic may set the transient property as first-level-cache. I guess i am not the only one using that possibility.

Properties starting with an underscore (_languageUid) are ignored, @transient properties should also be ignored.

That could reduce database load a lot in certain contexts.

Author Philipp Wrann
Created 09/22/15, 15:54
Updated 10/18/26, 18:09
Bug
New Quiet FormEngine aka TCEforms TYPO3 CMS 8

#94158 Select type selectSingle fields (and likely other renderTypes too) do not support eval=null

Example TCA:

'field' => [
    'label' => 'LLL:EXT:myext/Resources/Private/Language/locallang_db.xlf:table.field',
    'config' => [
        'type' => 'select',
        'renderType' => 'selectSingle',
        'foreign_table' => 'tx_foo',
        'eval' => 'null',
    ],
],

Expectation:

Field should render with the “Set value” checkbox identical to how eval=null works on for example simple input fields.

Current behavior:

Option eval=null is ignored and does not render a “Set value” checkbox above the field.

References:

Similarly reported for RTE fields on https://forge.typo3.org/issues/88480

Author Claus Due
Created 05/19/21, 12:34
Updated 10/18/26, 16:32
Bug
Needs Feedback Quiet Workspaces TYPO3 CMS 12

#107915 Workspace switching bridged to all sessions of the current user

The workspace is stored in the “backend user data” – and not in the users “session data”.

Thereby workspace switches are completely bridged between all sessions of the same user!
Without any visual hint, that the workspace changed.

User logs in with two different Webbrowsers – e.g. Chrome and Firefox:

  1. User switches to Workspace-Foo in Chrome
  2. User switches to Workspace-LIVE in Firefox
  3. User creates new content element in Chrome – showing Workspace-Foo – but stores (unknown to the user) in Workspace-LIVE

User-A and User-B share the same account: User-A logs in on PC-A and User-B logs in on PC-B

  1. User-A on PC-A switches to Workspace-Foo
  2. User-B on PC-B switches to Workspace-LIVE
  3. User-A on PC-A creates new content element – showing Workspace-Foo – but stores (unknown to User-A) in Workspace-LIVE
Author Ayke Halder
Created 10/29/25, 17:11
Updated 10/18/26, 13:08
Bug
Under Review Quiet DataHandler aka TCEmain TYPO3 CMS 13

#106655 pasteDataMap overridden for each command in DataHandler::process_cmdmap

The `$pasteDataMap` is initialized as array before iterating the whole `$this->cmdmap`. However inside the third nested `foreach`, that iterates over the actual commands array, the `$pasteDataMap` is initialized once more.

This leads to all data set during processing of previous commands, to be lost. Therefore only the data from the last command is available after the whole command map has been processed.

I don’t know, if this is reproducable with a standard TYPO3 installation, because I’m not sure, if there actually is a way to trigger multiple move or copy commands, with additional update data, that would trigger this bug. I found it, with an upgrade wizard, that would use the data handler to save the changes, made to the records. In my case, I was moving multiple content elements into a container element, which get the container parent and colPos data to be updated after the move.

The extra line has been introduced with https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773.

Author Thorben Nissen
Created 05/06/25, 09:42
Updated 10/18/26, 12:06
Task
Under Review Quiet TYPO3 CMS 15

#111122 Prepare upload validator options once per validation

Resolve allowed file extensions, file size bounds and byte-size labels once per validation call rather than once per uploaded file. Preserve storage defaults, custom error messages, per-file error indexes and safe reuse of validator instances.

Author Wouter Wolters
Assigned to Wouter Wolters
Created 10/17/26, 16:51
Updated 10/18/26, 11:13
Bug
Under Review Quiet Extbase + l10n TYPO3 CMS 15

#111128 Extbase does not write the relation table for an MM field mapped to a single object

A TCA field with MM and maxitems => 1 (for example type=select, renderType=selectSingle, foreign_table, MM) mapped to a single domain object property is persisted differently by Extbase than by DataHandler.

DataHandler stores the relation in the MM table and writes the number of relations into the field. Extbase writes the uid of the related object into the field and never touches the MM table:

Action DataHandler Extbase
set tag 2 on an empty field MM row (1, 2), field = 1 field = 2, no MM row
set the property to null MM row removed, field = 0 field = 0, MM row stays
replace tag 1 by tag 2 MM row (1, 2) replaces (1, 1), field = 1 field = 2, MM row (1, 1) stays, no row for tag 2

Reading through the MM table (backend, record API, Extbase itself after reload) therefore returns the old relation or none at all.

Reproduce: persist a model with such a property through update() and persistAll() and compare the field and the MM table with the result of the same change through DataHandler.

Author Alexander Schnitzler
Assigned to Alexander Schnitzler
Created 10/18/26, 06:18
Updated 10/18/26, 07:03
Bug
New Quiet DataHandler aka TCEmain TYPO3 CMS 14

#111104 Default schema for uuid does not allow an empty string for required=false

With #103141 the default db schema has been changes from Types::STRING to Types::GUID.
An empty string therefore is not valid anymore.
For

         'uuid_notrequired' => [
            'config' => [
                'type' => 'uuid',
                'required' => false,
            ],
        ],

DataHandler tries to write an empty string. This leads to a database error.
The default schema should only use Types::GUID, if required = false.

Author Daniel Windloff
Assigned to Daniel Windloff
Created 10/17/26, 05:28
Updated 10/17/26, 05:28
Task
Author Elias Häußler
Assigned to Elias Häußler
Created 11/12/25, 08:53
Updated 10/16/26, 13:25
Bug
Under Review Quiet Dashboard TYPO3 CMS 14

#108573 DashBoard widget error: has no argument named "$configuration"

Hello,

with TYPO3 14 we have a new Interface: “WidgetRendererInterface” which expects method “renderWidget(WidgetContext $context)”. Thanks to WidgetContext we now have direct access to WidgetConfiguration object. So I have remove WidgetConfiguration from my Widget constructor which results in:

In ResolveNamedArgumentsPass.php line 87: Invalid service "dashboard.widget.innodb.bufferpool": method StefanFroemken\MySqlWidget\Widgets\InnoDbBufferPool::__construct()" has no argument named "$configuration". Check your service definition.

I have compared $this->configuration with $context->configuration. Both are exactly the same objects.

I would recommend to remove the constructor implementation from DashboardWidgetPass.

Stefan

Author Stefan Froemken
Created 12/26/25, 14:18
Updated 10/15/26, 22:10
Epic
New Quiet Backend User Interface

#83669 Improve file list / file browser

Ideas

Layout

Provide different layouts like

  • list
  • gallery view
  • thumbnails

Filters

Author Georg Ringer
Created 01/24/18, 10:45
Updated 10/12/26, 20:35
Epic
Author Oliver Hader
Created 05/26/25, 19:24
Updated 10/12/26, 19:30
Bug
Under Review Quiet Localization TYPO3 CMS 13

#110008 Regression in language fallback handling (strict)

The change in https://review.typo3.org/c/Packages/TYPO3.CMS/+/88828 introduced a regression (or intentional change?) how elements behave in strict mode and a given fallback.

ive got the following setup

  - languageId: 0   # German (default)
    fallbackType: strict
    fallbacks: ''

  - languageId: 1   # English
    fallbackType: strict
    fallbacks: ''

  - languageId: 2   # English UK
    fallbackType: strict
    fallbacks: '1'  # fallback to English

On an L=2 page, an editor may want to hide a translated element while the corresponding element in L=1 remains visible. With this patch, that is no longer possible because the system falls back to the L=1 record and displays the element.

Reverting the change restores the behavior from v11 and v12.

Author Johannes Seipelt
Assigned to Maike Kiebele
Created 06/05/26, 11:55
Updated 10/12/26, 19:02
Task
New Quiet Logging TYPO3 CMS 13

#110719 LinkFactory / Logging way too noisy

The LinkFactory logs the whole exception when something can not be linked. While this might be useful for debugging in some situations, this tends to make logs too noisy in production because the exception is triggered by bad user data. So in every single request you will spam your log with the whole stack trace when the exception gets serialized.

In my case the content editors forgot to translate lots of pages (new site in development) and in every request my container log is spammed with useless stack traces (the whole middleware-chain included and so on).

Common situations, that will trigger the log pollution:

  • page is not translated but it should be
  • page is hidden but was linked somewhere
  • cross-site-link with non-matching language configurations

I suggest to only log information, that is required to investigate further, like what could not be linked.

When i start my stack locally (debug settings) and the runtime logs are displayed, 1 single request will produce 0.5MB of entirely useless stack traces in the logs, this is crazy

Author Philipp Wrann
Created 09/16/26, 09:48
Updated 10/09/26, 08:13
Bug
Under Review Quiet Fluid TYPO3 CMS 13

#108236 Make f:form.select viewhelper work with PHP enum

Using an enum for the select ViewHelper does not work out of the box:

<f:form.select
        id="gender"
        options="{genderOptions}"
        name="user.gender"
        prependOptionLabel="- Bitte auswählen -"
        prependOptionValue=""
/>

if variable genderOptions contains something like GenderEnum::cases(), GenerEnum beeing a backed enum, which has a clear identifying value.

(1/1) #1247826696 TYPO3Fluid\Fluid\Core\ViewHelper\Exception
No identifying value for object of class "Wco\WcoBeratungCore\Domain\Model\Enum\GenderEnum" found.

in /var/www/html/vendor/typo3/cms-fluid/Classes/ViewHelpers/Form/SelectViewHelper.php line 189

You have to define both the optionValueField and optionLabelField parameters eveen though a good default would be possible:

<f:form.select
        id="gender"
        options="{genderOptions}"
        name="user.gender"
        prependOptionLabel="- Bitte auswählen -"
        prependOptionValue=""
        optionValueField="value"
        optionLabelField="label"
/>

It would be even greater if we could just pass the name of the Enum, for example:

<f:form.select
        id="gender"
        options="\MyVendor\MyExtension\Enums\GenderEnum"
        name="user.gender"
        prependOptionLabel="- Bitte auswählen -"
        prependOptionValue=""
/>
Author Lina Wolf
Assigned to Christian Spoo
Created 11/21/25, 05:58
Updated 10/07/26, 20:22
Bug
New Quiet Backend API TYPO3 CMS 14

#110948 Record history: rolling back a workspace publish in live does nothing, although the pre-publish record is stored

After a workspace is published, the live record history lists the published records with the action “published”, including a diff of the changed fields. Rolling these entries back (“Rollback all changes shown”, per record or per field) does not restore anything. Editors cannot undo an accidental or wrong publish, although the data needed for it is in sys_history.

Steps to reproduce

1. Create a page “Live title” in live.
2. Create a workspace, switch to it and change the page title to “WS title”. Save.
3. Publish the change
4. Switch to live. Page -> History: an entry “published” shows the diff “Live title” → “WS title”.
5. Click “Rollback all changes to this state” on that entry, then “Rollback all changes shown” and confirm.

Expected result

The page title is “Live title” again, as it is for any other modification. A content element deleted in the workspace is restored.

Actual result

The title stays “WS title”. No error is shown, and no new history entry is written.

Author Amir Arends
Created 10/07/26, 11:23
Updated 10/07/26, 11:23
Bug
Under Review Quiet TYPO3 CMS 13

#110173 Spooled sending of emails fails with PHP TypeError for HttpTransports

When 'transport_spool_type' => 'memory', or 'transport_spool_type' => 'file', is set (see https://docs.typo3.org/permalink/t3coreapi:confval-globals-typo3-conf-vars-mail-transport-spool-type) and mail is sent via a 3rd party transport via dsn (see https://docs.typo3.org/permalink/t3coreapi:confval-globals-typo3-conf-vars-mail-dsn)
a PHP error occurs on sending the mail from spool:


(1/1) TypeError

Symfony\Component\Mime\MessageConverter::toEmail(): Argument #1 ($message) must be of type Symfony\Component\Mime\Message, Symfony\Component\Mime\RawMessage given, called in vendor/symfony/mailer/Transport/AbstractApiTransport.php on line 33
in vendor/symfony/mime/MessageConverter.php line 29

{
    /**
     * @throws RuntimeException when unable to convert the message to an email
     */
    public static function toEmail(Message $message): Email
    {
        if ($message instanceof Email) {
            return $message;
        }

at Symfony\Component\Mime\MessageConverter::toEmail()
in vendor/symfony/mailer/Transport/AbstractApiTransport.php line 33

    protected function doSendHttp(SentMessage $message): ResponseInterface
    {
        try {
            $email = MessageConverter::toEmail($message->getOriginalMessage());
        } catch (\Exception $e) {
            throw new RuntimeException(\sprintf('Unable to send message with the "%s" transport: ', __CLASS__).$e->getMessage(), 0, $e);
        }

at Symfony\Component\Mailer\Transport\AbstractApiTransport->doSendHttp()
in vendor/symfony/mailer/Transport/AbstractHttpTransport.php line 71

    protected function doSend(SentMessage $message): void
    {
        try {
            $response = $this->doSendHttp($message);
            $message->appendDebug($response->getInfo('debug') ?? '');
        } catch (HttpTransportException $e) {
            $e->appendDebug($e->getResponse()->getInfo('debug') ?? '');

at Symfony\Component\Mailer\Transport\AbstractHttpTransport->doSend()
in vendor/symfony/mailer/Transport/AbstractTransport.php line 90

            $sentMessage = new SentMessage($message, $envelope);

            try {
                $this->doSend($sentMessage);
            } catch (\Throwable $error) {
                $this->dispatcher->dispatch(new FailedMessageEvent($message, $error));
                $this->checkThrottling();

at Symfony\Component\Mailer\Transport\AbstractTransport->send()
in vendor/typo3/cms-core/Classes/Mail/FileSpool.php line 172

                }
                if ($message instanceof SentMessage) {
                    // This may throw an exception if something goes wrong.
                    // That is expected and will cause the `.sending` file to remain within the spooler.
                    $transport->send($message->getMessage(), $message->getEnvelope());
                    $count++;
                    unlink($file . '.sending');
                } else {
                    $this->logger?->error(

at TYPO3\CMS\Core\Mail\FileSpool->flushQueue()
in vendor/typo3/cms-core/Classes/Command/SendEmailCommand.php line 72

                } else {
                    $transport->recover();
                }
            }
            $sent = $transport->flushQueue($mailer->getRealTransport());
            $io->comment($sent . ' emails sent');
            return Command::SUCCESS;
        }
        $io->error('The Mailer Transport is not set to "spool".');

This does only happen for the combination of a HTTP transport and activated spooling. Spooled SMTP works, HTTP without spooling works.

MessageConverter::toEmail() expects a Symfony\Component\Mime\Message, but receives a Symfony\Component\Mime\RawMessage from both spoolers (file/memory) in $transport->send($message->getMessage(), $message->getEnvelope());, as SentMessage::getMessage() returns the RawMessage: https://github.com/symfony/mailer/blob/8.2/SentMessage.php#L53

Both spoolers must use $message->getOriginalMessage() instead.

Author Stephan Großberndt
Assigned to Stephan Großberndt
Created 07/08/26, 13:21
Updated 10/07/26, 07:32
Bug
Under Review Quiet Workspaces TYPO3 CMS 12

#105578 Lost MM relations in workspaces

Description

During the publishing process of related records the relations get lost.

Relations between two or more entities (e.g. products and references) are lost as soon as the products and the related references have an editing status in the editorial (non-live) workspace and are subsequently published.

See my TCA attached.

How to reproduce?

Initial situation

Products tx_solutions_domain_model_product
*References* tx_solutions_domain_model_reference
*MM Table* tx_solutions_domain_model_product_reference_mm

Products and references are linked via an MM table.
All data is in the live workspace

Products tx_solutions_domain_model_product
_.uid _.t3ver_oid _.t3ver_wsid _.t3ver_state
1 0 0 0
References tx_solutions_domain_model_reference.
_.uid _.t3ver_oid _.t3ver_wsid _.t3ver_state
1 0 0 0
2 0 0 0
Relation tx_solutions_domain_model_product_reference_mm
_.uid_local (product uid) _.uid_foreign (reference uid)
1 1
1 2

Editing reference

A reference (uid 1) is edited in the Editorial Workspace.
A copy with a new uid 3 of the data record is automatically created.
tx_solutions_domain_model_reference.t3ver_oid = 1
tx_solutions_domain_model_reference.t3ver_wsid = 1
tx_solutions_domain_model_reference.t3ver_state = 1

Products tx_solutions_domain_model_product
_.uid _.t3ver_oid _.t3ver_wsid _.t3ver_state
1 0 0 0
References tx_solutions_domain_model_reference.
_.uid _.t3ver_oid _.t3ver_wsid _.t3ver_state
1 0 0 0
2 0 0 0
3 1 1 1
Link tx_solutions_domain_model_product_reference_mm
_.uid_local (product uid) _.uid_foreign (reference uid)
1 1
1 2

Editing product

A product (uid 1) is edited in the Editorial Workspace.
A copy with a new uid 2 of the data record is automatically created.
tx_solutions_domain_model_product.t3ver_oid = 1
tx_solutions_domain_model_product.t3ver_wsid = 1
tx_solutions_domain_model_product.t3ver_state = 1

Products tx_solutions_domain_model_product
_.uid _.t3ver_oid _.t3ver_wsid _.t3ver_state
1 0 0 0
2 1 1 1
References tx_solutions_domain_model_reference.
_.uid _.t3ver_oid _.t3ver_wsid _.t3ver_state
1 0 0 0
2 0 0 0
3 1 1 1
Relation tx_solutions_domain_model_product_reference_mm
_.uid_local (product uid) _.uid_foreign (reference uid)
1 1
1 2
2 3

Publication of the product

The changes to the product are published.
The changes to the data record are transferred from ‘uid 2’ to ‘uid 1’.
In the relation table, the additional entry (uid_local 5) is removed and the original entry uid_local 1 is updated with the uid 4 of the edited reference.
However, the reference uid 3 is not available in the live workspace.

Products tx_solutions_domain_model_product
_.uid _.t3ver_oid _.t3ver_wsid _.t3ver_state
1 0 0 0
2 1 1 1
References tx_solutions_domain_model_reference.
_.uid _.t3ver_oid _.t3ver_wsid _.t3ver_state
1 0 0 0
2 0 0 0
3 1 1 1
Relation tx_solutions_domain_model_product_reference_mm
_.uid_local (product uid) _.uid_foreign (reference uid)
1 3
1 2
1 3

Publication of the reference

The changes to the reference are published.
The changes to the data record are transferred from uid 3 to uid 1.
There is no change in the relation table.
However, the reference uid 3 is not available in the live workspace.

Products tx_solutions_domain_model_product
_.uid _.t3ver_oid _.t3ver_wsid _.t3ver_state
1 0 0 0
References tx_solutions_domain_model_reference.
_.uid _.t3ver_oid _.t3ver_wsid _.t3ver_state
1 0 0 0
2 0 0 0
3 1 1 1
Relation tx_solutions_domain_model_product_reference_mm
_.uid_local (product uid) _.uid_foreign (reference uid)
1 3
1 2

I would have expected the entry in the relation table to be updated when publishing the reference.

BTW: If a related record is edited in a non-live workspace, the stored relation is no more visible in the record view (backend). An editor has no information if the relation is really lost or not shown because of the workspace overlay.
May be it is an separate issue.

Please let me know if you need any further information.

Author Ruben Zielke
Created 11/12/24, 09:14
Updated 10/03/26, 05:42
Bug
Needs Feedback Quiet TYPO3 CMS 14

#109825 TYPO3 14.3.1 update BREAKING - ERROR: [TYPO3_PATH_APP]/packages/sysext/*/" directory does not exist.

Classic installation (symlinks)
Update from 14.3.0 to 14.3.1 not possible, after changing the symlinks the error appears:

The "D:/typo3-test-version/typo3-14.localhost/packages/sysext/*/" directory does not exist.

Completely new installation, new directory fresh new symlinks the same error appears instantly.
Clear / delete cache manually – no change.
Server restart – no change.
Set the symlinks back to 14.3.0 – clear cache – works again.

PHP 8.5
env TYPO3_CONTEXT=Development/Server
env TYPO3_PATH_APP=D:/typo3-test-version/typo3-14.localhost
env TYPO3_PATH_ROOT=D:/typo3-test-version/typo3-14.localhost/public

Perhaps related to:

https://github.com/typo3/typo3/commit/770c5383930
https://forge.typo3.org/issues/109685#change-568598
https://forge.typo3.org/issues/109686#change-568607

Author Christian Hackl
Created 05/12/26, 14:17
Updated 10/05/26, 14:19
Feature
New Quiet

#102651 Rendering of links in plaintext mails

In plaintext mails of the mail finisher links are gone, only the linktext is visible (because of f:format.stripTags viewhelper). It would be great if the link is added in brackets after the linktext (like in plaintext rendering of directmail).

Author Bernhard Eckl
Created 12/11/23, 13:50
Updated 10/05/26, 07:15
Bug
Under Review Quiet TYPO3 CMS 13

#110908 Backend re-login modal appears unreliably or far too late

Problem

After the backend session expires, the re-login modal sometimes
appears and sometimes does not. In the second case the backend still
looks fine, but every AJAX action (page tree, context menu, drag and
drop, inline records, …) silently does nothing until the user
reloads the page.

Two causes:

  1. The session check runs on a fixed interval of sessionTimeout - 60
    seconds, counted from the moment the backend was loaded (since #76364,
    2016). The session itself expires sessionTimeout seconds after the
    *last request*. So the first check only catches the “about to expire“
    window if the user did nothing in the first 60 seconds after login.
    Otherwise the session expires unnoticed, and the next check comes
    another ~8 hours later (with the default timeout).
  2. When the session is gone, the BackendUserAuthenticator middleware
    answers AJAX routes with a bare 401. AjaxRequest rejects the promise
    and nothing in the backend reacts to it, so the user gets no hint.

Steps to reproduce

  1. Set $GLOBALS['TYPO3_CONF_VARS']['BE']['sessionTimeout'] = 300.
  2. Log in to the backend and click around for two minutes.
  3. Wait five minutes without touching the backend.
  4. Right-click a page in the page tree: the context menu does not open, no modal is shown, no error is visible.

Expected

The “session about to expire” modal appears shortly before the session
expires, regardless of when the backend was loaded. If the session is
already gone, the first failed request opens the login form.

Fix

  • /ajax/login/timedout additionally returns expires_in (seconds
    until the session expires). The client schedules the next check from
    that value instead of polling on a fixed interval.
  • AjaxRequest dispatches typo3:ajax-request:unauthorized on the
    top frame for a 401 response. The login refresh module listens and
    shows the login form at once.
Author Wolfgang Klinger
Assigned to Wolfgang Klinger
Created 10/04/26, 16:01
Updated 10/04/26, 16:26
Bug
Accepted Quiet Site Handling, Site Sets & Routing TYPO3 CMS 9

#86835 Static route sitemap.xml is still not working on single-page tree

The bug #86615 already exists after an update to TYPO3 9.5.1.

I have a multi-language, single-page tree site configuration. I added a sitemap.xml into the config.yaml via the new Site Management menu.

rootPageId: 3
base: ‘https://www.example.net/‘
baseVariants:
-
base: ‘http://example.ddev.local:8080/‘
condition: ‘applicationContext "Development"'
-
base: 'https://staging.example.net/'
condition: 'applicationContext “Production/Staging”‘
-
base: ‘http://testing.example.net/‘
condition: ‘applicationContext == “Testing”‘
languages:
-
title: English
enabled: true
languageId: ’0’
base: /en/
typo3Language: default
locale: en_US.utf8
iso-639-1: en
navigationTitle: English
hreflang: en
flag: us
-
title: Deutsch
enabled: true
languageId: ’1’
base: /de/
typo3Language: de
locale: de_DE.utf-8
iso-639-1: de
navigationTitle: Deutsch
hreflang: de
fallbackType: strict
flag: de
errorHandling:
-
errorCode: ’404’
errorHandler: Page
errorContentSource: ‘t3://page?uid=96’
routes:
-
route: sitemap.xml
type: uri
source: ‘t3://page?uid=3&type=1533906435’

Using /sitemap.xml redirects me to /en/.

Calling /?type=1533906435 redirects me also to /en/. But using /en/?type=1533906435 shows me the sitemap index. Calling the URL from the sitemap xml:

http://example.ddev.local:8080/en/?sitemap=pages&cHash=0fe835841492c3b52e6090c6a7f6f310

shows me the content from /en and no sitemap.

Addition: I encounter this problem on a local ddev environment with the default .htaccess delivered with the core.

Author Chris Müller
Created 11/02/18, 13:24
Updated 10/02/26, 12:32
Bug
Under Review Fresh RTE (rtehtmlarea + ckeditor) TYPO3 CMS 11

#102053 ckeditor - fixAttrib.class.default of A-link not applied when link is inside a list element

Hi,

this is a follow up to this old closed issue : #92756

When I set this in YAML, the class is not applied to the tag inside an

  • one :
  • processing:
      HTMLparser_db:
        tags:
          a:
            fixAttrib:
              class:
                default: external-link

    I’ve simply fixed this by adding “ul” to the switch/case test of block elements in TYPO3\CMS\Core\Html\RteHtmlParser::TS_transform_db

    I don’t know if it’s the right way, please find the attached patch to review.

    Author RVVN no-lastname-given
    Created 09/27/23, 18:40
    Updated 11/13/26, 20:33
    Bug
    Under Review Fresh TYPO3 CMS 10

    #98185 IRRE translations created by language syncronisation are not hidden by default, nor can it be configured at all

    Scenario:

    • TYPO3 with 2 languages (EN, DE)
    • create a page with a content element (e.g. Slideshow) that holds inline records “slides” (separate slide table) configured with allowLanguageSynchronization=true
    • translate the page and thus the content element (connected mode)

    Problem:

    Adding a new IRRE slide in the default-language (EN) content element does translate it to the translated content element (DE) as well .. as expected.

    tt_content (EN)
      - slide A (EN)
      - slide B (EN)  --> new
    
    tt_content (DE)
      - slide A (DE)
      - slide B (DE)  --> auto created by language syncronisation, not hidden

    However, these translations are always visible (hidden = false) despite any hideAtCopy setting. Thus, any new IRRE relation in the default language content-element will always be localized to all connected translations and be visible there from the start. This is not consistent with the regular translation behaviour where it can be configured and is hidden by default

    I found that is due to the fact that these translations are created by the DataHandling\Localization\DataMapProcessor and not by the DataHandlers localize command.

    Expected Behaviour:
    • newly created translations should be hidden as set by TCA/TCEMAIN
    Author Martin Schulz
    Created 08/22/22, 10:13
    Updated 11/13/26, 19:47
    Bug
    Under Review Fresh Themes TYPO3 CMS 14

    #109670 Camino Theme: lib.contentElement reset caused by fluid_styled_content dependency in Site Sets

    Hello,

    The extension theme_camino implements a custom `lib.contentElement` TypoScript object from scratch, intentionally omitting a dependency on the core extension `fluid_styled_content` (FSC).

    The Conflict

    The Camino architecture relies on a dynamic `templateName` resolution based on the `CType` field:

    lib.contentElement = FLUIDTEMPLATE
    lib.contentElement {
      templateName >
      templateName.ifEmpty.cObject = TEXT
      templateName.ifEmpty.cObject {
        field = CType
        required = 1
        case = uppercamelcase
      }
    }

    When a third-party extension (e.g., `mpc_vidply`) is installed that defines `typo3/fluid-styled-content` as a dependency in its `config.yaml`, the Site Set logic loads FSC after the Camino Site Set. Since FSC explicitly clears the object path via `lib.contentElement >`, the entire Camino rendering logic is purged.

    Observed Impact

    The system fails with an `InvalidTemplateResourceException`. This occurs because FSC replaces Camino’s dynamic `templateName` logic with a hardcoded `templateName = Default`.

    Consequently, the Fluid engine searches for a `Default.html` template for every Camino-based content element within the FSC fallback paths. As these templates do not exist for Camino’s custom CTypes, the frontend rendering breaks instantly.

    This behavior demonstrates a fundamental interoperability issue between custom theme engines and extensions enforcing a fluid_styled_content dependency via Site Sets.

    Author Stefan Froemken
    Created 04/21/26, 12:27
    Updated 11/14/26, 12:46
    Task
    Under Review Fresh Extension Manager TYPO3 CMS 14

    #110301 Remove DB table for Extension Manager as cache

    Author Benni Mack
    Assigned to Benni Mack
    Created 07/27/26, 14:43
    Updated 11/13/26, 15:00

    Showing results 226 to 250 of 1561