Showing results 676 to 700 of 1561

Task
Under Review Stale TYPO3 CMS 15

#110464 Deprecate QueryBuilder::castFieldToTextType

ExpressionBuilder::castText() is its replacement.
Fix the remaining 4 callers so no core usages are left.

Author Wouter Wolters
Assigned to Wouter Wolters
Created 08/12/26, 20:16
Updated 08/12/26, 20:19
Bug
Under Review Stale Backend API TYPO3 CMS 13

#110369 Remove internal from public API for backend preview

TYPO3 has a way to alter the rendering of TCA records via a public API as documented at: https://docs.typo3.org/permalink/t3tca:confval-ctrl-previewrenderer. This references the public Interface TYPO3\CMS\Backend\Preview\PreviewRendererInterface https://docs.typo3.org/permalink/t3coreapi:configurece-preview-preview-renderer which I would consider public API.

This interface now has type hints to classes which are marked as @internal, leading to a public API forcing users into using internal API, which seems incompatible to me.

So either the whole concept and interface is not public yet, or the internal classes should become public, which I would prefer.

Mainly: TYPO3\CMS\Backend\View\BackendLayout\Grid\GridColumnItem @internal this is experimental and subject to change in TYPO3 v10 / v11

But it would also be cool if other classes can be made public as well, as it is very likely that those will be used in that context:
- TYPO3\CMS\Backend\View\BackendLayout\Grid\Grid @internal this is experimental and subject to change in TYPO3 v10 / v11
- TYPO3\CMS\Backend\View\BackendLayout\Grid\GridRow @internal this is experimental and subject to change in TYPO3 v10 / v11
- TYPO3\CMS\Backend\View\BackendLayout\Grid\AbstractGridObject @internal this is experimental and subject to change in TYPO3 v10 / v11

This was reported by PHPStan and reveals that developers need to take extra care during each update to check compatibility.

Author Daniel Siepmann
Created 08/04/26, 08:17
Updated 08/11/26, 09:44
Feature
New Stale Frontend

#110411 Hide in default - for content elements

There are various issues with copying content from a page / language in connected mode to a page / language in free mode, e.g. #109624 #90610
One translation loophole was closed in v14 with invoking the translation dialogue when translating an element, but copy/pasting is still a problematic action.

In one of my projects we accidentally ended up with quite some pages in mixed mode and they are very hard to debug and clean up.
Maybe the technical aspects were not clear to the users and initially the frontend looked right, thus the errors only showed up later as work on the content started again and content was moved around.

My proposal is: we should provide a way to make Free Mode for content an exception or an explicit choice when a page/translation is set up as you can not easily revert your decision later. Converting a connected / mixed language to free may work, but the other way around is a nightmare when container elements etc. are involved.

Pages can already be configured to be hidden in default, only translations show up. Thus it would be great to have a similar feature also for content.
—> All content can / must be created in default and localized / translated as needed, so the usage of Free Mode can hopefully be limited to a very few exceptions, e.g. pages that have totally different content or only have content in sys_language_uid > 0

Author Andreas Kießling
Created 08/10/26, 16:01
Updated 08/10/26, 16:01
Bug
New Stale Localization TYPO3 CMS 10

#90610 Copy-pasting a record that's already translated in "connected" mode, to a different language causing "free" mode, creates duplicate(s) in "connected" translations

Steps to reproduce:

  • Have at least three languages.
  • Start with an empty page translated to at least three languages.
  • Create content record in original language.
  • Translate to “Connected” mode for one language.
  • Copy (context-menu “copy”) the original language version.
  • Click the “paste” icon in a third language.

Expectation:

  • One “free mode” copy of the original language record is created in the third language.
  • Visually – one content record exists in each of three languages; one in original language, one in “connected” mode language and one in “free” mode language.

Observed incorrect behavior:

  • One “free mode” copy of the original language record is created in the third language
  • All translated versions of original language record now have a duplicate
  • Visually – one content record exists in original language, TWO exist in “connected” mode language, one exists in “free” mode language.

Cause:

  • TYPO3 perceives the “paste” operation to a different language the same as had the record been pasted in original language.
  • TYPO3 therefore attempts to synchronise localized versions of the copy when it should be disconnected; exists in a different language that is NOT the source of localisation.
Author Claus Due
Created 03/01/20, 23:51
Updated 08/10/26, 14:14
Bug
Under Review Stale Image Cropping TYPO3 CMS 6.2

