Showing results 601 to 625 of 1561

Bug
Under Review Quiet Workspaces TYPO3 CMS 14

#111245 Reverting from the oldest history entry of a workspace-versioned record marks it for deletion

Summary

Reverting from the oldest history entry of a record that has been edited in a workspace marks the record for deletion, instead of just undoing the edit. Publishing the workspace then deletes it from the live site.

Environment

  • TYPO3 version: 14.3.10 (also present in 13.4 and 12.4 – the relevant code predates all of them)
  • Affected component: EXT:backend, TYPO3\CMS\Backend\History\RecordHistory / RecordHistoryRollback
  • No third-party extensions required to reproduce

Steps to reproduce

  1. Set up a page with EXT:workspaces active, and a draft workspace.
  2. In live, create a page with a content element on it.
  3. Switch the backend to the draft workspace.
  4. Edit the page’s title (or the content element’s header) and save. This is the record’s first save in the workspace – DataHandler silently creates a workspace version of it (versionizeRecord() -> copyRecord_raw() -> insertDB()), logged to sys_history as ACTION_ADD.
  5. Open the record’s History (Web > History, or the record’s “Last changes” panel).
  6. Two entries are shown: an “insert” (the version’s own silent creation) and a “change” (the title edit).
  7. Click the oldest entry (the “insert”) and revert from it (“Revert all” / revert the whole record).
  8. The page (and, for a page, any content nested under it) is now marked for deletion in the workspace (t3ver_state = 2, DELETE_PLACEHOLDER).
  9. Publishing the workspace (manually, or via the scheduled publish task) deletes the page/content from the live site.

Expected result

Reverting from that entry should only undo the title edit, restoring it to the value it had before this workspace touched the record. It must never delete the record.

Actual result

The record (and anything nested under it, for a page) is marked for deletion and removed on publish.

Root cause

DataHandler::insertDB() logs the creation of any new database row – including the workspace version it silently creates for an existing live record – as RecordHistoryStore::ACTION_ADD. RecordHistory::getDiff() treats every ACTION_ADD row as “this record was inserted,” with no way to distinguish a workspace version of an existing live record from a record genuinely created in the workspace. RecordHistoryRollback::performRollback() then turns that “insert” into a ['delete' => 1] DataHandler command.

The two cases are already distinguishable, though: insertDB()’s history_data payload for ACTION_ADD is the row’s own full field array, which includes t3ver_oid. A workspace version of an existing live record carries t3ver_oid = the live record’s uid (> 0); a record actually created in the workspace carries t3ver_oid = 0 (and t3ver_state = NEW_PLACEHOLDER). No extra DB lookup is needed – the already-logged row says which case it is.

Suggested fix

Filter these bookkeeping ACTION_ADD rows out in RecordHistory::getHistoryData(), since both the History module’s visible row list and getDiff() (which drives revert) consume its output. This hides the bookkeeping row from the History list and makes it un-revertible-as-a-delete, while a genuinely-new-in-workspace record (t3ver_oid = 0) still shows and reverts as a real insert. Patch attached.

Author Jure Milic
Created 10/26/26, 08:30
Updated 10/26/26, 09:17
Bug
Under Review Quiet FormEngine aka TCEforms TYPO3 CMS 13

#81996 Read-only select field 'renderType' => 'selectSingle' renders all available items

Readonly select field with ‘renderType’ => ‘selectSingle’ renders all available items in the select box.

Instead, only currently selected item should be rendered. This influences performance when there are many available elements.

Author Tymoteusz Motylewski
Created 07/28/17, 13:33
Updated 10/24/26, 09:14
Bug
Needs Feedback Quiet Import/Export (T3D) TYPO3 CMS 12

#101920 Export and import with impexp CLI - page structure ok, missing content / files / TS template (ddev / docker)

Export with backend / GUI:
- .t3d contains everything i want
- file-DIR with files is created
- import works, all Elements and relations ok(pages, tt_content, templates, files)

Export with CLI (same settings as with GUI):
- export shows no errors
- .t3d file is created (but missing: tt_content, TS templates …)
- file-DIR is created, but empty
- import (with backend/GUI): seems ok, pages / page-structure is ok, but no CEs / files (as they are already missing in .t3d)

