Showing results 1051 to 1075 of 1561

Bug
New Orphaned Frontend TYPO3 CMS 11

#79234 Special Menu "Section Index" in "Backend User Section" are not rendered in the Frontend (TYPO3: 6.2, 7.6, 8.5)

Problem Description
> “Special Menu” content elements from type “Section Index” in “Backend User Sections” are not rendered in the Frontend.

tested TYPO3 Versions
> this problem occurs in TYPO3 versions 6.2, 7.6, and 8.5. It was tested in empty typo3 instances.

!SectionIndexBackend.png!
Section Index CE on “Page”

!SectionIndexBackendBackendUserSection.png!
Section Index CE on “Backend User Section”

!SectionIndexFrontend.png!
Frontend Output normal Page

!SectionIndexFrontendBackendSection.png!
Frontend Output Backend User Section

Author Sebastian Stein
Created 01/10/17, 09:36
Updated 08/01/25, 16:21
Epic
In Progress Orphaned System/Bootstrap/Configuration

#103034 Unified Settings API

We should have a new and unified Settings API.

For Content, we have TCA and FormEngine / DataHandler, but for settings, this is all inconsistent and not unified:

  • Extension Configuration API (“cryptic syntax”)
  • TypoScript Constants API (“cryptic syntax”)
  • Site Settings API (no visual API yet)
  • User Settings API (custom API, could be moved into a TCA.be_users.settings custom field)
  • “System-wide” settings / global settings (Install tool via DefaultConfiguration.yaml), not extendible

Settings API means the definition of a setting, by various kinds to be configurable, and stored depending on the actual level.

The location where it is persisted is not scope of this epic currently, however the definition, the validation, the usage and the UI is part of it.

We need a new API which superseds at least the first three parts in order to move forward.

For Site Settings, it is a must-have to include site setting presets from extensions and to override them.

As a future step: Dashboard Widgets need to be able to use Settings as well.

Author Benni Mack
Created 02/04/24, 13:29
Updated 08/01/25, 09:30
Bug
Under Review Orphaned Workspaces TYPO3 CMS 12

#107154 No way to review workspace changes from all sites or webmounts

Since https://forge.typo3.org/issues/96548 it is no longer possible to get an overview of all changes of all webmounts or all sites via the virtual root page uid=0) in the workspaces backend module.

Instead a message is triggered that is actually wrong:

> Please select a page in the page tree to review and publish changes.

This message is wrong page, because it is shown even if the page with the virtual id=0 is selected by a user, but the workspaces module denies to respect the desire of the user.

See https://forge.typo3.org/issues/95854 for an issue where the same usecase was reported and fixed previously (3 months before the mentioned change broke it again).

Author Benjamin Franzke
Created 07/28/25, 11:29
Updated 07/30/25, 09:39
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
Task
Accepted Orphaned Database API (Doctrine DBAL) TYPO3 CMS 11

#101235 Make additional DB connections optional sometimes, e.g. in case of SchemaMigration

While one can expect that the default DB connection for a TYPO3 is always available, there are scenarios where additional databases might not be available temporarily. Especially in case of schema migration this can result in problems, e.g. because a “not so important” additional DB should be ignored, while still wanting the schema migration to take place for the default connection.

A common scenario where this could occur is during deployment when and if the EXT:typo3_console command database:updateschema is run.
Currently, running this command with an unavailable additional DB is not possible as an unhandled exception would be thrown before the actual migration, due to the connection timeout.

So there seems to be the general idea there could be a need to be able to “skip” additional databases in some scenarios, most probably (but perhaps in other cases as well) during :
  • SchemaMigration
So the database configuration needs to cater for different scenarios:
  1. no schema migration should be done (table is completely managed by a 3rd party)
  2. schema migration only for mapped tables (in general tables are managed by a 3rd party, but a few tables were created by TYPO3)
  3. full schema control (like TYPO3 default, 3rd party tables not mapped should be removed)
While this covers the intended altering of tables, in order to cope with connection issues perhaps additionally
  • the schema migration should have an option to skip unavailable connections (handle the exceptions) and still run for the others