#58705 data-type-gettext-file inside FILES renderObj GIFBUILDER

Is it a normal behavior that data-type-gettext-file is not accessible inside the following structure?

uid:46 is a valid image file.

page >
page = PAGE

page.10 = FILES
page.10 {
  files = 46

  renderObj = IMAGE
  renderObj.file = GIFBUILDER
  renderObj.file.XY = 400,400
  renderObj.file.10 = IMAGE
  renderObj.file.10.file {
    import.data = file:current:publicUrl
    width = 400c
    height = 400c
  }
}

Save publicUrl to a register to access it later works:

page.20 = FILES
page.20 {
  files = 46

  renderObj = COA
  renderObj {
    1 = LOAD_REGISTER
    1.publicUrl.cObject = TEXT
    1.publicUrl.cObject.data = file:current:publicUrl

    10 = IMAGE
    10 {
      file = GIFBUILDER
      file {
        XY = 400,400

        10 = IMAGE
        10.file {
          import.data = REGISTER:publicUrl
          width = 400c
          height = 400c
        }
      }
    }
  }
}
Author Christian Stern
Created 05/12/14, 08:16
Updated 08/08/26, 22:44
Bug
Under Review Stale Themes TYPO3 CMS 14

#110388 Missing dependency for typo3/theme-camino

Camino uses typo3/cms-impexp but does not require this dependency in composer. If this package is not installed, typo3 extension:setup fails with a cryptic message:

[WARNING] theme_camino contains data to be imported, but the required component is not installed. Make sure to define corresponding requirements.                                                                                  
Author Dmitry Dulepov
Created 08/06/26, 20:23
Updated 08/08/26, 16:07
Feature
Under Review Stale Backend User Interface

#103515 Add an option to render filter field above reach SelectCheckBoxElement

To enhance usability of the SelectCheckBoxElement, especially with lengthy lists, an option (TCA) should be available to display a filter field above each element of this type.

This feature should accommodate both flat lists and grouped lists (rendered using tables):

  • Typing in the filter field should display only items that match the entered text.
  • If no items match the filter text and there are multiple item groups, the list should be hidden.
  • For a single list without groups, if no items match the filter text, the list should appear empty.

This work is part of the ACL Improvements Phase 2 .

Author Marcin Sągol
Assigned to Marcin Sągol
Created 04/02/24, 06:41
Updated 08/07/26, 19:37
Bug
Under Review Stale RTE (rtehtmlarea + ckeditor) TYPO3 CMS 14

#109254 No link resolving in RTE table caption

TYPO3 v14 is also affected but the problem started with CKEditor 5 in TYPO3 v13.

Links inserted within table captions using the RTE are not resolved – they display the t3:// URI format instead of being converted to proper frontend URLs.

Steps to reproduce the problem:
  1. Create a new content element with RTE field
  2. Insert a table using the table toolbar button
  3. Add a caption to the table using the table caption feature
  4. Insert a link within the table caption text
  5. View the page in frontend

*Expected Behavior*
The link within the table caption should have a proper frontend URL in the href attribute.

