Showing results 351 to 375 of 1561

Task
Under Review Orphaned Extbase TYPO3 CMS 13

#101461 Use php cache frontend for ClassSchema cache entries

Author Alexander Schnitzler
Assigned to Alexander Schnitzler
Created 07/27/23, 13:40
Updated 11/07/25, 17:22
Task
New Orphaned Localization TYPO3 CMS 14

#108144 Consolidate general purpose action labels

There are general purpose action labels like “Edit”, “Delete” etc defined in multiple domains. Consolidate general purpose action labels into a single file

Author Lina Wolf
Assigned to Lina Wolf
Created 11/16/25, 05:50
Updated 11/16/25, 05:50
Task
Under Review Orphaned Localization TYPO3 CMS 14

#108139 Move live search related labels

Author Lina Wolf
Assigned to Lina Wolf
Created 11/15/25, 17:40
Updated 11/16/25, 05:16
Feature
Under Review Orphaned

#107870 Modernize backend login provider registration

Backend login providers are currently registered via $GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['backend']['loginProviders']. This could be easily migrated to an attribute-based approach.

Author Elias Häußler
Assigned to Elias Häußler
Created 10/27/25, 20:04
Updated 11/20/25, 17:32
Task
New Orphaned Backend User Interface TYPO3 CMS 14

#108316 Separate visual connection of page-tree-header and doc-header

The page-tree and doc-header/content-area are visually completley connected by the horizontal lines.
But they do not belong together.

Current state

Suggestion – shortened lines

.tree-toolbar__menu {
  padding: var(--tree-toolbar-padding-y) 0;
  padding-inline-start: 0;
  margin-inline-start: var(--tree-toolbar-padding-x);
  padding-inline-end: 30px;
  margin-inline-end: var(--tree-toolbar-padding-x);
}
.module-docheader-navigation {
  padding: var(--module-docheader-padding-y) 0;
  margin: 0 var(--module-docheader-padding-x);
}

Suggestion – no middle line with reduced height

Suggestion – complete pagetree header overhaul without horizontal lines

Author Ayke Halder
Created 11/25/25, 15:34
Updated 11/25/25, 17:20
Bug
New Orphaned Extbase TYPO3 CMS 12

#102529 Properly support HTTP Status Code 201 within extbase

Sources regarding HTTP Status Code 201:

The 201 status code can contain a location header, like the 3xx redirect status codes.
This is currently not possible via Extbase, as Extbase has hard checks regarding >= 300 within the Bootstrap class after internal dispatching of the request. Returning a redirect with 201 and a url is therefore not working as expected.

Browsers (tested with Firefox) probably do not support this, but APIs might need to conform to this.

The corresponding checks regarding >=300 could be adjusted to also check for 201 status code.

Author Daniel Siepmann
Created 11/27/23, 14:53
Updated 11/24/25, 15:38
Bug
Needs Feedback Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 13

#107972 When moving a page that was created as a rootpage into the pagetree of a diffrend rootpage Sets /Sitepackages will not load correctly

in typo3 13.4.8
typo3 composer.json says php 8.2 while php -v says PHP 8.4.5
Running in Windows wsl : Podman Desktop : typo3 runson an image based on webdevops/php-nginx
under certain conditions a subpage loades the wrong Sets/Siteconfiguration that dose not come form it current root page

when a rootpage is moved into the pagetree of a different root page it will still use it own Sets/Site Configuration instead that of the the parrend root page.
(if one run into this use you can copy the page with will work since the created page gets a new uid )

Reproduction:
Operation:
New installed typo3
create page in root : testbug0
add sitesets to Home
add different sitesets to testbug0
copy testbug0 to root making : “testbug0 (copy 1)“
move “testbug0 (copy 1)” into Home
copy testbug0 into home making testbug0

Images serve to show the subpages of Home do not have the same Typoscript load

