Showing results 426 to 450 of 1561

Bug
Under Review Quiet Language Manager (backend) TYPO3 CMS 11

#97080 Language of translated content element is not adjusted under certain conditions

If a backend editor has access to all languages, but the access right for tt_content:sys_language_uid is not given. The editor is able to create content in all languages and they are added in the correct language.

The problem is: The editor also sees the “Translate” button when there are no content elements in the destination language. When using this button and continuing the process in the modal, the translated content element is generated, but in the original language.

Author Michael Telgkamp
Created 03/02/22, 11:11
Updated 11/02/26, 08:51
Bug
Under Review Quiet RTE (rtehtmlarea + ckeditor) TYPO3 CMS 14

#110146 Default "target"-value for ckeditor linkbrowser has no effect

Setting a default value for the target attribute in the ckeditor linkbrowser config has no effect:

buttons:
  link:
    file:
      properties:
        target:
          default: '_blank'

editor:
  # ...

The documentation only mentions being able to set a default class:
https://docs.typo3.org/c/typo3/cms-rte-ckeditor/main/en-us/Configuration/Reference.html#link-browser-specific-options

Looking at the code, it looks like it should work, but the `$target` variable was not used on accident: https://github.com/TYPO3/typo3/blob/main/typo3/sysext/rte_ckeditor/Classes/Controller/BrowseLinksController.php#L364

Author Marcel Schüßler
Created 07/02/26, 17:22
Updated 11/02/26, 19:58
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 12

#89678 After creating a new content element in page module or deleting one, scroll back to where I left

Use case: As an editor, in the backend, I use the Page module to edit content on a long page with lots of content elements. I scroll down to some content element on say half of the page and edit it. Then I want to edit that same element again (because I forgot something, after checking the outcome in the frontend) or I want to continue with the element right below.

Currently: After having edited my element and clicking close or save, I am being redirected back to the top of the page module. That is really annoying because I have to search and scroll again until I find the element I was editing.

This could be easily improved as follows: After saving/closing a content element, I am being redirected back to the anchor / height of that element so that I can easily spot it again.

Author Moritz Ahl
Created 11/13/19, 23:32
Updated 11/09/26, 07:39
Task
Under Review Fresh TYPO3 CMS 15

#111106 Read image orientation independently of ext-exif, including AVIF and HEIC

Problem

Photos often store their pixels sideways and say how to turn them upright: JPEG, TIFF, PNG and WebP with an EXIF orientation, AVIF and HEIC with the irot and imir properties of their primary item.

TYPO3 reads the orientation only through exif_read_data(), i.e. only where ext-exif is loaded, and ext-exif reads JPEG and TIFF alone. As a result:

  • the width and height in sys_file_metadata are those of the sideways raster for PNG, WebP, AVIF and HEIC always, and for JPEG and TIFF without ext-exif, while ImageMagick renders these images upright, so aspect ratios are wrong in the cropping wizard and in rendered width/@height@ attributes
  • GIFBUILDER, which draws with GD, places unscaled images sideways, since GD applies no orientation. The AVIF decoder of GD ignores irot/@imir@ as well.

Solution

  • An ImageOrientationReader reads the EXIF orientation of JPEG, TIFF, PNG and WebP, through ext-exif where it is loaded for JPEG and TIFF, by itself otherwise.
  • Of AVIF and HEIC it reads irot/@imir@ of the primary item and expresses them as the equivalent EXIF orientation. All eight orientations are cross-checked against ImageMagick, which applies them through libheif.
  • ImageInfo reports the upright size, GraphicsCanvas (GIFBUILDER) turns images upright.
  • An upgrade wizard corrects the dimensions of images indexed before
Author Benjamin Kott
Created 10/17/26, 08:41
Updated 11/09/26, 00:31
Bug
Under Review Fresh Backend API TYPO3 CMS 14

#108473 TYPO3\CMS\Backend\Routing\UriBuilder::buildUriFromRoute doesn't respect if $GLOBALS['TYPO3_CONF_VARS']['BE']['entryPoint'] contains a domain

