Showing results 701 to 725 of 1561

Bug
New Stale Workspaces TYPO3 CMS 13

#108958 user sees custom stages despite no stage permissions - disable or hide those stages in the dropdown

We want to use CUSTOM workspaces with several users and each user has either the permissions for one or more stages.

An example would be the following user:

The user has the permission only for CUSTOM STAGE 3 but not for Bearbeiten, CUSTOM STAGE 1/2 or Bereit zum Veröffentlichen (see screenshot)

Now, the changed record is in the stage CUSTOM STAGE 1 and the user sees every stage the record can be send to.
When he chooses for example one of the stages Bearbeiten, CUSTOM STAGE 1/2/3 or Bereit zum Veröffentlichung, the modal with the email selection appears and after clicking the “OK” button, the modal disappears and the record stays in CUSTOM STAGE 1 because the user has no permission for CUSTOM STAGE 1. So this is correct but also confusing for the user.

Why show every step when he has only the permission for CUSTOM STAGE 3.

I would suggest to disable all stages in the dropdown menu, when the permission don’t allow it that the selected record can be sent to a certain stage, so it’s clear for the user what he can do or not. If multiple records are selected, one in CUSTOM STAGE 1 and one in CUSTOM3 STAGE 3 then the dropdown should still disable all options because it’s not possible for this user to send all selected records to the choosen custom stage.

I also noticed the filter dropdown, where users can filter the records for certain stages. Maybe it’s possible to pre-select the filters based on the stages the user has permission for (multiple options have to be possible) so that the user only sees the records in the stages he has permission for from the beginning.

Author David Menzel
Created 02/12/26, 12:38
Updated 08/06/26, 16:02
Bug
New Stale Backend User Interface TYPO3 CMS 14

#108900 messages.xlf files are ignored by the new label syntax with domains

Test to reproduce the issue:

the labels defined in sysext/scheduler/Resources/Private/Language/messages.xlf

Are used in

sysext/scheduler/Resources/Private/Partials/GroupUnusedList.fluid.html
sysext/scheduler/Resources/Private/Partials/TaskList.fluid.html

as the body message of the modals triggered when you delete a task or a group, but they are ignored and the modal writes a generic “Are you sure?” that looks
like a fallback…

Please note that if you rename the messages.xlf file into whatever.xlf, then change the domain accordingly in the partials, it works.

Author Riccardo De Contardi
Created 02/08/26, 10:08
Updated 08/06/26, 16:02
Bug
New Stale Workspaces TYPO3 CMS 13

#108614 Workspace preview does not shrink down to mobile sizes

Under certain circumstances (e.g. with new pages), there is a notice displayed “The previewed page has been created in a workspace and has no live counterpart.”

This notice is very wide and disallowed by CSS from wrapping, thus the whole page including the preview iframes is wider than the viewport if you shrink down to mobile sizes (300-400px wide). See attached screenshot for an example.

Author Andreas Wolf
Created 01/09/26, 15:56
Updated 08/06/26, 16:02
Bug
Under Review Stale Backend JavaScript TYPO3 CMS 13

#108333 "Show hidden content elements" and Flex "Toggle all" buttons don't work when clicking directly on the icon

Buttons don’t work when clicking directly on the icon.

“Show hidden content elements”

Flex’ “Toggle all”

Author Ayke Halder
Created 11/26/25, 19:28
Updated 08/06/26, 16:02
Bug
New Stale Backend User Interface TYPO3 CMS 13

#108238 Deleting a record with translation does not mention the deletion of translations

TYPO3 13.4 actual situation

  1. you select multiple / all records
  2. visually only the source records are stated als “selected”
  3. pressing delete does not mention the not selected translations
  4. all selected source records and translations were removed correctly
  5. however, an editor without that deep knowledge should be informed about what is happening with translations too

What to do?

I think this is kind of UX improvement task to transport such information before deleting records.

Author Josef Glatz
Created 11/21/25, 08:38
Updated 08/06/26, 16:02
Bug
New Stale FormEngine aka TCEforms TYPO3 CMS 13

#107979 TCA disableNoMatchingValueElement in renderTypes != selectSingle

In a Select-field with renderType=‘selectMultipleSideBySide’ I’m getting no indication when there are invalid items selected in an existing record.

In the docs the property “disableNoMatchingValueElement” is mentioned to be valid for all renderTypes:
https://docs.typo3.org/m/typo3/reference-tca/main/en-us/ColumnsConfig/Type/Select/MultipleSideBySide/Index.html#confval-select-byside-disablenomatchingvalueelement

