Showing results 51 to 75 of 1561

Feature
New Orphaned Security

#87300 Limit amount of concurrent user sessions for same user

TYPO3 allows to use multiple sessions per user which is a feature on the one hand, but could also be a security risk on the other. In order to enhance the scenario it should be possible to limit the amount of concurrent user sessions per user (or disable concurrent logins at all).

Behavior either can be configured for the whole system or (optionally) per user.

Author Oliver Hader
Created 12/27/18, 13:53
Updated 04/03/25, 12:23
Feature
New Orphaned Categorization API

#66155 Backend display of localized records

If you translate a category the translated cat is not shown in the category list of another language.
If you translate aacat, in the database table you see a new category – but not a translated one.
So it is not possible to assign categories whith / or to translations.

IMHO a big problem.

I found similar issues like #61923 and #64417

Author Andrea Herzog-Kienast
Created 03/30/15, 18:09
Updated 04/01/25, 13:34
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#106150 Improve contrast in backend dark mode for Better Usability

The dark mode in the backend appears confusing.

While the exact cause is unclear, it seems to be due to insufficient contrast between various interface elements.

Increasing the contrast by approximately 10% could significantly improve readability and overall usability.

Author Christian Toffolo
Created 02/11/25, 09:01
Updated 04/01/25, 13:10
Task
Accepted Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 12

#99655 Backend: Set correct Site in site attribute of request when the current request has sufficient contextual information

With the introduction of the site-config we added more and more multisite-specific features, that are configured in the site-config.

This works perfectly for the frontend. But when you rely on the site-config in the backend, you will need to add a middleware, that sets an internal site attribute for various backend routes. Otherwise you will often just have a NullSite, which is useless.

An example would be: You implement an api and each site has its own credentials because the site should only have access to a subset of data. So you configure the credentials in the site-config. But if you need to add some backend-features, that needs those credentials, you will often need to determine the rootpage by grabbing some id from the current queryParams and then retrieving the site-config from the rootpage id.

In my opinnion the site-config should be available whenever possible.

for example – it is possible to determine the site and set it as attribute when:

- you edit the site config itself
- you edit any tca record located inside the page-tree
- on any view you have relation to a page uid

At the moment i need to add a middleware for each extension, that makes extensive use of the site configuration.

Unfortunately i did not test the behaviour in V11, so i need to tag the typo3 version to 10. Once i can confirm this still exists in V11/V12, i can update this issue.

Update

This is still valid for V11/V12.

Author Philipp Wrann
Assigned to Benni Mack
Created 01/20/23, 09:42
Updated 03/31/25, 15:42
Bug
New Orphaned Pagetree TYPO3 CMS 9

#91305 Wrong mount points cause empty page tree, exceptions (multiple errors in the code)

Before TYPO3 9.5 pages table only contained records for the default language. Since TYPO3 9.5 they also contain records in other languages. Unfortunately be_groups TCA definition was not updated to allow only records in the default language. This causes the following problem: if the user mistakenly adds a db mount for the page in non-default language, this page becomes inaccessible to the non-admin user and the whole page tree is not displayed with the exception.

Same problem is for be_users table with db mounts.

The exception itself is cryptic:

Core: Exception handler (WEB): Uncaught TYPO3 Exception:
 trim() expects parameter 1 to be string, null given | TypeError thrown in file
/home/prod/web/typo3/sysext/backend/Classes/Controller/Page/TreeController.php in line 267

This happens inside the function named pagesToFlatArray because it gets an empty array in $page parameter. The cause of this problem is inside getAllEntryPointPageTrees which has the following check:

            $entryPoint = $repository->getTree($entryPoint, function ($page) use ($backendUser) {
                // check each page if the user has permission to access it
                return $backendUser->doesUserHaveAccess($page, Permission::PAGE_SHOW);
            });
            if (!is_array($entryPoint)) {
                unset($entryPoints[$k]);
            }

