Showing results 551 to 575 of 1561

Feature
Under Review Fresh Form Framework

#89690 ext:form - read selectOptions from a database table

The options for a select in the form editor can currently only be configured in YAML:

selectOptions:
  10:
    value: 'image/jpeg'
    label: 'formEditor.elements.ImageUpload.editor.allowedMimeTypes.jpg'
  20:
    value: 'image/png'
    label: 'formEditor.elements.ImageUpload.editor.allowedMimeTypes.png'

It would be nice to have the possibility, of reading the selectOptions from a database table. This could be configured similarily to the way it is already done in TCA. (https://docs.typo3.org/m/typo3/reference-tca/master/en-us/ColumnsConfig/Type/Select.html)

Author Christian Eßl
Assigned to Christian Eßl
Created 11/15/19, 10:47
Updated 11/15/26, 16:06
Bug
Under Review Fresh RTE (rtehtmlarea + ckeditor) TYPO3 CMS 15

#111452 CKEditor inserts the raw t3://record href as link text

Problem

When a record link is inserted without a text selection, the rich text editor
uses the URL itself as the link text, for example
@t3://record?identifier=news&uid=12@. The link balloon shows the same raw
href, and “Open link” and Ctrl+Click do nothing. Page, file, folder, URL, email
and telephone links get a resolved title.

Steps to reproduce

  1. Configure a record link handler, for example TCEMAIN.linkHandler.news for a
    table with records on a page.
  2. Edit a text element, place the caret without selecting text.
  3. Open the link browser, choose the record tab and pick a record.
  4. The inserted link text is t3://record?identifier=news&uid=12.

Cause

LinkPreviewController::resolveAction() (route link_preview) matches
@TYPE_PAGE@, TYPE_FILE, TYPE_FOLDER, TYPE_URL, TYPE_EMAIL and
@TYPE_TELEPHONE@. A record link falls into default => $result and comes back
with title and url null. rte-link-browser.ts then uses an empty link
text and typo3-link.ts inserts linkText || href.

Suggested fix

Resolve TYPE_RECORD: table from TCEMAIN.linkHandler.<identifier>.configuration.table
of the page the edited record is stored on, tables_select and
@readPageAccess()@ of the record’s page as LinkElement does, title via
@BackendUtility::getRecordTitle()@, path of the record’s page. Keep the
access safeguards the existing preview tests cover.

Becomes urgent with #111379, which turns links to content elements into record
links.

Author Oliver Bartsch
Assigned to Oliver Bartsch
Created 11/14/26, 17:40
Updated 11/15/26, 11:12
Bug
Under Review Fresh Image Cropping TYPO3 CMS 14

#111431 SVG crop is ignored when the crop area starts at the top-left corner (x=0, y=0)

When an SVG file reference has a crop variant whose area starts at x=0 and y=0
(e.g. the left half of the image), the crop is ignored and the original,
uncropped SVG is delivered. Any crop with an offset (e.g. x=0.25) works.

Steps to reproduce (TYPO3 14.3.10):
1. Upload an SVG, e.g. 342 × 160 px.
2. In a content element, crop it in the image manipulation wizard to its left
half, anchored at the top-left corner: {“x”:0,“y”:0,“width”:0.5,“height”:1}.
3. Render it, e.g. <f:image image="{file}" cropvariant="default"></f:image>
or <f:uri image="{file}" cropvariant="default"></f:uri>.

Expected: a processed SVG showing the left half (viewBox cropped, 171 × 160).
Actual: the URL of the original SVG, uncropped.

Cause:
ImageProcessingInstructions::fromProcessingTask() passes the crop dimensions as
$incomingWidth / $incomingHeight to fromCropScaleValues() when a crop is set
($isCropped is computed but never used). At the end of fromCropScaleValues(),
the crop area is reset to null when it has offset 0/0 and the same size as
$incomingWidth / $incomingHeight:

if ((int)$cropArea->getOffsetLeft() = 0
&& (int)$cropArea->getOffsetTop() = 0
&& (int)$cropArea->getWidth() = $incomingWidth
&& (int)$cropArea->getHeight() = $incomingHeight) {
$cropArea = null;
}

Since $incomingWidth / $incomingHeight are the crop’s own size, this condition
is always true for a crop anchored at the top-left corner, so the crop is
dropped and SvgImageProcessor delivers the original file.

Possible fix: compare against the original file’s dimensions instead of the
incoming (crop) dimensions, or skip this reset when the image is cropped.

Author Stéphane Balet
Created 11/13/26, 09:15
Updated 11/15/26, 07:50
Bug
Under Review Fresh TYPO3 CMS 14

#111458 "Missing folder permissions" when switching from Backend Admin user to Editor in Media module

Steps to reproduce

  • Go to Media module
  • Create 2 folders “One”, “Two”
  • Create a file mount on folder “Two”
  • Create a backend user group and assign that group the file mount
  • As Admin user, click on Folder “One”
  • Go to User Module and witch to Editor
  • Open Media Module
  • Missing folder permissions. You have no access to the folder “1:/One/”.

This is because the folder is stored in local storage and loaded after switching the user automatically. This must be avoided.

Author Simon Schaufelberger
Assigned to Simon Schaufelberger
Created 11/14/26, 19:33
Updated 11/14/26, 21:21
Bug
New Fresh Image Cropping TYPO3 CMS 14

#111437 Writing avif files in image rendering tests generate files not working on Firefox

The generated files work with normal image viewers, chromium-based browsers, but not Firefox.

'/usr/bin/convert' -interlace 'None' -auto-orient -background none '+profile' '*' -auto-orient -geometry 300x225! -sharpen 1x2 -quality 85 -colorspace 'sRGB' 'heif:/var/www/vendor/typo3/cms-install/Resources/Public/Images/TestInput/Test.avif[0]' '/var/www/public/typo3temp/assets/images/installTool-write-avif6af7086fcbbe7411290651.6af7086ff2d5b0.74333909.tmp.avif'
identify /var/www/public/typo3temp/assets/images/installTool-read-avif6af70871a2672871049577.6af70871b49637.69154280.tmp.avif
AVIF 300x225 300x225+0+0 8-bit sRGB 21231B 0.010u 0:00.001
convert --version
Version: ImageMagick 7.1.1-43 Q16 x86_64 22550 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC Modules OpenMP(4.5) 
Delegates (built-in): bzlib djvu fftw fontconfig freetype heic jbig jng jp2 jpeg lcms lqr ltdl lzma openexr pangocairo png raw tiff webp wmf x xml zlib zstd
Compiler: gcc (14.2)
convert -list format | grep -i AVIF
     AVIF  HEIC      rw+   AV1 Image File Format (1.23.6)
heif-info --version
1.23.6
libheif: 1.23.6
plugin path: /usr/lib/x86_64-linux-gnu/libheif/plugins
heif-info  /var/www/public/typo3temp/assets/images/installTool-read-avif6af70871a2672871049577.6af70871b49637.69154280.tmp.avif
MIME type: image/avif
main brand: avif
compatible brands: mif1, avif, miaf

image: 300x225 (id=1), primary
  colorspace: YCbCr, 4:2:0
  bit depth: 8
  color profile: no
  alpha channel: yes 
  depth channel: no
metadata:
  none
transformations:
  crop: left=0 top=0 right=0 bottom=1
region annotations:
  none
text items:
  none
properties:
none
MIME items:

AI not really helpful yet, what the issue might be.
Suspicion is the

transformations:
  crop: left=0 top=0 right=0 bottom=1
Author Markus Klein
Created 11/13/26, 13:30
Updated 11/13/26, 13:30
Bug
New Fresh Caching TYPO3 CMS 9

#91561 Lifetime of cache is not properly computed for "Insert Records" CE

Use case

  • A content element (text/image/…) is prepared and corresponding start/end times are specified
  • This content element is to be used at multiple places on the website and is thus referenced (paste as reference when using EXT:gridelements or simply using “Insert Records” TYPO3-native CE

Expected

  • When the content element on the “master” page finally shows up (or disappears), every page having a reference to that content element should be automatically updated, that is the cache should be invalidated.

Actual behaviour

  • Only the cache of the “master” page is automatically flushed
  • Other page’s caches are not invalidated and a manual flush is required (or a force-reload while being logged-in into the Backend).

Reason

Method \TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::getFirstTimeValueForRecord() is supposed to compute the cache lifetime of CEs on a given page. But it only takes into account the start/end fields of the corresponding records.

For “Insert Records” (= shortcut) content element, only the start/end times of the shortcut are taken into account but not the ones of the referenced records.

Expected behaviour: both start/end times of the shortcut CE and all the associated records should be taken into account in that particular context.

In addition, and this could be a real improvement for extension authors, it would be useful to allow extensions to “hook” (PSR-14 if speaking from TYPO3 v10 or master branch, signals/whatever before) so that plugins may benefit from the same possibility than this very shortcut CE to post-process the lifetime in the context, e.g., of a plugin doing some temporary caching of external data and where one way (only “good” one?) to properly handle such case is to add tags to the corresponding page cache and to flushByTags() asynchronously when fetching remote data (or force the whole page to be cached for a shorter period of time).

Author Xavier Perseguers
Created 06/03/20, 13:59
Updated 11/13/26, 13:05
Bug
Under Review Fresh Link Handling & Redirect Handling TYPO3 CMS 13

#109367 Redirect URL ignores additional parameters, if "keep_query_parameters" is not set

In the redirects module, additional parameters can be set via wizard or directly (Example: t3://page?uid=2065 - - - &utm_source=something). The additonal parameters are even shown in a nice info box (see screenshot). But for any reason, the only work when “keep_query_parameters” is enabled for this redirect record.

This does not make sense to me and I guess, it is a bug.

I would expect the option “keep_query_parameters” only control, if the original request parameters are kept. For example when calling https://example.org/my/old/path/?foo=bar the foo=bar would be attached additionally to the target page.

Author Albrecht Köhnlein
Created 03/25/26, 16:35
Updated 11/13/26, 10:52
Bug
New Fresh TYPO3 CMS 12

#108312 sys_file info modal does not show user uploaded the image

When clicking the “info” modal of a file through file list or a used image in a content element, the user originally uploading the image is not shown.

This is due to the RecordHistory looking for a record of `sys_file`, but only the history of creating the sys_file_reference is being recorded.

Somehow, the creation of the original file is not being recorded.

Having the recorded could help show who managed a certain file

Author Soren Malling
Created 11/25/25, 13:52
Updated 11/13/26, 10:42
Feature
Needs Feedback Fresh Install Tool

#110808 Extension Scanner: the mandatory restFiles reference makes rules impossible for undocumented API removals

This is a request for a decision, not a patch proposal. I ran into a structural limit of the Extension Scanner while measuring, and I would like to know which direction the team considers acceptable before writing anything.

The constraint

A scanner rule must reference a changelog file, and this is enforced twice:

  • Load time — AbstractCoreMatcher::validateMatcherDefinitionKeys() throws InvalidArgumentException 1500496068, “Each configuration must have at least one referenced restFiles entry”, when restFiles is empty.
  • Display time — UpgradeController resolves every entry with Finder->name($fileName) against EXT:core/Documentation/Changelog and throws RuntimeException 1499803909 when the result is not exactly one file.

So a rule can only exist for an API change that has its own .rst file in the core. There is no placeholder, no external link, and no way to express “this was removed, and it is not documented anywhere”.

Why that is a practical limit, measured

The core’s own changelog metadata says that for v14.0, of 99 breaking changes 34 are FullyScanned, 5 PartiallyScanned and 58 NotScanned. This ticket is about a structural reason why that ratio is hard to improve.

I diffed the public API of typo3/cms-core v13.4.35 against v14.3.7 and generated candidate scanner rules from the diff: 636 rules, of which 590 are not covered by the shipped rule set (2424 rules in 13.4.35). Then I tried to give each one a restFiles reference by matching it against a corpus of TYPO3 changelog entries (3824 entries; 787 of them in the 13.0–14.3.x series).

Result for the 590 rules count share
symbol matched verbatim in an entry 30 5.1 %
only the class name matched 321 54.4 %
nothing matched at all 239 40.5 %
usable as a restFiles reference 45 7.6 %

The 321 class-only hits are mostly coincidence. In a sample of six, five did not mention the member anywhere in the matched document — the class simply appears in an unrelated entry. Entering those as restFiles would show users a wrong explanation, which is worse than none. Relaxing the rule to “class matched and the member name appears somewhere in the same document” raises the yield to 93, but also produces mismatches. The defensible statement is a range:

> 45 to 93 of 590 rules — 8 to 16 % — can be given a changelog reference mechanically.

For the 239 with no match I checked whether they might be documented in an older series (deprecated in v12, removed in v14). Across all 3824 entries exactly 4 more appear, and those are coincidental too.

> 235 of 590 rules — 39.8 % — describe API removals that appear in no changelog entry at all.

Limits of the measurement

  • The corpus is from 16 July 2026, v14.3.7 is from 8 September 2026. Entries added after that are missing, so the range is a lower bound.
  • The corpus was converted to Markdown, so the exact .rst file names are not available. The measurement answers “is there an entry”, not “which file”.
  • The assessment of the class-only hits is a sample: 6 of 321 were read.
  • Only typo3/cms-core was diffed for the rule generation.

Three ways forward

1. Contribute the 45–90 rules that can be given a hand-checked reference. Honest, small, immediately doable — and it covers roughly a sixth of the gap.
2. Change what restFiles requires. For instance: allow a rule without a reference and let the UI say “no changelog entry”; or allow one shared umbrella entry for undocumented removals; or make the display-time lookup non-fatal. This is the decision I am asking about.
3. Write the ~235 missing changelog entries. Arguably the correct answer, but a different order of magnitude, and not something one person does on the side.

I have no preference to push. Option 3 may well be what the team wants, and then the useful contribution of this measurement is simply the number: 235.

A side observation

The display-time check throws RuntimeException 1499803909 when a referenced file is not found. A renamed or removed .rst therefore does not degrade to “link missing” — it makes the whole scan result view fail. That may deserve its own ticket regardless of what is decided here.

What I can contribute

The diff tooling and the mapping script exist and the measurement is reproducible. I am happy to hand over the data, to hand-check the 45–90 references, or to write the patch once there is a direction.

Author Olivier Dobberkau
Created 09/26/26, 20:51
Updated 11/13/26, 09:23
Epic
New Fresh

#93528 Backlog of UX ideas for Editors

This ticket serves as an umbrella for ideas on how to enhance the UX for editors.

Feel free to create/attach subtasks if you get such feedback from your editors/clients.

Author Xavier Perseguers
Created 02/17/21, 10:12
Updated 11/13/26, 08:54
Feature
Under Review Fresh Link Handling & Redirect Handling

#109530 Add additional link attributes to link browsers/link handlers

Currently, the amount of available link attributes in the link browsers/handlers is very scarce (‘target’, ‘title’, ‘class’, ‘params’, ‘rel’ (and I see download is being added)). There also seems to be no trivial and official way to modify them yourself in any way, other than having to directly modify the core.

Especially when we look at accessibility for example, editors definitely should be able to set basic aria attributes like ‘aria-label’s.
Now, since there are (or perhaps in the future will be) a lot of possible attributes which could be added, I suggest some type of configuration or event that offers developers the possibility to add additional link attributes and extend the current list of allowed ones. Or, from an accessibility standpoint, to at least add the aria-label attribute to the link browsers/handlers.

Author Lennart Radloff
Created 04/09/26, 13:22
Updated 11/13/26, 07:22
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 13

#108634 Inactive input fields, placeholder and toggle switches-insufficient contrast

Input fields with placeholder text and states such as “disabled”, as well as toggle switches, currently show insufficient color contrast. Text requires at least 4.5:1 contrast (WCAG 2.1 – 1.4.3), non‑text UI elements (e.g., toggle indicators, outlines) require at least 3:1 (WCAG 2.1 – 1.4.11). 

Reproduction Steps

  1. Open any form page. (e.g. page or content element)
  2. Locate a disabled input containing placeholder text.
  3. Display a toggle switch in inactive/active state.
  4. Measure contrast between text/placeholder and background, and between UI element and background using a contrast tool (e.g., Axe/DevTools).
  5. Current contrast falls below required thresholds.

Impact

  • Users with low vision struggle to perceive states and content; the implementation fails WCAG 2.1 and creates compliance risk. 

Recommended Solution

  • Adjust placeholder and disabled state colors so that text achieves at least 4.5:1 against its background.
  • Adjust toggle outlines/fills/indicators to achieve at least 3:1 against adjacent background.
  • Update design tokens/CSS variables centrally and roll out across affected components. 

Definition of Done

  • All affected components (inputs incl. placeholders, disabled states, toggles) use updated colors.
  • Contrast checks confirm ≥4.5:1 for text and ≥3:1 for non‑text UI in all states and themes (light/dark). 

Acceptance Criteria

  • Placeholder text, input text, labels, and error messages meet ≥4.5:1 against background. 
  • Disabled inputs remain perceivable and meet ≥4.5:1 for text; decorative elements excluded. 
  • Toggle switches (track/knob/outline) meet ≥3:1 against adjacent background for active/inactive/focus/hover. 

References

Author Christian Jung
Created 01/14/26, 15:21
Updated 11/13/26, 07:16
Bug
Author Oliver Bartsch
Assigned to Juliane Wundermann
Created 02/05/26, 14:49
Updated 11/12/26, 21:59
Bug
Under Review Fresh File Abstraction Layer (FAL) TYPO3 CMS 14

#111137 Copying a file does not copy translated metadata

When a file is copied, only the metadata of the default language is copied. The translated metadata records of the source file are lost.

Steps to reproduce
  1. Add a title to a file, then translate its metadata into another language
  2. Copy the file into another folder
  3. Open the metadata of the copy: only the default language record exists

*Expected*
The copy gets the translated metadata records, too.

*Cause*
@ResourceStorage::copyFile()@ copies $file->getMetaData()->get(). This is a single record, resolved for the current language. Records with sys_language_uid > 0 are not copied.

This also affects copying a folder, which uses the same code since #111081.

Author Wolfgang Klinger
Assigned to Wolfgang Klinger
Created 10/19/26, 06:10
Updated 11/12/26, 21:13
Bug
Under Review Fresh File Abstraction Layer (FAL) TYPO3 CMS 15

#111081 Copying a folder in filelist does not copy metadata of contained files (while single file copy does)

When a user copies a folder via the filelist module (copy → paste into another folder), the metadata (title, description, alternative, etc.) of all contained files is lost. Copying the same files individually works correctly and preserves metadata.

*Steps to reproduce*
1. Upload a few files to fileadmin/some_folder/
2. Edit their metadata (set title and description)
3. Copy the folder some_folder/ and paste it into another storage location
4. Open the copied files and check their metadata: title and description are empty

*Expected behaviour*
Metadata (title, description, alternative, etc.) of contained files should be copied to the new files — exactly as it happens when copying a single file.
Actual behaviour
- The physical files are copied on disk.
- The copied files are not indexed into sys_file during the operation.
- When later indexed (lazy/on browse or via the File Storage Indexing scheduler task), MetaDataRepository::createMetaDataRecord() creates an empty sys_file_metadata record (only file uid + timestamps).
- All manually-set metadata fields are lost.

*Root cause*
There is an inconsistency between ResourceStorage::copyFile() and ResourceStorage::copyFolder():

copyFile() (typo3/sysext/core/Classes/Resource/ResourceStorage.php:1959-1965) explicitly copies the source file’s metadata inline:

if ($file instanceof File && $newFileObject !== null) {
    $metaDataAspect = $newFileObject->getMetaData();
    $metaDataAspect->add(array_replace($file->getMetaData()->get(), $metaDataAspect->get()));
    $metaDataAspect->save();
}

copyFolder() (ResourceStorage.php:2327-2367) does not:

- It only calls $this->driver->copyFolderWithinStorage() (line 2356), which performs a raw filesystem copy (LocalDriver::copyFolderWithinStorage() at Driver/LocalDriver.php:1075, using PHP copy()).
- It never calls getAllFileObjectsInFolder() to enumerate contained files.
- It never calls the indexer to create sys_file records.
- It never copies sys_file_metadata records.

By contrast, moveFolder() (line 2265) does iterate contained files via getAllFileObjectsInFolder() (line 2276) and calls $this->getIndexer()->updateIndexEntry($fileObject) (line 2296). copyFolder() skips all of this.

The AfterFolderCopiedEvent is dispatched (lines 2362-2364) but:
- It carries no source→target file identifier mapping (so a listener would have no way to associate copied files with their sources).
- It has zero registered listeners anywhere in the core (confirmed across all sysext *.yaml and *.php files).
The driver-level copyFolderWithinStorage() also returns only a boolean true, unlike moveFolderWithinStorage() which returns an old→new identifier $identifierMap.

*Additional context*
- There is an existing functional test copyFileCopiesMetadata() in typo3/sysext/core/Tests/Functional/Resource/StorageRepositoryTest.php:543 verifying metadata copy for single files, but no equivalent test for folder copy.
- copyFolderBetweenStorages() is not implemented (throws NotImplementedMethodException), so this only affects same-storage folder copy.

*Suggested fix*
@ResourceStorage::copyFolder()@ should, after the driver copies the folder:
1. Enumerate source files via getAllFileObjectsInFolder($folderToCopy).
2. For each source file, locate the corresponding copied file in the target folder and either call $this->copyFile(...) (which already handles metadata) or replicate the metadata-copy logic from copyFile() lines 1959-1965.
3. The driver’s copyFolderWithinStorage() should return an old→new identifier map (like moveFolderWithinStorage() already does) so the storage layer can associate copied files with their sources.
Alternatively, copyFolder() could loop over source files before the driver call and call copyFile() for each file individually, leaving only directory creation to the driver.

Author Philipp Kitzberger
Created 10/15/26, 13:47
Updated 11/12/26, 21:13
Epic
In Progress Fresh Backend User Interface

#90674 Backend UI not reflecting permissions

This is an umbrella Epic for the issues about the flaws of UI where permissions and allowances of non-admin backend users are not checked properly.

Author Riccardo De Contardi
Created 03/07/20, 17:08
Updated 11/12/26, 18:35
Feature
Under Review Fresh Backend User Interface

#100976 Improve UX of Reports module

Gathering the details of the checks executed when a user accesses the backend module System → Reports → Status Reports takes some time. Especially on a slow system or if the user accesses the backend from a distance (latency). If the user switches the dropdown box at the top from, for example, Overview to Status Report, nothing happens for a few seconds, before the results are shown.

An enhancement of the user experience would be a rework of the module, so that the page appears straight away and the checks are executed by Ajax requests. One check at a time. The results are shown dynamically. An animated loading spinner for each check could indicate that the system works in the background.

Author Michael Schams
Created 06/08/23, 07:40
Updated 11/12/26, 17:02
Bug
Under Review Fresh TYPO3 CMS 15

#111411 fe_group of page translations is editable but not synchronized from the default language

Since #104311, the fe_group column of pages is generated by the TCA enrichment. The column lost its 'l10n_mode' => 'exclude' setting, which was part of the static pages TCA up to v12.4.

As a result, the “Usergroup Access Rights” field (fe_group) can be edited on a page translation, and the value is saved. The frontend ignores it, because access to a page is evaluated only on the default language record (see PageRepository::getPageOverlaysForLanguage()). Editors get no indication that the setting has no effect.

Steps to reproduce

  1. Create a page in the default language without access restrictions.
  2. Create a translation of that page.
  3. On the translation, set “Usergroup Access Rights” to e.g. “Show at any login” and save.
  4. Open the translated page in the frontend without being logged in.

Expected

fe_group is synchronized from the default language page and can’t be edited on the translation, as in v12.4.

Actual

The field can be edited on the translation, but the translated page stays accessible without login.

Author Torben Hansen
Assigned to Torben Hansen
Created 11/11/26, 15:00
Updated 11/12/26, 14:42
Bug
Under Review Fresh FormEngine aka TCEforms TYPO3 CMS 14

#107112 TCA: onChange on link fields not possible

Given:

- Reload on a link field, eg tt_content/header_link

`$GLOBALS[‘TCA’][‘tt_content’][‘columns’][‘header_link’][‘onChange’] = ‘reload’;`

Expected:

- After a link is chosen in the link browser, the reload modal should be visible and the editor is able to trigger the reload

Actual:

- The reload modal is shown twice and the editor is not able to click on any button

Investigation:

- Configuring an ‘onChange’ option in TCA results in a change-Handler in JavaScript (Build/Sources/TypeScript/backend/form-engine/request-update.ts:38)
- When a link target is select, the FormEngineLinkBrowserAdapter triggers a change event (Build/Sources/TypeScript/backend/form-engine-link-browser-adapter.ts:83) and afterwards the form field value is changed due to FormEngine.processOnFieldChange (Build/Sources/TypeScript/backend/form-engine-link-browser-adapter.ts:88 // ‘typo3-backend-form-update-value’ is triggered) which triggers another change event on that field
- both modals are added to the DOM but setting the z-index on the second modal backdrop fails due to wrong nextElementSibling (Build/Sources/TypeScript/backend/modal.ts:594)

Author Nicole Hummel
Created 07/18/25, 10:28
Updated 11/10/26, 19:59
Bug
Under Review Fresh Extension Manager TYPO3 CMS 13

#108513 Failed to upload or install extension by Classic mode TYPO3 installation

When the Extension Manager option “Install extensions automatically after download from TER or file upload” (basic.automaticInstallation) is enabled,
uploading an extension ZIP in TYPO3 classic mode (source package installation without a Composer-based project) often fails with errors like “Extension <extension_key> is not available”.</extension_key>

In multiple cases the extension files are already extracted to typo3conf/ext/, but the extension is shown as inactive (gray) or fails on manual installation with class/autoload errors (PSR-4 not resolved, incomplete or empty autoload_psr4.php / autoload_classmap.php).
Even though PSR-4 autoload is correctly defined in the extension (via composer.json or ext_emconf.php), these autoload definitions are sometimes removed or ignored automatically during the failed installation attempt, leading to missing classes.

It appears that TYPO3 attempts to install the extension before ZIP extraction and package information/autoload data are fully available, resulting in a broken extension state. Disabling automatic installation and installing the extension manually after upload works reliably.

This seems related to an older issue describing the same behavior:

https://forge.typo3.org/issues/100730

Author Yassine Berqiqch
Created 12/18/25, 09:20
Updated 11/10/26, 19:38
Bug
Under Review Fresh Extension Manager TYPO3 CMS 12

#100730 Unable to upload extensions in ExtensionManager

Version: 12.3.0

When uploading an extension from TER in the Extension manager, I always get error messages like this one:
“Extension typo3_console is not available”.

The problem seems to be the if-condition here:
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/Package/PackageManager.php#L1030-L1036

The method has already been called before the ZIP file has been extracted and therefore, the “$this->packagesBasePaths” variable already contains the system extensions and scanning the directories for the new uploaded and extracted extension is skipped.

Author Aimeos no-lastname-given
Created 04/24/23, 14:58
Updated 11/10/26, 19:38
Bug
Under Review Fresh Backend JavaScript TYPO3 CMS 13

#107301 Drag and drop operations in the page tree do not trigger a ContentContainer refresh.

Description

For example, if you cut a page using the context menu of the page tree and paste it elsewhere, the ContentContainer is reloaded afterwards. If you perform the same operation using drag and drop, the subsequent reload is omitted. This means, for example, that no Flash messages are displayed after drag and drop operations in the PageTree.

Thanks for the great work on TYPO3 and all the effort

Author George Miller
Created 08/16/25, 14:55
Updated 11/10/26, 18:22
Feature
Under Review Fresh Backend User Interface

#111292 Compare every page preview with the live page and merge the workspace preview into the preview bar

Problem

The workspace preview is a page of its own (route workspace_previewcontrols) with its own top bar. It has no simulation (date, hidden pages and content, frontend login), and editors outside a workspace cannot compare a preview with the live page at all. Since #110664 every backend preview runs on the preview page with a bar above the frame, so two different preview pages exist.

Proposal

  • The preview page of the backend is the only preview page. Its bar gets a menu “Compare with live”: Off, Slider, Side by side, Stacked. Off is the default, the chosen mode is stored per backend user.
  • The live frame shows the page as a visitor sees it now: no workspace, no hidden records, current date, no frontend login. It follows the preview to other pages and keeps the scroll position at the same element, matched by its HTML id, or at the same percentage.
  • The live frame of the slider keeps the full height and is clipped, so its content does not reflow; the divider between the frames can be dragged or moved with the keyboard.
  • In a workspace the bar shows the stage, publish and discard buttons, added by EXT:workspaces through a new PSR-14 event BeforePreviewPageRenderedEvent. The former route workspace_previewcontrols redirects to the preview page. The bar shows no frontend address any more.
  • New Page TSconfig options.preview.compareModes (slider, columns, rows); workspaces.splitPreviewModes is deprecated and still read as fallback.

Notes

Follow-up of #110664. Depends on #111290 (publishing from the workspace preview).

Author Matthias Vogel
Created 10/30/26, 14:06
Updated 11/10/26, 10:22
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 13

#109623 click on bookmark missing page tree scroll

When I click on a bookmarked page in the TYPO3 backend (TYPO3 bookmark! – no browser bookmark) I noticed that
1) the page on the right side changes to the bookmarked page and
2) the page is correctly highlighted in the page tree

but what’s missing is that the page tree scrolls, so that the bookmarked page is visible/in the view in the tree.

So the user has to scroll manually in the page tree.

Use Case:
If you have a documentation in the backend then you bookmark just the main page of the documentation, so I expected that the page tree also scrolls so that the highlighted page is in the view, visible for the user.

Not sure if that is the intended behaviour but as an editor I would have expected that I also see the page visible in the page tree.

Author David Menzel
Created 04/17/26, 10:44
Updated 11/10/26, 07:43
Bug
Under Review Fresh DataHandler aka TCEmain TYPO3 CMS 14

#111353 Copying a translated record creates duplicate translations of records referenced with localizeReferencesAtParentLocalization

If a select or group field is configured with localizeReferencesAtParentLocalization = true, copying a record together with its translation creates a new translation of every record referenced in this field, although the referenced translation already exists. Every further copy adds another duplicate.

The backend shows only one translation of the referenced record, because translation lookups use LIMIT 1. In the select field of the translated record, however, the duplicates show up as additional, identical items.

Preconditions

  • A site with a default language (0) and a second language (1)
  • Two language-aware tables, e.g. tx_news_domain_model_news and tx_eventnews_domain_model_organizer
  • A select (or group) field without MM that references the second table, with localizeReferencesAtParentLocalization enabled:
$GLOBALS['TCA']['tx_news_domain_model_news']['columns']['organizer']['config'] = [
    'type' => 'select',
    'renderType' => 'selectSingle',
    'foreign_table' => 'tx_eventnews_domain_model_organizer',
    'localizeReferencesAtParentLocalization' => true,
];

Steps to reproduce

  1. Create an organizer (uid 1) in the default language and translate it into language 1 (uid 2).
  2. Create a news record in the default language with organizer = 1.
  3. Translate the news record into language 1. The translation correctly references organizer = 2.
  4. Copy the default language news record (e.g. copy & paste in the list module). Its translation is copied as well.

Expected result

The copied translation references the existing organizer translation (uid 2). No new organizer record is created.

Actual result

A new organizer record (uid 3, sys_language_uid = 1, l10n_parent = 1) is created, and the copied translation references it. Every further copy creates another one.

Cause

When the translation is copied, copyRecord_processManyToMany() is called with $language = 1. The field value already contains the translated uid 2. The method looks for a translation of uid 2 in language 1 (l10n_parent = 2), finds none and calls localize() for uid 2. localize() takes over the l10n_parent of uid 2 (= 1) and creates another translation of uid 1.

Author Peter Kraume
Created 11/05/26, 16:27
Updated 11/10/26, 06:19

Showing results 551 to 575 of 1561