Showing results 26 to 50 of 1561

Feature
Under Review Orphaned

#107035 Introduce System Settings API

Provide a unified System settings API similar to site settings for * “System-wide” settings / global settings (Install tool via DefaultConfiguration.yaml), not extendible * Extension Configuration API (“cryptic syntax”)

The API should replace the internal DefaultDescription.yaml
and extension ext_conf_template APIs.

Also system settings should be definable by Setting objects
via PHP attributes, allowing to implicitly define settings
and inject them in consuming code.

Author Benjamin Franzke
Assigned to Benjamin Franzke
Created 07/04/25, 11:41
Updated 09/22/25, 09:19
Bug
New Orphaned Extbase TYPO3 CMS 10

#94899 Exbase: Expression #1 of ORDER BY clause is not in SELECT list

TYPO3 10.4.19
MySQL 5.7.35

When I do an individual Query in my Repository with an order_by to a related table field, an error like:

Expression #1 of ORDER BY clause is not in SELECT list, references column 'typo3.tx_lux_domain_model_pagevisit.tstamp' which is not in SELECT list; this is incompatible with DISTINCT

came up

Example function in a Repository:

    public function findSomething(): QueryResultInterface
    {
        $query = $this->createQuery();
        $query->setOrderings(['relatedTable.tstamp' => QueryInterface::ORDER_DESCENDING]);
        return $query->execute();
    }

When I do a “select SQL_MODE;” – this is the definition:

ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
Author Alex Kellner
Created 08/16/21, 11:00
Updated 09/18/25, 08:41
Bug
New Orphaned TYPO3 CMS 13

#107444 WCAG: focus after element creation

The user creates a page and updates it – Focus setting / screen reader is used.

Incorrect behavior:

After updating, the focus jumps to the top of the page.

Expected behavior:

After updating a page, users should be taken to where they were last (focus setting) – currently, the focus jumps to the top of the page.

Author Christian Rath-Ulrich
Created 09/12/25, 07:58
Updated 09/12/25, 07:59
Feature
Needs Feedback Orphaned Localization

#88766 Unpredictable allowLanguageSynchronization behaviour with file references

The TCA behaviour “allowLanguageSynchronization” has some user experience or design issues in combination with sys_file_references.

For the following examples I’ve used the actual TYPO3 CMS Master (10.0.x-dev) and the media field in page properties. Make sure you have at least one page with a translation.

Let’s beginn simple:

1. Parallel display of buttons to add relations and translation behaviour

IMHO the buttons to add relations should only be displayed on translations if “custom value” is chosen.
Or the other way round, if you add a relation in a translation it should automatically switch to “custom value”.

ATM if you add a relation and hit the save button while “value of default language” is still selected, the relation wont be saved. -> Bad UX
(see also topic 3)

2. Custom value != custom value

Starting with a empty media field (also in translations)
Step 1: Add a relation in default language and save
Step 2: Switch the translation behaviour to “custom value” in your translation and save.
Step 3: Go back to the default language of the page, delete the relation and save.

The relation is also deleted on the translated page with “custom value”. The editor would first have to delete the image and add it again in the translation to keep it.
Just because the l10n_parent is set, it is not necessary right to delete the relation. The translation behaviour isn’t taken into account.

3. Resync relations

Starting again with a empty media field (also in translations)
Step 1: Set translation behaviour “custom value” in translation
Step 2: Add a relation in default language

No relation added on translation. Yay, expected behaviour :-D

Step 3: Change translation behaviour to “value of default language” and save

The image is resynced correctly :-D

Step 4: Delete relation relation while keeping “value of default language” active and save

The image is gone for the translation until somebody saves the default language. This can be misleading for editors if they forget to switch to “custom value” at this point. This can be solved along with topic 1

4. Show warning when relation of translation is deleted

Starting again with a empty media field (also in translations)
Step 1: Add a relation on translation with “custom value” behaviour
Step 2: Switch translation behaviour to “value or default language” and save

Custom relation of translation is kept.

Step 3: Switch to default language and add save

Custom relation of translation is still there.

Step 4: Add new relation on default language and save

The new translation is added for all languages and the custom relation of the translation is deleted.