cause:
cause even after moving the page the site configuration still persists in config/sites/**
so the sets and Site Configuration of its self are used over that from the root of the pagetree.

Still new to how to write bugreports so feel free to criticise me.

Author Max Shade
Created 11/03/25, 16:34
Updated 11/05/25, 21:13
Feature
New Orphaned Linkvalidator

#89266 Prevention of running link checking more than once and visible feedback about still running checks

This is about running “check links” in the Info module, not in scheduler:

  • Once “Check links” is started, you get a flash message that it started, but not when it finishes
  • No check if another task is still running. This may result in several tasks being started concurrently and lead to duplicates (this is reproducible)
  • If a task is still running, you get no information about it in the “Report” (just “No broken links to show”). Since the “Check links” task removes all broken links at the beginning, this can be especially misleading.
  • After a check is done, the GUI should automatically switch back to “Report”. This used to work, but apparently no longer does.
Author Sybille Peters
Created 09/25/19, 14:35
Updated 10/20/21, 20:11
Bug
New Orphaned Backend User Interface TYPO3 CMS 10

#95049 Wrong default values of excluded localized fields

If a BE user doesn’t have access to a field in a localized record, this field gets the default value upon save instead of the parent record value.

Use case:
Default language is Italian and a BE user must only translate (edit) secondary language Spanish. We want to simplify the experience of this user so we only display the title (header) and text (bodytext) fields of tt_content. With this bug instead is mandatory to enable all fields in “Allowed excludefields”.

Step to reproduce:
1. BE user can’t edit tt_content.header_layout of a localized tt_content record because is not selected in “Allowed excludefields”.
2. tt_content.header_layout value in parent record is 5.
3. BE user saves the localized tt_content record

Result:
Localized tt_content record have now value 2 (default value for header_layout) instead of parent record value 5.

Author Christian Toffolo
Created 08/31/21, 09:29
Updated 08/31/21, 09:29
Feature
New Orphaned FormEngine aka TCEforms

#94368 Add option to remove new record link in translations

Oftentimes it is desired to keep inline fields always in sync with the default language. The problem is the new record button is always displayed even in other languages. Editors are able to create mixed content on inline field level. The best way would be to only add new inline elements with the showAllLocalizationLink-Button.

Author Nikita Hovratov
Created 06/17/21, 18:43
Updated 06/17/21, 18:43
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 10

#94003 Automatic update of subpages slugs not working for copy of subtree

The slug updater for subpages checks if the old slug of the parent page is part of the slug of the child pages. Otherwise no slug update is performed.
When you copy a page (parent-page) with subpages, the slug of the copied parent page is immediately changed (parent-page-1) thus the slug checks for the copied child pages (parent-page/child-page) fail.

Code in TYPO3\CMS\Redirects\Service\SlugService L264:

protected function updateSlug(array $subPageRecord, string $oldSlugOfParentPage, string $newSlugOfParentPage): ?string
    {
        if (strpos($subPageRecord['slug'], $oldSlugOfParentPage) !== 0) {
            return null;
        }
...

The check should work for copied pages as well.

Author Stefan Terborg
Created 04/28/21, 07:07
Updated 04/28/21, 22:01
Bug
New Orphaned Extbase + l10n TYPO3 CMS 9

#70154 Extbase 'sorting' l10nmode

When I use in the TCA ctrl-section of an item

‘sortby’ => ‘sprting’

the translated items are on the same position as the default ones in the backend. But in the frontend the order is wrong.
When I add

protected $defaultOrderings = array(
        'sorting' => \TYPO3\CMS\Extbase\Persistence\QueryInterface::ORDER_ASCENDING,
    );

in the repository the sorting worsk correct in the default language. But in another language the sorting is wrong. The problem is, that the sorting in the translated language is another number than in the default language, but it has to be the same because you can’t move only the translated language. I hope you can understand the problem.

Author Marc Hirdes
Created 09/28/15, 14:03
Updated 04/28/21, 11:51
Bug
New Orphaned Localization TYPO3 CMS 10

#93872 Localization problems (for tt_content) if source is a non-default language

Starting point
  1. Create page DE
  2. Create the content elements DE.A and DE.B on the page DE
  3. Create page ES
  4. Translate content elements from page DE to ES (connected mode) -> ES.A and ES.B
  5. Create page CL
  6. Translate content elements from page ES to CL (connected mode) -> CL.A and CL.B
PROBLEM 1:
  • Create a third content element DE.C on page DE
  • The translate button is now displayed on the CL page, but if you press it, no content elements are available in the popup and the process fails while localization
  • Problem can only be solved if the content element DE.C is translated to ES before and then it can be translated for the CL page
  • If there are many languages ​​in a project, it is impossible to know which language you initially used for Localization and there is no indication which language has been used as the source language!
PROBLEM 2:
  • Translate element DE.C directly for page CL (Edit Element DE.C on page DE and select the option “CL [NEW]” in the top selection box)
  • Delete element CL.B on page CL
  • If you click on the translate button on the CL page, ALL content elements of the default language are listed for translation even though they have already been translated

The problem also occurs in TYPO3 version 9 and 8.

Author Sandra Leitner
Created 04/07/21, 13:17
Updated 04/07/21, 13:17
Bug
New Orphaned TYPO3 CMS 10

#91718 DatabaseQueryProcessor should find tt_content entries by uid regradless the pid

I created a content element (Footer) which is located on pid 88. I then created a lib to get the content element to all of my pages by addding it on my Layout.

lib.footer = CONTENT
lib.footer.table = tt_content
lib.footer.select.pidInList = 88
lib.footer.select.uidInList=201

When i call it on the page 88 everything works fine. If i call it on another page (55) on the other hand, then the element is found but the information is not there. The variable defined on the DatabaseQueryProcessor comes back empty.
I debuged the query and it seems that TYPO3 request the footer element but on the current pid and not on the pid i defined here:

lib.footer.select.pidInList = 88

The query:

SELECT * FROM `footer` WHERE (`footer`.`pid` IN (55)) AND (2011) AND (`footer`.`sys_language_uid` IN (0, -1)) AND ((`footer`.`deleted` = 0) AND (`footer`.`t3ver_state` <= 0) AND (`footer`.`t3ver_wsid` = 0) AND (`footer`.`t3ver_oid` = 0) AND (`footer`.`starttime` <= 1593183420) AND ((`footer`.`endtime` = 0) OR (`footer`.`endtime` > 1593183420)))

My footer.typoscript

dataProcessing {
   330 = TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor
   330 {
      table = footer
      where.field = uid
      where.dataWrap = |{field:footer_relation}
      as = footerInfo

Now here, if the pid is not defined than it should be ignored and find the tt_content by it’s ID regardless the PID, which it doesn’t do. It always requires a pid and returns an empty footerInfo if called on another page.

If i however add this on my DatabaseQueryProcessor:

pidInList = 88

Then i get the content element’s information on the other pages as well and the query looks like this:

SELECT * FROM `footer` WHERE (`footer`.`pid` IN (88)) AND (2011) AND (`footer`.`sys_language_uid` IN (0, -1)) AND ((`footer`.`deleted` = 0) AND (`footer`.`t3ver_state` <= 0) AND (`footer`.`t3ver_wsid` = 0) AND (`footer`.`t3ver_oid` = 0) AND (`footer`.`starttime` <= 1593183840) AND ((`footer`.`endtime` = 0) OR (`footer`.`endtime` > 1593183840)))

Now i get the content only because i specifically defined the 88 on the DatabaseQueryProcessor

Author Aristeidis Karavas
Created 06/26/20, 17:10
Updated 03/17/21, 09:30
Feature
Accepted Orphaned Backend User Interface

#93669 New TCA column type - Multiple input fields to csv values

I request a feature related to TCA column select type. I currently use the select fields with their grouping functionality a lot for giving a user certain settings for the content elements.

Apart from that for more complex content elements I often also have a lot of settings that need individual user input e.g. I have a map content element, so users need to set latitude, longitude, markers, lng and lat for markers, filter groups for those markers etc.

What I would love to have is a group of input fields next to each other like in a palette, that will be saved to one database column comma seperated.
So I would like to set an items array just like for the select type, but for each item I get an input field rendered out.
I never need to filter database queries by these settings, so storing them in one column would also stay efficient. Of course to correctly access the fields either the key needs to be saved aswell or empty fields also need to be stored at least with a comma to access the correct values by index.
Handling all those fields in own database columns is unnecessary, time consuming and it’s easy to loose a structured way by defining so many fields.

I know the current way to do it are flexforms, which I currently do use, but the problem is, for large setting groups its more time consuming to create the xml structure instead if a simple items array.
Additionally flexform fields can not be shown side by side like palettes so for a long settings list its hard to not loose track on scrolling down those lists and its very unnecessary to have a complete row available for a very small generic input.
On top of that I need to define each tca column type per field whereas I simply want all fields to be the same type so I end up copy pasting and repeating a lot of code.
Though I want to mention that I love the new FlexFormProcessor since v11.

Anyways, what do you think about such a column type, do you also consider this useful enough to be a core feature. I don’t know too much about the internal processing of the core, but it seems to me like this might not be too hard to implement as the general structures already exist (input fields, paletts, comma-seperated-storing and CSVDataProcessor), so it would just be a different combination of those techniques.

Author Benny Bachmann
Created 03/06/21, 11:19
Updated 03/08/21, 08:32
Feature
New Orphaned TypoScript

#87551 Explicitly allow ignoring "pidInList" in TS select function

Currently, the implementation of the TypoScript function “select” will automatically set “pidInList” to “this” if it is not set, even when “uidInList” is specified and points to a uid on a different page.
The result will then be empty, even if the record exists and could be displayed. This is confusing and hard to understand, especially since there is no documented way of ignoring “pidInList”. Instead, some people implement workarounds with high recursion limits e.g. descending from the site’s root page.

My proposal is to add a new setting “ignore” that will lead to the value not being evaluated. This works already, since the non-empty value will prevent the default of “this” from being used. However, it is undocumented behaviour and thus might break in the future w/o any notice. Therefore, let’s make it explicit and document it.

Author Andreas Wolf
Assigned to Andreas Wolf
Created 01/25/19, 15:59
Updated 02/05/21, 16:57
Bug
New Orphaned Workspaces TYPO3 CMS 10

#93286 Workspace notification Email not showing multiple page IDs

*Description:*
- When changing the stage of multiple pages at the same time, the notification mail will generate only one preview link for one page.

*Steps to reproduce*
1. Go to live mode
2. Create two pages with one or to content objects in each.
3. Switch to workspace
4. Make changes on two content objects from different pages
5. Switch to workspaces module
6. Select all the changed objects and send them to a different stage with a mass action

*Actual behavior*
An Email will be sent. In this Email there is only one preview link and all changes are listed under one site Id

*Expected behavior*
There should be one preview link for each site with changes on it. Also all changes are listed under one site.

Author Victor Manuel Grande Escanciano
Created 01/14/21, 07:33
Updated 01/14/21, 07:33
Bug
New Orphaned Install Tool TYPO3 CMS 10

#91800 Calculation of the relative path of the Typo3 library during CoreUpdate in combination with softlinks in the document path

Hello,

i have at my new webhoster there is an unusual directory structure. It has a mixture of softlinks and real directories.

Simplified and similar to this example:
/abc/softlink :: <- Link to /abc
/abc/customer/htdocs :: <- real directory with Typo3

For whatever reason, the hoster has now set it up so that the document path is: /abc/softlink/customer/htdocs

Unfortunately CoreUpdateService does not work like this. Because in the method: CoreUpdateService#activateVersion($version) the “realpath()” is created by the path of the Typo3 library:

$newCoreLocation = @realpath($this->symlinkToCoreFiles . '/../') . '/typo3_src-' . $version;

But then the method CoreUpdateService#getRelativePath(…) is used:
$newCoreLocation = $this->getRelativePath($newCoreLocation);

However, CoreUpdateService#getRelativePath(…) directly uses the document path (Environment::getPublicPath()) without “normalizing” it with realpath.
At my webhosts this unusual softlink is in the root directory. This creates a totally long and relative path. Which does not even work.

Therefore, the method CoreUpdateService#getRelativePath(…) suggests this correction:

    /**
     * Get relative path to TYPO3 source directory from webroot
     *
     * @param string $absolutePath to TYPO3 source directory
     * @return string relative path to TYPO3 source directory
     */
    protected function getRelativePath($absolutePath)
    {
        $sourcePath = explode(DIRECTORY_SEPARATOR, @realpath(Environment::getPublicPath()));
        $targetPath = explode(DIRECTORY_SEPARATOR, @realpath(rtrim($absolutePath, DIRECTORY_SEPARATOR)));
        while (count($sourcePath) && count($targetPath) && $sourcePath[0] === $targetPath[0]) {
            array_shift($sourcePath);
            array_shift($targetPath);
        }
        return str_pad('', count($sourcePath) * 3, '...' . DIRECTORY_SEPARATOR) . implode(DIRECTORY_SEPARATOR, $targetPath) ;
    }