In case if $GLOBALS[‘TYPO3_CONF_VARS’][‘BE’][‘entryPoint’] contains a domain to make the backend accessible via an own domain this is lost in the link generation.

Precondition to understand the problem:
- the backend is accessible via https://backend.dev14.ddev.site/
- the frontend is accessible via https://www.dev14.ddev.site/
- typo3/cms-adminpanel is visible in the frontend.

When I want to open the adminpanel and ajax request to /ajax/adminpanel/toggleActiveState?token=f99d26618a037279563e9dbf02c5a936a16eff2f36801e1245788b1db0a530de is made.

This is answered with a 404 error, because /ajax/adminpanel/toggleActiveState is not available. This is a backend ajax route that is missing the domain of the backend.

The url generated for the ajax route is generated with TYPO3\CMS\Backend\Routing\UriBuilder::buildUriFromRoute which calls UriBuilder::buildUri

In buildUri the $requestContext is gathered via TYPO3\CMS\Core\Routing\RequestContextFactory::fromBackendRequest which calls TYPO3\CMS\Core\Routing\BackendEntryPointResolver::getPathFromRequest.

In getPathFromRequest the correct $entryPoint is found BUT only the path of that is used.

I think it would be better if RequestContextFactory::fromBackendRequest would use BackendEntryPointResolver::getUriFromRequest instead. Which would result in https://backend.dev14.ddev.site/ajax/adminpanel/toggleActiveState?token=f99d26618a037279563e9dbf02c5a936a16eff2f36801e1245788b1db0a530de with the host instead of only resulting in /ajax/adminpanel/toggleActiveState?token=f99d26618a037279563e9dbf02c5a936a16eff2f36801e1245788b1db0a530de without the host.

Author Sebastian Fischer
Created 12/11/25, 19:42
Updated 11/09/26, 09:08
Feature
Under Review Fresh CLI

#111374 Show the data of the Configuration module on the command line

Problem

The data of the System > Configuration backend module is only reachable through the backend: TCA, $GLOBALS['TYPO3_CONF_VARS'], event listeners, middlewares, routes, backend modules, site sets and the other providers. Over SSH, in deployment scripts, when comparing environments and for AI coding agents there is no way to read it without a backend login. Existing commands such as configuration:show or debug:backend:routes each cover one provider.

Proposal

A command lowlevel:inspect that reads the same providers as the module, including the ones extensions register with the lowlevel.configuration.module.provider service tag.

  • Without arguments it lists the providers, grouped as in the module.
  • Each further argument selects one key level: bin/typo3 lowlevel:inspect tca tt_content columns header
  • --format=tree (default) is an overview of about 200 lines, --format=flat writes one line per value with a path that can be pasted back as arguments, --format=json writes JSON. flat and json are complete and refused above 1 MB unless --no-size-limit is given.
  • --resolve-labels[=<lang>] translates label references.
  • Shell completion for providers, keys and languages; errors on stderr with exit code 2 for invalid input and 1 for a provider that cannot run on the command line.

The command only reads and changes nothing.

Author Matthias Vogel
Created 11/09/26, 10:29
Updated 11/09/26, 11:22
Bug
Under Review Fresh Reports TYPO3 CMS 14

#111402 Status Report module executes all status providers twice per request

Opening System > Reports > Status Report runs every registered status provider twice. StatusReportController::handleRequest() first calls StatusService::getSystemStatus() to build the view and then StatusService::collectAndStoreSystemStatus(), which internally calls getSystemStatus() again just to store the highest severity in the registry.

Since some providers are expensive (environment checks, extension status), the module takes about twice as long to render as necessary.

How to reproduce

  1. Add sleep(3); to the start of StatusService::getSystemStatus()
  2. Open System > Reports > Status Report

Expected: the page takes about 3 seconds longer than before.
Actual: the page takes about 6 seconds longer, as the method is called twice.

Solution

Add StatusService::storeHighestSeverity() which stores the highest severity of an already collected status collection. The controller reuses the collection it has already loaded; collectAndStoreSystemStatus() (used by the scheduler task) delegates to the new method and behaves as before.

Related: #100976