IMHO this is correct, but for better usability I would prefer a warning dialog when an editor changes to “value of default language” and if there are any relations without l10n_parent.
Something like: “Some relations are not connected to the default language. Are you sure to remove them?” and then delete them directly on approval.

5. Permission error

Starting with a empty media field (also in translations) and “value of default language” enabled
Step 1: Add relation on default language and save
Step 2: Add to “custom value, add a new relation on the translation and save
Step 3: Back on default add a new relation and save
Step 4: Switch translation behaviour back to “value of default language” and save

You should get an error like “1: Attempt to modify record ‘rawpixel-1046262-unsplash.jpg’ (sys_file_reference:292) without permission. Or non-existing page.” for the relation added in step 2.

—-

I hope those cases can help to improve the US with the allowLanguageSynchronization behaviour for editors.

Author André Buchmann
Created 07/15/19, 17:00
Updated 09/04/25, 12:58
Bug
New Orphaned Backend API TYPO3 CMS 14

#107344 Deleting page results in 503: "You don't have access to this page" if switch user to non-admin user

It looks like the page can be deleted but the currently selected page in page tree is still selected and this results in the error.

This problem is not reproducible with older versions, e.g. v12. Also, it is not reproducible as admin user.

Reproduce

Using latest TYPO3 instance from git repo “main” branch (v14.0.0-dev) and “styleguide” extension.

1. With styleguide extension create “styleguide frontend demo” test pages
2. If BE user does not exist, add BE user
3. Switch to BE user
4. Create test pages or test page
6. Jump to new page in page tree
7. Try to delete page by using context menu “Delete” in page tree

Result:

> 503
> Oops, an error occurred!
> You don’t have access to this page

However, page is deleted. So I assume it gets deleted, but current page is now the deleted page.

Author Sybille Peters
Created 08/28/25, 16:24
Updated 08/28/25, 16:24
Bug
New Orphaned RTE (rtehtmlarea + ckeditor) TYPO3 CMS 12

#105749 Unable to use "&"/ampersand character within URL parameters of "rte_ckeditor" link wizard/popup

When trying to use the “buttons.link.queryParametersSelector” optin within the “rte_ckeditor” extension, its possible to add custom parameters to a URL. But is seems not to be possible to add a “&” character. Using the ViewHelpers “uri.typolink” or “link.typolink”, the result is always a mixed up URL.

Entered data in the “queryParametersSelector” field within the backend:
test=begin&end

Output of saved (raw) data within the fronend:
t3://page?uid=123 – - – test=begin&end

Result after using the ViewHelper/s:
/testpage?end=&test=begin&cHash=c1234567890123456789012345678901

That of cause was expected, because the string “&end” is treated as an additional parameter “end”. But trying to use the URL encoded form “%26” of the “&” character is not possible: After commiting the added URL parameters by exiting the wizard, the “%26” character is immediately replaced by the standard “&” character.
So it is not possible to enter and save the parameter in the already encoded form “test=begin%26end”.

What would be the correct way to use “&” characters within URL parameters? In the meantime, is there a workaround?

Author Stefan Wagler
Created 12/03/24, 12:38
Updated 08/20/25, 09:20
Bug
Under Review Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 12

#100097 Long external parameters causes TYPO3 crash in Extbase Routing Enhancer

If an external parameter is added to a page, which is resolved using an Routing-Enhancer, this might cause a crash, if the parameter name is too long.

Steps to reproduce:

