Showing results 826 to 850 of 1561

Bug
Under Review Orphaned Caching TYPO3 CMS 14

#106593 Deadlock in Typo3DatabaseBackend::set() on concurrent invocations

Description

If Typo3DatabaseBackend::set() is called many times concurrently database deadlock exceptions occur.

A reproduction example is available on GitHub: https://github.com/adamkoppede/reproduce-deadlock-with-fluidtypo3-vhs-7-1

Background

fluidtypo3/vhs 7.1.1 calls Typo3DatabaseBackend::set() four times per request in certain situations: TODO downstream reference

Author Adam Koppe
Created 04/21/25, 20:41
Updated 04/22/26, 11:05
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 14

#109313 "Paste in clipboard content" modal from filelist uses generic action buttons for both copy and move

Steps to reproduce the issue:

1. In filelist, use copy or cut from the kebab menu of a file
2. move to a different folder
3. in the header the button “Paste in clipboard content” appears, click on it

The modal message always have the [Close] and [OK] button. It should be better to use “Cancel” instead of “Close” and a different main action button for the 2 cases.

The logic in /sysext/filelist/Classes/ContextMenu/ItemProviders/FileProvider.php can be applied

Author Riccardo De Contardi
Created 03/22/26, 17:30
Updated 04/22/26, 07:27
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 11

#92945 Copyright notice on login screen has accessibility issues

The small text has several issues for screen readers:

  • two URLs are repeatedly linked in close proximity (nuisance)
  • more than once the link text is “click for details” (hides link purpose)
  • text is in capitals (may result in spelling letter by letter)
  • The word “copyright” is duplicated in text and as symbol (symbols will be read)

And for all users the text is a horrible mess and hard to read.

Author Martin Kutschker
Assigned to Martin Kutschker
Created 11/27/20, 21:55
Updated 04/22/26, 07:16
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 12

#103328 UX: CEs preview-text is linked but not fully clickable

In the BE there is some preview text for each content-element. Unfortunatelly the clickable area is non-continuous, which results in flickering on hover and missed clicks.

This behaviour can be reproduced in Firefox and also in Chrome.

Technical background

This can only be shown in Firefox Dev Tools. Chrome just shows a continous link-area, but also behaves like having a non-continuous link-area.

Suggested fix

Add padding-top and padding-bottom to the a element.

Author Ayke Halder
Created 03/07/24, 18:05
Updated 04/22/26, 06:56
Bug
Under Review Orphaned AdminPanel TYPO3 CMS 12

#104057 Singleton instances are not possible for LogWriter

This leads to the InMemoryLogWriter of the admin panel to be instaciated as new class. Therefor all the logs will not be shown, because they got written in another instance.

The problem lies in the LogManager and GeneralUtiliy:makeInstance

The line $logWriter = GeneralUtility::makeInstance($logWriterClassName, $logWriterOptions); when $logWriterOptions=[]

Then GeneralUtiliy:makeInstance will not get the container:

if (self::$container !== null && $constructorArguments === [] && self::$container->has($className)) {
            return self::$container->get($className);
}
Author Eike Starkmann
Created 06/11/24, 15:04
Updated 04/22/26, 06:56
Bug
Under Review Orphaned DataHandler aka TCEmain TYPO3 CMS 9

#92093 Sorting of records in frontend with sys_language all (-1) and normal

Using a multilanguage setup, we experience problems regarding sorting of normal language records mixed with “all” language records.

The sorting seems to be done in the DataHandler Class.

We patch the DataHandler to get the in our opinion better order.

Can someone please help to get this into the core.

Might be nearby 70154

Author Markus Gerdes
Created 08/25/20, 09:46
Updated 04/22/26, 06:55
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 13

#104566 Closing notification message has movement on close animation

The content of notifaction messages ‘moves’ while the notification is closed.

Moving objects are also recognized by peripheral vision. There is no need to recognize a closing notification.