Author Georg Ringer
Assigned to Georg Ringer
Created 11/10/26, 20:52
Updated 11/10/26, 20:53
Bug
Under Review Fresh TYPO3 CMS 10

#92906 File Metadata are not editable when translation doesn't exist yet

In the backend form of sys_file_reference inline records, typically there’s a link where you can edit the metadata of the selected file.

Since the fix for #82178 this link is removed if there is not sys_file_metadata record in the same language as sys_file_reference record.

However obviously editors want to edit metdata for files which have not been explicitly localized before. So I suggest that sys_file_metadata translations are created on demand in this situation.

Author Sebastian Michaelsen
Created 11/23/20, 13:52
Updated 11/11/26, 10:04
Task
Under Review Fresh Fluid TYPO3 CMS 15

#111408 Sort select ViewHelper options using Collator

Follow-up to #111310.

The ViewHelpers <f:form> and <f:form> sort their options by label when sortByOptionLabel=“true” is set. Since #111310 they use SORT_STRING on PHP 8.6 and newer (SORT_LOCALE_STRING is deprecated there) and SORT_LOCALE_STRING on older PHP versions.</f:form></f:form>

The resulting order therefore depends on
  • the PHP version,
  • the process locale (LC_COLLATE), which TYPO3 only sets in frontend context, so the backend effectively sorts byte wise,
  • whether the locale of the site language is installed on the server.

Byte wise comparison sorts all upper case letters before lower case ones and puts every non-ASCII character behind “z” (e.g. “Banana” before “apple”, “Äpfel” after “Zebra”).

Both ViewHelpers should sort with \Collator instead, using the collation of the current locale: the site language in frontend context, the backend user’s language in backend context, and the argument alternativeLanguage for <f:form>. Labels keep being compared as strings (\Collator::SORT_STRING), so “10” still sorts before “9”. ext-intl is already required, and core sorts this way in SelectItemProcessor and FileList.</f:form>

This changes the rendered option order in some setups, so it is a breaking change for main only.

Author Benni Mack
Created 11/11/26, 14:15
Updated 11/11/26, 14:18
Bug
New Orphaned Install Tool TYPO3 CMS 13

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

The headache

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

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

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

Trying to override the path with additional.php

Adding

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

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

Resume

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

Instructions

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

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

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

Proposed solutions and brainstorm

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

I cheer for the path being relative to projectDir

Author Soren Malling
Assigned to Stefan Bürk
Created 10/20/25, 10:14
Updated 10/20/25, 10:20
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 14

#102530 Mandatory fields only recognisable visually and after validation errors

Description

Required fields, e.g., page title, are marked visually as required but not recognized by AT.

Reproduction steps

- open an existing page
- Remove the entered page title
- The field is marked, but this has no effect because the icon (!) cannot be reached.

Impact

Target group

Screen reader

Severity

high

Frequency

common

Definition of Done

As a user, when I enter the field, I receive a message indicating that it is a required field.

Recommended solution

The symbol should be output as an SVG with a title and be part of the input label or connected via aria-describedby.
References / WCAG 2.2 Reference

1.3.1,
4.3.1,
3.3.2

Prioritizing the removal of the issues found

medium

Screencast or Screenshot

—-

Original ticket text:

Mandatory fields can only be recognized visually and only after an error has occurred. These are marked with an exclamation mark, which has no structural alternative. To make matters worse, the exclamation mark displays two different pieces of information (affected tab and affected field).

Author Christian Rath-Ulrich
Created 11/27/23, 15:18
Updated 10/16/25, 15:09
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 14

#92625 Form elements have insufficient color contrast and focus style

The form elements do not have sufficient contrast for users with a visual impairment. A contrast of 3:1 for input fields and buttons is required, as long as there is no sufficiently contrasted icon (3:1) or text (4,5:1) element placed inside. The contrast can be measured border and fill or border and background.

Reproduction steps

- Use colour contrast analyser
- Measure contrast (between border/fill or border/background)

Impact

Target group

visual

Severity

high

Frequency

very common

Definition of Done

WHEN I measure contrast of input field or button (without text or icon inside) against background or fill, the contrast is at least 3:1 or more

Recommended solution