Current state is:
  • If a table mapping exists, then the whole connection is treated by the SchemaMigration
Some incomplete approaches for the current situation are:
  • additional.php: Check if additional condition is up (and perhaps if on CLI), perhaps remove connection.
  • read-only user for db access
Author J. Peter M. Schuler
Assigned to Stefan Bürk
Created 07/04/23, 23:41
Updated 07/25/25, 12:02
Bug
Accepted Orphaned SEO TYPO3 CMS 12

#105837 Sitemap.xml can be called with every URL of one domain

So I am accusing a strange behavior:
If I add /sitemap.xml to every URL in my domain, i can call the sitemap.xml

test.de/sitemap.xml
test.de/anotherURL/sitemap.xml
test.de/anotherPath/to/anotherURL/sitemap.xml
etc.
These are also no redirects e.g. from test.de/anotherURL/sitemap.xml -> test.de/sitemap.xml

My sitemap configuration looks like this:

routeEnhancers:
  PageTypeSuffix:
    type: PageType
    map:
      sitemap.xml: 1533906435

Am I doing something wrong?
I thought the sitemap.xml should only be displayed at test.de/sitemap.xml

This occurs in v12 and 13

Author Fabian Schiller
Assigned to Benni Mack
Created 12/17/24, 10:55
Updated 07/18/25, 13:46
Feature
New Orphaned Site Handling, Site Sets & Routing

#91222 Make dependency injection possible for errorPhpClassFQCN

Because TYPO3\CMS\Core\Site\Entity\Site::getErrorHandler() passes two arguments to the constructor of classes declared as errorPhpClassFQCN, dependency injection is not possible.

I guess, the solution should be to change the method PageErrorHandlerInterface::handlePageError() to accept the $statusCode and $errorHandlerConfiguration. Or add a new interface method for compatibility/deprecation reasons.

Additionally, a new method Site::getErrorHandlerConfiguration(int $status) could remove the binding of creating and configuring an errorPhpClassFQCN.

What are your thoughts? I’d also be happy to provide some code for this.

Author Christian Futterlieb
Assigned to Benjamin Franzke
Created 04/28/20, 14:41
Updated 07/16/25, 18:50
Bug
Needs Feedback Orphaned Link Handling & Redirect Handling TYPO3 CMS 13

#107099 Redirects on Language Rootpages

In out System we have the configuration

routeConfiguration:
trailingSlash: ‘never’

base: ‘https://test.com/’

languages:
-
title: English
enabled: true
languageId: 0
base: /en
locale: en_US.UTF-8
navigationTitle: English
flag: us
hreflang: ‘‘
websiteTitle: ‘‘
-
title: German
enabled: true
locale: de-DE
hreflang: de-DE
base: /de
websiteTitle: ‘‘
navigationTitle: ‘‘
fallbackType: strict
fallbacks: ‘‘
flag: de
languageId: 1

The Problem now is that i can not delete the / in the German Rootpage Page Properties.
Because of that it will generate the link for

https://test.com/de
everytime as
https://test.com/de/
in the sitemap.xml

The crawler can not crawl the page, because it is an 301 redirect now.

Author Torsten Niederberger
Created 07/15/25, 09:01
Updated 07/15/25, 09:09
Bug
New Orphaned Extbase + l10n TYPO3 CMS 14

#107082 'l10n_mode' => 'exclude' doesnt update localized record

If an inline field has got

‘l10n_mode’ => ‘exclude’

Child localized records are created with the same values as the source record (l10n), but then they are no longer updated .
The same in T3-13 (not tested in T3-12)
The inline field TCA configuration:

        'children' => [
            'exclude' => false,
            'l10n_mode' => 'exclude',
            // 'l10n_display' => 'defaultAsReadonly',
            'label' => 'Children',
            'description' => '',
            'config' => [
                'type' => 'inline',
                'foreign_table' => 'tx_testing_domain_model_child',
                'foreign_field' => 'parent',
            ],
        ],

Attached the video and the ext for testing

NB: in ext for testing, pls do not take into account the “Include” domain: it was for a previous test

.