Author Ayke Halder
Created 08/07/24, 14:55
Updated 04/22/26, 06:54
Bug
Under Review Orphaned DataHandler aka TCEmain TYPO3 CMS 13

#107375 DataHandler->isTableAllowedForThisPage() no longer checks doktype of correct page

This seems to be introduced via https://git.typo3.org/typo3/typo3/-/commit/9490df3 #106382.
The old code fetched the doktype of target page and passed that one down the chain.
The new code uses the doktype of the page record to insert, which seems to be the wrong logic.

https://git.typo3.org/typo3/typo3/-/commit/9490df3#2e113d50d07e048063e4879bbf366c06ea2235ac_7278_7224

Steps to reproduce:
  1. Create a custom page type.
  2. Prevent pages on the new custom page type.
  3. Create a page of custom page type.
  4. Copy the new page.
  5. Paste the copy onto a normal page.

Expected Behaviour:
The page is inserted, page tree is reloaded

Actual Behaviour:
An error is shown: 1: Attempt to insert record "pages:8854" on a page (34) that can't store record type

Normal pages should allow all new page types. But the system will respond with an error that the page is not allowed.

I suggest to keep the old logic to fetch the doktype from target page.

Author Daniel Siepmann
Created 09/03/25, 05:38
Updated 04/22/26, 06:51
Bug
Under Review Orphaned Logging TYPO3 CMS 12

#105514 Append requested URL to formatted log message in ErrorHandler

In the AbstractExceptionHandler, the requested URL is appended within the web context.
This is highly advantageous when an error is thrown, as the provided URL helps locate the error more quickly.
However, if only an ErrorHandler is triggered, no URL is appended.

Author Amir Arends
Created 10/29/24, 14:26
Updated 04/22/26, 06:49
Bug
Under Review Orphaned Localization TYPO3 CMS 9

#92488 Default language does not support fallback language ids

Problematic

I have a multi-site install where the default language can be semantically any of English, French, German or Italian.

Some pages are shared and mounted from a common shared “subsite” (in the context of TYPO3 v9, for the sake of being able to properly create slugs but conceptually, just a bunch of pages in an outside page tree). Those shared pages have arbitrarily their default language in English and are then translated (=overlaid) into French, German and Italian.

In the database we have pages and content with sys_language_uid=0..4 since:

  • sys_language_uid=0 is any semantic default language
  • sys_language_uid=1 is German
  • sys_language_uid=2 is French
  • sys_language_uid=3 is Italian
  • sys_language_uid=4 is English

E.g., when sys_language_uid=0 represents English, then sys_language_uid=4 is not used.

Up to TYPO3 v8 inclusive, the trick to have everything work properly was to never configure a Frontend website to use sys_language_uid=0 but only 1 to 4 and rely on fallback chain to read 0 if the corresponding language is undefined. This way, content from a website in any default language (and translated) can use a common set of shared pages where the default language is semantically English (thus possibly another one).

TYPO3 v9

To do that in TYPO3 v9, the language configuration for a German-first website needs to be this one:

languages:
  -
    title: Deutsch
    enabled: true
    base: /de/
    typo3Language: de
    locale: 'de_CH.utf8,de_CH.UTF-8'
    iso-639-1: de
    websiteTitle: ''
    navigationTitle: Deutsch
    hreflang: de-CH
    direction: ''
    fallbackType: fallback
    fallbacks: '0'
    flag: de
    languageId: '1'
  -
    title: Français
    enabled: true
    base: /fr/
    typo3Language: fr
    locale: 'fr_CH.utf8,fr_CH.UTF-8'
    iso-639-1: fr
    websiteTitle: ''
    navigationTitle: Français
    hreflang: fr-CH
    direction: ''
    fallbackType: fallback
    fallbacks: '0'
    flag: fr
    languageId: '2'
  -
    title: Italiano
    enabled: true
    base: /it/
    typo3Language: it
    locale: 'it_CH.utf8,it_CH.UTF-8'
    iso-639-1: it
    websiteTitle: ''
    navigationTitle: Italiano
    hreflang: it-CH
    direction: ''
    fallbackType: fallback
    fallbacks: '0'
    flag: it
    languageId: '3'
  -
    title: English
    enabled: true
    base: /en/
    typo3Language: default
    locale: 'en_GB.utf8,en_GB.UTF-8'
    iso-639-1: en
    websiteTitle: ''
    navigationTitle: English
    hreflang: en-GB
    direction: ''
    fallbackType: fallback
    fallbacks: '0'
    flag: en-us-gb
    languageId: '4'