You need a page with configured Extbase Plugin Enhancer.
If you call this page it should work in the frontend with the normal output of the extbase plugin used.
If you call this page with a manipulated URL (add a long parameter, e.g. ?L_Instagram_FeedAd_EstimatedAdRecall=whatever you see an error in the frontend.

I expect the non-TYPO3 parameter is simply ignored.

I have stripped this down to https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/Routing/Enhancer/VariableProcessor.php#L61

if the parameter is longer than 31 chars and it’s not a valid hash, the OutOfRangeException is throwed, which leads to an error in the frontend.

As for shorter parameters the input argument is simply returned, I suggest to change the method resolveHash to return the value from $this->hashes, if the key $hash exists, and $hash otherwise.

This would make the method shorter and more stable.

I’m unsure, if this might have unwanted side effects.

I found this in a TYPO3 10.4.36 instance, but the method and the error is also in current main. It seems not related to the PHP version.

Author Marc Willmann
Created 03/06/23, 12:27
Updated 08/15/25, 12:49
Bug
Accepted Orphaned Frontend TYPO3 CMS 9

#88631 Page type parameter is ignored in POST requests/parameters

Since TYPO3 9 the page type parameter is ignored when set in POST parameters (for example from a form field). If it’s set in GET parameters (query string) everything is fine. This is because the PageArguments object is instantiated at several points with only the type parameter from the query params (for example in \TYPO3\CMS\Frontend\Middleware\PageResolver) not respecting the POST parameters. On the other hand the TypoScriptFrontendController is instantiated in \TYPO3\CMS\Frontend\Middleware\TypoScriptFrontendInitialization with GeneralUtility::_GP(‘type’) handling both POST and GET parameters. This is inconsistent behaviour and should be fixed as soon as possible. Or is this intended and not a bug?

Author DMK E-BUSINESS GmbH
Created 06/26/19, 10:19
Updated 08/12/25, 10:50
Feature
New Orphaned Fluid

#107090 f:link.typolink removes entire tag when no valid link target can be generated, causing CSS class loss

The <f:link></f:link> ViewHelper completely removes the entire link tag when it cannot generate a valid link target (e.g., when linking to a hidden page). This behavior causes CSS classes and other attributes to be lost, potentially breaking the layout and styling of frontend elements.

<!-- Input -->
<f:link.typolink class="test" parameter="{linkToHiddenPage}">
   <span>Link Text</span>
</f:link.typolink>

<!-- Output when page is hidden or inaccessible -->
<!-- Only slot content is rendered - entire link is removed -->
<span>Link Text</span>

Impact

  • Layout breaks: CSS styling fails when expected classes are missing
  • Unpredictable behavior: Works in 99% of cases but fails when pages are hidden/inaccessible
  • Manual workarounds required: Developers need to implement explicit condition checks

*Possible solution:*
Render an tag with a placeholder href.
This causes CSS styling like “a.test” to be valid and simply replaces the incorrect link with a “#” placeholder.

<a href="#" class="test">
   <span>Link Text</span>
</a>
Author Felix Ranesberger
Created 07/14/25, 08:28
Updated 08/08/25, 17:46
Bug
Under Review Orphaned Workspaces TYPO3 CMS 12

#107154 No way to review workspace changes from all sites or webmounts

Since https://forge.typo3.org/issues/96548 it is no longer possible to get an overview of all changes of all webmounts or all sites via the virtual root page uid=0) in the workspaces backend module.

Instead a message is triggered that is actually wrong:

> Please select a page in the page tree to review and publish changes.

This message is wrong page, because it is shown even if the page with the virtual id=0 is selected by a user, but the workspaces module denies to respect the desire of the user.

See https://forge.typo3.org/issues/95854 for an issue where the same usecase was reported and fixed previously (3 months before the mentioned change broke it again).

Author Benjamin Franzke
Created 07/28/25, 11:29
Updated 07/30/25, 09:39
Task
Accepted Orphaned Database API (Doctrine DBAL) TYPO3 CMS 11

#101235 Make additional DB connections optional sometimes, e.g. in case of SchemaMigration

While one can expect that the default DB connection for a TYPO3 is always available, there are scenarios where additional databases might not be available temporarily. Especially in case of schema migration this can result in problems, e.g. because a “not so important” additional DB should be ignored, while still wanting the schema migration to take place for the default connection.

A common scenario where this could occur is during deployment when and if the EXT:typo3_console command database:updateschema is run.
Currently, running this command with an unavailable additional DB is not possible as an unhandled exception would be thrown before the actual migration, due to the connection timeout.

So there seems to be the general idea there could be a need to be able to “skip” additional databases in some scenarios, most probably (but perhaps in other cases as well) during :
  • SchemaMigration
So the database configuration needs to cater for different scenarios:
  1. no schema migration should be done (table is completely managed by a 3rd party)
  2. schema migration only for mapped tables (in general tables are managed by a 3rd party, but a few tables were created by TYPO3)
  3. full schema control (like TYPO3 default, 3rd party tables not mapped should be removed)
While this covers the intended altering of tables, in order to cope with connection issues perhaps additionally
  • the schema migration should have an option to skip unavailable connections (handle the exceptions) and still run for the others
Current state is:
  • If a table mapping exists, then the whole connection is treated by the SchemaMigration
Some incomplete approaches for the current situation are:
  • additional.php: Check if additional condition is up (and perhaps if on CLI), perhaps remove connection.
  • read-only user for db access
Author J. Peter M. Schuler
Assigned to Stefan Bürk
Created 07/04/23, 23:41
Updated 07/25/25, 12:02
Bug
New Orphaned Workspaces TYPO3 CMS 13

#107071 Duplicated references (same language and parent) after publishing

When creating a translation in a workspace. Prior to publishing the records, the same page content is translated in the LIVE workspace
causing conflicting records in the database. (See the attached file)

For example uid 45 and 46 both have the same language and the same l18n_parent which does not work

uid sys_language_uid header t3ver_oid t3ver_wsid sys_language_uid l18n_parent t3ver_state deleted MY COMMENT
—- ———————— ———————————— ————- ————— ———————— —————- —————- ———- ———————————————————
45 30 GERMAN EDIT WORKSPACE 0 0 30 42 0 0 EXPECTED LIVE VALUE AFTER PUBLISHING
46 30 GERMAN EDIT LIVE LIVE 0 0 30 42 0 0 EVIL
42 0 Some Record to play with 0 0 0 0 0 0 OK

Steps to reproduce:

1. Go to a workspace and translate records from e.g. US to danish and change the content
2. Go to the LIVE workspace and tranlate the same records to the same language e.g. US to danish
3. Go to the workspace and publish the records

See the old record in the list module – Page module looks ok but the DB has now conflicting records.

Note: The same happens for sys_file_metadata

Author Jochen Roth
Created 07/10/25, 15:21
Updated 07/10/25, 15:23
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 14

#107041 Make live search more prominent in topbar

The Live Search is really good. And it should be made more prominent rather than being “hidden” behind a small button.

Author Andreas Nedbal
Created 07/04/25, 15:19
Updated 07/04/25, 16:08
Task
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 13

#107039 Add settings type helpers that ease integration of repeating element patterns

The UI of the stringlist is hard to reimplement in custom settings type.
The core should offer reusable components to be used by settings type in order to ease the generation of rich custom types.

Author Benjamin Franzke
Assigned to Benjamin Franzke
Created 07/04/25, 11:55
Updated 07/04/25, 11:55
Feature
Needs Feedback Orphaned Extbase

#104383 Better error messages for “Validation failed while trying to call …Controller->detailAction()”

Sometimes it is really hard to find out the problem itself when extbase only says “Validation failed while trying to call …Controller->detailAction()” and nothing more in TYPO3 log file. So why not tell the developer which validation fails?

Author Bernhard Eckl
Created 07/12/24, 14:04
Updated 06/05/25, 05:27
Bug
New Orphaned File Abstraction Layer (FAL) TYPO3 CMS 13

#106800 Filelist offers to create new file metadata but the user does not have sufficient permission to create it

After #106215, it is possible to select an image (or other file) in the file list MANAGE mode and typo3 will offer to create a new file metadata record. Upon saving it errors with

Sorry, you didn't have proper permissions to perform this change.
Access to table sys_file_metadata for user 119 was denied by a ModifyRecordEditUserAccessEvent listener 1662727149

Edit form could not be loaded
The edit form could not be loaded for the requested records. This might be due to insufficient permissions.

ZThe user is configured to not have write permission in this folder.

Author Oliver Eglseder
Created 05/30/25, 12:20
Updated 05/30/25, 12:20
Bug
Needs Feedback Orphaned Localization TYPO3 CMS 13

#81328 Translation didn't sort Elements correct.

This bug was found in TYPO3 7.6 and reproduced now in TYPO3 8.7

Whats the Bug

The bug is that the sorting of content elements can be different between the original language and a translation.

How can I reproduce the bug

1.) Create a new Page A
2.) Create a new Content Element A on Page A
3.) Translate the Page A and the Content Element A to another Language
4.) Create a new Page B
5.) Create a new Content Element B on Page B
6.) Translate the Page B to the same Language to which you translate Page A. Do not translate any Content Element now only the Page.
7.) Copy the Content Element A from Page A to Page B. The Translation of the Content Element A should be copied with the default Element.
8.) Translate now the Content Element B on Page B

