Showing results 976 to 1000 of 1561

Task
Under Review Orphaned Localization TYPO3 CMS 14

#108139 Move live search related labels

Author Lina Wolf
Assigned to Lina Wolf
Created 11/15/25, 17:40
Updated 11/16/25, 05:16
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 13

#108101 Writing table delimiters in cell values creates unwanted columns in table content element

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:

  • 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 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.

Author Andreas Nedbal
Assigned to Andreas Nedbal
Created 11/13/25, 16:26
Updated 11/13/25, 16:26
Task
Author Matthias Vogel
Created 11/11/25, 12:56
Updated 11/12/25, 12:22
Task
Author Matthias Vogel
Created 11/11/25, 16:21
Updated 11/11/25, 23:40
Task
Author Lina Wolf
Assigned to Lina Wolf
Created 10/28/25, 12:09
Updated 11/11/25, 03:53
Feature
Accepted Orphaned Linkvalidator

#107983 Make Link Validator (linkvalidator) accessible for Preview-Workspace users

Scenario:

- I have a large corporate multi site with many users with limited user (role) rights.
- Editors only have access to “Preview Workspace”.

Problem:

Since the module “Link Validator” is only accessible for users with the right to “Edit live”, there is no possibility for Editors to check for broken links.

Solution:

Make the module “Link Validator” accessible for all workspaces.

Author Thomas Mock
Created 11/05/25, 09:54
Updated 11/10/25, 19:49
Feature
Under Review Orphaned Frontend

#104529 Missing hook to enhance the page cache data content

Currently the TypoScriptFrontendController does not offer the option of manipulating the content of the page cache data set before it is send to the cache backend. For example, to extend the page cache data with additional data. Extending the data set is useful, for example, for content that is otherwise only calculated or loaded in the event of a cache miss. Examples of this are the inlineLanguageLabels or the inlineSettings in the PageRenderer.

Author Tim Weisenberger
Created 08/01/24, 20:40
Updated 11/08/25, 19:36
Task
Under Review Orphaned Extbase TYPO3 CMS 13

#101461 Use php cache frontend for ClassSchema cache entries

Author Alexander Schnitzler
Assigned to Alexander Schnitzler
Created 07/27/23, 13:40
Updated 11/07/25, 17:22
Bug
Needs Feedback Orphaned Authentication TYPO3 CMS 12

#107984 Changing SYS/cookieDomain breaks BE login

After changing the SYS/cookieDomain backend users are stuck in the backend login screen: even though they enter the correct credentials, they’re presented with the login mask again and again. No error message whatsoever.

This can only be resolved by flushing the application cache via the browsers dev tools. Then login works flawlessly again.

I’m wondering how we can prevent such a situation in the future. For starters a clear error message would definitely help non-developer backend users.

Author Philipp Kitzberger
Created 11/05/25, 11:10
Updated 11/06/25, 17:15
Bug
Needs Feedback Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 13

#107972 When moving a page that was created as a rootpage into the pagetree of a diffrend rootpage Sets /Sitepackages will not load correctly

in typo3 13.4.8
typo3 composer.json says php 8.2 while php -v says PHP 8.4.5
Running in Windows wsl : Podman Desktop : typo3 runson an image based on webdevops/php-nginx
under certain conditions a subpage loades the wrong Sets/Siteconfiguration that dose not come form it current root page

when a rootpage is moved into the pagetree of a different root page it will still use it own Sets/Site Configuration instead that of the the parrend root page.
(if one run into this use you can copy the page with will work since the created page gets a new uid )

Reproduction:
Operation:
New installed typo3
create page in root : testbug0
add sitesets to Home
add different sitesets to testbug0
copy testbug0 to root making : “testbug0 (copy 1)“
move “testbug0 (copy 1)” into Home
copy testbug0 into home making testbug0

Images serve to show the subpages of Home do not have the same Typoscript load