So my expectation is that “wrong” items are handled in a way like with ‘selectSingle’ (because if the are not handled at all with this renderType, why would the docs mention the option to disable that handling for all renderTypes?).

When searching the source for access to the property “disableNoMatchingValueElement”, I found this function:
\TYPO3\CMS\Backend\Form\FormDataProvider\TcaSelectItems->addInvalidItemsFromDatabase

This function starts with this block:

// Early return if there are no items or invalid values should not be displayed
if (empty($fieldConf['config']['items'])
  || ($fieldConf['config']['renderType'] ?? '') !== 'selectSingle'
  || ($result['pageTsConfig']['TCEFORM.'][$table . '.'][$fieldName . '.']['disableNoMatchingValueElement'] ?? false)
  || ($fieldConf['config']['disableNoMatchingValueElement'] ?? false)
) {
  return $fieldConf['config']['items'];
}

If renderType !== 'selectSingle' , the function returns, so it can not work for ‘selectMultipleSideBySide’.
I also do not understand the first part of the condition – why does it also return when there are no entries in $fieldConf['config']['items'] ? If I follow the code correctly, this array holds the valid options. So if it is empty, it’s even more likely that there are non-matching values selected. Maybe the line should read empty($databaseValues) instead? Because if nothing is selected in the DB there can be no non-matching items…

The behaviour is identical in V13.4.19 and an older version (tested on 11.5.41).

Author Harald Glaser
Created 11/04/25, 15:03
Updated 08/06/26, 16:02
Bug
New Stale Backend API TYPO3 CMS 12

#106807 Warning "Unused elements detected on this page" not displayed in "Language comparison" "All languages"

Steps to reproduce

1. Create problematic state, e.g. by changing the colpos of a (translated) container child to invalid colpos
2. Now jump to “Language comparison” and select “All languages”

Result: The warning will not be displayed, the warning will only be displayed if the language of problematic element is selected.

If someone always works in “All languages” mode, they will never see the problem. The problematic elements (with missing colpose) are also not displayed in this mode.

The warning is displayed if problematic language is selected:

> Unused elements detected on this page
> These elements don’t belong to any of the available columns of this page. You should either delete them or move them to existing columns. We highlighted the problematic records for you.

Versions:

  • 12.4.21
Author Sybille Peters
Created 06/02/25, 10:58
Updated 08/06/26, 16:02
Bug
New Stale Install Tool TYPO3 CMS 13

#106797 Missing reverse Proxy leads to perpetual loading Install tool login

Using the docker image martinhelmich/typo3:13.4 in a Container based hosting (Mittwald) that lies behind a reverse proxy,

If you fail to define the reverse proxy and try to log in the install tool login will perpetually load it self.

If you forcefully reload, it is stuck in showing “Checking session and updating silent configuration update”

There is no error message shown, no entry in the TYPO3 log or server logs.

The problems resolves by setting

‘reverseProxyIP’ => ‘‘,
’reverseProxySSL’ => ‘
’,

Or setting the correct reverse proxies.

I would expect and which for a error message and or log entry in such a case.

Author Lina Wolf
Created 05/30/25, 06:37
Updated 08/06/26, 16:02
Bug
Under Review Stale Extbase TYPO3 CMS 12

#106483 Exception 1546632293 Could not get value of property [model] make sure the property is either public or has a getter

This exception is also thrown when the extbase model has a public getter and or the property is public but the TCA for the field is missing.

Can we detect this case and give a more specific error message? If not I would suggest to change the error message to also include TCA

Author Lina Wolf
Created 04/02/25, 08:01
Updated 08/06/26, 16:02
Bug
Accepted Stale File Abstraction Layer (FAL) TYPO3 CMS 13

#105699 Using <f:image in SystemEmail trigger exception in backend context

To reproduce the bug:

in settings.php

'EXTENSIONS' => [
   'backend' => [
      'loginLogo' => 'fileadmin/user_upload/test.jpg',
   ],
],

in SystemEmail.html, use `<f:image base64="true" src="{typo3.systemConfiguration.backend.loginLogo}"></f:image>`

Then, use the “forgot password” link before you log in the backend

It will trigger this exception

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1375955684: You are not allowed to access the given folder: "_processed_" | TYPO3\CMS\Core\Resource\Exception\InsufficientFolderAccessPermissionsException thrown in file /var/www/html/vendor/typo3/cms-core/Classes/Resource/ResourceStorage.php in line 875. Requested URL: https://test-distrib.ddev.site/typo3/login/password-reset/initiate-reset?loginProvider=1433416747 

A mail sent by EXT:form in a frontend context will work nice as expected.

