Showing results 1076 to 1100 of 1561

Bug
Needs Feedback Orphaned Extbase TYPO3 CMS 11

#102299 Incomprehensible behavior: Entity in a forward argument

Hello,

I’m not quite sure if this is a bug or if I fundamentally misunderstood something.

In my self programmed controller I have several actions. Many small Actions do their job and forward a few arguments to a larger Action method, which then organizes everything else and whose template is rendered.

But now when I put an entity into the forward arguments, it only goes well once.
Ex: user clicks on a submit button. Then he lands in my small action method. This validates and forwards among other things also a manipulated entity. This is fast, the errors are displayed. Everything is top. But if the user clicks the button again, it takes many seconds until the page is loaded again.

Currently I convert the entity into an array by hand to put it into the arguments, so that the “big” method “copies” the array back into an entity. This works reliably and quickly.

But surely this can’t be intentional? Is there a caching mechanism or some other generic algorithm interfering?

Can anyone else confirm this behavior? Or show me where in the manual it says not to put Entity in the forward arguments?

I thought the advantage of forwards was just that you can transport more complex objects from action to action without going through the browser….

Thanks for your help… Clemens

Author C. Gogolin
Created 10/31/23, 19:36
Updated 06/06/25, 09:38
Feature
Needs Feedback Orphaned Extbase

#104383 Better error messages for “Validation failed while trying to call …Controller->detailAction()”

Sometimes it is really hard to find out the problem itself when extbase only says “Validation failed while trying to call …Controller->detailAction()” and nothing more in TYPO3 log file. So why not tell the developer which validation fails?

Author Bernhard Eckl
Created 07/12/24, 14:04
Updated 06/05/25, 05:27
Feature
New Orphaned Backend User Interface

#106802 Allow custom group labels and icons for groupName in TCA ctrl configuration

I would like to define custom icons and labels for each groupName used in the TCA ctrl configuration,
so that I can organize multiple distinct groups of records within a single extension in the “New Record” wizard, each with its own meaningful visual identity.

Current Behavior

Currently, TYPO3 allows grouping records in the “New Record” wizard using the TCA configuration:

$GLOBALS['TCA']['my_table']['ctrl']['groupName'] = 'my_extension_key';
However:
The label for the group is derived automatically in 1 of 2 ways:

The icon for the group is always taken from the extension icon (ext_icon.svg).
There is no way to override the group label or icon per groupName.

https://github.com/TYPO3/typo3/blob/60e08ed6d6efd6e23371639897cba1055cb16d46/typo3/sysext/backend/Classes/Controller/NewRecordController.php#L422

Although you technically can define multiple groups, all of the groups will have the same title and icon.
This logically limits developers to only one visual group per extension, even if they want to logically separate different types of records (e.g. content types vs. configurations) under the same extension.

Desired behaviour

Add support for:
  • Custom group label localization, e.g. via a dedicated label key (e.g. group.[groupName].title)
  • Custom group icons, e.g. via EXT:my_extension/Resources/Public/Icons/GroupMyGroup.svg or iconIdentifier tx-myext-mygroupicon

Configuration option (example):

$GLOBALS['TCA']['my_table']['ctrl'] = [
    'groupName' => 'custom_group_1',
    'groupLabel' => 'LLL:EXT:my_extension/Resources/Private/Language/locallang_db.xlf:group.custom_group_1.title', 
    'groupIcon' => 'EXT:my_extension/Resources/Public/Icons/GroupCustomGroup1.svg', // or 'tx-myIconIdentifier'
];

But since we don’t want to redefine groupLabel and groupIcon for each individual table, we would need something like a group metadata.
We could use, for example

$GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['my_extension']['groupMetadata'] = [
    'custom_group_1' => [
        'label' => 'LLL:EXT:your_extension/Resources/Private/Language/locallang_db.xlf:group.news',
        'icon' => 'EXT:your_extension/Resources/Public/Icons/group-news.svg',
    ],
    'custom_group_2' => [
        'label' => 'LLL:EXT:your_extension/Resources/Private/Language/locallang_db.xlf:group.events',
        'icon' => 'tx-myext-iconIdentifier',
    ],
];