but the problem we face is that asking for generating a link for sys_language_uid=0 (in whichever context, for instance an API) leads to an internal catched exception when invoking typolink_URL(). It throws InvalidArgumentException 1522960188 which is “Language 0 does not exist on site xyz.”.

What is expected

In such context, logically speaking the default language (thus the first one in the definition) should be checked for “fallbacks”, something that is normally not expected to happen because TYPO3 wrongly thinks the default language is always 0.

Suggestion

diff --git a/typo3/sysext/core/Classes/Site/Entity/Site.php b/typo3/sysext/core/Classes/Site/Entity/Site.php
index 3d20c20f2a..ea7748b533 100644
--- a/typo3/sysext/core/Classes/Site/Entity/Site.php
+++ b/typo3/sysext/core/Classes/Site/Entity/Site.php
@@ -242,6 +242,11 @@ class Site implements SiteInterface
     {
         if (isset($this->languages[$languageId])) {
             return $this->languages[$languageId];
+        } else {
+            $defaultLanguage = $this->getDefaultLanguage();
+            if (in_array($languageId, $defaultLanguage->getFallbackLanguageIds(), true)) {
+                return $defaultLanguage;
+            }
         }
         throw new \InvalidArgumentException(
             'Language ' . $languageId . ' does not exist on site ' . $this->identifier . '.',
Author Xavier Perseguers
Created 10/06/20, 08:52
Updated 04/22/26, 06:48
Task
Under Review Orphaned TYPO3 CMS 14

#109451 Rate Limit: log warning on failed login attempt

In #93825 a rate limit was introduced for BE logins. Once exceeded, a user gets an error message telling him when he can try again.

However, there are no hints about the failed login attempts which led to exceeding the rate limit.

There are log entries but only for the DEBUG log level since #88230. The rationale behind this back then was that sensitive login data should not show up in logs by default.

However, this was tackled generally in #93925 afterwards thus login data is redacted before being logged.

Altogether the logging of failed login attempts should be reverted to the WARNING log level to have it logged by default. This improves auditing/tracing of login attempts and gives a clear explanation for exceeded rate limits.

Author Mathias Brodala
Assigned to Mathias Brodala
Created 04/01/26, 08:42
Updated 04/22/26, 06:47
Task
Under Review Orphaned TYPO3 CMS 13

#108812 Unneeded instanceof on xxx|null. Use a null check instead.

This is a pre-patch for #108652

Author Simon Schaufelberger
Created 01/30/26, 12:58
Updated 04/22/26, 06:45
Bug
Author Elias Häußler
Assigned to Elias Häußler
Created 03/12/26, 13:56
Updated 04/22/26, 06:43
Bug
Under Review Orphaned Backend JavaScript TYPO3 CMS 13

#106193 JavaScript table wizard in TYPO3 table content element breaks cell values

In the content element “table” the JavaScript table wizard has two issues:

  1. Changes to table_delimiter and table_enclosure are not recognized immediately and taken into account on next save of the content element
  2. Using the delimiter also in a cell value gets the cell value displayed in two cells instead of one after next save

How to reproduce # 1:

  • Create a table content element
  • Default value for table_delimiter is “Pipe” and table_enclosure is “none”
  • Set table_delimiter to Comma and table_enclosure to “Double quotes”
  • Enter foo,bar into a cell
  • Save the content element

Result:

  • foo and bar are displayed in different cells
  • In the database the field bodytext is filled with foo,bar

Expected behaviour:

  • The Wizard shows only one cell with foo,bar
  • In the database the value is stored with "foo,bar"

Next step:

  • Change foo to foo2
  • Save the content element
  • The bodytext DB field is now correctly filled with "foo2","bar"

How to reproduce # 2:

  • Create a table content element
  • Set table_delimiter to Comma and table_enclosure to “Double quotes”
  • Save the element without entering data into any cell!
  • After save, enter foo,bar into one cell and save

Result:

  • foo and bar are displayed in separate cells
  • bodytext field in database is saved with foo,bar

Expected behaviour:

  • The Wizard shows only one cell with foo,bar
  • In the database the value is stored with "foo,bar"

Next step:

  • Change the value of one cell and save
  • Now bodytext is correctly saved with "foo2","bar"

Further observations:

  • The frontend rendering is correct for what is stored in the bodytext database field
  • If you only fill bodytext accordingly, e.g. by making direct changes in the database, the frontend output also functions correctly
  • The data in the database only breaks when you use the wizard and save the content element

I assume that # 2 can be fixed within writeTableSyntaxToTextarea() in Build/Sources/TypeScript/backend/form-engine/element/table-wizard-element.ts
For # 1 I have no idea so far.

Unfortunately I’m not good in JavaScript to provide a patch.

Author Peter Kraume
Created 02/18/25, 09:10
Updated 04/22/26, 06:42
Task
Author Simon Schaufelberger
Assigned to Simon Schaufelberger
Created 01/16/26, 09:57
Updated 04/22/26, 06:41
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 13

#108584 Module "Layout": Waste no space for thumbnail images in content elements

Current implementation

Proposal: Images still are 64px wide.

Author Ayke Halder
Created 12/30/25, 16:44
Updated 04/22/26, 06:38
Bug
Under Review Orphaned Mailer API TYPO3 CMS 13

#99350 Mail for reset password has broken logo if triggered by CLI

The cli command backend:resetpassword expects two parameters the backend login URL and the email address.
The backend login URL is then used as a prefix to create the RESET PASSWORD link.
However the TYPO3 Logo which is taken from backend extension configuration is not prefixed with that URL, but rather the cli path, thus with a backend logo extension config of
@EXT:mysitepackage/Resources/Public/Images/backend/provider.png@
this results in a HTML mail image url of http://vendor/bin/typo3conf/ext/mysitepackage/Resources/Public/Images/backend/provider.png" and thus a broken logo

Author J. Peter M. Schuler
Created 12/12/22, 23:40
Updated 04/22/26, 06:33
Bug
Under Review Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 10

#99217 Pagetypes not working with trailing Slashes if default PageTypeSuffix is set

I use Pagetypes for Ajax Calls then this example Url work:

dasisteine/url?mitparement=1&type=93939

and that will not work

dasisteine/url/?mitparement=1&type=93939

i debugged thru the code and found that this
https://github.com/TYPO3/typo3/blob/1b0fea17a5591de55e9c49ca3dd563d8cb95c245/typo3/sysext/core/Classes/Routing/Enhancer/PageTypeDecorator.php#L[…]18
will set the Type to 0 because in my site config i have set this:

PageTypeSuffix:
  type: PageType
  default: /
  suffix: /
  index: ''
  map:
    /: 0
But i think that ist wrong. If i have an Parameter set with type i want to use this and not the default…
Author Oliver Krammer
Created 11/29/22, 09:48
Updated 04/22/26, 06:33
Bug
Under Review Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 12

#107283 PageTypeDecorator should add default slash suffix for unconfigured type

This configuration

PageTypeSuffix:
  type: PageType
  default: '/'
  index: ''
  map:
    'sitemap.xml': 1533906435

should result in URLs like this:

Current buggy result – trailing slash missing:
Author Ayke Halder
Created 08/14/25, 10:37
Updated 04/22/26, 06:32
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 13

#107394 Search modal: Label background cuts off outline of focused item

Search modal: Label background cuts off outline of focused item

Author Ayke Halder
Created 09/04/25, 14:28
Updated 04/22/26, 06:32
Bug
Author Oliver Bartsch
Assigned to Oliver Bartsch
Created 01/20/25, 10:19
Updated 04/22/26, 06:30
Bug
Under Review Orphaned Form Framework TYPO3 CMS 10

#93722 form variants error when using . inside a key

I created a form variant and noticed that when you use a . inside a key and save the form in the backend again the form variant options get “corrupted”

example:

1. Creating a new variant option in the yaml file.

variants:
-
identifier: multicheckbox-1
condition: ‘formValues[“singleselect-1”] && formValues[“radiobutton-1”] == “TEST”‘
properties:
options:
‘test (test2) test3. test4’: TEST

2. make (any) changes in the form editor in the BE and save the form again.

3. the variant changes to

options:
‘test (test2) test3’:
‘ test4’: TEST

I only noticed that because I copied and pasted the values. The original key was longer and was also split before the closing bracket but I couldn’t reproduce this in this example.

Author David Menzel
Created 03/12/21, 13:39
Updated 04/22/26, 06:26
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 13

#102369 Hide "Add content"-button for localized columns on disabled mod.web_layout.localization.enableCopy

tl;dr

The “Add content”-button for localized columns should be hidden if mod.web_layout.localization.enableCopy is disabled.

Steps to reproduce

1. Page TSconfig:

mod.web_layout {
  localization {
    // Only "translate" is enabled --> translation-mode "connected"
    enableCopy = 0
    enableTranslate = 1
  }
}

2. Module “Web: Page”: Editor can add new content

  • No translation-mode visible.
  • Editor should not be able to add new content.

3. Add new CE:

  • This sets translation-mode to “Free Mode” (see blue badge)
  • And there are many “Add content”-buttons visible…

4. Click on “Translate”:

  • “Can’t translate” caused by page is in “Free Mode” but only “Connected Mode” is allowed.

What should happen instead

1. Page TSconfig:

mod.web_layout {
  localization {
    // Only "translate" is enabled --> translation-mode "connected"
    enableCopy = 0
    enableTranslate = 1
  }
}

2. Module “Web: Page”: Editor can’t add content:

  • No “Add content”-button visible
  • Translation mode “Connected Mode” already visible (see blue badge)

3. Click on “Translate” (already working):

  • Wizards jumps directly to step 3 of 4 (already working).

4. Editor sees records to translate (already working):

  • Still no “Add content”-buttons visible (already working).
  • Translation mode “Connected Mode” visible (see blue badge; already working).
Author Ayke Halder
Created 11/13/23, 19:31
Updated 04/22/26, 06:25
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 12

#105528 Clear-button not visible for input-field with 'bad input' error

The clear-button is not visible if an input-field has ‘bad input’ error.

Should look like:

——

Also see: https://developer.mozilla.org/en-US/docs/Web/API/ValidityState/badInput

Author Ayke Halder
Created 10/31/24, 19:07
Updated 04/22/26, 06:25
Bug
New Orphaned Localization TYPO3 CMS 8

#82558 The relation of MM table records are saved wrong for element translations in TYPO3 8.7.

I appended a patch. I think it was just a small logic error. Hopefully I’m not totally wrong. :)

How to reproduce?

1. Create a TCA with an inline column. Both of them needs to use multilanguage settings.
2. The inline column needs to use the MM table configuration
3. Create some test records and localize them.
4. Go to the parent TCA in the default language.

Result:
You will see, that the localized records are shown within the default language with the default record under it in the inline element list. If you switch to the translation of the parent TCA, then you will see, that the records are missing, or shown as “not translated”.

Author Fabian Galinski
Created 09/25/17, 15:49
Updated 04/22/26, 05:26

Showing results 826 to 850 of 1561