Showing results 1176 to 1200 of 1561

Feature
New Orphaned Database API (Doctrine DBAL)

#105439 MM_match_fields not respected when auto-generating MM tables on relations without MM_opposite_field

I am not sure whether this is actually a bug, a missing feature or a documentation inconsistency (https://docs.typo3.org/m/typo3/reference-tca/13.4/en-us/ColumnsConfig/CommonProperties/Mm.html does not mention this at all, neither as a feature or a limitation).

Since v11 MM tables are autogenerated. The fields in MM_match_fields are not autogenerated, but have to be declared manually in ext_tables.sql. I expected them to be auto-generated, but they are not.

If this is intended behaviour the docs should have a note about this limitation.

EDIT: I noticed that it works when having MM_opposite_field alongside. But MM_match_fields do not neccessarily require an opposite field (it is totally valid architecture to have two, or more, local fields poitning to the same foreing table, using the same MM table without bidirectional usage).

Author S P
Created 10/24/24, 13:08
Updated 12/11/24, 12:06
Feature
Needs Feedback Orphaned RTE (rtehtmlarea + ckeditor)

#103625 Deterioration for editors - Removed pre-defined link title attributes in RTE link browser

A lot of configuration options are missing in ckeditor/link-browser for links. Since the title attribute has been removed (https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Breaking-98275-RemovedPreDefinedLinkTitleAttributesInRTELinkBrowser.html), ediors have to deal with cryptic identifiers/class-names instead of meaningful expressions.

I think it would be useful to bring back the title option — at least for the backend.

Author wini2 no-lastname-given
Created 04/13/24, 19:12
Updated 12/06/24, 06:33
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
New Orphaned FormEngine aka TCEforms

#96728 Make it possible to synchronize translation with original language for entire Flexform (allowLanguageSynchronization)

Make allowLanguageSynchronization possible for entire Flexform

Use case

Plugins are translated. Often the settings are the same for both languages. Once the settings are changed in the default language, this change must be made in the translations too, which may get forgotten.

(I am currently testing this in v10, don’t have an extension which works in v12)

Possible scenario:

with synchronized language

Author Sybille Peters
Created 02/02/22, 10:26
Updated 12/01/24, 13:23
Task
Author Christoph Lehmann
Created 11/23/24, 00:13
Updated 11/25/24, 12:35
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#103458 UX inconsistency - the "lens" button on several search bars is disabled until something is entered on the field

The following modules have a “search bar” with a “lens” icon (which is a button)

  • DB Check module > full search
  • Recycler module
  • Configuration module
  • Workspaces module

The icon is disabled until something is entered on the input field.

Instead on the list and filelist module, the icon is clickable from the beginning.

[I have not checked other places]

Is there a reason for a different behavior? Should the behavior become more consistent?

Author Riccardo De Contardi
Created 03/21/24, 15:09
Updated 11/22/24, 15:33
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
Bug
New Orphaned File Abstraction Layer (FAL) TYPO3 CMS 12

#103707 Duplicate entries in sys_file table

We have encountered an issue where there are duplicate entries in the sys_file table pointing to the same physical file. This results in the Filelist module not displaying references to those files correctly. Consequently, these files can be deleted even though there are references pointing to another sys_file entry that shares the same file in the filesystem.

To check for duplicates, you can run:

SELECT COUNT(*), `identifier` FROM `sys_file` GROUP BY `identifier` HAVING COUNT(*) > 1;

Here is an example of a duplicate entry:

SELECT * FROM `sys_file` where identifier like "/user_upload/Bilder/Wirtschaftspruefer/Veranstaltung_2024/mbs_04.jpg";
+------+-----+------------+--------------+---------+---------+------+----------+----------------------------------------------------------------------+------------------------------------------+------------------------------------------+-----------+------------+------------+------------------------------------------+--------+---------------+-------------------+
| uid  | pid | tstamp     | last_indexed | missing | storage | type | metadata | identifier                                                           | identifier_hash                          | folder_hash                              | extension | mime_type  | name       | sha1                                     | size   | creation_date | modification_date |
+------+-----+------------+--------------+---------+---------+------+----------+----------------------------------------------------------------------+------------------------------------------+------------------------------------------+-----------+------------+------------+------------------------------------------+--------+---------------+-------------------+
| 2792 |   0 | 1711288107 |   1711288107 |       0 |       1 | 2    |        0 | /user_upload/Bilder/Wirtschaftspruefer/Veranstaltung_2024/mbs_04.jpg | ed3516d8ff67f42ae9a0b4ca9443989421b21324 | 928bfe2c54bf0575ae5ad65b55cb3deee6aaa658 | jpg       | image/jpeg | mbs_04.jpg | 61782595dddae96224e259cf7170dd646fb4e3d1 | 562574 |    1711288107 |        1711288107 |
| 2794 |   0 | 1712041049 |   1712041049 |       0 |       1 | 2    |        0 | /user_upload/Bilder/Wirtschaftspruefer/Veranstaltung_2024/mbs_04.jpg | ed3516d8ff67f42ae9a0b4ca9443989421b21324 | 928bfe2c54bf0575ae5ad65b55cb3deee6aaa658 | jpg       | image/jpeg | mbs_04.jpg | 61782595dddae96224e259cf7170dd646fb4e3d1 | 562574 |    1712041049 |        1711288107 |

In another instance, there are multiple sys_file records pointing to files outside the fileadmin directory. This might indicate that the problem is not related to the Filelist module and user uploads, but could also be rooted in page rendering.

| uid  | pid | tstamp     | last_indexed | missing | storage | type | metadata | identifier                                                          | identifier_hash                          | folder_hash                              | extension | mime_type     | name        | sha1                                     | size | creation_date | modification_date |
+------+-----+------------+--------------+---------+---------+------+----------+---------------------------------------------------------------------+------------------------------------------+------------------------------------------+-----------+---------------+-------------+------------------------------------------+------+---------------+-------------------+
| 2754 |   0 | 1680786128 |            0 |       0 |       0 | 2    |        0 | /typo3conf/ext/sitepackage/Resources/Public/Icons/Flags/flag_at.svg | aa8d82349adeaa66fa834c0bab77a507d74bbd3a | 15b08915cf0ec6b4ffef65022ba6219d4111ee18 | svg       | image/svg+xml | flag_at.svg | 87fcd7ee2c2fe0e53935bd952efdb97dde1b3c66 |  226 |    1680786117 |        1680786007 |
| 2755 |   0 | 1680786128 |            0 |       0 |       0 | 2    |        0 | /typo3conf/ext/sitepackage/Resources/Public/Icons/Flags/flag_at.svg | aa8d82349adeaa66fa834c0bab77a507d74bbd3a | 15b08915cf0ec6b4ffef65022ba6219d4111ee18 | svg       | image/svg+xml | flag_at.svg | 87fcd7ee2c2fe0e53935bd952efdb97dde1b3c66 |  226 |    1680786117 |        1680786007 |

This issue appears to be at least four years old, as i found the extension https://extensions.typo3.org/package/elementareteilchen/unduplicator, which was created to find and fix such duplicates. The extension dates back to 2020.

We found these problems in many other projects. However, we do not have a TYPO3 v12 or v13 instance that is not an upgrade from TYPO3 v11, so we are currently unsure if this issue affects TYPO3 v12 or v13 as well.

Author Ulrich Mathes
Created 04/23/24, 09:29
Updated 11/22/24, 07:53
Bug
Under Review Orphaned TYPO3 CMS 13

#105054 Flexform migrations executed during schema generation is expensive

Scenario:

  • EXT:bootstrap_package is installed
  • A page contains 140 “Accordion” content element, each contains an empty item (=280 records)

Symptoms

If said page is opened in the “Page” module, loading the module is slow and needs roughly 4 seconds on a MacBook Pro M3, while running TYPO3 in ddev. The situation gets worse when the “Debug” preset is enabled, the loading time expands to 20-30 seconds.

Technical explanation

BackendLayoutRenderer makes use of RecordFactory, which in turn resolves the records and their relations. While creating Record objects, RecordFieldTransformer may hit on flexform fields (pi_flexform). This will invoke FlexFormSchemaFactory->createSchemataForFlexField(). This code path is expensive, as it will run online FlexForm migrations for the full TCA per content element.

If logging to the deprecation log is enabled (which is given by enabling the “Debug” preset), things get worse as each repetitive migration may trigger the same deprecations over and over again, resulting in writing 16 GB of data into the deprecation log per request.

Author Andreas Kienast
Created 09/20/24, 06:06
Updated 11/18/24, 13:58
Bug
Needs Feedback Orphaned FormEngine aka TCEforms TYPO3 CMS 10

#96385 Treelevel wrong in PageTS conditions

For an TYPO3 upgrade I’ve had to migrate oldschool PageTS conditions to symfony expression syntax.

That’s when I’ve noticed that [tree.level = X] is behaving differently than [treeLevel = X] used to do. We’ve usually used this to show certain fields only on site root level, e.g. is_siteroot, backend_layout and backend_layout_next_level.

First off we hide certain fields globally:

TCEFORM.pages.is_siteroot.disabled = 1
TCEFORM.pages.backend_layout.disabled = 1
TCEFORM.pages.backend_layout_next_level.disabled = 1

But show them on root pages (old syntax):

[treeLevel = 0]
TCEFORM.pages.is_siteroot.disabled = 0
TCEFORM.pages.backend_layout.disabled = 0
TCEFORM.pages.backend_layout_next_level.disabled = 0
[global]

Which translates to the new syntax:

[tree.level == 1]
TCEFORM.pages.is_siteroot.disabled = 0
TCEFORM.pages.backend_layout.disabled = 0
TCEFORM.pages.backend_layout_next_level.disabled = 0
[global]

As you can see, there’s a difference in what’s considered to be treelevel 0. In my opinion that’s a bug.

Another thing is that for nested sites the treelevel is not reset even though there’s a sys_template record with root=1 set that is processed correctly in FE TypoScript.

So to make the snippet work for PageTS we gotta use this for a root site that’s located on absolute treelevel 3:

[tree.level == 4]
TCEFORM.pages.is_siteroot.disabled = 0
TCEFORM.pages.backend_layout.disabled = 0
TCEFORM.pages.backend_layout_next_level.disabled = 0
[global]
Author Philipp Kitzberger
Created 12/18/21, 09:35
Updated 11/14/24, 09:03
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

#91900 Editor with language restriction to non-default language can't edit records of tables with inline fields configured with l10n_mode => exclude

In one of our projects we have a table for locations. This table has a file relation field for images, which is configured with ‘l10n_mode’ => ‘exclude’.

The default language is German. There is a folder in the page tree, which contains only russian locations (they aren’t translations of a german record, but created directly in russian).

When an editor, who is restricted to only the russian language, tries to edit those records, he gets an error: “Sorry, you didn’t have proper permissions to perform this change. ERROR: Language was not allowed.”.

This likely happens, because the file relation in sys_file_reference is created with sys_language_uid = 0 when l10n_mode is set to exclude, resulting in an error, because the editor can’t access the default language.

I tested this in the most recent versions of TYPO3 8, 9 and 10. They all behave identically.

Author Tobias D
Created 07/30/20, 13:06
Updated 10/31/24, 08:29
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
Feature
New Orphaned Database API (Doctrine DBAL)

#105456 Auto-generate foreign keys on pure SQL relation fields when doing TCA auto-generation

It would be nice if the core would auto-create foreign keys when generating single-table MM tables or single-table inline relations. Probably optionally/configurable, with ‘dbCreateForeignKey’, ‘dbOnDeleteCascade’, and so on in TCA MM config.

CREATE TABLE tx_package_lcoal_foreign_mm
(
    FOREIGN KEY fk_local (uid_local) REFERENCES local_table (uid) ON DELETE CASCADE,
    FOREIGN KEY fk_foreign (uid_foreign) REFERENCES foreign_table (uid) ON DELETE CASCADE
);
Author S P
Created 10/25/24, 07:01
Updated 10/25/24, 07:01
Bug
New Orphaned Workspaces TYPO3 CMS 12

#105389 Workspace typolink to translated page does not work

Scenario:
  • Multilanguage site
  • In a workspace and translated content element, page A links to page b (t3://page?uid=4352&L=5)
  • Page b is
    • enabled in the default language and Live workspace, as well in the staging workspace
    • the translated page is hidden in the Live workspace, but enabled in the staging workspace

In \TYPO3\CMS\Core\Domain\Repository\PageRepository::getPageOverlaysForLanguage the language overlays are done and later on workspace overlays. But this does not create the links in the translation.
I’d expect to ignore the hidden flag if we are in a workspace and check the visibility AFTER versionOL is called flag is set

Author Andreas Kießling
Created 10/22/24, 10:14
Updated 10/22/24, 10:14
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 felogin TYPO3 CMS 12

#100772 Disabling of referer redirect via redirectReferrer flag is not persisted on login failure

There is the redirectReferrer flag for the frontend login form to force deactivation of a configured referer redirect:

This is set by https://example.org/login/?redirectReferrer=off
Or in custom solutions can also be conditionally set via Fluid.

Right now this parameter is only read from GET but not from POST.
In the Fluid login form the parameter is set only as POST.
So in the end it gets lost when the form is send.

In case the provided login credentials are not correct, the form reloads and redirectReferrer is not set anymore.

Author Ayke Halder
Created 04/27/23, 16:17
Updated 10/18/24, 13:43
Task
Under Review Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 12

#103818 Streamline `PageContentErrorHandler`

Since #103399 the PageContentErrorHandler uses Guzzle to make a
full external request for external error page content urls with
a specific header to guard calling the same TYPO3 instance with
a invalid error page.

A dedicated sub method has been added to handle the external
request handling, while keeping the internal sub-request in
the main `handlePageError()` method.

Author Stefan Bürk
Assigned to Stefan Bürk
Created 05/11/24, 17:24
Updated 10/18/24, 13:31
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 12

#102630 (Re-)add missing checkbox labels

Most of the toggle buttons widely used in the TYPO3 backend do not have a meaningful

Some of the missing labels existed before and must have been dropped while switching the controls from classic checkboxes to the toggle buttons.
To improve the accessibility of the backend, the toggle buttons should have a proper label aswell.

Author Willi Wehmeier
Created 12/08/23, 10:05
Updated 10/18/24, 13:30
Bug
Under Review Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 12

#103060 ViewHelper won't work with link modifications

TYPO3 delivers some ViewHelper for link generation.
Those accept arguments like class.

TYPO3 itself, and extensions via Events, might add their own arguments, e.g. rel=“noreferrer”.

This will break as ViewHelper don’t provide their own downstream to the link generation. But ViewHelpers fetch the result from the generation and overwrite their own info.

Author Daniel Siepmann
Assigned to Daniel Siepmann
Created 02/06/24, 10:26
Updated 10/18/24, 13:30
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
Task
Under Review Orphaned Backend API TYPO3 CMS 13

#105278 Use new format of permission preset

With introduction of deployable backend group permission presets (see https://review.typo3.org/c/Packages/TYPO3.CMS/+/85577) we should same format for permission sets in CORE. For that reason we should align ext:install default group generator preset format with latest iteration.

Author Tomek W
Created 10/11/24, 14:01
Updated 10/15/24, 09:46

Showing results 1176 to 1200 of 1561