*Actual Behavior*
The link within the table caption contains the internal TYPO3 URI format in the href attribute (e.g., href=“t3://file?uid=123” or href=“t3://page?uid=456”).

Author Ulrich Mathes
Created 03/16/26, 09:42
Updated 08/07/26, 17:42
Feature
Under Review Stale

#110383 Site settings cache location

It should be possible to put site settings cache inside database, while the current file based solution stays the default. It’s relevant for cluster environments

Author Sven Liebert
Assigned to Sven Liebert
Created 08/06/26, 16:07
Updated 08/07/26, 15:14
Task
Under Review Stale TYPO3 CMS 14

#107707 Imprecise title for search dialog button (mobile)

The title attribute for the search dialog button in topbar, which is only available on mobile view, is not precise enough:

It no longer serves as toggle, but rather only opens the search window.

Author Elias Häußler
Assigned to Elias Häußler
Created 10/15/25, 12:58
Updated 08/07/26, 14:12
Feature
Under Review Stale Backend User Interface

#104034 Allow to preview forms based on backend group permissions

Managing permissions in TYPO3 is often a time-consuming task, especially when verifying that a given group has access only to the appropriate form fields of a specific record.

To make this process easier for integrators, it would be beneficial to have an option to preview a form when editing backend group permissions. This way, integrators can grant permissions to certain fields and instantly verify if they appear in the form and how the entire form looks.

Author Marcin Sągol
Assigned to Marcin Sągol
Created 06/11/24, 07:19
Updated 08/06/26, 22:27
Feature
Under Review Stale

#109383 Allow overriding wizard steps

It should be possible to extend the existing steps using events.
An example use-case can be found in the initial desgin.
In this design it was possible to select page presets.

To cover this kind of uc an event to modify the existing step data should be added.
Also it would be great to be able to modify the page data before persisiting.

Author Bastien Lutz
Assigned to Bastien Lutz
Created 03/26/26, 14:54
Updated 08/06/26, 21:36
Bug
Under Review Stale File Abstraction Layer (FAL) TYPO3 CMS 13

#109630 Predefined value options for `sys_file_metadata.color_space` are wrong and incomplete

The accepted values for sys_file_metadata.color_space are defined as:

[
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.RGB', 'value' => 'RGB'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.sRGB', 'value' => 'sRGB'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.CMYK', 'value' => 'CMYK'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.CMY', 'value' => 'CMY'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.YUV', 'value' => 'YUV'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.grey', 'value' => 'grey'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.indx', 'value' => 'indx'],
]

They date back to https://github.com/TYPO3/typo3/commit/df73316a942141418285df633c2f0f18dfb59d7b#diff-9351198f2961db2960ea6ffd6589c2317efdb0768cc3ae360e6d0929c74dfe79R361-R366, which was reviewed and approved in https://review.typo3.org/c/Packages/TYPO3.CMS/+/24715/1 on 2013-10-15.

Some of these values are incorrect, and many options are missing.

The incorrect list was carried over from DAM (https://extensions.typo3.org/extension/dam), which defined:

        'color_space' => array(
            'label' => 'LLL:EXT:dam/locallang_db.xml:tx_dam_item.color_space',
            'l10n_mode' => 'exclude',
            'l10n_display' => 'defaultAsReadonly',
            'exclude' => '0',
            'config' => array(
                'type' => 'select',
                'items' => array(
                    array('', ''),
                    array('RGB', 'RGB'),
// This is not a colorspace but a color profile                    array('sRGB', 'sRGB'),
                    array('CMYK', 'CMYK'),
                    array('CMY', 'CMY'),
                    array('YUV', 'YUV'),
                    array('Grey', 'grey'),
                    array('indexed', 'indx'),
                ),
                'default' => ''
            )
        ),

Note that DAM already incorrectly defines 'grey' rather than the canonical 'GRAY', and it incorrectly defines 'YUV' rather than the canonical 'YCbr'.

But DAM correctly excludes sRGB, as sRGB is not a valid ICC color space data signature. (The ICC spec uses ‘RGB ‘ as the signature for any RGB-encoded image, regardless of whether the specific encoding is sRGB, Adobe RGB, ProPhoto, etc. Which specific RGB encoding is in use is conveyed by the attached ICC profile, not by the ColorSpaceData field.)

The conflation of the two was mistakenly introduced in https://github.com/TYPO3/typo3/commit/294a837b2222d1ebdb54337cba2fe6cbebede4ae (reviewed in https://review.typo3.org/c/Packages/TYPO3.CMS/+/44220), resolving https://forge.typo3.org/issues/70946, which was already based on the same incorrect premise.

The incorrect addition of sRGB to the color space list had worked as a band-aid to incorrect assumptions in EXT:extractor, but it must be removed, and metadata extraction fixed by no longer conflating color mode (fixed: https://github.com/xperseguers/t3ext-extractor/issues/89), color profile (unfixed) and color space.

The TYPO3 core’s incorrect color space list has also surfaced as https://github.com/xperseguers/t3ext-extractor/issues/83, although the actual bug is in TYPO3 EXT:filemetadata:

The ColorSpaceData value "GRAY", as observed in EXT:extractor#83, is in fact canonical, while 'grey' defined in https://github.com/TYPO3/typo3/blob/aa737bfbafc09cfd532d93582e5dcd693d5795a9/typo3/sysext/filemetadata/Configuration/TCA/Overrides/sys_file_metadata.php#L413-L419 is incorrect.

Aligning sys_file_metadata.color_space with the canonical ICC definition:

The set of correct values is defined in https://www.color.org/specification/ICC.1-2022-05.pdf in Table 19 — Data colour space signatures, in section 7.2.6 Data colour space field (bytes 16 to 20) on numbered page 21, which maps to physical PDF page 35.

Table 19 — Data colour space signatures

_.Colour space type _.Signature _.Hex encoding
nCIEXYZ or PCSXYZ ‘XYZ ’ 58595A20h
CIELAB or PCSLAB ‘Lab ’ 4C616220h
CIELUV ‘Luv ’ 4C757620h
YCbCr ‘YCbr’ 59436272h
CIEYxy ‘Yxy ’ 59787920h
RGB ‘RGB ’ 52474220h
Gray ‘GRAY’ 47524159h
HSV ‘HSV ’ 48535620h
HLS ‘HLS ’ 484C5320h
CMYK ‘CMYK’ 434D594Bh
CMY ‘CMY ’ 434D5920h
2 colour ‘2CLR’ 32434C52h
3 colour (other than those listed above) ‘3CLR’ 33434C52h
4 colour (other than CMYK) ‘4CLR’ 34434C52h
5 colour ‘5CLR’ 35434C52h
6 colour ‘6CLR’ 36434C52h
7 colour ‘7CLR’ 37434C52h
8 colour ‘8CLR’ 38434C52h
9 colour ‘9CLR’ 39434C52h
10 colour ‘ACLR’ 41434C52h
11 colour ‘BCLR’ 42434C52h
12 colour ‘CCLR’ 43434C52h
13 colour ‘DCLR’ 44434C52h
14 colour ‘ECLR’ 45434C52h
15 colour ‘FCLR’ 46434C52h

ICC.1:2022 © ICC 2022 – All rights reserved

ICC.1:2022 is the current version: https://www.color.org/icc_specs2.xalter

“Signature” is the value which must be saved to sys_file_metadata.color_space. (Trimming avoids roundtrip issues with VARCHAR columns which are auto-trimmed by some databases in some collations.)

The correct values for sys_file_metadata.color_space must therefore be defined as:

[
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.XYZ',  'value' => 'XYZ'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.Lab',  'value' => 'Lab'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.Luv',  'value' => 'Luv'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.YCbr', 'value' => 'YCbr'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.Yxy',  'value' => 'Yxy'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.RGB',  'value' => 'RGB'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.GRAY', 'value' => 'GRAY'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.HSV',  'value' => 'HSV'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.HLS',  'value' => 'HLS'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.CMYK', 'value' => 'CMYK'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.CMY',  'value' => 'CMY'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.2CLR', 'value' => '2CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.3CLR', 'value' => '3CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.4CLR', 'value' => '4CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.5CLR', 'value' => '5CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.6CLR', 'value' => '6CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.7CLR', 'value' => '7CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.8CLR', 'value' => '8CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.9CLR', 'value' => '9CLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.ACLR', 'value' => 'ACLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.BCLR', 'value' => 'BCLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.CCLR', 'value' => 'CCLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.DCLR', 'value' => 'DCLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.ECLR', 'value' => 'ECLR'],
    ['label' => 'filemetadata.db:sys_file_metadata.color_space.FCLR', 'value' => 'FCLR'],
]

dbFieldLength remains unchanged at 4.

The corresponding language labels must be:

  <trans-unit id="sys_file_metadata.color_space.XYZ">
    <source>nCIEXYZ or PCSXYZ</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.Lab">
    <source>CIELAB or PCSLAB</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.Luv">
    <source>CIELUV</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.YCbr">
    <source>YCbCr</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.Yxy">
    <source>CIEYxy</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.RGB">
    <source>RGB</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.GRAY">
    <source>Gray</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.HSV">
    <source>HSV</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.HLS">
    <source>HLS</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.CMYK">
    <source>CMYK</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.CMY">
    <source>CMY</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.2CLR">
    <source>2 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.3CLR">
    <source>3 colour (other than those listed above)</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.4CLR">
    <source>4 colour (other than CMYK)</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.5CLR">
    <source>5 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.6CLR">
    <source>6 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.7CLR">
    <source>7 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.8CLR">
    <source>8 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.9CLR">
    <source>9 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.ACLR">
    <source>10 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.BCLR">
    <source>11 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.CCLR">
    <source>12 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.DCLR">
    <source>13 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.ECLR">
    <source>14 colour</source>
  </trans-unit>
  <trans-unit id="sys_file_metadata.color_space.FCLR">
    <source>15 colour</source>
  </trans-unit>

Migrations:

- grey is migrated to the correct GRAY.
- YUV is migrated to the correct YCbr.
- indx (indexed color) is removed, as it is a storage encoding, not an ICC color space signature. This was a misconception in DAM, conflating color mode/encoding and color space.
- sRGB equally is not an ICC color space signature; it was introduced to work around incorrect assumptions in EXT:extractor and must be fixed there.

Side note regarding indx and color mode conflation:

A separate sys_file_metadata.color_mode could be introduced, but that is out of scope of this bug report, which only aims at cleaning up the cargo cult of incorrect color space definitions, and finally allowing clean mapping from image files’ ColorSpaceData field to sys_file_metadata.color_space, without conflation of concepts.

Side note regarding sRGB:

The legacy and mostly obsolete EXIF ColorSpace tag describes either ICC RGB (tagged “sRGB”, “Adobe RGB”, “Wide Gamut RGB”) or none (tagged “Uncalibrated”). The tag has been superseded by ICC profile embeddings.
Notably, extracting the ICC profile description tag, such as “sRGB IEC61966-2.1” or “Adobe RGB (1998)” is out of scope. If it were in scope, then the obsolete EXIF ColorSpace tag would translate into that additional image file metadata field.

Author Leonie Philine
Created 04/17/26, 12:55
Updated 08/06/26, 20:30
Bug
Under Review Stale Localization TYPO3 CMS 14

#109195 Timezone in f:format.date Viewhelper isn't respected when using pattern

Calling the ViewHelper with a defined timezone and format works correctly.
However, when using pattern instead of format, the formatting does not work as expected. In this case, the date string is always formatted using the PHP default timezone.

*The issue*
In TYPO3\CMS\Core\Localization\DateFormatter , within the format method, the IntlDateFormatter is instantiated without passing the timezone of the date object. As a result, the timezone information from the date object is lost during the formatting process.

*Example fix*
When creating the IntlDateFormatter, the timezone from the date object should be passed explicitly:
@new \IntlDateFormatter($locale, \IntlDateFormatter::FULL, \IntlDateFormatter::FULL, $date->getTimezone(), …);@
This ensures that the formatter uses the correct timezone associated with the date object.

Author Julian Pohl
Created 03/09/26, 20:05
Updated 08/06/26, 19:40
Bug
Under Review Stale Backend User Interface TYPO3 CMS 15

#110386 SVG icons rendered via `<img>` cannot adapt their color for dark mode.

`SvgIconProvider::generateMarkup()` renders the default (non-inline) icon markup as a plain `` tag. Because the SVG is loaded as an external image resource, its content is opaque to the host document: CSS from the page (e.g. `currentColor`, or dark/light backend theme rules) cannot reach into the SVG.

`AbstractSvgIconProvider` already solves this for the `“inline”` markup identifier via `generateInlineMarkup()` / `getInlineSvg()`, which embeds the sanitized SVG directly into the DOM where it can be styled normally. That inline path is only used when a caller explicitly requests `$icon->getMarkup(‘inline’)`, though — the default `$icon->getMarkup()` still returns the `` variant, so those icons don’t adapt correctly between dark and non-dark mode.

Steps to reproduce

1. Render an SVG icon via `SvgIconProvider` using the default markup (no identifier).
2. Switch between dark and light backend mode.

Expected behaviour

The icon adapts its color in both dark and non-dark mode, since the markup is inline SVG and styleable.

Actual behaviour

The default markup renders an `` tag, so CSS color rules cannot affect the icon and it keeps its baked-in SVG color.

Author Tim Weisenberger
Created 08/06/26, 19:26
Updated 08/06/26, 19:28
Task
Under Review Stale Backend User Interface TYPO3 CMS 13

#104048 Merge Acces module into the Backend Users module

The Access module (which will be renamed to Permissions in TYPO3 13) should be merged into Backend Users to have a single and central place where integrators manage permissions.

Author Marcin Sągol
Assigned to Marcin Sągol
Created 06/11/24, 11:27
Updated 08/06/26, 17:04
Bug
New Stale Install Tool TYPO3 CMS 14

#102664 Unneeded/misleading check for character_set_server on MySQL-based databases

The core checks for character_set_server and throws a notice (e.g. in the Environment Status) if it is not one of the utf8 ones, see TYPO3\CMS\Install\SystemEnvironment\DatabaseCheck\Platform\MySql. This check is existing for at least TYPO3 10 to 14, but I think it was in there “forever”.

character_set_server, however, is the SQL service’s global fallback value if no other value is ever specified when creating a specific Database (but there is character_set_client and character_set_connection and character_set_system even).

So this check is misleading. For TYPO3 only the actually persisted character_set_database variable is relevant (the charset of the actually used Database). This value checked as well already.

Imagine this situations:

1) You have 10 Databases, 9 are non-TYPO3-related and need some specific non-utf8-charset. Only the last one is a TYPO3 database which correctly has a utf8-based charset and collation. Then it is meaningful to have the most common charset as the server default.

2) If you have no root server (which is most common) you often can not change these system-wide settings at all.