The problem here that it will be always an array but it can be empty array. So the check should not be is_array($entry) but empty($entry). When changed to empty($entry) page tree is displayed. However the problem with be_groups TCA should still be fixed!

I see another possible problem in function named fetchDataAction, code:

        if (!empty($request->getQueryParams()['pid'])) {
            $entryPoints = [(int)$request->getQueryParams()['pid']];
        } else {
            $entryPoints = $this->getAllEntryPointPageTrees();
        }

If the condition is true, $entryPoints will not be in the correct format for pagesToFlatArray, which expects a full page record. This will also cause exceptions.

To reproduce the issue

  1. Have more than one language
  2. Have a non-admin user
  3. in the backend group for the user select a translation for the web mount instead of a default language page
  4. Login with that user and go to the Page module
Author Dmitry Dulepov
Created 05/05/20, 11:37
Updated 03/23/25, 22:32
Bug
Needs Feedback Orphaned Extbase + l10n TYPO3 CMS 11

#69022 Translated records can't be found when the original is hidden

If you deactivate a record and try to get the translated one you will get a: “#1297759968: Exception while property mapping at property path “”:Object with identity “123” not found.”

This happens because extbase always works with the uid’s of the original records and does the language overlay at last.
So if the original is hidden it can’t be found and so either you can’t get the translated overlay.

I guess best would be to expect translated items will be deactivated too if I deactivate the original one, otherwise you have to create a single record in the target language.

Checking everytime if a record is translated would be a mess for this edge case…

Author Daniel Dorndorf
Created 08/13/15, 15:55
Updated 03/23/25, 17:40
Feature
Under Review Orphaned Security

#106380 Switch backend maintainer re-auth (sudo-mode) from password to MFA if available

As a backend administrator with maintainer rights one currently logs in to the backend like any editor and on accessing maintainer modules one is asked to re-auth with the password (in PRODUCTION context, IIRC in DEV context this is skipped).

I think under the condition that the user has MFA enabled, instead of asking for the password, an MFA-auth should be done.
The basic principles used here are:
  • re-auth makes sense to escalate privileges, e.g. avoid scenarios with unlocked and unattended devices, session hijacking and device not locked but accessible by others, session hijacked or simply unintended mishaps
  • passwords are not safe as static secrets. Thus, additional MFA (e.g. TOTP, WebAuthn based hardware tokens) are added because they have better protection (e.g. access to a physical device or being only valid for a small time).
  • stealing a session is as easy, stealing a password is easy. stealing an addtional MFA-factor is hard.

In conclusion the re-auth to escalate to the maintainer modules should probably also use MFA (if available), instead of the password, as re-authing a session with a password seems weaker than re-authing it with an MFA.

This here does not consider 3rd party extensions supplying authentication providers in general, just the MFA providers to make it simpler.

Author J. Peter M. Schuler
Created 03/18/25, 10:27
Updated 03/19/25, 12:36
Bug
New Orphaned Backend API TYPO3 CMS 12

#106175 itemsProcFunc does nothing with type=selectTree

https://docs.typo3.org/m/typo3/reference-tca/12.4/en-us/ColumnsConfig/Type/Select/Tree/Index.html#confval-select-tree-itemsprocfunc

The documentation mentions the usage of itemsProcFunc in combination with the selectTree-type. This option however does nothing. If I change the type from selectTree to selectMultipleSideBySide, my class is being used and I can alter the items array.
Either the documentation is wrong here, or there is a bug with the selectTree.

I am trying to use this in a FlexForm context.

Author Kevin Ditscheid
Created 02/13/25, 20:50
Updated 02/18/25, 08:47
Bug
New Orphaned AdminPanel TYPO3 CMS 12

#106036 Admin panel does not trigger nonce to be consumed

When you activate the admin-panel on a frontend page as a logged-in backend user which does not have a consumed nonce, errors will show up regarding CSP. This is due to the fact the admin panel does add script and link tags with a nonce, which is never been triggered to be consumed, so the nonce does not appear in the frontend content security policy. Only the nonce string is fetched.