Maybe add an API function that populates that config, e.g. ExtensionManagementUtility::addTcaCtrlGroup($extkey, $groupName, $label, $icon)

If no group metadata exists we can still use the mechanic we have today

Author Thomas Rawiel
Created 06/01/25, 16:30
Updated 06/01/25, 16:30
Bug
New Orphaned File Abstraction Layer (FAL) TYPO3 CMS 13

#106800 Filelist offers to create new file metadata but the user does not have sufficient permission to create it

After #106215, it is possible to select an image (or other file) in the file list MANAGE mode and typo3 will offer to create a new file metadata record. Upon saving it errors with

Sorry, you didn't have proper permissions to perform this change.
Access to table sys_file_metadata for user 119 was denied by a ModifyRecordEditUserAccessEvent listener 1662727149

Edit form could not be loaded
The edit form could not be loaded for the requested records. This might be due to insufficient permissions.

ZThe user is configured to not have write permission in this folder.

Author Oliver Eglseder
Created 05/30/25, 12:20
Updated 05/30/25, 12:20
Bug
Needs Feedback Orphaned Localization TYPO3 CMS 13

#81328 Translation didn't sort Elements correct.

This bug was found in TYPO3 7.6 and reproduced now in TYPO3 8.7

Whats the Bug

The bug is that the sorting of content elements can be different between the original language and a translation.

How can I reproduce the bug

1.) Create a new Page A
2.) Create a new Content Element A on Page A
3.) Translate the Page A and the Content Element A to another Language
4.) Create a new Page B
5.) Create a new Content Element B on Page B
6.) Translate the Page B to the same Language to which you translate Page A. Do not translate any Content Element now only the Page.
7.) Copy the Content Element A from Page A to Page B. The Translation of the Content Element A should be copied with the default Element.
8.) Translate now the Content Element B on Page B

Now the Content Element A and the Content Element B do not have the same sorting in both languages. Because sorting in the foreign language is not available you can not sort the elements in the correct order.

This behaviour was tested on TYPO3 7.6.16 and 8.7.17

A video of the reproduction in TYPO3 8.7 can be found in file section below.

How could this Bug be fixed

In my opinion we are having two possible solutions for this way

1. Check at every translation the original sorting. And Update it if nessecary for all other languages.
2. Don’t block the sorting function, when you translate content elements.

Author Markus Gehrig
Created 05/24/17, 10:24
Updated 05/28/25, 15:35
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#106782 Wrong icon in page backend_layout(_next)