Why should TYPO3 care about what is happening outside its own relevant environment?

I think this environment check should be dropped without replacement, because it can only cause confusion, is arbirtary (why not character_set_system or character_set_connection?), often not be changed anyways and is irrelevant if the Database itself is consistent (which is checked as well, and the whole DBAL layer ensures this anyways nowadays).

Author S P
Assigned to Stefan Bürk
Created 12/13/23, 07:59
Updated 08/06/26, 16:30
Task
New Stale Backend User Interface TYPO3 CMS 12

#91203 Deleting a page with subpage(s) doesn't mention subpages in modal confirm box

Problem/Description

The modal does not show the proper information, that subpages are also deleted (if your editor user has recursive delete option activated).

Author Josef Glatz
Created 04/27/20, 09:55
Updated 08/06/26, 16:04
Bug
New Stale FormEngine aka TCEforms TYPO3 CMS 11

#94574 TCA type selectSingeBox and selectSingle with size > 1: selected item not in view on open

Reproduce

  1. Use a selectSingleBox in TCA with more than 8 items (e.g. in a FlexForm)
  2. Select one item of the list on the bottom, e.g. item 9
  3. Open the form again

Same can be reproduced with selectSingle and size > 1.

Result

The list is always scrolled to the top. The selected item is not visible.