enhance contrast of border

References / WCAG 2.2 Reference

1.4.11

Prioritizing the removal of the issues found

must have

Screencast or Screenshot

—-

Original Ticket Text:

The form elements in the Edit section have the border color #bbb. When the form elements receive focus, the border color is #aaa. Both of those colors surrounded by the background color #ededed have an insufficient contrast ratio of 1.98:1, see WebAIM Color Contrast Checker

When the form elements receive focus, the elements get a subtle box-shadow and the border-color changes from #bbb to #aaa, which is an insufficient contrast change from 1.21:1, see WebAIM Color Contrast Checker

Author Mylene Kreiger
Created 10/21/20, 11:52
Updated 10/16/25, 14:11
Bug
Under Review Orphaned FormEngine aka TCEforms TYPO3 CMS 12

#103532 Using TSconfig TCEFORM to change existing flexform field configuration does not work

You can use TSconfig TCEFORM to change attributes of flexform fields via:

TCEFORM.tx_styleguide_flex.flex_file_1.default.sDEF.input_1.label = Override Label

However, you can not change the “config” section of a field, for example to add a enableRichtext attribute, or change the rows/cols of an input. This is currently only possible to change for main-level fields like “tt_content.header”, but not for flexform fields:

TCEFORM.tx_styleguide_flex.flex_file_1.default.sDEF.input_1.config.max = 30
TCEFORM.tx_styleguide_flex.flex_file_1.default.sDEF.input_1.config.size = 5

You can already use PSR-14 events (AfterFlexFormDataStructureParsedEvent) to modify a flexform, but this is a bit more complicated than just using TSconfig. So I’d argue that setting it via TSconfig should be possible.

Author Garvin Hicking
Created 04/04/24, 11:10
Updated 10/16/25, 10:34
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 11

#91390 Page translation of a shortcut does not respect type changed to standard

If you translate a page that has the type “Shortcut” in the main language, and change it to “Standard” in the translation, it will still behave like a shortcut in the frontend.

In my opinion, this individual setting should work, but if this is not possible or desired, then the type dropdown for translations is superfluous, isn’t it?

Author Benjamin Robinson
Created 05/13/20, 22:31
Updated 10/02/25, 11:16
Feature
Author Alexander Schnitzler
Assigned to Alexander Schnitzler
Created 09/25/23, 06:04
Updated 10/01/25, 12:02
Task
Under Review Orphaned Backend JavaScript TYPO3 CMS 13

#107573 Generate TypeScript declarations (d.ts)

Export TypeScript declarations (d.ts) for each system extension.

Author Oliver Hader
Created 10/01/25, 07:29
Updated 10/01/25, 08:16
Bug
New Orphaned Authentication TYPO3 CMS 13

#107472 FE-Login in second Browser-Tab yield inconsistent Userstate and Login-Error

Steps to reproduce:
  • fe_user are located on any sys_folder
  • $GLOBALS[‘TYPO3_CONF_VARS’][‘FE’][‘checkFeUserPid’] = true
  • Page with fe-login-Plugin
  • Login page opened in two browser tabs
  • in first browser tab do a login with username and password
  • do the same login in second tab afterward
  • Login-Error is displayed

If $GLOBALS[‘TYPO3_CONF_VARS’][‘FE’][‘checkFeUserPid’] = false is used,
no error is displayed
In this case even wrong password or inexistend user yield same result

Reason for Login-Error:
@AbstractUserAuthentication::fetchValidUserFromSessionOrDestroySession();@, which relys on $checkPid_value, is executed before
@BeforeRequestTokenProcessedEvent@ has been dispatched.
@\TYPO3\CMS\FrontendLogin\Event\ProcessRequestTokenListener@ sets `$checkPid_value` to late.

Deeper in middleware-stack the frontend-user is not logged in, while its session has a user id:
@frontendUser->getSession()->getUserId() !== $frontendUser->getUserId()@

It would be nice , if both configuration variants yield same behavior.

Users getting this type of login error, try to change password and run in same problem again.
How could it be possible, to detect and handle the “new login while already authenticated”-condition and inform the user about the mistake?