So you can put “any” path in there and internally this method always works with the real paths.

Best regards
Clemens

Translated with www.DeepL.com/Translator (free version)

Author C. Gogolin
Created 07/14/20, 09:40
Updated 08/16/20, 14:28
Bug
New Orphaned Logging TYPO3 CMS 7

#78849 Show logged records of DatabaseWriter in ext:belog

Log entries that have been persisted using the logging-framework are not visualized in ext:belog.
The reason is, that the logging-framework uses different field names for the sys_log table that are not considered.

Author Oliver Hader
Created 12/01/16, 12:33
Updated 07/08/20, 23:49
Feature
New Orphaned Reports

#91668 Add system communication API

A system communication API could be used to retrieve data from official typo3.org services or send back anonymous usage data in order to help understand TYPO3-use-cases much better.

Scenarios

  • compare current TYPO3 version with latest TYPO3 version & warn about missing security updates
  • fetch and display vendor messages for selected topics – e.g. release updates, important security notifications, etc.
  • send anonymous usage data back to granted services (typo3.org or custom endpoints)

Requirements

  • non-blocking – most of the communication shall happen in the background or in the client only (AJAX)
  • HTTP requests need to provide as less information as possible (no referrers, no cookies, …)
  • each used communication stream/channel must be opt-in – users or site admins have to subscribe