Also there are some link and script tags, generated by the admin panel, which do not use inline CSS or JS but refer to files using the src/href attribute, but nevertheless get a nonce attribute. When not using inline, the nonce is not needed.

requirements:
  • Frontend content security policies enabled
  • Page without any nonce (when not logged in)
  • Logged in backend user
  • The same page opened from the backend
  • Admin panel enabled
  • Admin panel activated in the page (switch in lower right corner turned from red to green)

Open the console and watch the CSP errors regarding script-src and style-src directives

Author Patrick Broens
Created 01/30/25, 15:38
Updated 01/31/25, 13:51
Bug
New Orphaned Content Rendering TYPO3 CMS 11

#96294 PageContentErrorHandler ignores configured additionalHeaders

When using a page e.g. as 404 error page the in TypoScript configured additionalHeaders are ignored and not set. Most likely these headers are lost when fetching the internal error page via HTTP and deliver the result to the client.

This behaviour was detected in TYPO3 10LTS, but is the very same in 11LTS.

TS:

page.config.additionalHeaders.10.header = X-Powered-By: nothing

works fine on every page, except the error pages.

Author Marc Willmann
Created 12/08/21, 17:08
Updated 01/29/25, 08:39
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 13

#106005 Not quite sure if it's a "feature" - displaycond has effect although the related field is not displayed when creating a new content element

I habe a TCA definition for a field:

‘field_1’ => [
‘exclude’ => 1,
‘onChange’ => ‘reload’,
‘label’ => ‘LLL:EXT:ext_name/Resources/Private/Language/locallang.xlf:field_1_label’,
‘config’ => [
‘type’ => ‘check’,
‘renderType’ => ‘checkboxToggle’,
‘items’ => [
[
0 => ‘’,
1 => ‘’,
]
],
‘default’ => ’1’
]
],

The default for this checkbox is “checked”. However, this Checkbox is by configuration not part of my form. The reason for this is That my extension has two plugins. One Plugin that has the checkbox, the other plugin does not. Both plugins share a common tt_content.php in TCA/Overrides. And both use this text element:

‘text_input’ => [
‘label’ => ‘LLL:EXT:artofffunc/Resources/Private/Language/locallang_be.xlf:text_input’,
‘displayCond’ => ‘field_1:REQ:false’,
‘config’ => [
‘type’ => ‘input’,
‘size’ => 200,
],
],

As one can see I have a display condition in it which tells to show the field ‘text_input’ when the field ‘field_1’ is unchecked. I use ‘text_input’ in both plugins – and both plugins are based on tt_content as the database table.

So for the plugin that has ‘field_1’ and ‘text_input’ in its form ‘text_input’ is not shown as ‘field_1’ is checked by default. This is as it should be.

However, when I create a new content element of the second plugin ‘text_input’ is also not shown although ‘field_1’ is not part of its form. I would have expected that the display condition only holds when the appropriate form field is in the palette – and otherwise the display condition should not have any effect. Also the value of “field_1” is stored in the database although it is not part of the form. That is not the behaviour I expect – and it only applies to new content elements. Once it’s saved and I change that value for “field_1” to 0 manually in tt_content afterwards everything works a expected from then on.

Is this a feature or a bug?

Author Michael Perlbach
Created 01/29/25, 00:21
Updated 01/29/25, 08:39
Feature
New Orphaned Link Handling & Redirect Handling

#105934 Allow redirect to internal page regexp capturing groups

In sys_redirects module I want wo insert a redirect using regex to an internal page containing a placeholder like this:

Source path: #^/mylink/([a-zA-Z]{1}[a-zA-Z0-9_/-]+)#
Target: t3://page?uid=1$1

But the placeholder in target ($1) does not work. It works if I insert an absolute link (no t3: link) like this: https://domain.tld/my/final/link/$1

Author Bernhard Eckl
Created 01/15/25, 09:29
Updated 01/15/25, 14:48
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 9

#83970 Localize / Synchronize buttons are missing for Text & media assets