Author Davide Alghi
Assigned to Tymoteusz Motylewski
Created 07/13/25, 06:59
Updated 07/13/25, 06:59
Bug
New Orphaned Localization TYPO3 CMS 13

#107078 Bidirectional editing of records with multiple languages sets wrong uids in mm-table

Im trying to have a bidirectional link across two models. One Product can contain multiple productgroups and one productgroup can contain multiple products. Best case is to edit records on both sides in backend. So I configured the TCA like this:

// TCA of tx_sitepackage_domain_model_product.php

'groups' => [
    'label' => 'Groups',
    'l10n_mode' => 'exclude',
    'config' => [
        'type' => 'group',
        'foreign_table' => 'tx_sitepackage_domain_model_group',
        'allowed' => 'tx_sitepackage_domain_model_group',
        'MM' => 'tx_sitepackage_domain_model_product_group_mm',
    ]
],

// TCA of tx_sitepackage_domain_model_group.php

'products' => [
    'label' => 'Products',
    'l10n_mode' => 'exclude',
    'config' => [
        'type' => 'group',
        'foreign_table' => 'tx_sitepackage_domain_model_product',
        'allowed' => 'tx_sitepackage_domain_model_product',
        'MM_opposite_field' => 'groups',
        'MM' => 'tx_sitepackage_domain_model_product_group_mm',
    ]
],

Works nice as long there is only one language available in the system. I can edit both ways and my models contain all related models.
As soon as I add another language and start translating my records, the behaviour gets strange.

let’s create „Group 1“ and „Product 1“ and translate it („Group 1 EN“ / „Product 1 EN“). Let’s edit Group 1 and add Product 1 to it. So far it seems to be fine. But if edit Product 1 we see in our groups field both „Group 1“ and „Group 1 EN“. Also in our product model in frontend, in default language there are both groups and in translated model is no group.

MM table looks like this:

_.uid_local (product) _.uid_foreign (group)
1 5
1 6

UIDs of records:
Product 1: 1
Product 1 EN: 2
Group 1: 5
Group 1 EN: 6

In my opinion uid local in second row should be the translated uid (2) instead of defaultlanguage uid (1). If I change it in DB from 1 to 2, it seems to work as indented.

Author Philipp Schlosser
Created 07/11/25, 12:31
Updated 07/11/25, 13:51
Bug
New Orphaned Workspaces TYPO3 CMS 13

#107071 Duplicated references (same language and parent) after publishing

When creating a translation in a workspace. Prior to publishing the records, the same page content is translated in the LIVE workspace
causing conflicting records in the database. (See the attached file)

For example uid 45 and 46 both have the same language and the same l18n_parent which does not work

uid sys_language_uid header t3ver_oid t3ver_wsid sys_language_uid l18n_parent t3ver_state deleted MY COMMENT
—- ———————— ———————————— ————- ————— ———————— —————- —————- ———- ———————————————————
45 30 GERMAN EDIT WORKSPACE 0 0 30 42 0 0 EXPECTED LIVE VALUE AFTER PUBLISHING
46 30 GERMAN EDIT LIVE LIVE 0 0 30 42 0 0 EVIL
42 0 Some Record to play with 0 0 0 0 0 0 OK

Steps to reproduce:

1. Go to a workspace and translate records from e.g. US to danish and change the content
2. Go to the LIVE workspace and tranlate the same records to the same language e.g. US to danish
3. Go to the workspace and publish the records

See the old record in the list module – Page module looks ok but the DB has now conflicting records.

Note: The same happens for sys_file_metadata

Author Jochen Roth
Created 07/10/25, 15:21
Updated 07/10/25, 15:23
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 14

#107041 Make live search more prominent in topbar

The Live Search is really good. And it should be made more prominent rather than being “hidden” behind a small button.

Author Andreas Nedbal
Created 07/04/25, 15:19
Updated 07/04/25, 16:08
Bug
Needs Feedback Orphaned DataHandler aka TCEmain TYPO3 CMS 13

#107030 Fields hidden, starttime and endtime do not sync