Author Andreas Häfner
Created 09/17/25, 12:36
Updated 09/17/25, 12:36
Bug
New Orphaned TYPO3 CMS 13

#107450 WCAG: Module menu: Headings/hierarchies of the individual modules

The individual menu items and hierarchy levels within the module menu are not comprehensible to the user.

The burger menu does not have a clear label and is therefore not recognizable as such.
“I’m missing a structure that is navigable. There are no headings for the widgets, so I don’t understand the structure.”
Navigation of the menu tree is not immediately intuitive: Screen readers do not read the lowest level consistently (web in the test example);
Focusing does not work consistently with the cursor keys; the menu tree can be opened with the cursor (right), but cannot be closed with the left cursor key.

Solution idea
The menu items must be provided with headings. All menu items should be given an H1 so that they have the same level. The sub-items should then be given an H2.

Expected result
The menu items are provided with headings and separated from each other. Orientation is provided and output by the screen reader.
The menu can be opened and closed easily using the cursor keys.

Addition:
Minimize module menu is read incorrectly (miniminimieren), depending on the screen reader; it should be checked whether the button is necessary at all for visually impaired users.

Further information/comments
Organizing the dashboard or individual menu items by region is not effective due to the customizability.

Internal reference: ITZBUNDPHP-4976

Author Christian Rath-Ulrich
Created 09/12/25, 08:57
Updated 09/12/25, 08:57
Bug
New Orphaned TYPO3 CMS 13

#107446 WCAG: Functionality of the “Numbering” button

Screenshot I

The user is in the workspace of their page and has already added content modules to the Top, Main, or Bottom areas.

There is a small icon in front of the title of the content module, which is output as “numbering” by the screen reader.

When selected (left mouse button), a context menu opens. When attempting to navigate through it, the focus jumps, for example, to the path (top right) or to the drop-down menu (layout/language comparison) at the top left, but the context menu remains open.

Screenshot II

The icon/functionality Numbering is also located in the path of an image selection, which is not understandable here. The number sign (blue image) is not displayed meaningfully at this point, as we can edit the module here à it is also included in the frame.

Screenshot III + IV:

Display of the Numbering icon also for image files and at the end of pages.

Display on screenshot is shown as a cross-reference – but is not one

Solution idea:

Find intuitive/understandable naming
Is the function necessary or already covered by the editing function? Remove the function?
Expected result:

Selecting the icon opens the context menu, which I can navigate using the tab key.
Make the icon label more intuitive.
Remove the function at this point.
Additional comments:

The numbering function/icon appears in several places and is not self-explanatory.

internal reference: ITZBUNDPHP-4987

Author Christian Rath-Ulrich
Created 09/12/25, 08:35
Updated 09/12/25, 08:35
Bug
New Orphaned TYPO3 CMS 13

#107445 WCAG: Contrast / Inverted display - Headings, names & icons

Framework conditions: Zoom 150% / inverted mode / external monitor

Description:

Example 1:

The user navigates through the various files in the “File List” module. The file names are not inverted in inverted mode and appear in black font on a black background.

Example 2:

The user navigates through the page titles. These are not displayed in inverted mode and appear in black font on a black background.

Example 3:

The workspace is structured with tabs; inverted display makes it impossible to see which tab you are currently in.

Example 4:

The Typo3 bar in the header region is not highlighted in color in high contrast mode. As a result, it is not clear which work environment you are in.

Example 5:

The contrast of the icons needs to be sharper; depending on the background color selected, the contrast is insufficient. This primarily affects clickable icons and graphics.

Example 6:

Hover icons must not be used and must be displayed constantly to enable orientation; the corresponding icons must also be given a clear title (examples: Dashboard —> Move / Delete) so that the screen reader can output them.

Example 7:

In the inverted display, pop-ups are not clearly recognizable because a black area appears on a black background. The “X” for closing the pop-up could also be displayed larger.

Example 8:

Preview function: Buttons are not displayed in inverted mode; furthermore, there is no clear distinction from the website.

Faulty behavior:

It appears as if some of the fonts are “hard coded.”

There is a lack of contrast.

Expected behavior:

Even in inverted mode, users should be able to clearly read all labels and names.

Author Christian Rath-Ulrich
Created 09/12/25, 08:14
Updated 09/12/25, 08:16
Task
New Orphaned TYPO3 CMS 14

#107377 Drop usage of pageId_* cache tags

We already have pages_*. It might be a good idea to (finally) drop pageId_* and streamline caching behavior for pages with other tables (<table>_<uid>).

This is of course highly breaking, but lowers maintenance barriers in the future and also makes bugfixes like #107376 easier to implement.

Author Elias Häußler
Created 09/03/25, 09:07
Updated 09/03/25, 09:07
Bug
New Orphaned TypoScript TYPO3 CMS 13

#107308 PageTSconfig won't get inherited to site if included in rootline before site

  1. introduced the option to include PageTSconfig to sites. However it seems that this also removes the option to inherit PageTSconfig from higher up pages in the rootline if those aren’t part of a site (i.e. defining a site/rootpage drops all includes on pids above).

I have a page tree where I include PageTSconfig (via pages.tsconfig_includes) above the actual sites/rootpages (e.g. have multiple parent “template” or “configuration” nodes and the actual Sites below that). The PageTSconfig is included in the parent nodes correctly, but on the actual sites/rootpages below, the formerly included PageTSconfig is not available.

So the sitestructure is like

A (PageTSconfig definition)
`A1
 `A1.1 (Site, Rootpage)

If I look into Module PagesTSconfig / Included pageTSconfig in 13LTS it doesn’t show the entries for pagesTsConfig-page-<pid of page A>-includes-0 which were available in 12LTS. In that place the new “site pageTSconfig include” is there, but the former includes are missing, which would be expected to be there as well.
It seems somewhere in https://review.typo3.org/c/Packages/TYPO3.CMS/+/83586/21/typo3/sysext/core/Classes/TypoScript/IncludeTree/TsConfigTreeBuilder.php#176 there is a hiccup which focusses on sites and site subpages, but leaves out the parent pages of a site.

(Obviously I can refactor away from inheritance to site include, but nevertheless this seems like there is an bug).

Author J. Peter M. Schuler
Created 08/18/25, 13:48
Updated 08/23/25, 15:38
Feature
New Orphaned Site Handling, Site Sets & Routing

#89552 Redirect URLs with trailing slashes to their canonical non-trailing-slash URL (or the other way around)

I noticed that in TYPO 9 LTS, the following two URLs will show the same page:

Live example:

For various reasons (including SEO and web analytics, https://searchfacts.com/url-trailing-slash/ ) it would be great to have only one of these URLs be canonical, while a request to the other URL results in a 301 Redirect to the canonical URL.

TYPO 9 seems to generate URLs without a trailing slash (which I also prefer). (Pre-TYPO 9) realurl seems to generate URLs with a trailing slash.

Author Gerrit Hübbers
Created 10/30/19, 18:12
Updated 08/14/25, 10:05
Feature
New Orphaned Backend User Interface

#107218 Allow manually changing filename in case of conflict

Currently, if a file is uploaded that already exists, it is possible to resolve the conflict by renaming the file. However, unlike almost everywhere else, the user cannot change the filename manually. Instead, a suffix _NN is appended automatically.

To make this process more user-friendly, the user should be given a possibility to manually change the filename. This would also need an automated check if the new filename exists already.

Prior art: There is #64363, but that is classified as a bug, so I guess creating a feature-ticket is probably justified.

Author Andreas Wolf
Assigned to Andreas Wolf
Created 08/07/25, 18:35
Updated 08/07/25, 18:35
Feature
New Orphaned Security

#107153 Sudo-mode should work with other authentication methods than username and password

When using extensions like “oauth2”, where the authentication is done outside of TYPO3 and the be_users record does not have a password, it is not possible to confirm the sudo mode (even as admin). Only system maintainers could use the install tool password to bypass it.

That may be related to https://forge.typo3.org/issues/106380

Author Remo H.
Assigned to Oliver Hader
Created 07/28/25, 09:25
Updated 07/28/25, 09:25

Showing results 426 to 450 of 1561