Author Oliver Hader
Created 06/17/20, 17:46
Updated 06/17/20, 17:46
Bug
New Orphaned TYPO3 CMS 10

#91408 Improvements for slug handling of records in global storage

The fix for uniqueInSite handling and the resulting troubles some limitations in flexibiltiy regarding URL generation when records are stored in a global folder.

The issue here is, that one cannot know in which site a record, that is stored anywhere, is eventually rendered and URLs are generated/resolved for.

Therefore we cannot:

1. Know based on which site(s) de-dulpication needst to be performed on
2. Know which total URLs this slug will finally have and thus cannot add a preview for editors

One idea to address that would be to evaluate TSConfig on the record storage, which holds the required information.

We could for example re-use the preview page ID configuration to assume a single site.
But to cover the case that records might be shown on multiple sites, we would need to introduce TSConfig setting
which lets developers add multiple sites in which these records will be rendered.

Additionally, if feasible, it would be nice to also disallow adding a storage page to plugin settings, which is not suitable for the site this plugin is on.

Author Helmut Hummel
Created 05/14/20, 18:19
Updated 05/14/20, 18:19
Feature
New Orphaned File Abstraction Layer (FAL)

#90545 Add videofile_ext, audiofile_ext and applicationfile_ext

I’ve seen there is already https://forge.typo3.org/issues/90305… Perhaps the following might be another improvement:

Currently there is no variable for plain “audio”, “video” or “application” file extensions. So getFalFieldTcaConfig()’s 3rd parameter needs to get passed hardcoded when dealing only with those certain file types. This is not upgrade-safe.

By introducing an additional “videofile_ext”, “audiofile_ext” and “applicationfile_ext” variable, backend definitions could be done straight with frontend behaviour (fluid media rendering). The abstract file class already contains all 5 types…

\TYPO3\CMS\Core\Resource\File::FILETYPE_TEXT
\TYPO3\CMS\Core\Resource\File::FILETYPE_IMAGE
\TYPO3\CMS\Core\Resource\File::FILETYPE_AUDIO
\TYPO3\CMS\Core\Resource\File::FILETYPE_VIDEO
\TYPO3\CMS\Core\Resource\File::FILETYPE_APPLICATION

…and perhaps in near future, FSC’s integrated media rendering will be extended with the missing types related to this :)

Author Jan Kornblum
Created 02/27/20, 03:03
Updated 02/27/20, 07:39
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 9

#90405 Slugs are not maintained reasonable when copying pages/pagetrees

If you copy a page (or smaller portion of the pagetree) from one page to another, the resulting slugs are not really maintained in reasonable way.

Example:

- Main X
— Submain X
—- Subsub X
- Main Y
— Copy of Submain X
—- Copy of Subsub X -> resulting slug: main-x/submain-x/subsub-x-1