Now the Content Element A and the Content Element B do not have the same sorting in both languages. Because sorting in the foreign language is not available you can not sort the elements in the correct order.

This behaviour was tested on TYPO3 7.6.16 and 8.7.17

A video of the reproduction in TYPO3 8.7 can be found in file section below.

How could this Bug be fixed

In my opinion we are having two possible solutions for this way

1. Check at every translation the original sorting. And Update it if nessecary for all other languages.
2. Don’t block the sorting function, when you translate content elements.

Author Markus Gehrig
Created 05/24/17, 10:24
Updated 05/28/25, 15:35
Bug
New Orphaned Database API (Doctrine DBAL) TYPO3 CMS 13

#106719 Install tool - SchemaMigrator & DBAL 4 - MySQL float type

Hi,

In my extension i have a field declare as my_field FLOAT,
In typo3 v12, in the Analyze Database Structure the field type stay as float.
In typo3 v13, it returns an update like ALTER TABLE `my_table` CHANGE `my_field ` `my_field ` DOUBLE PRECISION.

This can throw a lot of exceptions in extensions if the dev doesnt cast to float or check the entry type.
I think this a side effect of DBAL 4 and we should be allowed to use a MySQL float type.

In typo3, the process is located in \TYPO3\CMS\Core\Database\Schema\Parser\TableBuilder::getDoctrineColumnTypeName() :