Expected behaviour

The selected item should be in the visible area, meaning the list should scroll down on open. This is the default behaviour using the pure HTML,e.g.

<select name="data[tt_content][366][pi_flexform][data][sDEF][lDEF][settings.selectSingleBox][vDEF][]" multiple="multiple" onchange="TBE_EDITOR.fieldChanged('tt_content','366','pi_flexform','data[tt_content][366][pi_flexform][data][sDEF][lDEF][settings.selectSingleBox][vDEF]');" id="tceforms-multiselect60f3b3b59cc51299281504" class="form-select " data-formengine-validation-rules="[{&quot;type&quot;:&quot;select&quot;,&quot;minItems&quot;:0,&quot;maxItems&quot;:99999}]">
<option value="0">List option 1 [0]</option>
<option value="1">List option 2 [1]</option>
<option value="2">List option 3 [2]</option>
<option value="3">List option 3 [3]</option>
<option value="4">List option 4 [4]</option>
<option value="5">List option 5 [5]</option>
<option value="6">List option 6 [6]</option>
<option value="7">List option 7 [7]</option>
<option value="8">List option 8 [8]</option>
<option selected="selected" value="9">List option 9 [9]</option>
<option value="10">List option 10 [10]</option>
</select>

Author Sybille Peters
Created 07/18/21, 05:08
Updated 08/06/26, 16:03
Bug
Accepted Stale Install Tool TYPO3 CMS 10