Tested with current master (9.2.0-dev).

If some “assets” are inserted into “Text & media” and translated (translate, not copy) and the elements in the original language are changed (order changed, new ones inserted etc.), I would expect the buttons “Localize all records” / “Synchronize with original language” to be displayed for the translation.

This does work with CE “bootstrap carousel” from bootstrap_package using “Items”, but not with Text & Media “assets”.

Note : for “Carousel” (CType “carousel”) with bootstrap_package 15.0.0 (with TYPO3 13) no button appears if the order is changed, but a button appears if a new item is added in original language.

Reproduce

Use installation with several languages, e.g. coredev installation with “styleguide”

  1. Create a page
  2. Translate the page
  3. Add “Text & Media” CE
  4. Add 2 images in “assets” field in tab “media”
  5. translate content with “translate” button, use “translate” (connected) mode
  6. Now change order of images in CE of original language, save
  7. Edit translated CE (to see if there is a button to synchronize)
  8. Now add a new asset in the original
  9. Edit translated CE again

I would now expect a way to synchronize the “assets” with original language.

Do the same thing with bootstrap_package “Carousel” items and check if buttons appear in translated CE after change in original language.

Analysis

May be missing TCA options ‘showSynchronizationLink’ and ‘showAllLocalizationLink’?

Versions

  • originally reported for TYPO3 v9
Author Sybille Peters
Created 02/20/18, 00:23
Updated 12/19/24, 19:44
Task
New Orphaned TypoScript TYPO3 CMS 13

#102102 Refactor TS IncludeTree Import detail

The TS parser is essentially three parts: tokenizer, include / condition tree builder, ast builder.

While it seems we got tokenizer and ast builder pretty right in v12, the include tree is a bit clumsy.

One detail is that the object construct of @import / include_typoscript is a bit unfortunate:

When a snippet contains import, that snipped is marked isSplit=true. That's good, since "split=true" says that the entire snipped is represented by it's child nodes. Having two lines, one a simple assignment, another one the import, will then create two child nodes: one for the assignment “segment”, one for the import. However, the import is one object. The content of the imported file is set as lineStream, and the import code line itself is set as "originalLine". This leads to the situation that no child node is generated when an import does not resolve to a file, which then gives headaches with the syntax scanner looking for invalid imports, as well as the source renderer in the backend modules.

It would be better to split this: An import / include_typoscript should *always* create a child node that represents the import code line. If it does not resolve to something, it should create a “invalidImport” object or similar. The content of the included file(s) should then be child nodes of that node.

Doing this will simplify the overall code, will improve the BE module renderings, and we can get rid of the “original” properties in the include classes, will simplify the code that looks for ‘empty’ includes, and will streamline the source rendering in the backend modules.

Author Christian Kuhn
Created 10/06/23, 11:46
Updated 12/17/24, 11:21
Feature
New Orphaned Site Handling, Site Sets & Routing

#105726 Resolve placeholders in Yaml config with site set settings

Before, I could easily do:

routeEnhancers:
  NewsDetail:
    type: Extbase
    extension: News
    plugin: Pi1
    limitToPages:
      - '%settings.detailpids.news%'

as the settings were part of the config itself.

But now with site sets it’s no longer possible, as the settings are stored in a separate file and are also not imported into the config.

I could of course add the settings to the config again or (which I’m currently doing) just specify the page ids directly instead of using placeholders.

It would be great if thise feature is extended to include site sets settings as well.

Greetings

Author Lars Peter Søndergaard
Created 11/29/24, 08:59
Updated 12/13/24, 21:36
Task
New Orphaned FormEngine aka TCEforms TYPO3 CMS 12

#100221 Improve mass editing performance

Author Christian Eßl
Created 03/20/23, 13:59
Updated 12/04/24, 11:09
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#103059 Not possible to see references if no access to content where files are referenced in filelist

In the file list you can see the number of references for files which are referenced from content which you do not have access to, and you can also click on the link, but the references will not be displayed.