This behaviour is irritating and not SEO friendly.
ATM one could only resolve by cleaning all slugs via DB and regenerating them with the update-wizard.
Non-core solutions are e.g. EXT:sluggi

Author Clemens Riccabona
Created 02/17/20, 11:58
Updated 02/17/20, 13:26
Bug
Accepted Orphaned Extbase TYPO3 CMS 8

#89671 Allow for Collation in extbase repository queries

We are experiencing issues with sorting database results.
We use utf8_unicode_ci as collation in all our databases and string columns.

utf8_unicode_ci do not support the danish characters Æ,Ø,Å.
The character Å as sorted as A – giving us wrong sortings.

For example:
SELECT header FROM `tt_content` ORDER BY header ASC
A is the first letter in danish alphabet
Å is the last letter in danish alphabet
B
C

SELECT header FROM `tt_content` ORDER BY header COLLATE utf8_danish_ci ASC
A is the first letter in danish alphabet
B
C
Å is the last letter in danish alphabet

The easy fix is of course to change the database collation to utf8_danish_ci and get the sortings correct.

But we have quite a few multilanguagal sites using the same db and tables. So it would sort correctly in one language
but not in others and we would very much like to control the sorting from the typo3 side.

The problem: You can´t use COLLATE in Extbase repository queries for sort order using the query object.

So in a extbase repository you can do:

$orderings[‘title’] = QueryInterface::ORDER_DESCENDING;

But this will not work:
$orderings[‘title’] = ‘COLLATE utf8_danish_ci ‘.QueryInterface::ORDER_ASCENDING;

$query->setOrderings(
$orderings
);

https://api.typo3.org/TYPO3_8-7/_typo3_db_query_parser_8php_source.html#l00261
protected function parseOrderings(array $orderings, Qom\SourceInterface $source) {
foreach ($orderings as $propertyName => $order) {
if ($order !== QueryInterface::ORDER_ASCENDING && $order !== QueryInterface::ORDER_DESCENDING) {
throw new UnsupportedOrderException(‘Unsupported order encountered.’, 1242816074);
}
….

What is the reason for this check in the parseOrderings function ?

Regards
Henrik

Author Henrik Jensen
Created 11/13/19, 13:31
Updated 01/14/20, 10:10
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 9

#88929 TCAM:N relation -> leave record with unsaved changes redirects to list instead to create wizard

Hey,

changing items on a TCA m:n table relation and then trying to add create new items from a specfic type (the “+” button) will show the modal “you are leaving the page with unsaved changes”. If you click “save and close” you expect to go to the wizard which will enable you to create a new item. you will get redirect to the list view instead.

I’ve shot a video which I think can describe this better

Possibly related to https://forge.typo3.org/issues/88875, however I have not yet tried the fix.

- Pascal

Author Pascal Querner
Created 08/07/19, 15:34
Updated 10/01/19, 20:36

Showing results 351 to 375 of 1561