#93221 Environment status: error message for disable_functions ist not helping

My hoster currently has proc_open included in the disable_functions, this causes errors with the new Symfony mailer.

They do show up in the error log:
_Core: Error handler (FE): PHP Warning: proc_open() has been disabled for security reasons in /var/www/foo/bar/vendor/symfony/mailer/Transport/Smtp/Stream/ProcessStream.php line 41_

However, the error message from the Environment module does not help at all
> Some PHP functions disabled
> disable_functions=passthru shell_exec system proc_open popen parse_ini_file show_source These function(s) are disabled. TYPO3 uses some of those, so there might be trouble. TYPO3 is designed to use the default set of PHP functions plus some common extensions. Possibly these functions are disabled due to security considerations and most likely the list would include a function like exec() which is used by TYPO3 at various places. Depending on which exact functions are disabled, some parts of the system may just break without further notice.

I’d expect to get a more detailed information, so i can tell my hoster what to change and why that setting is needed, before i get the first error in the log

Author Andreas Kießling
Created 01/05/21, 14:54
Updated 08/06/26, 16:03
Bug
New Stale Backend User Interface TYPO3 CMS 10

#92909 Page Translation list is not orderable, but is rendered always in first position

In the list view for translated pages the “Page Translation” list is always on top.

In the daily work of content editors this list will hardly ever be the most important one, but there is no possbility to reorder it, because mod.web_list.tableDisplayOrder doesn’t have any effect on it.