I would expect it to be possible to see the references (read-only) and also be able to see which pages the references are on (ideally by having a “view page” button).

Otherwise you cannot delete files and you can’t find out (as normal editor) where they are still being referenced from.

This means, these cases can only be resolved by admin users or by users with access to both the files and the content.

Example

user A
- access to pages /a/
- access to files fileadmin/a

user B
- access to pages /b/
- access to files fileadmin/b

Content in /a/ links to file /b/test.png. Now, user b cannot see references for test.png and cannot delete test.png.

Ideally, the user should be able to see the references (but of course not edit content they have no permissions for).

Screenshots

Author Sybille Peters
Created 02/06/24, 10:22
Updated 12/01/24, 13:55
Feature
Under Review Orphaned Localization

#103905 Make default language uid configurable

Once upon a time there was the all mighty sys_language_uid 0.

To support record sharing across multiple sites with different language configurations the “default” language uid should be configurable.

The SiteConfig already supports this behavior as it just returns the first language of the SiteConfiguration.

$site->getDefaultLanguage()->getLanguageId()

—-

*Example Usecase by @sorenmalling*
(Quote from Slack: https://typo3.slack.com/archives/C05D7UF1L8M/p1715761552677479)

University of Copenhagen is eager to share our case and situation and work together with any knowledge, testing etc. to help.
Link to original thread: https://typo3.slack.com/archives/C03AM9R17/p1715684411418909
Original content follows here:
Curious to know about the language handling ( languageId in site settings) and having a default language that is not languageId: 0 )
The site tree only displays pages with sys_language_uid = 0 .
So having multiple sites in a installation, some with danish - languageId: 0 as default and others with english - languageId: 1 requires me to use the “hide default language” (l18n_cfg).
With the concept of languages as entrypoints, and the method getDefaultLanguage on a Site object to take the first language in the array, is it something pointing towards, that the pagetree could handle sites, with a default language different than 0?

This would be one site with danish as default language, english as secondary

base: 'https://cms-distribution.ddev.site/'
languages:
  -
    title: Sundhed
    enabled: true
    locale: da_DK
    hreflang: da-DK
    base: /sund
    websiteTitle: ''
    navigationTitle: Dansk
    flag: dk
    solr_core_read: core_da
    languageId: 0
    piwik_app_id: ''
  -
    title: English
    enabled: true
    locale: en_US
    hreflang: da-DK
    base: /health
    websiteTitle: ''
    navigationTitle: English
    fallbackType: free
    fallbacks: ''
    flag: en-us-gb
    languageId: 1
rootPageId: 3
websiteTitle: 'Site name'

And another site with english as primary/only language is named english-only

base: 'https://cms-distribution.ddev.site/'
contentSecurityPolicies: {  }
languages:
  -
    title: English
    enabled: true
    locale: en_US
    hreflang: ''
    base: /english-only
    websiteTitle: ''
    navigationTitle: English
    fallbackType: free
    fallbacks: ''
    flag: en-us-gb
    languageId: 1
rootPageId: 73
websiteTitle: 'English only'

This last one can not render in the frontend, and the slug field does not show including the base – because there is no languageId: 0
One issue here is, that we have translated announcements living on pid = 0 – if we use languageId: 0 in the english-only site, it will get the announcements in danish, because danish announcements are with sys_language_id: 0

Author André Buchmann
Assigned to André Buchmann
Created 05/24/24, 21:01
Updated 11/22/24, 14:26
Feature
Under Review Orphaned

#97991 Allow unset variables in site configuration

USE CASE:

I had a site config with %env(ENV_NAME_AS_SUFFIX)% and we thought we could define the env only when needed. It turned out that TYPO3 doesn’t like undefined variables.

Having also worked with shell variable expansion (adopted in eg. docker compose files and Gitlab configuration files), I’d appreciated if I could use an undefined variable without breaking the site configuration.

SUGGESTION:

Use another syntax borrowed from Symfony: %env(fallback:<fallback_value>:ENV_NAME)% .