I have records that I want to keep some field in sync in the translated version.
I’ve add l10n_mode=exclude dans l10n_display=defaultAsReadonly to the fields hidden, starttime and endtime.
In the translated record in the backend, I see the original value (defaultAsReadonly), but in the database, the value can be different.
When I update the original record, those fields are not kept in sync with the original record, as it do with other fields.
Not sure if a bug, a feature or I’m missing something.
By records are used in an IRRE, but it work with other fields (ex: a custom title field).
It’s a custom table, not a tt_content.

I use Content-Block to create my records, and I use the content-blocks dataProcessor to retreive the content.
Is it the dataProcessor that do not do the overlay as it should? Overlay is only for tt_content, no?

Author Maxime Lafontaine
Created 07/03/25, 18:41
Updated 07/04/25, 13:54
Task
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 14

#107040 Streamline array vs object handling in settings type values

A custom settings type that implements a rich value (e.g. consisting of sub-objects or arrays) has to handle the value as an array or as an object depending on which context calls transformValue():

    public function transformValue(mixed $value, SettingDefinition $definition): array
    {
        return array_map(static fn (array|object $entry) => is_object($entry) ? (array)$entry : $entry, $value);
    }

We should ideally deliver yaml objects as php stdClass objects and arrays as arrays, always, but that might be breaking for existing anonymous (pre v13) settings, that are used to use array, even if objects were configured in yaml.

Author Benjamin Franzke
Assigned to Benjamin Franzke
Created 07/04/25, 11:59
Updated 07/04/25, 11:59
Task
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 13

#107039 Add settings type helpers that ease integration of repeating element patterns

The UI of the stringlist is hard to reimplement in custom settings type.
The core should offer reusable components to be used by settings type in order to ease the generation of rich custom types.

Author Benjamin Franzke
Assigned to Benjamin Franzke
Created 07/04/25, 11:55
Updated 07/04/25, 11:55
Bug
New Orphaned TYPO3 CMS 13

#107028 Invalid site sets are hard to debug and show missleading information

When having misconfigured Site Sets it´s hard to find where the problem is.

In the settings interface i can see that this site has an invalid set.
And it´s telling me that it’s missing a dependency. But the set is available and included in the same package.
I have no way to access the current settings anymore nor i get presented any relevant information in this view,
that would explain the error.

The situation is the same for the sites module.

I need to scroll down to find a new section that displays invalid sets, but not all of them

I can now see some messages but without context to the site.
I can see that an invalid page type is provided by “blog/static“
I can see that “blog/standalone” is disabled due to a missing dependency, but blog/static is available – but it´s broken / has errors

My expectation would have been that i was getting the message that the blog/static has a problem in the first place.
So i would have expected to see the root cause of the problem and not the end of the chain.

Author Benjamin Kott
Created 07/03/25, 13:28
Updated 07/03/25, 13:28
Bug
Accepted Orphaned Pagetree TYPO3 CMS 13

#104697 Unexpected behaviour - placing new items in the page tree. Safari Desktop

When adding a new item to the page tree (Page, Mount Point etc) I expect to see the blue line which indicates where my new item will be placed in the page tree.

In both Safari Desktop 17.6 & 18.0 Preview the blue line appears intermittently.

Examples attached.

Author Tom Warwick
Assigned to Benjamin Kott
Created 08/22/24, 11:38
Updated 07/02/25, 09:19
Feature
New Orphaned FormEngine aka TCEforms

#106977 SuggestWizardController: Add alphabetic sorting for group fields with multiple tables

The sorting of the suggestions can be controlled with a page tsconfig like this:

TCEFORM.<table>.<field>.suggest.default.orderBy = title asc

Unfortunately, if you have a group field which can have records assigned from multiple tables, this sorting is done per table and therefore does not really work, because the results of the tables are just concatenated after each other. It would be nice, if at least an alphabetic sorting by title could be activated in this case.

My idea is to add a sorting of $resultRows by label before this line: https://github.com/TYPO3/typo3/blob/v13.4.14/typo3/sysext/backend/Classes/Controller/Wizard/SuggestWizardController.php#L194

This multi-table label sorting could also be activated by page tsconfig.

Author Kai Strecker
Created 06/25/25, 15:47
Updated 06/25/25, 20:54
Feature
New Orphaned FormEngine aka TCEforms