Author Sebastien Convers
Created 11/26/24, 07:54
Updated 08/06/26, 16:02
Bug
New Stale Workspaces TYPO3 CMS 12

#105814 StageChangeNotification needs more love

Just got some complients by a client using workspaces about the StageChangeNotification mails:

  • the mail is in english only
  • the preview links don’t work if records are changed because those are inside a sysfolder.

suggestions:

  • localize it
  • give it more love
  • modify the links and change those to be backend only because those links can be really shared and via the backend a possible FE link can be created
Author Georg Ringer
Created 12/11/24, 19:18
Updated 08/06/26, 16:02
Bug
Under Review Stale Form Framework TYPO3 CMS 11

#105459 wrong structural order of checkbox and radiobutton elements in ext:form Bootstrap 5 templates (FrontendVersion2)

The default ext:form Bootstrap 5 templates(FrontentVersion2) have the wrong order of elements in the partials which breaks the style when using Botstrap 5 and have to be rewritten by an integrator.
The current ext:form Bootstrap 5 partials use <input> elements within a

From the Bootstrap 5 “Checks and radios” documentation: https://getbootstrap.com/docs/5.3/forms/checks-radios/#approach

Structurally, our <input>s and <label>s are sibling elements as opposed to an <input> within a <label>. This is slightly more verbose as you must specify id and for attributes to relate the <input> and <label>.

This is an issue since TYPO3 11.5 and is still an issue in the current main-branch

For example:
https://github.com/TYPO3-CMS/form/blob/main/Resources/Private/FrontendVersion2/Partials/Checkbox.html#L13
https://github.com/TYPO3-CMS/form/blob/main/Resources/Private/FrontendVersion2/Partials/MultiCheckbox.html#L17
https://github.com/TYPO3-CMS/form/blob/main/Resources/Private/FrontendVersion2/Partials/RadioButton.html#L17

Author David Menzel
Created 10/25/24, 08:03
Updated 08/06/26, 16:02
Bug
Accepted Stale Backend User Interface TYPO3 CMS 12

#105547 Record selector should not render page translations

If using a page selection, e.g. TCA type group, then it is possible to select a page translation, see screenshot

this leads to troubles because e.g. records are not persisted on a translation page but on the default language record’s pid

Author Georg Ringer
Created 11/06/24, 08:03
Updated 08/06/26, 16:02
Task
Accepted Stale Mailer API TYPO3 CMS 12

#102335 TransportFactory should instantiate custom transports via DI container

Currently, when using $GLOBALS['TYPO3_CONF_VARS']['MAIL']['transport'] = '<classname>'; and/or $GLOBALS['TYPO3_CONF_VARS']['MAIL']['transport_spool_type'] = '<classname>';, the class in question is instantiated via makeInstance() along with constructor arguments, which does not allow to use a configured service here which itself allows for DI. this also blocks extending AbstractTransport which does a lot of useful logic already you don’t want to reimplement.

The core should use a signaling interface here like MailSettingsAware which passes the mail settings to the service (if needed) instead of passing those along as constructor arguments, especially since those are available through $GLOBALS anyway…

Author Alexander Schnitzler
Created 11/07/23, 10:04
Updated 08/06/26, 16:02
Bug
New Stale Backend User Interface TYPO3 CMS 11

#100876 Clipboard : "Copy elements" from the mode toggle button still present when copy permissions are disabled

Hi,

even if we disable files and folder copy permissions for a backend user group, the toggle button of the clipboard still displays “Copy elements”.

(However, user cannot copy effectively. An error message occurs when trying to paste)

Author RVVN no-lastname-given
Created 05/15/23, 09:01
Updated 08/06/26, 16:02
Feature
Under Review Stale

#107914 Display Status Reports in System Toolbar

Enhance visibility of status reports by displaying them directly in the system toolbar, in addition to their current location in the About module.
This change includes incrementing the badge count to draw user attention to new or unread status reports.

Author Michael Binder
Created 10/29/25, 17:02
Updated 08/06/26, 15:51
Feature
Accepted Stale Backend User Interface

#77990 Visible Access Check for BE-Users and their given DB-Mounts

Situation:

A new BE-User is created and receives a BE-Usergroup. This usergroup might contain DB-Mounts. Additionally, the user might receive DB-Mounts on its own.
Then one or more pages are created, that match the new user DB-Mounts.

Problem:

The Admin creating the pages might not be part of any of the groups the new user belongs to. So the result can be, that the user, even with the according DB-Mounts, is not permitted to access the page.

Solution:

Upon creation of the User record, an access check for each DB-Mount the user receives reports via flashmessage about the status. So the admin is at least aware of any shortcommings in page access settings and can adjust them.
The test could be available always in the BE-Users module and / or as part of the reports module, so changes in access settings preventing users from accessing their DB-Mounts don’t go unnoticed.

Author Anja Leichsenring
Created 09/19/16, 09:18
Updated 08/06/26, 15:51
Feature
Accepted Stale Workspaces

#103639 Record Info: Show workspace in reference list

An editor wants to delete a file, but couldn’t, because it shows a reference. In the referencing element the file reference is not visible – it’s only visible in a workspace.

In the list of record references the workspace name/number would be a nice addition. The record edit link then could also contain the workspace (don’t know if possible)

Author Christoph Lehmann
Created 04/16/24, 11:54
Updated 08/06/26, 15:51
Bug
Accepted Stale Backend User Interface TYPO3 CMS 7

#75890 editor with only read access to page - some interface improvements

Steps to reproduce the issue

1) set up a page where an “editor” BE user has ONLY the “show” permission.
2) translate also the page on an alternative language
3) enter as the editor, go to the page and do the following:

3.1) Switch to “languages” view

RESULT:

see attached file schermata1.png
– the “edit” pencil icons are still present
3.1.1) if you click on the pencil > see attached file schermata2.png
- the error is not much evident (maybe a Bootstrap alert panel would be better)
– the name of the user should be used instead of/altogether with the id
– the name of the page should be used instead of/altogether with the id
– the error number “1437679336” should not be shown – for the editor, it means nothing
– last but not the least, it should be better to not show the pencil at all, I guess.

3.2) Switch to “quickedit” view

RESULT:

see attached schermata3.png

- the error is not much evident (maybe a Bootstrap alert panel would be better)
– if you click on the arrows, nothing happens; again I guess it should be better to not show them at all

Hope I made myself clear enough. have a nice day.

Author Riccardo De Contardi
Created 04/24/16, 10:02
Updated 08/06/26, 15:50
Task
Accepted Stale Backend JavaScript TYPO3 CMS 15

#109690 Prevent Chrome XMLHttpRequest deprecation messages

Chrome reports in the Backend when Build/Sources/TypeScript/backend/storage/persistent.ts is used:

> Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check https://xhr.spec.whatwg.org/.

WhatWG says:

> Synchronous XMLHttpRequest outside of workers is in the process of being removed from the web platform as it has detrimental effects to the end user’s experience. (This is a long process that takes many years.) Developers must not pass false for the async argument when the current global object is a Window object. User agents are strongly encouraged to warn about such usage in developer tools and may experiment with throwing an “InvalidAccessError” DOMException when it occurs.

The usage comes from the only Core place that sets `async=false`:

const request = new XMLHttpRequest();
const async = false;
request.open('GET', url.toString(), async);
request.send();

This means somehow™ we need to convert this in a working asynchronous call, ideally without breaking consumers

Author Garvin Hicking
Created 04/22/26, 18:41
Updated 08/06/26, 15:50
Feature
New Stale Frontend

#103887 Site config / Site language based language file handling for FRONTEND required since deprecation of "typo3Language" - controlling it by locale only is not enough in every use case

With the deprecation of the SiteLanguage property “typo3Language” in 12LTS it became impossible to have different language files for site languages with the same “locale”.

One quick example from our work with various big companies.

Lets say company X has different websites for different countries in the same TYPO3 instance and every page has an english variant (site language).

So lets say:

Website Germany (Site Config “site_germany”)
  • English for Germany (in 11LTS “locale” -> “en_GB” and “typo3Language” -> “en_DE”)
  • German (“locale” and “typo3Language” -> “de_DE”)
Website Hungary (Site Config “site_hungary”)
  • English for Hungary (in 11LTS “locale” -> “en_GB” and “typo3Language” -> “en_HU”)
  • Hungarian (“locale” and “typo3Language” -> “hu_HU”)

In this case not every label for “en_DE” has the same translation like for “en_HU”. Most of the time they are the same but in nuances they often vary. So one single “locallang.xlf” for english is not enough.

With 11LTS it was possible to just keep the locale at “en_GB” but control the chosen language files by adding custom languages (“en_HU”, “en_DE” etc.) which was possible by the “custom language” feature found here https://docs.typo3.org/m/typo3/reference-coreapi/11.5/en-us/ApiOverview/Localization/ManagingTranslations.html#xliff-translating-languages and setting this custom language in the “typo3Language” of the site language. So in the end you had a “locallang.xlf” for the labels and variations of it by “en_DE.locallang.xlf” or “en_HU.locallang.xlf”.