This allows for unset variables and has a fallback value as a bonus.

See https://symfony.com/doc/current/configuration/env_var_processors.html

PS:
Other formats that might be of use in a site configration are IMHO env(bool:FOO), env(not:FOO), env(int:FOO) and env(float:FOO) .

Author Martin Kutschker
Created 07/21/22, 13:25
Updated 11/12/24, 10:44
Bug
New Orphaned Localization TYPO3 CMS 11

#84119 Limiting a BE-User to default language results in inconsistent saves.

scenario

I have a backend user who is only allowed to edit the default language.
This user now tries to edit a text media content element.

expected behavior

The user is able to save the content element.

What actually happens

The user gets this error:
@recordEditAccessInternals() check failed. [ERROR: Language was not allowed.]@

I assume this is because of the new copying behaviors. If I check the \TYPO3\CMS\Core\Authentication\BackendUserAuthentication::recordEditAccessInternals method, I see that all languages are checked for which a translation of the content element exists.

Workaround

I extended the BackendUserAuthentication class and removed that specific call to checkLanguageAccess. The other languages are still not visible but they could be edited now.

Author Anonymous
Created 03/02/18, 15:34
Updated 10/31/24, 07:21
Task
Accepted Orphaned Backend User Interface TYPO3 CMS 13

#105457 Guide users to site sets as an alternative to TypoScript records in TypoScript record wizards

We received reports that integrators are confused that not typoscript includes are available (because they are not educated by TYPO3 that site sets are to be uses)

An integrator who creates a new site should be guided to use site sets instead of TypoScript records if possible.

An idea would be to add a info message/tile to the edit-typoscript-record overview that is displayed when a site has to sys_template record assigned yet:

Also the “Include TypoScript sets” select box could educate the use to look for site sets instead of TypoScript sets:
!include-typoscript-sets.png!

Author Benjamin Franzke
Created 10/25/24, 07:42
Updated 10/25/24, 07:42
Task
Under Review Orphaned TYPO3 CMS 12

#104785 Ensure resorting of package in legacy mode

Author Stefan Bürk
Assigned to Stefan Bürk
Created 08/30/24, 18:30
Updated 10/18/24, 13:59
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 12

#103586 UX: Backend Page Module - horizontal scrollbar

When the content of the page module is very wide (e.g. because of multiple languages and multiple columns), the horizontal scrollbar is only visible when the user scrolls to the bottom of the page:

This behavior was different in earlier versions (e.g. screenshot from TYPO3 11) where the horizontal scrollbar was immediately visible at the bottom of the window:

Seems this was introduced in https://review.typo3.org/c/Packages/TYPO3.CMS/+/79759

Author Albrecht Köhnlein
Created 04/10/24, 09:34
Updated 10/18/24, 13:25
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 9

#88672 SlugHelper->isUniqueInSite() slow for installations with many sites and similar URL structures

If a large installation has a lot of sites / root pages, each with similar or identical page structures of a few levels, calling fixUniqueInSite() and especially fixUniqueInSiteForSubpages() in the DataHandler becomes slow due to the way potentially duplicate URLs are retrieved in SlugHelper->isUniqueInSite().

A fix could include a different or two alternative approaches for duplicate URL retrieval, taking into account the size and the overall page structure of the installation.

Also, the runtime cache could be used inside isUniqueInSite(), as this method is called recursively from inside fixUniqueInSiteForSubpages() and some of the necessary data (e.g. site definitions, root page association of a single page) should not be changed from the outside inbetween these calls.

Author Thomas Fischer
Created 07/02/19, 14:13
Updated 10/15/24, 10:05
Feature
Under Review Orphaned Extbase

#102677 Introduce configuration file for Extbase plugin registration and configuration

It should also be possible to register an Extbase plugin with just one configuration file.

Author Torben Hansen
Assigned to Torben Hansen
Created 12/15/23, 18:33
Updated 10/15/24, 09:46

Showing results 51 to 75 of 1561