#106978 SuggestWizardController: Set max-height to suggestion box and add scrollbar

One might want to increase the number of suggestions with page tsconfig:

TCEFORM.<table>.<field>.suggest.default.maxItemsInResultList = 30

But a high suggestion box is impractical, especially if you have a small screen. Therefore, I think it is a good idea, to set a max-height and add a scrollbar. This behaviour could be activated and the max-height set with page tsconfig:

TCEFORM.<table>.<field>.suggest.default.maxHeightInListItems = 10
Author Kai Strecker
Created 06/25/25, 15:48
Updated 06/25/25, 20:54
Feature
Accepted Orphaned Backend User Interface

#65505 Add paging for IRRE-records (working with many IRRE-entries)

There exist cases when many child-records are added to an entry. If an entry with 50 or more IRRE-relations gets opened in the backend things quickly get slow and are also not really easy to work with. Find a way to handle “many IRRE-relations” in one record.

Author Stefan Neufeind
Created 03/04/15, 11:58
Updated 06/24/25, 10:02
Feature
Accepted Orphaned Backend User Interface

#26139 un-/hide multiple records with one click

using the clipboard 1 to 3 (other than normal) you can do some edits/ changes to multiple records at once:
> * copy/move (with the actual clipboard,
> * edit,
> * delete

but you can’t hide/unhide multiple records at once.

clicking fast multiple lightbulbs (Extended view) an rebuild/reload of the BE will limit you to just a few records which change status (by racing requests?)

would it be possible to un-/hide multiple (selected) records with one click?
would it be possible to have further action to multiple (selected) records at once?

Author Bernd Wilke
Created 04/20/11, 01:09
Updated 06/23/25, 20:08
Feature
Accepted Orphaned Workspaces

#103042 Workspaces Feature: Compare changes view for non-editors

In the Workspace Extension for TYPO3, there is a great preview mode when I’m logged in as an editor, that offers a comparison of the unpublished and live version

But when I send a link from the Workspace module to a client who doesn’t have a login, it only contains the unpublished version, without the comparison.

Would it be possible to add the feature that it is possible to send the comparison to external users as well?

The screenshot shows an example of the compare view.

Author Urs Braem
Created 02/04/24, 19:44
Updated 06/20/25, 12:39
Feature
Accepted Orphaned Backend User Interface

#44001 Enhance usability of Web / Access in the BackEnd

To set the owner/group access rights in the backend
in a more comfortable way there could be a clipboard like function:
With checkmarks in front of the pages it should be possible to check
pages and then change teir access-rights within one form.

In short it should be possible to work with the pages access-rights
just like we do with the pages properties or the pages content-elements.

Author Paul A. Auwehla
Created 12/14/12, 11:14
Updated 06/20/25, 11:04
Bug
New Orphaned DataHandler aka TCEmain TYPO3 CMS 11

#102554 Cannot move content element over another in workspace

The behavior only occurs if you move an element in a workspace over another element that is already present in Live and the calculated new sort number is not smaller than that of the subsequent element. In this case, a function is called which should increase the sort number of the subsequent element. However, as workspace is enabled for tt_content, t3ver_oid = 0 is appended to the query. As the subsequent element in the t3ver_oid column has a reference to the live element, this is not updated and the sort number is not increased and therefore the order is not adjusted. This makes it appear to the user as if nothing is changing.

Described function: TYPO3\CMS\Core\DataHandling::increaseSortingOfFollowingRecords

Author Konstantin Wagner
Created 11/29/23, 13:32
Updated 06/17/25, 13:03
Task
New Orphaned TypoScript TYPO3 CMS 13

#106877 Log a warning if site set provided TypoScript is overwriten by a sys_template record if clear flag

It is very hard to debug – in tests and in real scenarios – if site set provided TypoScript is overwritten by a sys_template record that has the clear flag set.

A warning (and ideally a message in the backend) should appear that informs the integrator about this configuration, that is probably a mistake.

Author Benjamin Franzke
Assigned to Benjamin Franzke
Created 06/13/25, 07:31
Updated 06/13/25, 07:31

Showing results 1051 to 1075 of 1561