The fact that you also can’t really collapse it (#92907) makes the situation worse.

Author Sebastian Michaelsen
Created 11/23/20, 15:24
Updated 08/06/26, 16:03
Bug
Under Review Stale System/Bootstrap/Configuration TYPO3 CMS 13

#110111 Maintenance module crashes when settings.php is not writable

I am referring to the previously closed bug report at https://forge.typo3.org/issues/103702

I was able to reproduce the bug when integrating a TYPO3 system as a read-only Docker container. It occurs when `settings.php` contains configurations for a Composer package that does not exist on the current system. In our case, the configuration for `EXT:filefill` was present, but the extension itself was missing from the production system.

`LayoutController->executeSilentExtensionConfigurationSynchronizationAction()` then attempts to remove the configuration from `settings.php` which fails.

Steps to reproduce:

Add a configuration in the EXTENSION section:

        'foo' => [
            'bar' => '1',
        ]

Chmod the settings.php to readonly.

Open the Maintenance modul.

Author Hendrik F.
Assigned to Maike Kiebele
Created 06/26/26, 12:00
Updated 08/06/26, 16:02
Bug
New Stale Backend User Interface TYPO3 CMS 13

#109994 Show newly created (e.g. copy pasted) content element - even when hidden elements are hidden

A newly created (e.g. copy pasted) content element should be always visible – even when hidden elements are hidden in Content Page view.

Otherwise you copy-paste a CE and keep wondering why nothing happens and no error is shown.
(The CE is technically created, but not visibly shown.)

Author Ayke Halder
Created 06/03/26, 16:54
Updated 08/06/26, 16:02
Task
Under Review Stale Extbase TYPO3 CMS 14

#109606 Pull down the UID and PID accessors of AbstractDomainObject

Avoid warnings about accesses to internal methods.

Author Oliver Klee
Assigned to Oliver Klee
Created 04/16/26, 14:30
Updated 08/06/26, 16:02
Task
Under Review Stale DataHandler aka TCEmain TYPO3 CMS 15

#109304 Add workspace regression coverage for language-all clipboard paste

Summary

The TYPO3 Core already contains a dedicated DataHandler guard for language-all records (sys_language_uid = -1) in the extended paste command path:

if ($row[$languageField] === -1 && (int)$languageId === 0) {
    $value['update'][$languageField] = $row[$languageField];
}

The live clipboard paste scenario is already covered by functional tests. However, the corresponding workspace copy scenarios are still missing.

Context

Relevant runtime path:

This path can process an all-language content element while the page layout UI sends update[sys_language_uid] = 0 for the target column. The guard ensures that the copied record stays -1 instead of being downgraded to default language.

Missing coverage

Dedicated workspace copy coverage is missing for:

  • draft workspace state
  • publish of the copied workspace record
  • publish all workspace changes
  • discard of the copied workspace record

Proposed solution

Add functional regression coverage for the workspace variants of the existing language-all clipboard paste scenario.

The following tests should be added:

  • WorkspacesModify::copyLanguageAllContent()
  • WorkspacesPublish::copyLanguageAllContent()
  • WorkspacesPublishAll::copyLanguageAllContent()
  • WorkspacesDiscard::copyLanguageAllContent()

Existing live reference:

Acceptance criteria

  • Functional tests exist for all relevant workspace copy variants
  • The copied record remains sys_language_uid = -1 in all covered scenarios
  • Publish, publish-all, and discard behavior are asserted explicitly
Author Eric Harrer
Assigned to Eric Harrer
Created 03/20/26, 12:24
Updated 08/06/26, 16:02

Showing results 676 to 700 of 1561