...
case RealDataType::class:
case FloatDataType::class:
case DoubleDataType::class:
$doctrineType = Types::FLOAT;
break;
...

We force Types::FLOAT for this fields type who result in :

 public function getFloatDeclarationSQL(array $column): string
{
 return 'DOUBLE PRECISION' . $this->getUnsignedDeclaration($column);
}

I think the correct doctrine type is Types::SMALLFLOAT who will keep the MySQL float type.

Author Yohann CERDAN
Assigned to Stefan Bürk
Created 05/16/25, 11:39
Updated 05/23/25, 15:13
Bug
Under Review Orphaned Authentication TYPO3 CMS 12

#106367 Pages with "show at any login" are not accessible to users without any assigned group

I stumbled upon the following scenario:

I have a page which is restricted to logged in users. The virtual group “show at any login” has the id -2. My expectation is that users with a login (active, valid session) should be able to access that page.

That user however, does not have any group assigned.

When \TYPO3\CMS\Frontend\Authentication\FrontendUserAuthentication::createUserAspect() assembles all groups of a user, it only assigns -2 if the user already has at least one group assigned.

$userGroups = [0];
$isUserAndGroupSet = is_array($this->user) && !empty($this->userGroups);
if ($isUserAndGroupSet) {
    // group -2 is not an existing group, but denotes a 'default' group when a user IS logged in.
    // This is used to let elements be shown for all logged in users!
    $userGroups[] = -2;
    $groupsFromUserRecord = array_keys($this->userGroups);
} else {
    // group -1 is not an existing group, but denotes a 'default' group when not logged in.
    // This is used to let elements be hidden, when a user is logged in!
    $userGroups[] = -1;
    if ($respectUserGroups) {
        // For cases where logins are not banned from a branch usergroups can be set based on IP masks so we should add the usergroups uids.
        $groupsFromUserRecord = array_keys($this->userGroups);
    } else {
        // Set to blank since we will NOT risk any groups being set when no logins are allowed!
        $groupsFromUserRecord = [];
    }
}

So I think this is a bug, actually. Users without a user group, that are logged in, should be given the -2 group.

Author Alexander Schnitzler
Created 03/13/25, 10:36
Updated 05/14/25, 07:15
Bug
Accepted Orphaned Backend User Interface TYPO3 CMS 13

#102736 Install Tool Configuration Presets broken for image handling settings with debug mode enabled

Hello,

Upgrade from 11.5.33auf 12.4.9.

If “Configuration Presets” ist set to Debug the “Configuration Presets” is broken. It returns an AJAX Error:

Core: Error handler (BE): PHP Warning: file_exists(): open_basedir restriction in effect. File(/opt/local/bin/identify) is not within the allowed path(s): (/usr/bin/) in /typo3_src-12.4.9/typo3/sysext/install/Classes/Configuration/Image/ImageMagick6Preset.php line 81
Core: Error handler (BE): PHP Warning: file_exists(): open_basedir restriction in effect. File(/opt/local/bin/gm) is not within the allowed path(s): (/usr/bin/) in /typo3_src-12.4.9/typo3/sysext/install/Classes/Configuration/Image/GraphicsMagickPreset.php line 77

Temporär solution set “Configure Installation-Wide Options” -> [GFX][processor_path] from /usr/bin/ to /usr/bin. Then “Configuration Presets” load without error. Set Debug mode to off an then you can use “Configuration Presets” again to switch preset between GraphicsMagick and ImageMagick6.

Author Arne Bracht
Created 01/01/24, 14:59
Updated 05/13/25, 12:15
Feature
Needs Feedback Orphaned Backend User Interface

#99423 Let editors remove/unlink content from colpos with an action button in the contents "more actions" button list

Hello,

We want the editors stop hidding useless contents instead of deleting them, and cluttering their own working area.

This improvement is splitted in smaller, and if possible, independant patches.

link to the full video (publically accessible): https://drive.google.com/file/d/1cxHaU7JHPiDE1_4hFsfDiM1m2YxfHoLz/view?usp=share_link

This tasks relates to the time 1.13min of the video

Rachel

Author Rachel Foucard
Created 12/23/22, 16:28
Updated 04/19/25, 08:27
Bug
Needs Feedback Orphaned Frontend TYPO3 CMS 13

#97037 Shortcut in menu to root page is always active

In version 11.5.6 and 11.5.7 the shortcut in the menu to the root page is always marked as active. (I use the MenuProcessor).

Also testet with a fresh installation of 11.5.7 with the Introduction Package. See my screenshot:
Customize is the real current page, and Home is marked as active too.

Author extremo74 no-lastname-given
Created 02/25/22, 10:21
Updated 04/13/25, 13:19
Epic
New Orphaned Extbase

#102682 Make Extbase plugin registration and configuration more comfortable

This epic is about how to make extension developers life more comfortable when creating Extbase plugins.

Author Torben Hansen
Created 12/16/23, 11:55
Updated 04/11/25, 11:32
Feature
New Orphaned Backend User Interface

#105381 Make translate button in sys_file_reference IRRE element more prominent

I think the main problem here are:

  • the button “Localize” (e.g. in sys_file_reference relation in “textmedia” field “assets) does not look active the way it is displayed currently
  • and it is not visible this is the relation from the original language. Usually if content from original language is displayed, it is displayed with the flag icon.

Reproduce

1. Create a textmedia element
2. Translate it (connected)
3. Now add image in tab “media” field “assets” in element with original language

Now, in the translated element go to tab media and see the greyed out relation from the original language.

The buttons “Display information” and “Localize” also look greyed out.

Suggestion

  • make the buttons look active and clickable
  • possibly make the button “localize” marked as primary button (e.g. with class=“btn btn-primary”)
  • show a flag symbol for the reference from the default language

Screenshot

Versions

  • v11 … v14 (main)
Author Sybille Peters
Created 10/21/24, 15:34
Updated 04/10/25, 19:43
Bug
New Orphaned Localization TYPO3 CMS 9

#88966 Backend translation of contents should show warnings related to defined fallbackType from Site Configuration

There are currently 3 types for Frontend: strict, fallback and free.

In Backend there are two modes: connected (translate) and free (copy), (and mixed if you count that).

Problem is that they are independent and very misleading to editors in certain setups. For example: if we define the fallbackType: free, backend still shows red warings if we mix both modes in backen – what is totally fine for the frontend.
Or we define fallbackType: fallback and create only free translated contents in backen – no warning, but in frontend no translation is shown but the default contents.

I think the warnings in Backend should be related to the fallbackType set.

Author Anonymous
Created 08/16/19, 09:48
Updated 04/03/25, 13:35

Showing results 26 to 50 of 1561