cause:
cause even after moving the page the site configuration still persists in config/sites/**
so the sets and Site Configuration of its self are used over that from the root of the pagetree.

Still new to how to write bugreports so feel free to criticise me.

Author Max Shade
Created 11/03/25, 16:34
Updated 11/05/25, 21:13
Task
New Orphaned Backend User Interface TYPO3 CMS 14

#107954 Enhance breadcrumb node identifier with popup menu

It would be nice if clicking on the icon of a page shown in a breadcrumb offered a popup dealing with the related page actions.

Displaying the icon kind of nudges users into thinking that these trigger the menu just like other places where the icon is displayed (page tree, record listing). And it would allow to easily disable/show/copy/copy pages within the context.

(Classified as a ‘task’ instead of a ‘feature’ to round-off the existing feature #107794 )

Author Garvin Hicking
Created 10/31/25, 12:39
Updated 10/31/25, 12:39
Feature
Under Review Orphaned Form Framework

#91419 Disable caching on a per form basis

The form framework caches forms which causes issues when pre-filling fields with data. Any dynamic data retrieved via get params or database queries will be cached and can’t be overridden until caches are deleted.

Current solutions found in the typo3 slack channel fx. include disabling caching completely for the render function in the form controller:

$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['extbase']['extensions']['Form']['plugins']['Formframework']['controllers'][\TYPO3\CMS\Form\Controller\FormFrontendController::class]['nonCacheableActions'][] = 'render';

This of course changes caching for all forms which is not really an ideal solution.

Another solution suggested was using USER_INT instead of USER like this:

tt_content.form_formframework.20 = USER_INT

This would allow for disabling the cache on a per page basis. However certain forms which need to be uncached may be inserted by editors on multiple pages and makes it necessary to keep track of page ids where such forms are present and add them to our Typoscript.

It would be great to be able to disable caches for certain form configurations, perhaps as a yaml property. I am not sure if caches could be easily disabled via the form api in hooks where dynamic data is added, if this is the case that would also work for me.

Author Jarvis H
Created 05/16/20, 15:47
Updated 10/31/25, 10:37
Bug
New Orphaned TYPO3 CMS 12

#107901 Copied and changed parseFunc object has no effect

I have this Fluid template with 3 different parts:

<f:format.html parseFuncTSPath="lib.parseFunc_test">
    <test>
        Example 1
    </test>
</f:format.html>
<f:format.html>
    <test>
        Example 2
    </test>
</f:format.html>
<f:format.raw>
    <test>
        Example 3
    </test>
</f:format.raw>

and want to create a parseFunc to handle the <test> HTML tag.

When adding this TypoScript

lib.parseFunc_test < lib.parseFunc
lib.parseFunc_test.htmlSanitize = 0
lib.parseFunc_test.allowTags := addToList(test)

there is no change. All three examples give me an unparsed HTML output.

Only by adding

lib.parseFunc.htmlSanitize = 0
lib.parseFunc.allowTags := addToList(test)

it works fine for example 1 and 3. Which is not the way to go imho.

Another thing: If I reference the TypoScript object (lib.parseFunc_test =< lib.parseFunc) it throws an Exception because the frontend.typoscript object does not handle references.

Tested in TYPO3 v12.

Author Thomas Löffler
Created 10/29/25, 10:36
Updated 10/29/25, 10:36
Feature
New Orphaned

#107899 Add share directory for multi-node setups / clusters

Given TYPO3 is running on a multi-node setup / cluster, some filesystem directories need special care.

Some directories like locks must be shared between all nodes to ensure data consistency/integrity.

Some directories like caches should local on each node since they are easy to recreate and always produce the same result. Here one may expect a performance win when sharing between nodes (caches populated by one node can be used by another node) but usually the performance overhead of the sharing technology (e.g. NFS) defeats the purpose. A quick local filesystem access is usually faster here.

There should be a share directory similar to the one introduced in Symfony 7.4. Once TYPO3 defines and uses this directory for everything which may be shared, it can be promoted accordingly.

So the first steps:

1. Determine filesystem paths which are safe to share in multi-node setups and don’t suffer from network latency.
2. Add a share directory to TYPO3
3. Move the paths from 1. into this directory
4. Update guidelines/docs

Author Mathias Brodala
Created 10/29/25, 09:22
Updated 10/29/25, 10:26
Bug
Author Jasmina Ließmann
Created 10/27/25, 16:42
Updated 10/27/25, 16:42
Bug
New Orphaned felogin TYPO3 CMS 12

#105591 ext:felogin does not delete fe_typo_user Cookie on logout

We use felogin for a closed part of our website with redirect mode ‘Defined by GET/POST Parameters’ enabled.

In a newsletter we send out links to the login page with the access protected target page provided as redirect_uri query param.

The two usual cases work fine: If you are already logged in the correctly redirected page is displayed.
If you are not logged in the login page is displayed. After login you get redirected to the deeplinked page.

However: if you recently logged in and out again and then open the deeplink url again, you will incorrectly be redirected to the target page without displaying the login page – a 403 error is thrown.

Deleting the fe_typo_user cookie solves the problem. In TYPO3 v11 the cookie was still deleted after logout, but it seems not to be deleted with TYPO3 v12.

We are currently on TYPO3 12.4.21.

Author Carl-Fredrik Gustafsson
Assigned to Torben Hansen
Created 11/13/24, 14:30
Updated 10/25/25, 11:13
Feature
New Orphaned Backend User Interface

#107817 Allow to limit or hide page tree in element browser

Fields of TCA type “group” currently allow to set a default page ID when opening the element browser, using “ elementBrowserEntryPoints “. This allows for quicker access to records which are often stored in a central folder.

But the page tree on the left of the element browser does not preselect this page, nor are integrators able to limit/hide the page tree.

The Record link handler has the following options, which could be useful for the element browser as well.

  • pageTreeMountPoints : comma-separated list of pages/sysfolders which are visible in the page tree. Only records on these pages can be selected.
  • hidePageTree : boolean to hide the page tree. Useful if there is only one storage folder which is preselected with “ elementBrowserEntryPoints “.
Author Sebastian Klein
Created 10/23/25, 11:48
Updated 10/23/25, 11:48
Bug
New Orphaned Backend User Interface TYPO3 CMS 14

#107727 Tooltips are not shown for keyboard users and on touch devices

Description

The tooltip/title for the icon buttons only shows with hover and not on keyboard focus.

Reproduction steps

  1. Use the keyboard to navigate to an interactive element with a tooltip
  2. Tooltip is not shown

Impact

Missing information on icon button function

Target group

Keyboard users and users of touch devices

Severity

High

Frequency

On every page

Definition of Done

Tooltip can be implemented only on interactive elements (defined by semantic role) and which can get keyboard focus. title attributes on non interactive elements must be moved to an interactive element or the element must be made interactive.

Tooltip is shown on keyboard focus.

The visual style of the tooltip should have a good color contrast (Suggestion: AAA Contrast of text <> box larger than 7:1)

Suggestion: border, outline or shadow style has sufficient color contrast, page background <> border <> box background, each larger than 3:1

The minimum text-size of the tooltip is —bs-body-font-size. Currently 9pt (0.75rem), better would be 10.5pt (0.875rem).

The Tooltip content is not cut, instead the tooltip is repositioned or resized when required.

Recommended solution

Use an implementation of the referenced accessible tooltips.

References / WCAG 2.2 Reference

https://www.a11y-collective.com/blog/tooltips-in-web-accessibility/
https://tollwerk.de/projekte/tipps-techniken-inklusiv-barrierefrei/titel-tooltips-toggletips#der-einsatz-von-roletooltip
Acceptance criteria https://www.magentaa11y.com/#/web-criteria/component/tooltip

Maybe a solution can use https://developer.mozilla.org/en-US/docs/Web/API/Popover_API as non-modal popover.

Author Michael Telgkamp
Created 10/16/25, 12:52
Updated 10/22/25, 19:27
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#107744 Module menu no longer fully legible when font size is enlarged

Problem description
If an enlarged font size is activated in the browser via user-specific settings, the menu items in the main menu (left vertical bar) are no longer fully legible. Text is cut off, meaning that some of the menu item names are no longer recognisable. This prevents users from clearly identifying or selecting individual functions.

Recommended action
The menu items must be designed in such a way that they remain fully legible and usable even with an enlarged font size. The layout and container sizes must be flexible so that text content can be adjusted when the font size is changed without any loss of information or functionality.

Internal reference: 5806

Author Christian Rath-Ulrich
Created 10/17/25, 07:31
Updated 10/22/25, 19:16
Bug
Author Nikita Hovratov
Created 10/21/25, 15:16
Updated 10/22/25, 13:57
Bug
New Orphaned Install Tool TYPO3 CMS 13

#107788 Installing with SQLite writes a static string to settings.php

The headache

Installing TYPO3 with sqlite, writes a static string to settings.php.
The filename is random and path is absolute in terms of the current server. For ddev this is for example

/var/www/html/var/sqlite/cms-2d481814.sqlite

The path can be different from production but with settings.php in version control, this is an issue.

Trying to override the path with additional.php

Adding

$GLOBALS[‘TYPO3_CONF_VARS’][‘DB’][‘Connections’][‘Default’][‘path’] = \TYPO3\CMS\Core\Core\Environment::getVarPath() . ‘/sqlite/database.sqlite’;

is respected after installation but not taken into account during installation. This leaves the installation with a random named sqlite file with tables, and a empty database.sqlite file.

Resume

additional.php is not taken into account at this point of installation and settings.php is overridden upon installation, so setting the value is not a solution

Instructions

Running the following command (via ddev) for setting up a new site

ddev typo3 setup --driver=sqlite --admin-username admin --admin-user-password=Passw0rd! --admin-email=john.doe@example.org --server-type=other --project-name="SQLite installed TYPO3" --create-site=no --force

Install TYPO3 with sqlite and get’s a static path set to settings.php

Proposed solutions and brainstorm

  • “path” being relative to the projectDir
  • A env named “TYPO3_DB_PATH”

I cheer for the path being relative to projectDir

Author Soren Malling
Assigned to Stefan Bürk
Created 10/20/25, 10:14
Updated 10/20/25, 10:20
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 14

#107770 Improve positioning code of page modules page-column-header actions

Author Ayke Halder
Created 10/17/25, 16:11
Updated 10/17/25, 16:41
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 13

#107769 Improve accessibility of the view module menubar

The menubar is missing aria role attributes for itself and its items.

Also the menus keyboard interactions should be implemented via JS.

See https://www.w3.org/WAI/ARIA/apg/patterns/menubar/#keyboardinteraction

Author Ayke Halder
Created 10/17/25, 15:43
Updated 10/17/25, 15:44
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 12

#103583 Improve accessibility of elements with low opacity on focus by keyboard

There are some elements with a low value for opacity which only become fully visible on hover.

These elements must also become fully visible on focus/@focus-within@

Especially:
  • Filelist: the checkbox to de-/select an element to perform multi-element actions is not visible/selectable via keyboard at all.
  • Page Module: inactive/deactivated content elements stay grayed out on focus.
Some small icons:
  • Page Module: edit whole column action icon stays grayed out on focus.
  • Alert Dialogue: close-icon stays grayed out on focus and action-buttons don’t change background on focus.
  • View page: orientation-icon stays grayed out on focus.
Author Ayke Halder
Created 04/09/24, 19:09
Updated 10/17/25, 15:32

Showing results 976 to 1000 of 1561