When using the backend_layout table in the backend with an icon (which i placed under the fileadmin structure the default-not-found icon is shown instead of the icon selected in the table row. It looks like the FormEngineUtility::getIconHtml does not resolve the link correctly. The website is not running in the root but in an subdir.

What I could discover is checking the icon as site/subdir/subdir/image.jpg.

Author Rene Westendorp
Created 05/27/25, 12:28
Updated 05/27/25, 12:28
Bug
Needs Feedback Orphaned Fluid TYPO3 CMS 13

#106762 Fluid f:form.* ViewHelpers do not behave like documented when using property and value in conjunction

The documentation of, for example, the f:form.textfield VH says

> property
> Name of Object Property. If used in conjunction with <f:form object="...">, the “name” property will be ignored, while “value” can be used to specify a <strong>default</strong> field value instead of the object property value.</f:form>

This sounds that one can use value to specify a default fallback value if the object of the form does not contain the property (i.e. !isset()).

However, the actual behaviour: when specifying value it always wins over the actual property in the object. Either this is a bug in the VH API or in the documentation.

Not sure whether this is relevant, as object I am using an array, which works totally fine elsewise. In my use-case I can not use an actual class instance, because I have dynamically built forms, so can not define a hard-coded DTO class (which would require to know all fields beforehand). So maybe this is only a bug when using an array.

Intuitively I’d expect it to behave like the documentation says (so, bug in VH, not in docs):
if a property isset(), then the value from the property is taken, else (and only then!) pre-fill with the value.

Author S P
Created 05/26/25, 09:13
Updated 05/26/25, 19:07
Bug
New Orphaned Database API (Doctrine DBAL) TYPO3 CMS 12

#106585 database:updateschema breaks on Data Type 'VECTOR'

When running vendor/bin/typo3 database:updateschema on CLI or “Analyze Database Structure” in the Install Tool, they throw an error.

This happens when you got a ext_tables.sql in your project that adds a field with the new Data Type ‘VECTOR’.

myext/ext_tables.sql

CREATE TABLE tx_myext_domain_model_chunk
(
    pid       tinyint(3) unsigned DEFAULT '0' NOT NULL,
    title     VARCHAR(255) NOT NULL DEFAULT '',
    url       VARCHAR(255) NOT NULL DEFAULT '',
    content   LONGTEXT     NOT NULL DEFAULT '',
    embedding VECTOR(1024) NOT NULL,
    VECTOR    INDEX (embedding)
);

This new data type was introduced on in MariaDB 11.7.2: https://mariadb.com/kb/en/vector-overview/

This data type is used in AI for search of text by their coordinates in an multi dimensional space.

Database analysis failed
[SQL Error] line 0, col 240: Error: Expected BIT, TINYINT, SMALLINT, MEDIUMINT, INT, INTEGER, BIGINT, REAL, DOUBLE, FLOAT, DECIMAL, NUMERIC, DATE, TIME, TIMESTAMP, DATETIME, YEAR, CHAR, VARCHAR, BINARY, VARBINARY, TINYBLOB, BLOB, MEDIUMBLOB, LONGBLOB, TINYTEXT, TEXT, MEDIUMTEXT, LONGTEXT, ENUM, SET, or JSON, got 'VECTOR' in statement: CREATE TABLE tx_nitosite_domain_model_chunk ( pid tinyint(3) unsigned DEFAULT '0' NOT NULL, title VARCHAR(255) NOT NULL DEFAULT '', url VARCHAR(255) NOT NULL DEFAULT '', content LONGTEXT NOT NULL DEFAULT '', embedding VECTOR(1024) NOT NULL, VECTOR INDEX (embedding) );

When I add this field manually to the DB, TYPO3 is working fine, I can even add vectors to this table with doctrine.

When I add it manually and remove it from ext_tables.sql it still crashes, just with stack trace:

(1/1) Doctrine\DBAL\Exception\InvalidArgumentException
Unknown database type "vector" requested, TYPO3\CMS\Core\Database\Platform\MariaDB1010Platform may not support it.

in /var/www/html/vendor/doctrine/dbal/src/Platforms/AbstractPlatform.php line 354

        $dbType = strtolower($dbType);

        if (! isset($this->doctrineTypeMapping[$dbType])) {
            throw new InvalidArgumentException(sprintf(
                'Unknown database type "%s" requested, %s may not support it.',
                $dbType,
                static::class,
            ));
at Doctrine\DBAL\Platforms\AbstractPlatform->getDoctrineTypeMapping('vector')
in /var/www/html/vendor/typo3/cms-core/Classes/Database/Schema/SchemaManager/ColumnTypeCommentMethodsTrait.php line 57
     */
    private function determineColumnType(string $dbType, array &$tableColumn): string
    {
        $platform = ($this instanceof AbstractPlatform) ? $this : $this->platform;
        $type = $dbType !== '' ? $platform->getDoctrineTypeMapping($dbType) : '';
        if (isset($tableColumn['comment'])) {
            $type = $this->extractDoctrineTypeFromComment($tableColumn['comment'], $type);
            $tableColumn['comment'] = $this->removeDoctrineTypeFromComment($tableColumn['comment'], $type);
        }
at TYPO3\CMS\Core\Database\Schema\SchemaManager\MySQLSchemaManager->determineColumnType('vector', array('table_name' => 'tx_nitosite_domain_model_chunk', 'field' => 'embedding', 'type' => 'vector(1024)', 'null' => 'NO', 'key' => 'MUL', 'default' => null, 'extra' => '', 'comment' => '', 'characterset' => null, 'collation' => null, 'name' => ''))
in /var/www/html/vendor/typo3/cms-core/Classes/Database/Schema/SchemaManager/MySQLSchemaManager.php line 241
        // Following line differs from \Doctrine\DBAL\Schema\MySQLSchemaManager::_getPortableTableColumnDefinition,
        // taken from:
        // - https://github.com/doctrine/dbal/blob/61446f07fcb522414d6cfd8b1c3e5f9e18c579ba/src/Schema/MySQLSchemaManager.php#L186-L192
        // - https://github.com/doctrine/dbal/blob/61446f07fcb522414d6cfd8b1c3e5f9e18c579ba/src/Schema/PostgreSQLSchemaManager.php#L427-L429
        $type = $this->determineColumnType($dbType, $tableColumn);

        switch ($dbType) {
            case 'char':
            case 'binary':
at TYPO3\CMS\Core\Database\Schema\SchemaManager\MySQLSchemaManager->parentGetPortableTableColumnDefinition(array('table_name' => 'tx_nitosite_domain_model_chunk', 'field' => 'embedding', 'type' => 'vector(1024)', 'null' => 'NO', 'key' => 'MUL', 'default' => null, 'extra' => '', 'comment' => '', 'characterset' => null, 'collation' => null, 'name' => ''))
in /var/www/html/vendor/typo3/cms-core/Classes/Database/Schema/SchemaManager/MySQLSchemaManager.php line 108
        /** @var DoctrineMariaDBPlatform|DoctrineMySQLPlatform $platform */
        $platform = $this->platform;
        $tableColumn = $this->normalizeTableColumnData($tableColumn, $platform);
        return $this->processCustomDoctrineTypesColumnDefinition($tableColumn, $platform)
            ?? $this->parentGetPortableTableColumnDefinition($tableColumn);
    }

    /**
     * @param array<string, mixed> $tableColumn
at TYPO3\CMS\Core\Database\Schema\SchemaManager\MySQLSchemaManager->_getPortableTableColumnDefinition(array('TABLE_NAME' => 'tx_nitosite_domain_model_chunk', 'field' => 'embedding', 'type' => 'vector(1024)', 'null' => 'NO', 'key' => 'MUL', 'default' => null, 'EXTRA' => '', 'comment' => '', 'characterset' => null, 'collation' => null))
in /var/www/html/vendor/doctrine/dbal/src/Schema/AbstractSchemaManager.php line 670
    protected function _getPortableTableColumnList(string $table, string $database, array $tableColumns): array
    {
        $list = [];
        foreach ($tableColumns as $tableColumn) {
            $column = $this->_getPortableTableColumnDefinition($tableColumn);

            $name        = strtolower($column->getQuotedName($this->platform));
            $list[$name] = $column;
        }

The people from DDEV said, they are planing to add MariaDB 11.8 when the LTS is released.

Beside the DB compare, TYPO3 12 + 13 seem to work well with MariaDB 11.7.x.

Author Nikolai Townsend
Assigned to Stefan Bürk
Created 04/17/25, 14:26
Updated 05/23/25, 21:21
Bug
New Orphaned Database API (Doctrine DBAL) TYPO3 CMS 13

#106719 Install tool - SchemaMigrator & DBAL 4 - MySQL float type

Hi,

In my extension i have a field declare as my_field FLOAT,
In typo3 v12, in the Analyze Database Structure the field type stay as float.
In typo3 v13, it returns an update like ALTER TABLE `my_table` CHANGE `my_field ` `my_field ` DOUBLE PRECISION.

This can throw a lot of exceptions in extensions if the dev doesnt cast to float or check the entry type.
I think this a side effect of DBAL 4 and we should be allowed to use a MySQL float type.

In typo3, the process is located in \TYPO3\CMS\Core\Database\Schema\Parser\TableBuilder::getDoctrineColumnTypeName() :

...
case RealDataType::class:
case FloatDataType::class:
case DoubleDataType::class:
$doctrineType = Types::FLOAT;
break;
...

We force Types::FLOAT for this fields type who result in :

 public function getFloatDeclarationSQL(array $column): string
{
 return 'DOUBLE PRECISION' . $this->getUnsignedDeclaration($column);
}

I think the correct doctrine type is Types::SMALLFLOAT who will keep the MySQL float type.

Author Yohann CERDAN
Assigned to Stefan Bürk
Created 05/16/25, 11:39
Updated 05/23/25, 15:13
Feature
New Orphaned Site Handling, Site Sets & Routing

#106753 Add a pageType parameter to Plugin Enhancer and Extbase Plugin Enhancer

It would be useful to be able to set the pageType in a plugin or extbase enhancer, without using the PageTypeDecorator.
Would permit to have clean url to call JSON pages, without using the pageType decorator (by calling directly a plugin, instead of a page, via TypoScript).

Author Maxime Lafontaine
Created 05/22/25, 15:11
Updated 05/22/25, 15:11
Bug
New Orphaned Extension Manager TYPO3 CMS 13

#106671 Classic Installation: Installing a Site Package in the Extension Manager Fails

This report is based on a Test, that Randy Fay made for us, thanks a lot to him!

I am working on improving the documentation on how to install a site package in a classic TYPO3 13.4 installation as there has been repeated request for this. So I generated a site package with the site package builder https://get.typo3.org/sitepackage and then tried to upload it in the extension manager. I only get the not very helpful message “Extension some_package is not available”:

If I unzip the site package, manually move it into folder typo3conf/ext/some_package where some package is the exact Extension name I can activate it in the Extension Manger.

Choosing the site package based on the bootstrap package the first thing I see is an Exception of some bootstrap package classes not beeing found:

Then

If we want to keep supporting the Classic Installation I think it is very important that this keeps working.

Author Lina Wolf
Created 05/08/25, 13:32
Updated 05/19/25, 05:43
Bug
New Orphaned TYPO3 CMS 10

#94327 TCA type=inline and l10n_mode=exclude doesn't respect hidden field

In TYPO3 10.4 LTS, having a TCA column of a type=inline configured with l10n_mode=exclude doesn’t respect hidden field of default language record.

Example:

Having a site configured with fallbackType=fallback and having a product model with images.

There’s a product record:
- Product1 (default language)
– image1 (hidden=0)
– image2 (hidden=1)

In the FE:
- in the default language page only image1 is shown (correct)
- in the translated page both image1 and image2 are shown

Other things like sorting of images work.

Author Christian Toffolo
Created 06/12/21, 17:26
Updated 05/16/25, 10:09
Bug
New Orphaned Extension Manager TYPO3 CMS 11

#102609 Wrong processing order while installing extensions

Hello,

yesterday I tried to install my mysqlreport extension on a TYPO3 11 LIVE system configured as standalone. Instantly the website crashes with error 500. In logs I found that file XY of my mysqlreport extension could not be found. I logged into InstallTool, click button for AutoLoader and website is running again.

Today I have removed the dev-main version of our extension bynder2 from a composer based TYPO3 11 and directly installed bynder2 in version 2.0.3 afterwards. TYPO3 crashes because of too less arguments for bynder2 Configuration/ExtConf constructor. I have searched the cached DI file in var/cache/code/DI, but there are no “Bynder” entries available. I have visited the InstallTool, click Flush Cache (which also rebuilds this cache file), and the error was gone.

It seems that TYPO3 has a wrong extension installation process order

Stefan

Author Stefan Froemken
Created 12/06/23, 08:00
Updated 05/15/25, 08:01
Task
Under Review Orphaned Linkvalidator TYPO3 CMS 13

#106677 Improve Linkvalidator broken URL output in E-Mail Report

Right now the report provides the actual broken Target/URLs.
Those are cropped at 15 characters, but fully available as a title attribute on a <span> tag.

It would make sense to turn the <span> tag into a <a> tag with an actual link.
That way people receiving the report could directly check the broken url right from the email.

This only affects the HTML E-Mail as the plain text E-Mail already provides the full URL.

One could also add links to edit the broken Link. But TYPO3 isn’t able to build absolute URLs to its backend in CLI context right now.

Author Daniel Siepmann
Assigned to Daniel Siepmann
Created 05/12/25, 06:44
Updated 05/14/25, 07:15
Bug
Under Review Orphaned Authentication TYPO3 CMS 12

#106367 Pages with "show at any login" are not accessible to users without any assigned group

I stumbled upon the following scenario:

I have a page which is restricted to logged in users. The virtual group “show at any login” has the id -2. My expectation is that users with a login (active, valid session) should be able to access that page.

That user however, does not have any group assigned.

When \TYPO3\CMS\Frontend\Authentication\FrontendUserAuthentication::createUserAspect() assembles all groups of a user, it only assigns -2 if the user already has at least one group assigned.

$userGroups = [0];
$isUserAndGroupSet = is_array($this->user) && !empty($this->userGroups);
if ($isUserAndGroupSet) {
    // group -2 is not an existing group, but denotes a 'default' group when a user IS logged in.
    // This is used to let elements be shown for all logged in users!
    $userGroups[] = -2;
    $groupsFromUserRecord = array_keys($this->userGroups);
} else {
    // group -1 is not an existing group, but denotes a 'default' group when not logged in.
    // This is used to let elements be hidden, when a user is logged in!
    $userGroups[] = -1;
    if ($respectUserGroups) {
        // For cases where logins are not banned from a branch usergroups can be set based on IP masks so we should add the usergroups uids.
        $groupsFromUserRecord = array_keys($this->userGroups);
    } else {
        // Set to blank since we will NOT risk any groups being set when no logins are allowed!
        $groupsFromUserRecord = [];
    }
}

So I think this is a bug, actually. Users without a user group, that are logged in, should be given the -2 group.

Author Alexander Schnitzler
Created 03/13/25, 10:36
Updated 05/14/25, 07:15
Bug
Accepted Orphaned Backend User Interface TYPO3 CMS 13

#102736 Install Tool Configuration Presets broken for image handling settings with debug mode enabled

Hello,

Upgrade from 11.5.33auf 12.4.9.

If “Configuration Presets” ist set to Debug the “Configuration Presets” is broken. It returns an AJAX Error:

Core: Error handler (BE): PHP Warning: file_exists(): open_basedir restriction in effect. File(/opt/local/bin/identify) is not within the allowed path(s): (/usr/bin/) in /typo3_src-12.4.9/typo3/sysext/install/Classes/Configuration/Image/ImageMagick6Preset.php line 81
Core: Error handler (BE): PHP Warning: file_exists(): open_basedir restriction in effect. File(/opt/local/bin/gm) is not within the allowed path(s): (/usr/bin/) in /typo3_src-12.4.9/typo3/sysext/install/Classes/Configuration/Image/GraphicsMagickPreset.php line 77

Temporär solution set “Configure Installation-Wide Options” -> [GFX][processor_path] from /usr/bin/ to /usr/bin. Then “Configuration Presets” load without error. Set Debug mode to off an then you can use “Configuration Presets” again to switch preset between GraphicsMagick and ImageMagick6.

Author Arne Bracht
Created 01/01/24, 14:59
Updated 05/13/25, 12:15
Feature
New Orphaned Backend User Interface

#103418 Encourage editors to edit default metadata when adding files to content elements, rather than overwriting it

As an editor I want to be encouraged to fill out some meta information for files, when I upload and attach them to a content element.

Backround

Right now I am able to upload an image within a content element. A little preview is shown, and fields to overwrite the title and the alternative text, which have no default value yet. Only after I hit »save«, I am able to click an edit button to be redirected to the meta form of the original file and change the default values in there.

I have observed that many editors don’t click the edit button in this situation but instead tend to “overwrite” non-existing meta information. And keep this behaviour for relations as well (only overwrite, never set a default value).

How can we improve UI/UX to encourage filling out the information of the original file first instead of always overwriting it only?

Author Dan Kleine (Untenzu)
Created 03/18/24, 12:47
Updated 05/13/25, 07:51
Feature
New Orphaned FormEngine aka TCEforms

#93905 Visualize hidden state of items in TCA selects

When a TCA select element (e.g. SelectMultipleSideBySideElement) is used to allow the selection of records, it is not possible to visually show, if the state of a record is hidden or not. This may lead to unexpected expectations for users selecting items of TCA selects.

Adding a visual indicator (e.g. different color/styling for hidden items, postfix for hidden items) may help to make this more clear.

Author Torben Hansen
Created 04/12/21, 13:41
Updated 05/05/25, 08:04
Bug
New Orphaned Link Handling & Redirect Handling TYPO3 CMS 10

#93327 Popups for Redirect

The popup for redirects is too general and never allows to verify created redirects on the fly.
Instead I prefer having the old URL respectively slug shown and the new one.
Then it’s much easier to decide about it and the list of redirects never has to be crawled till the correct one is found.
As the list of redirects can get quite long this visual feature would be very useful – especially in cases where the automatically created redirect would break something.
Also the display top right without any blocking-mechanism is too trivial considering that changes might break a whole site.

Author David Bruchmann
Created 01/20/21, 13:27
Updated 04/28/25, 20:00
Task
New Orphaned Backend User Interface TYPO3 CMS 14

#106624 Add "Create new root page" to page tree context menu

Currently – even if you never created a page you only find a “New subpage” entry in the page tree on root level. I would suggest to add an option “Create new rootpage” in the context menu:

If the “New root page” option is chosen, the page should be

  • Automatically created on rootlevel with pid=0
  • Have the “Root page” flag preselected
  • Automatically have a new site config attached
  • Prompt user that a site set or TypoScript record is needed before page can be displayed
  • Maybe offer to pick a site set from the list or create a basic TypoScript record as would be done in the install tool
Author Lina Wolf
Created 04/26/25, 09:35
Updated 04/26/25, 09:51
Feature
New Orphaned Frontend

#106619 Allow fine-grained control of Cache-Control headers

If config.sendCacheHeaders == 1, TSFE currently supports two possible values for the Cache-Control header, depending on whether the rendered response is cacheable or not.

If the response is not cacheable, belongs to a workspace or there is an active BE session, TSFE outputs Cache-Control: private, no-store. However, if the response is cacheable, only the calculated lifetime of the page is considered (as calculated by CacheLifetimeCalculator) and then hardwired Cache-Control: max-age=<lifetime> (or, from TYPO3 13, an additional s-maxage if needed).

There is no way to set additional flags for Cache-Control or to influence this process globally in any other way. However, for using TYPO3 behind a CDN, it would be great if we could append additional options to the generated Cache-Control header, depending on whether the response is cacheable or not. The most important options here would be, for example, stale-if-error and stale-while-revalidate, which can control more precisely how long the CDN may continue to deliver a cacheable response from TYPO3 if, for example, TYPO3 is briefly unavailable.

I have no concrete idea how this could be elegantly designed in TS – one possible idea would be, for example, to do this via additional fields in config. So far we have solved the problem using a PSR-15 middleware that rewrites the header after the rendering process, but I think a proper solution would be much better.

Author Christian Spoo
Created 04/25/25, 13:59
Updated 04/25/25, 14:01
Bug
Needs Feedback Orphaned Performance TYPO3 CMS 11

#104718 Filelist extremly slow having a lot of folders with subfolders on Rootlevel

Story

Loading the file tree takes ages on a storage which has many Folders on rootlevel (122 folder ins my Case) when the folders themselves are containing a lot of subfolders.
This might even lead to max_memory exceed errors or maximum_execution time exceed

Cause

The FileStorageTreeProvides determines the presence of subfolder in a very inefficent and redundant way. Due to recursive nature of the used fuction the performance impact is extremly high.

Solution

*Step 1*
To detect if a folder has a subfolder or not it is not neccessary to fetch all subfolder one is enought so change:
https://github.com/TYPO3/typo3/blob/11.5/typo3/sysext/backend/Classes/Tree/FileStorageTreeProvider.php#L64

 $hasSubfolders = !empty($folder->getSubfolders());

To:

 $hasSubfolders = !empty($folder->getSubfolders(0, 1));

*Step 2*
The prepareFolderInformation already holds the information if there is a subfolder or not. So no need to determine it again.

So remove this
https://github.com/TYPO3/typo3/blob/11.5/typo3/sysext/backend/Classes/Tree/FileStorageTreeProvider.php#L207

And referre to “prepareFolderInformation[‘hasChildren’]” instead and reaad the check for InaccessibleFolder here:
https://github.com/TYPO3/typo3/blob/11.5/typo3/sysext/backend/Classes/Tree/FileStorageTreeProvider.php#L223

I applied the above changes to a my testystem and the loading time dropped from 30-55s to 2-3s.

Affected Systems:

  • Confirmed on TYPO3 11
  • Code looks the same in TYPO3 12 and 13 (only tested on v11)
Author Nikolas Hagelstein
Created 08/23/24, 15:40
Updated 04/24/25, 09:02
Bug
Under Review Orphaned Content Security Policy TYPO3 CMS 13

#106598 Content Security Policy / Firefox

*Backend, Modul Filelist*
If selecting more than one file for Download, a CSP Violation occurs and the download fails with:

Details

Direktive / Verwendung
    frame-src / enforce
URI des Dokuments
    https://epx-typo3-demo.ddev.site/typo3/main?redirect=media_management&redirectParams=id%3D1%253A%2Fdummys%2F&referrer-refresh=1745390035 
Blockierte URI
    blob
User-Agent
    Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:136.0) Gecko/20100101 Firefox/136.0
UUID
    bc4181c2-f3fc-40fa-a2c7-212b3f2cabd4
Übersicht
    0cd9a0289ef425b5346bc4326c7aab82ff851f84

Browserlog

Content-Security-Policy: Die Einstellungen der Seite haben das Laden einer Ressource (frame-src) auf blob:https://epx-typo3-demo.ddev.site/ed93011d-dfda-4ce6-89a8-dedac737b323 blockiert, da sie gegen folgende Direktive verstößt: “frame-src ‘self’ https://*.youtube-nocookie.com https://*.youtube.com https://*.vimeo.com”

So the download of multiple Files fails

Author Michael Kasten
Created 04/23/25, 07:02
Updated 04/24/25, 08:57
Feature
New Orphaned Backend User Interface

#98297 [UX] - Highlight Save Button in Edit View

As an editor,
I want to find the Save Button quick,
so I can speed up my work, by not reading every button label, to find the correct action to use.

Acceptance criteria

  • the most important and most used action is highlighted

Acceptance test

  • I am logged in as an editor
  • I am editing view
  • the Save button is highlighted by color and I can identify the Save button as Primary button

Technical remarks

Author Annett Jähnichen
Assigned to Annett Jähnichen
Created 09/08/22, 10:35
Updated 04/23/25, 10:14
Task
Accepted Orphaned Backend API TYPO3 CMS 12

#104329 Do not use no-reply@example.com email addres as a fallback for the defaultMailFromAddress

The typo3/cms-core/Classes/Utility/MailUtility.php class offers helper methods to fetch several configuration values related to making, providing also some fallbacks.

One of them is this method:

public static function getSystemFromAddress(): string
{
    $address = $GLOBALS['TYPO3_CONF_VARS']['MAIL']['defaultMailFromAddress'] ?? null;

    if (!is_string($address) || !GeneralUtility::validEmail($address)) {
        // still nothing, get host name from server
        $address = 'no-reply@' . php_uname('n');
        if (!GeneralUtility::validEmail($address)) {
            // if everything fails use a dummy address
            $address = 'no-reply@example.com';
        }
    }
    return $address;
}

So, here as a very last fallback we have the no-reply@example.com used which might not be a good idea as it can expose some sensitive data.
It should be considered if this fallback should be used and even if the php_uname usage is intended.
$GLOBALS['TYPO3_CONF_VARS']['MAIL']['defaultMailFromAddress'], just throw some exception.

Author Marcin Sągol
Created 07/07/24, 11:24
Updated 04/20/25, 15:10

Showing results 1076 to 1100 of 1561