In 12LTS “typo3Language” is getting deprecated now (https://docs.typo3.org/m/typo3/reference-coreapi/12.4/en-us/ApiOverview/SiteHandling/AddLanguages.html#confval-sitehandling-addinglanguages-typo3language) and the language files are getting controlled only by the “locale” property.

This means that the use case above is no longer possible to implement.

For sure you could set an invented locale like “en_DE” for the “locale” property but this would first render e.g. every locale based formatting useless. And second it would spam the logs with “Locale en_DE not found.” error messages coming from “\TYPO3\CMS\Core\Localization\Locales::setLocale”.

In the end we need this dropped feature back since custom languages are now only usable in the backend but no longer in the frontend.

In a lengthy discussion in the TYPO3 slack right here https://typo3.slack.com/archives/C025BQLFA/p1716372529432749 Stefan Bürk came up with the idea of site identifier based language files like “locallang_db.site-identifier.de-DE.xliff”. (https://typo3.slack.com/archives/C025BQLFA/p1716463354137249?thread_ts=1716372529.432749&cid=C025BQLFA)
I think we would even need a site-language based approach since you can have websites that have multiple english variants in the same site config that share the same locale (e.g. “en_GB”) but need different language files.

Author Denis Mir
Created 05/23/24, 13:01
Updated 08/06/26, 15:50
Bug
Under Review Stale Backend User Interface TYPO3 CMS 13

#106846 Char counter partally hidden

In inline record, the char counter (typo3-backend-formengine-char-counter) of last input is partally hidden

Author Davide Alghi
Created 06/07/25, 13:28
Updated 08/06/26, 15:49
Feature
Under Review Stale Install Tool

#106986 Add Console Command to Execute Silent Migrations

Currently, silent migrations are automatically executed when the Install Tool is opened. However, with the growing preference for using console commands for development and deployment tasks, developers may overlook the need to run the Install Tool, leading to missed silent migrations.

Proposal:

Introduce a console command to manage silent migrations, with the ability to:

  • Check if all silent migrations have been applied
  • Apply any outstanding silent migrations

Use Cases:

  • Developers can ensure all necessary silent migrations are applied without leaving the CLI
  • CI/CD pipelines can include this command to verify or enforce migration consistency
  • Reduces dependency on the Install Tool, aligning with modern development practices
Author Lina Wolf
Assigned to Lina Wolf
Created 06/26/25, 16:42
Updated 08/06/26, 15:49
Bug
New Stale Install Tool TYPO3 CMS 11

#93739 Upgrade wizard usability: Confusing labeling of button "Execute" in the case of optional wizards

It may be possible to optimize the GUI and naming of labels.

current problems

There is no visible hint whether pressing “Execute” will immediately execute the wizard or provide an option to execute it or do not execute it (but mark it as done).

After pressing “Execute”

This may easily result in people never pressing “Execute” and dragging along these upgrade wizards. No huge problem, but I think there is a warning somewhere that appears and tells you that you have an “incomplete upgrade”.

Possible solution

Move the 2 options into the list for optional wizards, so that you already choose in the list. So that instead of the “Execute” button you have, for example 2 buttons:

  • button: No, do not execute but mark as done
  • button: Yes, execute and mark as done

Obviously, the text is a little too long, but could be split up into text within buttons and outside of button.

Related

Change in documentation: https://github.com/TYPO3-Documentation/TYPO3CMS-Guide-Installation/pull/198

Author Sybille Peters
Created 03/15/21, 09:43
Updated 08/06/26, 15:49
Feature
New Stale Database API (Doctrine DBAL)

#103448 Move DB index definition from ext_tables.sql to TCA

The TCA file should be extended to setup table indexes.

1. option


  'types' => [
  ...
  ],
  'columns' => [
  ...
  ],
  'indexes' => [
    'language_identifier' => ['l10n_parent','sys_language_uid'],
    'mn_key' => ['key_to_other_table'],
    ...
  ],

This would leave more room to also include fields set by Typo3 like pid or uid.

or

2. option


  'columns' => [
    'parent_key' => [
      'config' => [
         ...
        'foreign_table' => 'tx_extname_domain_model_parent',
        'index' => 'index_name',
      ],
    ],
    ...
  ],

With the 2. option one would just set the index by the field and if more than one field have the same index name it becomes an index over the all fields.

Maybe having both options could be useful?

As this is just the idea I have not thought about index types like primary, unique, … or order.

Author JAKOTA Design Group GmbH
Assigned to Stefan Bürk
Created 03/21/24, 08:36
Updated 08/06/26, 15:48

Showing results 701 to 725 of 1561