I think i followed the instructions (https://docs.typo3.org/c/typo3/cms-impexp/main/en-us/Usage/CommandLine.html) and compared them with the GUI settings which actually work when all is done in the backend.

#!/bin/bash

/var/www/html/vendor/bin/typo3 impexp:export \
--type="t3d" \
--pid="5" \
--levels="999" \
--table="sys_category,sys_file,sys_file_collection,sys_file_metadata,sys_file_reference,sys_template,tt_content,tx_news_domain_model_link,tx_news_domain_model_news,tx_news_domain_model_tag" \
--include-related="backend_layout,pages,sys_category,sys_file,sys_file_collection,sys_file_metadata,sys_file_reference,sys_template,tt_content,tx_news_domain_model_link,tx_news_domain_model_news,tx_news_domain_model_tag" \
--include-static="backend_layout,sys_file_storage" \
--exclude-html-css \
--title="export-ddev-id-5" \
--save-files-outside-export-file \
filename-export-ddev-id-5-v5
Author Stephan Kleiber
Created 09/14/23, 12:32
Updated 10/24/26, 07:18
Task
Under Review Quiet Backend User Interface TYPO3 CMS 13

#104882 Use button for dropdown instead of anchor

Author Ayke Halder
Created 09/10/24, 18:31
Updated 10/23/26, 21:57
Feature
Under Review Quiet CLI

#109131 Reset TOTP MFA provider from command line

When entering the wrong TOTP code 3x upon login, the TOTP MFA provider gets locked. The user gets the following message:

> This provider is temporarily locked!
>
> The maximum attempts for this provider are exceeded. Please use another provider or contact your administrator.

This is not temporarily because it requires an admin to reset/unlock the provider for this specific user.

Currently this is only possible via the backend, but not on the command line.

There should be a CLI command that unlocks the MFA provider for a given user ID or email address.

(This is with TYPO3 v12, but I believe there is no such command in v13 either)

Author Christian Weiske
Created 03/03/26, 08:48
Updated 10/23/26, 14:12
Task
Under Review Quiet Site Handling, Site Sets & Routing TYPO3 CMS 10

#89058 PageRouter::matchRequest could use a cache

Currently, on every request PageRouter::matchRequest collects all slug candidates and chooses the best candidate. Depending on the amount of records in the database, this may lead to a lot of queries.

For a route that has been resolved previously, the result might get cached for faster resolving. This needs a proper concept in terms of cache invalidation.

Author Andreas Kienast
Created 09/02/19, 11:49
Updated 10/23/26, 13:43
Bug
Under Review Quiet File Abstraction Layer (FAL) TYPO3 CMS 6.2

#91168 Design flaw in FAL with indexing of files after a move

This problem was reported by myself in the context of the TYPO3 extension extractor: https://github.com/xperseguers/t3ext-extractor/issues/25

Context

When moving a file in fileadmin, FAL is invoking extractors to extract metadata again which is totally wrong, it should be done during upload (if configured so for the underlying storage) but never afterwards.

Problem is that if a user changes the metadata by editing them, they will get overridden whenever the file is moved around!

\TYPO3\CMS\Core\Resource\ResourceStorage::moveFile() line 2020 is doing that:

$this->getIndexer()->updateIndexEntry($file);

which in turn does that:

$metaData = $this->extractRequiredMetaData($fileObject);

if ($this->storage->autoExtractMetadataEnabled()) {
    $metaData = array_merge($metaData, $this->getExtractorService()->extractMetaData($fileObject));
}
$fileObject->getMetaData()->add($metaData)->save();

This has the effect of possibly overriding changes made by the user and leads to loss of information!

How to reproduce: Start

  • Take a vanilla v6.2, v7, v8, v9 or v10 TYPO3 installation
  • Download and install EXT:extractor (https://extensions.typo3.org/extension/extractor or packagist causal/extractor)
  • Configure the extension by just enabling native PHP extraction (default settings, nothing to change, no need to configure additional external extraction services)
  • Upload a file containing metadata. As an example I attach a sample PDF (sample.pdf) coming from EXT:extractor itself to this ticket
  • Click the file name to edit the metadata, you get something like that:

  • Now change some metadata manually, like the title or the description. Save
  • You can edit again to check, your changes have naturally been persisted.

How to reproduce: DESIGN FLAW!

  • Move the file to another directory
  • Edit the metadata… BANG! your metadata have been reset to the content of the 3rd-party extractor services

Solution

  • Check if reindexing the file after moving it is actually required by FAL
  • In any case, DO NOT INVOKE metadata extraction again!
Author Xavier Perseguers
Created 04/22/20, 11:05
Updated 10/23/26, 12:19
Bug
New Quiet Backend User Interface TYPO3 CMS 13

#108918 Make “Create new page” action in page tree accessible for screen readers

In the TYPO3 backend page tree, the “Create new page” function is only visible via icon/context menu but not exposed as a separate, labeled action in the underlying structure.
Screen reader users do not get an explicit “Create new page” action and cannot easily find or trigger this function using the keyboard.
This violates basic accessibility requirements for keyboard operation and clear labeling (e.g. WCAG).

Reproduction Steps

  1. Log in to the TYPO3 backend.
  2. Navigate to the page tree in the “Page” module.
  3. Enable a screen reader (e.g. NVDA or JAWS) and use keyboard-only navigation.
  4. Focus a page entry with role=“treeitem”.
  5. Try to find and trigger a clearly named “Create new page” action as its own control.
  6. Observation: There is no explicit, focusable “Create new page” action.

Impact

  • Screen reader users cannot create new pages or can do so only with workarounds.
  • Accessibility and WCAG requirements (e.g. name, role, value; keyboard access) are not met.
  • Risk of accessibility issues in projects relying on TYPO3 backend accessibility.

Definition of Done

  • For every place in the page tree where a new page can be created, there is a clearly labeled, focusable control.
  • The function is fully operable by keyboard (including focus order and visible focus).
  • The solution is localized (e.g. “Neue Seite erstellen” / “Create new page” depending on backend language).
  • Existing functionality to create pages remains unchanged.
  • Manual tests with at least one screen reader (e.g. NVDA) in current browsers are performed.

Recommended Solution

  • Add a dedicated, focusable control (button or menu item) for “Create new page” in the context of each relevant treeitem.
  • Provide a meaningful, localized label (e.g. via aria-label / visible text) for this control.
  • Ensure the action can be triggered with standard keyboard keys (e.g. Enter/Space).
  • Reuse the existing logic for creating new pages; only improve the semantic representation and accessibility.

References

  • WCAG 2.1:
  • 2.1.1 Keyboard
  • 2.4.6 Headings and Labels
  • 4.1.2 Name, Role, Value
  • TYPO3 Backend Accessibility Guidelines (if available)

Acceptance Criteria

  • For all places in the page tree where a new page can be created, there is a distinct, focusable control with an accessible, localized name “Create new page”.
  • Screen readers (e.g. NVDA, JAWS) announce an explicit “Create new page” action when navigating the page tree.
  • The “Create new page” action is fully reachable and operable via keyboard only, without requiring mouse hover or context menu with a mouse.
  • Existing functionality for creating new pages remains intact; only semantic and accessible labeling is added/improved.
  • No regressions in behavior or layout of the page tree are observed for users without screen readers.
Author Christian Jung
Created 02/09/26, 14:46
Updated 10/22/26, 12:16
Bug
New Quiet Backend User Interface TYPO3 CMS 14

#109474 Add a Bypass Link to meet WCAG SC 2.4.1

Description

The System lacks an easy way to jump into either the sidebar nor the main content, commonly referred to as “bypass link” or “skip link”.

As the sidebar can get very long, it can be really hard to navigate the system just by keyboard.

A bypass link should link to the following places:

  1. The sidebar
  2. The page navigation (if shown)
  3. The main content

Reproduction Steps

Open any page and press the tab-key. Instead of a bypass link, the focus is moved to the next entry in the header.

Impact

Adding a Bypass Link will help to meet WCAG SC 2.4.1

Recommended Solution

Add a bypass link just below the opening <body>-tag which links to</body>

  1. The sidebar
  2. The page navigation (if shown)
  3. The main content

The sidebar already has an id: “sidebar” and can therefore be easily targeted.
The page navigation and main content are wrapped inside a div wiht the id: “main”. Since the page navigation can get very long, I recommend to not target “main”, but instead add 2 new id’s.

Definition of done

  1. When pressing the tab-key the first thing after loading the page is a set of skip links.
  2. When choosing a link, focus is moved to the chosen container.
  3. The page navigation is only offered as link target, if it is rendered and visible.
Author Philipp Tautz
Created 04/02/26, 15:17
Updated 10/21/26, 16:07
Epic
In Progress Quiet Backend User Interface

#89595 Improve accessibility of backend

This epic covers all tasks to make the backend more accessible.

Author Georg Ringer
Created 11/06/19, 21:19
Updated 10/20/26, 07:25
Bug
Under Review Quiet Extension Manager TYPO3 CMS 14

#110066 immediately show a login screen in Extension Manager after a timeout

After reopening of a lot of times before closed browser window the Extension Manager is shown in the same manner as before. The selected extension in listed in the window. There you click to deactivate the extension and confirm the button. But nothing happens. You wonder why. Then you realise that you have to reload the browser window and you have to reenter the backend user password. Then you repeat the steps and it works to deactivate the extension.

This should not happen in the first case. After a login timeout the Extension Manager window should immediately show the login screen before any other action is accepted which would fail without notice.

Author Franz Holzinger
Created 06/17/26, 07:11
Updated 10/19/26, 12:55
Task
Author Oliver Bartsch
Assigned to Oliver Bartsch
Created 10/13/26, 07:19
Updated 10/19/26, 07:27
Feature
Needs Feedback Quiet Backend User Interface

#101549 Improve pagination of tables inside list module.

When you have more that 50 records on a table inside the list module, a pagination can be shown , which is currently like this one:

This has the following flaws

  • there is a “reload” icon whose purpose is unclear: the user can mistake it for a “Go to” button by entering a page number and press it.
    The actual purpose of the button is to reload the list in case the data shown are not up-to-date with the actual data.
  • Also some users don’t know that they have to press enter to reach the page.
  • the input field works by steps but the arrows are really small

My proposal

  • add a label “Refresh” next to the reload icon
  • de-emphasize it or put it apart to avoid confusion
  • add an explicit “go to” button
  • use a plain input field (only numbers) to enter a page number – the up/down arrows should be removed as they’re too small

Here is a mockup:

Author Riccardo De Contardi
Created 08/03/23, 13:40
Updated 10/19/26, 07:27
Bug
Under Review Quiet Backend User Interface TYPO3 CMS 7

#77598 Editor without 'Files: Replace' option gets file replace option in the "File exists" modal

When an editor doesn’t have the permission to replace a file he still gets the option to replace a file in the “File exists” modal that appears when uploading an already existing file.

The upload bar goes to 100% and then it freezes. After page reload you see the flash message that the users isn’t allowed to replace a file

Author Frans Saris
Created 08/23/16, 10:37
Updated 10/19/26, 07:23
Bug
Under Review Quiet scheduler TYPO3 CMS 14

#110692 Problem on https://docs.typo3.org/c/typo3/cms-scheduler/main/en-us/Administration/StopTask/Index.html

Hello,

Thank you very much for the new API in Scheduler. I’m excited about the new approach. I now want to migrate my handful of Scheduler tasks with many parameters. Unfortunately, I’ve noticed two undesirable behaviors:

1. debug(....) no longer really works. Only if I put an exit; right after it do I see the debug output.

2. The validation is only semi-practical: if the method

public function validateTaskParameters(array $parameters): bool

returns false, the form forgets the incorrect input. In other words, if the user entered a longer JSON, for example, and validation says, “You forgot a key,” everything is gone. That’s very annoying…

Is there a solution for these two points?

Author C. Gogolin
Created 09/13/26, 17:47
Updated 10/18/26, 17:47
Bug
Needs Feedback Quiet Mailer API TYPO3 CMS 14

#111023 FluidEmail with the default layout crashes without normalizedParams in the request

Since TYPO3 v14, sending a FluidEmail with the default SystemEmail
layout fails when the request has no normalizedParams attribute. This
is the typical case in a CLI command or a scheduler task:

DefaultSystemResourcePublisher::getFrontendUrlPrefix(): Argument #2
($normalizedParams) must be of type NormalizedParams, null given

Affected versions: 14.3 and main. Reproduced on 14.3.7. The same code
works in 13.4.

Steps to reproduce

1. In a command, create a request:
new ServerRequest($site->getBase()) with the attributes
applicationType (REQUESTTYPE_FE) and site.
2. Create the mail with TemplatedEmailFactory::create($request) and
send it with the default template.

Cause

FluidEmail::setRequest() puts the request into the rendering context.
When the request has no normalizedParams, it creates a fallback from
$_SERVER, but only assigns it as the view variable “normalizedParams”.
The request in the rendering context stays without the attribute.

The layout renders the logo with f:uri.resource. Since the System
Resource API (#107537), this ViewHelper calls
DefaultSystemResourcePublisher with the request from the rendering
context. extractPublicPrefixFromRequest() reads normalizedParams from
the request and passes null to getFrontendUrlPrefix(), which requires
NormalizedParams.

In 13.4, f:uri.resource used PathUtility::getAbsoluteWebPath() and did
not need the request.

TemplatedEmailFactory::create() documents itself for backend and CLI
contexts, and passes the request to setRequest() unchanged.

Workaround

Add the attribute before creating the mail:
$request->withAttribute(‘normalizedParams’,
NormalizedParams::createFromRequest($request))

Possible solution

Put the fallback on the request too, for example with
withAttribute(‘normalizedParams’, …), before setRequest() hands the
request to the rendering context.

Found while documenting how to send FluidEmail from a command:
https://github.com/TYPO3-Documentation/TYPO3CMS-Reference-CoreApi/pull/7229

Author Lina Wolf
Created 10/11/26, 16:28
Updated 10/18/26, 16:02
Feature
Accepted Quiet Security

#104364 Add restrictions for sys_file_storage (better restrict file access when dealing with private storages)

When working with “private” storages (outside web root), access to any file from frontend context (typolink, image view helper, etc.) is automatically handled by core using the “eID=dumpFile” functionality. So access to any file is (theoretically) always possible when the token is known (or guessed). This is misleading and confusing, people might not be aware of this!

In my opinion, an integrator or developer should be able to rely on, that when making a storage physically “private”, there is absolutely no file access possible per default. Please add a storage restriction as Oliver suggests below.

Author Jan Kornblum
Created 07/11/24, 12:01
Updated 10/18/26, 15:57
Feature
Needs Feedback Quiet Image Cropping

#108598 Provide API to create default value for sys_file_reference.crop

Use case

A TYPO3 extension provides an API to create content elements with images.
When an image is imported and a content element created, the image must be connected to the content element via the sys_file_reference table.
To allow proper frontend rendering of the image, the sys_file_reference entry needs a valid value in the crop column – just as if it had been created by hand.

Problem

Manually creating that crop JSON is cumbersome and complex, see https://www.derhansen.de/2021/12/typo3-image-import-crop-variant-string.html
It would be better if TYPO3 would provide a public API method to build that JSON structure.

Author Christian Weiske
Created 01/06/26, 13:20
Updated 10/18/26, 11:40
Task
Accepted Quiet Extbase + l10n TYPO3 CMS 13

#107925 Different Translation Handling: DataHandler <==> Extbase

Hello,

I have created a blog with 2 post entries (EXT:blog_example).
If I translate the blog via DataHandler in backend, all related posts will be translated, too. Perfect.

Here the CSV:

"uid","sorting","sys_language_uid","l10n_parent","l10n_source","t3_origuid","blog"
"2","1","0","0","0","0","2"
"3","2","0","0","0","0","2"
"6","1","1","2","2","2","4"
"7","2","1","3","3","3","4"

You see 2 postings in default language related to blog UID 2. After the translation you see two additional postings related to the translated blog with UID 4.

As the blog->posts relation is TCA type “inline” I think this is expected behavior. PS: For TCA type “select” all relations have to relate to the record in default language.

Here you see the TCA of the blog_example delivered by TYPO3 itself in functional tests:

https://github.com/TYPO3/typo3/blob/13.4/typo3/sysext/extbase/Tests/Functional/Fixtures/Extensions/blog_example/Configuration/TCA/tx_blogexample_domain_model_blog.php#L63-L76

And now the IMO wrong part. This is the CSV of the extbase fixture to test localization:
https://github.com/TYPO3/typo3/blob/13.4/typo3/sysext/extbase/Tests/Functional/Persistence/Fixtures/TranslationTestImport.csv#L7-L18

As you see, ALL relations (independent of the translation) back to blog table are UID 1! In Extbase you create a new query based on $blog->getUid() which results in 1 in your tests for blog in default language. To get all related posts you need the UID 1 also in translated post records.
But, if you store a record in DataHandler the related blog UID is different for translated records. So, after querying posts in extbase all posts without translation will not appear in frontend if “translation fallback” to default language is activated in site configuration.

Stefan

Author Stefan Froemken
Created 10/29/25, 21:43
Updated 10/17/26, 13:51
Task
New Quiet Backend User Interface TYPO3 CMS 14

#96162 Extend Video via Text&Media to accept Player Options for Youtube

Youtube allows URL parameters to customize the embedded Player, see https://developers.google.com/youtube/player_parameters#Parameters

From TYPO3 Text&Media CE, only autoplay is supported.

In contrast, the file typo3/sysext/core/Classes/Resource/Rendering/YouTubeRenderer.php in method createYoutubeUrl would be able to cater for the parameters.
Sys_file_reference should be extended to accept Player Parameters to be set by editors.

Author Anja Leichsenring
Created 11/30/21, 13:11
Updated 10/17/26, 09:45
Feature
Under Review Quiet Form Framework

#110344 Ability to add static content to summary page

As an editor I want to be able to put static content (eg text) before or after the auto-generated form data summary.

As simple solution are two RTE fields that belong to step properties.

A more flexible solution allows static elements (eg text or containers) to be added on a summary page. As a step has currently one element collection the content may only be placed above or below the summary. Placement should be set by a step property.

If the summary step could feature two collections (ie renderable properties) an editor had full freedom.

Author Martin Kutschker
Assigned to Josua Vogel
Created 07/31/26, 10:42
Updated 10/16/26, 20:14
Task
Author Ayke Halder
Created 10/16/26, 15:03
Updated 10/16/26, 16:40
Feature
Under Review Quiet Fluid Styled Content

#71831 no posterimage for videos

the new ‘text & media’ element has no possibility to render a posterimage for videos.

before FSC there was at least the possibility to have an image with the same name as the video in the same folder to get an automatic poster image.

nice to have:
link the posterimage in the file properties.

Author Bernd Wilke
Created 11/25/15, 14:04
Updated 10/15/26, 21:36
Feature
Under Review Quiet Backend API

#78560 Loosen restrictions on tagnames in GeneralUtility::array2xml

GeneralUtility::array2xml is very restrictive when it comes to tagnames. Currently only alphanumeric characters, ‘-’ and ‘_’ are allowed in tagnames which makes working with FlexForms or namespaced XML impossible (because ‘.’ and ‘:’ are discarded).

The following line is responsible for the restriction:

// The tag name is cleaned up so only alphanumeric chars (plus - and _) are in there and not longer than 100 chars either.
$tagName = substr(preg_replace('/[^[:alnum:]_-]/', '', $tagName), 0, 100);

There are multiple ways this could be handled in the future:

1. Lift restriction to match the W3 XML spec: https://www.w3.org/TR/2008/REC-xml-20081126/#NT-Name ( potentially breaking )
2. Add an option to explicitly allow certain characters. The resulting call could look like this:

GeneralUtility::array2xml($array, $NSprefix, $level, $docTag, $spaceInd, [ 'allowInTagName' => ['.', ':'] ]);
Author Johannes Hertenstein
Created 11/03/16, 15:30
Updated 10/15/26, 20:54
Bug
Needs Feedback Quiet Backend User Interface TYPO3 CMS 12

#107551 You currently have unsaved changes modal appears even if no changes

When you create a text content element and close the window again, the modal window shows up:

You currently have unsaved changes which will be discarded if you close without saving.

That is not correct as I have not done any changes! This modal should only show up if I have changed any form values.

Author Simon Schaufelberger
Created 09/26/25, 23:34
Updated 10/14/26, 12:58

Showing results 601 to 625 of 1561