Showing results 1251 to 1275 of 1561

Bug
Accepted Orphaned Linkvalidator TYPO3 CMS 13

#104004 Incorrect handling of authMode in EditableRestriction in linkvalidator

With the class EditableRestriction restrictions for the current BE user are applied when fetching broken links records.

One of the restrictions is handling authMode. This is currently not correctly handled:

1. authMode is only applied for “type” fields. This is not correct.
2. authMode is not applied for “pages”. Pages might have to be handled differently because the SQL request is joined with pages, should be checked
3. If the $this->explicitAllowFields[$table][$type] is empty, no restrictions are applied, but this can also mean that no values are allowed.

Caveats: Only the “type” field is written to tx_linkvalidator_broken_links.element_type

Ideally add some more tests.

Details for 1.

This is currently evaluated only if the field containing this setting is a “type” field (as defined by $GLOBALS[‘TCA’][$table][‘ctrl’][‘type’]). I don’t think this is correct. While currently in the core, the authMode field is usually a type field (such as CType), this is not a prerequisite: you can also restrict access to any field (as long as it is type=“select”).

if ($table !== 'pages' && ($GLOBALS['TCA'][$table]['ctrl']['type'] ?? false)) {
                $type = $GLOBALS['TCA'][$table]['ctrl']['type'];
                $fieldConfig = $GLOBALS['TCA'][$table]['columns'][$type]['config'];
                // Check for items
                if ($fieldConfig['type'] === 'select'
                    && is_array($fieldConfig['items'] ?? false)
                    && isset($fieldConfig['authMode'])
                ) {
                    $this->explicitAllowFields[$table][$type] = $this->getExplicitAllowTypesForCurrentUser(
                        $table,
                        $type
                    );
                }
            }

Versions

  • applies to main, v12, v11
Author Sybille Peters
Assigned to Sybille Peters
Created 06/08/24, 06:30
Updated 07/12/24, 17:48
Bug
Under Review Orphaned Performance TYPO3 CMS 8

#82100 Backend Form Dataprovider load every foreign Entity, not only the related one

Hi,

I notice a massive performance drop if I add in TCA a label_userFunc.
I found the reason in the TYPO3\CMS\Backend\Form\FormDataProvider\AbstractItemProvider::processForeignTableClause

For my Setup

I have 2 Entities Post and Comment, these are Bidirectional Related with ManyToOne.
Post has a inline TCA which load all related Comments.
Comment has a label_userFunc in TCA which simply format a Datetime into the title.

After I Try to Debug the label_userFunc, i notice the method are called WAY TO OFTEN.
Then I look at the Queries. I saw that simply the sql Relation are missing in the Query.

That means every time I want to edit a Post, Typo3 load EVERY Comment from a certain PageId.
Example:
- Post_A has 3 Comments.
- All Posts together conatins over 9000 Comments.

If i want to edit Post_A, I expect that Typo3 Load only 3 Comments, but Actual load Every comment on the System and used on every Comment the label_userFunc.
In the End, i see only 3 comments (which is correct).

I worte myself a little workarund which redurce the system and Database load dramatically:
https://gist.github.com/anonymous/7e307e73e6842fd6d94f28ba62ab2a7d#file-abstractitemprovider-php-L135-L146

Post TCA:

    'comments' => [
            'exclude' => false,
            'l10n_mode' => 'exclude',
            'behaviour' => [
                'allowLanguageSynchronization' => true
            ],
            'label' => $ll . 'backend.tca.post.comments',
            'config' => [
                'type' => 'inline',
                'foreign_table' => 'tx_exampleBlog_domain_model_comments',
                'foreign_field' => 'post',
                'maxitems' => 9999,
                'appearance' => [
                    'collapseAll' => true,
                    'levelLinksPosition' => 'top',
                    'showSynchronizationLink' => false,
                    'showAllLocalizationLink' => false,
                    'showPossibleLocalizationRecords' => true,
                    'showRemovedLocalizationRecords' => true,
                    'enabledControls' => [
                        'info' => true,
                        'dragdrop' => true,
                        'localize' => true,
                    ],
                ],
            ],
        ],

Comment TCA:

    'post' => [
            'exclude' => true,
            'label' => $ll . 'backend.tca.post',
            'config' => [
                'type' => 'select',
                'renderType' => 'selectSingle',
                'foreign_table' => 'tx_exampleBlog_domain_model_post',
                'minitems' => 0,
                'maxitems' => 1,
            ],
        ],
Author Benjamin Rannow
Created 08/14/17, 16:13
Updated 07/12/24, 17:43
Bug
Under Review Orphaned Backend API TYPO3 CMS 12

#84247 TCA label_userfunc called for every record in current page/folder

We searched all the changelogs but the wasn’t an info regarding the internal handling of label_userfunc.

We are using a label_userfunc for a normal TCA table. Creating a new record within a folder which already contains thousands of records of this type will take 30+ seconds until the TCE Form will be rendered. Debugging it, we saw that the userfunc is called for every record within the current page.

We upgrading from 6.2 to 7 LTS / 8 LTS. In Typo3 6.2 the function seems to be called only one time, so there is no delay while opening the TCE Form.

return array(
    'ctrl' => array(
        'title'    => 'LLL:EXT:ffh_topics/Resources/Private/Language/locallang_db.xml:tx_ffhtopics_domain_model_content',
        'label' => 'text_headline',
        'label_userFunc' => 'RTFFH\\FfhTopics\\Userfuncs\\Tca->contentTitle',
        ...
    )
);

The userfunc is very simple. It only fetches the record and does some string operations

public function contentTitle(&$parameters, $parentObject) {
    $record = \TYPO3\CMS\Backend\Utility\BackendUtility::getRecord($parameters['table'], $parameters['row']['uid']);
    ...
}
Author Webadmin no-lastname-given
Created 03/13/18, 16:37
Updated 07/12/24, 17:43
Bug
Under Review Orphaned FormEngine aka TCEforms TYPO3 CMS 9

#82730 Opening record in backend painfully slow with foreign table and large main table

Opening a record in the backend can become painfully slow under the following circumstances:

The main table (10.000 records) has got a 1:n relation to a foreign table (3 records). When trying to open the record of the main table in the TYPO3 backend, the following SQL statement is executed that often that it takes an exceptionally long amount of time to actually open the record.

SELECT * FROM `tx_myext_domain_model_foreigntable` WHERE (`uid` = ?) AND (`tx_myext_domain_model_foreigntable`.`deleted` = 0)

TCA of main table:

'attribute' => [
    'exclude' => true,
    'label' => 'attribute',
    'config' => [
        'type' => 'select',
        'renderType' => 'selectSingle',
        'foreign_table' => 'tx_myext_domain_model_foreigntable',
    ],
],
Author Stefan Franke
Created 10/11/17, 11:30
Updated 07/12/24, 17:43
Bug
Under Review Orphaned FormEngine aka TCEforms TYPO3 CMS 10

#101121 Poor performance with INLINE + children having "label_alt" being set to a relation (n:1) column

I’ve noticed massive performance issues with INLINE relations when childrens have “label_alt” set to fields which are relations (n:1) themselves. Current scenario is:

  • There are 400 “seminars”, 4.000 “events”, 20 “locations”.
  • Database layout is “seminars” 1:n> “event” <n:1> “location.</n:1>
  • TCA form for “seminar” contains “events” defined as INLINE, and “event” contains “location” as SELECT SINGLE.
  • Table “event” has “label_alt => date, location, seminar” set (last two are n:1 relations).

Now opening the backend edit form for a “seminar” (which contains ~ 100 inline “events”) leads to a never ending request on live system (“gateway timeout” on DDEV local). On database level, nothing could be improved by setting additional indices for all relationál columns. As soon as “label_alt” is removed, there are no performance issues. In addition, this only happens when used within an INLINE relation. In plain list view for “event”, this “label_alt” setting containing relations doesn’t cause any problems.

I stumbled across this issue several times in the past. As far as is remember it always happens when “label_alt” refers to relations in combination with INLINE usage. I suppose the database queries in behind are not really good and perhaps they simply deal wrong with relations or don’t use plain left joins (“event” <n:1> “location”).</n:1>

The only way i could work around this was, to use a custom label user function for the “event” label, which does “BackendUtility::getRecord()” for “location” and “seminar” in behind. So the 100 inline records themselves are not the problem and in general, we are not talking about a huge amount of records at all.

Author Jan Kornblum
Created 06/19/23, 13:20
Updated 07/12/24, 17:43
Feature
New Orphaned Backend User Interface

#95447 Edit file properties directly from where it is referenced

Allow the BE editor to edit file properties (filename; metadata; delete the file) directly from where it is referenced instead of “force” the editor to switch to the Filelist module and search for the file.

Author Christian Toffolo
Created 10/02/21, 12:14
Updated 07/12/24, 06:25
Feature
New Orphaned Categorization API

#53091 sys_category: Additional relation direction to get a categories assigned child-categories

Each category object has a relation to its parent category. It would be very nice to have such a relation in the opposite direction, too: $category->getChildren()

Author Jan Kornblum
Created 10/24/13, 14:49
Updated 07/11/24, 09:11
Bug
New Orphaned Extbase + l10n TYPO3 CMS 12

#104130 Undesired translations of extbase relations are not sorted out like before

Following setup: There is a domain object that can not be translated (object A). This object has relations to some other object (B) that can be translated. All B objects have a field where the UID of object A is stored and all get the UID of object A even the translations. In the FE all related B objects are loaded no matter what language they are. Before TYPO3 12.4 all relations got sorted out that do not match the current FE language.

So my question is, is this intended behaviour, a bug or a problematic/faulty setup on my end? I could make object A translatable and than simply not use the UID of the default language object A for all relations but the UID of the translated object A. But than again object A needs no translations at least in TYPO3 10.4

Author Hannes Bochmann
Created 06/17/24, 14:33
Updated 07/08/24, 17:55
Bug
New Orphaned Extbase + l10n TYPO3 CMS 11

#102578 Translated content elements can not be found when the original element is disabled

Hi,

if you create a translated element in connected mode and disable the element in the default language, the translated element won’t show up anymore too, even though it still is enabled.

It seems like the record overlay can’t be fetched because of the disabled original, so it completely gets ignored.

This issue is has a longer history like an old issue I created for v6.2: https://forge.typo3.org/issues/69022

I really thinks this needs a solution as this is confusing for redakteurs.

Greetings
Daniel

Author Daniel Dorndorf
Created 12/01/23, 10:22
Updated 07/08/24, 17:55
Bug
New Orphaned Extbase + l10n TYPO3 CMS 9

#91487 Extbase repository query using equals on a relation field is different whether one passes $entity or $entity->getUid() in multi-language context

The following two queries behave differently if in L>0 context:

$query->matching(
  $query->equals('relation', $entity)
)->execute()
$query->matching(
  $query->equals('relation', $entity->getUid())
)->execute()

When dumping $entity it is always displayed with the L=0 uid (also in L>0 context) and the overlayed fields from L>0, which is correct.

In L=0 context both queries behave the same. The second one works correct also in L>0, the first one only in L=0 context.

In L>0 context the first query extracts and uses the _localizedUid from the object. This is the bug afaik.

Discovered in 9, probably present in 10 as well.

Author S P
Created 05/26/20, 10:46
Updated 07/08/24, 17:55
Bug
New Orphaned Extbase + l10n TYPO3 CMS 9

#88853 Updating relations of translated domain objects does not work if they already exist

Hey,

for my product import i must to sync relations of translated domain object models to every translated record. TYPO3 does this already right if i click on the “Save”-Button in the backend, because in my TCA configuration its set to “l10n_exclude”. But manually saving does not work for > 2500 products on a regular basis.

It works for the first time to insert m:n-relations, but for every next try it tries to insert the value, which of course already exists instead of checking for an already existing relation. Is it possible to quickly fix this or just ignore the sql error and continue with my import? Ignoring would be fine, if i only add relations instead of updating them. Exception: TYPO3\CMS\Extbase\Persistence\Generic\Storage\Exception\SqlErrorException ]
Duplicate entry ’2636-13674’ for key ‘PRIMARY’.

My current solution is to just delete all relations via sql before my import starts:
DELETE FROM tx_gwproductcatalog_product_category_mm WHERE uid_local IN (SELECT uid FROM tx_gwproductcatalog_domain_model_product WHERE sys_language_uid != 0);

I attached the error log calling this from a backend module.

Author Anton Fries
Created 07/29/19, 14:43
Updated 07/08/24, 17:55
Bug
New Orphaned File Abstraction Layer (FAL) TYPO3 CMS 12

#104331 \TYPO3\CMS\Core\Resource\FileRepository::findByRelation incapable of handling FAL relations in FlexForm in BE context

The method internally assumes that any fieldname passed to the function is a root-level TCA field. It completely ignores that FAL relations are also possible within a FlexForm context. Specifically, BackendUtility::getTcaFieldConfiguration($tableName, $fieldName) fails if $fieldName is not a root-level TCA field, causing the findByRelation to always return an empty set. Note that BackendUtility::getTcaFieldConfiguration is incapable of returning a TCEforms config array from within a FlexForm DS regardless of how you construct the $field argument.

The same problem does not exist in FE context because the method internally switches to a standard query. But in FE context another problem exists – it completely ignores any and all additional DB relation constraints like `MM_match_fields`, and ignores the workspace ID. As such it is broken for anything other than a completely vanilla FAL IRRE setup.

Unfortunately this means that the FileRepository is not trustworthy in either context. Either it is partially broken, or it is incomplete – neither context is fully functional.

One solution could be to make \TYPO3\CMS\Core\Resource\FileRepository::findByRelation require a TCA config array as argument, avoid the use of BackendUtility::getTcaFieldConfiguration and then make it use RelationHandler exclusively and drop the condition block that switches to a query in FE context. Not only would that fix the described problems, it would also reduce the complexity of FileRepository itself.

PS: This problem exists in all versions of TYPO3 since the introduction of FileRepository but the TYPO3 version of this issue has been set to 12 since that’s the only LTS that needs to be fixed. If ELTS also needs to be fixed this version goes back a lot further.

Author Claus Due
Created 07/08/24, 12:56
Updated 07/08/24, 12:56
Feature
New Orphaned Security

#104328 Add support for cookie partitioning

https://github.com/privacycg/CHIPS?tab=readme-ov-file

Browser start rolling out support for this kind of cookie attribute.

e.g. https://www.mozilla.org/en-US/firefox/129.0a1/releasenotes/

Author Markus Klein
Created 07/07/24, 10:59
Updated 07/08/24, 10:14
Bug
New Orphaned Localization TYPO3 CMS 9

#90790 List view - button to localize content already localized with free mode (leads to error)

This issue is present on TYPO3 8.7, 9.5 and 10.4.0-dev (latest master) and even on 7.6

Prerequisites

Multilanguage TYPO3 with at least 2 languages (e.g. Ita(default), Eng (ID=1)

Steps to reproduce

1) Create a page in 2 languages
2) Create a content element in default language and translate it using free mode

3) Switch to List view

h3, Resutls:

1) the “Localize To” button is still there (!), albeit the localization is already present

Additonal information

Clicking on it leads to an error page with the message:

 "1: Localization failed: there already are localizations (XXX) for language 1 of the "tt_content" record YYY!

Notes:
a) on TYPO3 8 and 9 the page reloads with the error message on top, but no content is created
b) on TYPO3 10.4.0-dev (latest master) an empty page with infinite spinning appears and no content is created
c) on TYPO3 7 the issue is the same but in this case a duplicate element is created

Author Riccardo De Contardi
Created 03/19/20, 21:50
Updated 07/07/24, 18:29
Feature
Accepted Orphaned Backend User Interface

#38512 Shortcut page default mode

The default shortcut mode for a shortcut page is “selected page”. In the process to create a page the edit page mask is not always displayed. Therefore editors must edit the newly created page right after the creation or an error is displayed in the frontend:

#1301648404: This page (ID 30) is of type "Shortcut" and configured to redirect to a page, which is not accessible (ID 0). (More information)

The default shortcut mode must not be a mode that leads into and error. Rather the default behavior should be to create a valid new page.

Solution might be to make shortcut mode “First subpage of current page”.

But also the first subpage might not be existing after the creation of a new page resulting in a different error:

#1301648328: This page (ID 30) is of type "Shortcut" and configured to redirect to a subpage. However, this page has no accessible subpages. (More information)

What could be a good solution? The only function not resulting in a fatal error would be to make “Parent page” the default.

Any other solutions/idead?

Author Felix Kopp
Created 07/01/12, 12:17
Updated 07/07/24, 16:42
Task
New Orphaned Backend User Interface TYPO3 CMS 13

#102497 Unify display and grouping of context menus

  • Buttons “Copy”, “Cut”, “Paste after” and “Paste into” should be grouped also in file list module
  • Button “Paste after” is not shown in file list module (when copying or cuting a file) – neither in same folder as the file which should be copied, nor in other folders
  • Button “Display information” respectively “Info” should always have the same name and almost the same position
  • Buttons of a file (file list module) should have the same size as in list module
  • Button for more menu options in file list should be a moved to its own button group
  • Delete button is missing in some context menus while being present in button groups / list views
Author Jasmina Ließmann
Assigned to Jasmina Ließmann
Created 11/23/23, 22:07
Updated 07/01/24, 10:28
Bug
New Orphaned DataHandler aka TCEmain TYPO3 CMS 11

#99894 Sorting translated domain entities breaks when sorting translated entity below not translated entity in list view

Let us assume the following case of three domain entity records:

A (available in language UID 0 and 1)
B (available in language UID 0 and 1)
C (available only in language UID 0)

Now let us sort B below C in the list view with the arrows. (so sorting the translated element below the non translated element)

We would expect to have the following sorting.

Language UID 0:

A, C, B

Language UID 1:

A, B

What happens is that the sorting for language UID 0 is OK but the sorting for language UID 1 is now:

B, A

I have also attached screenshots of the database result after sorting. One for language UID 0 (OK) and language UID 1(bug).

Author Denis Mir
Created 02/09/23, 10:14
Updated 06/28/24, 13:18
Feature
New Orphaned Backend User Interface

#99420 Rename "Delete" labels to "Move to recycler" for related cases

Hello,

We want the editors stop hidding useless contents instead of deleting them, and cluttering their own working area.

This improvement is splitted in smaller, and if possible, independant patches.

link to the full video (publically accessible): https://drive.google.com/file/d/1cxHaU7JHPiDE1_4hFsfDiM1m2YxfHoLz/view?usp=share_link

This tasks relates to the time 0.40min of the video

The “related cases” have to be defined because some records are really deleted and others are just in the recycler.

Rachel

Author Rachel Foucard
Created 12/23/22, 16:15
Updated 06/26/24, 16:02
Bug
Accepted Orphaned RTE (rtehtmlarea + ckeditor) TYPO3 CMS 12

#102595 Not possible to override richtextConfiguration via TSconfig if in a flexform

Normally, overriding settings in Flexform via TSconfig is possibe, for example like this:

# TCEFORM.[tableName].[fieldName].[dataStructureKey].[flexSheet].[flexFieldName with escaped dots].[propertyName]
TCEFORM.tt_content.pi_flexform.sfregister_create.sDEF.settings\.fields\.selected.addItems.ZZZ = ZZZ

see https://docs.typo3.org/m/typo3/reference-tsconfig/main/en-us/PageTsconfig/TceForm.html

But this does not seem to work with the richtextConfiguration if in a Flexform which would then be overridden with RTE, for example like this:

RTE.config.tx_news_domain_model_news.bodytext.preset = otherpreset

For a Flexform field, it should look for example like this:

RTE.config.tt_content.pi_flexform.powermail_pi1.thx.settings\.flexform\.thx\.body.preset = otherpreset

but this does not work.

Author Sybille Peters
Created 12/04/23, 05:11
Updated 06/26/24, 03:47
Bug
New Orphaned Extbase TYPO3 CMS 12

#103434 Extbase should check for property, not getter first

I have this custom code in my Extbase model:

class News extends AbstractEntity
{
    protected string $authors = '';
    protected string $subsidiaries = '';
...
    public function getSubsidiaries(): array
    {
        return GeneralUtility::trimExplode(',', $this->subsidiaries);
    }

In TCA, this is a field of type select / selectMultipleSideBySide.

Extbase / Symfony PropertyInfo is detecting the field as array, even though the property is a string, due to the getter method, and cannot handle an array yet:
https://github.com/TYPO3/typo3/blob/0e1b095b51edd20e10f05edbec630e0a57074c08/typo3/sysext/extbase/Classes/Persistence/Generic/Mapper/DataMapper.php#L251C17-L251C23

For this reason, the property will never get mapped.

If I create a getter “getAvailableSubsidiaries(): array” and remove the original mapper, the type will be detected as string and then populated in DataMapper.

I think the property should take precedence over the getter.

Author Benni Mack
Created 03/20/24, 11:19
Updated 06/24/24, 14:10
Feature
Under Review Orphaned Database API (Doctrine DBAL)

#101005 Add DefaultLanguageRestriction

Hello,

if you’re working with TYPO3 QueryBuilder, there are a lot of restrictions added to current query like DeletedRestriction, HiddenRestriction, StarttimeRestriction and some more. Would be cool to have a restriction which automatically adds a WHERE clause for default language to a query. Nearly everywhere in the TYPO3 core and also in extensions you need the records in default language to parse the resulting data through all these versionOL and translation methods of TYPO3 API.

Stefan

Author Stefan Froemken
Assigned to Stefan Froemken
Created 06/12/23, 19:17
Updated 06/23/24, 14:24
Bug
New Orphaned Link Handling & Redirect Handling TYPO3 CMS 11

#104179 inconsistent url encoding in redirects

I think there is a bug with inconsistent url encoding inside the redirect extension.

I want to match an url with parameters like url?foo[bar]=42
So i use #^/url\?foo%5Bbar%5D=([0-9]+)# as regex and as new target /path2/$1

The thing is, this will not work and outputs the target path without replacements.

After some debugging i found out that the url is first matched with the urldecoded version “url?foo%5Bbar%5D=42”.
But for the later preg_match which generates the capture groups to build the target uri, it is matched against “url?foo[bar]=42”.

As a workaround i now use as regex #^/url\?foo(?:%5B|\[)bar(?:%5D|\]=([0-9]+)# which matches in both cases.

I found a related task #94934 which introduced this change.

Author Mordamir
Created 06/21/24, 15:37
Updated 06/21/24, 15:37
Feature
Accepted Orphaned Content Rendering

#96366 Stop on additional bad doktypes for ContentObject slide

Behaviour of ‘slide = -1’ has changed in v9 when doktype filtering
has changed in the frontend to allow doktypes greater then 200 in
the frontend. Since then, sliding do not stop on sysfolders anymore,
which was also a usecase for someone and this was entitled as bugfix.

For other usecases this bugfix is a regression, as it do not work as
before but instances rely on this.

To get all use-cases togheter, a new configuration options is suggested,
so additional doktypes on which sliding should stop can be configured,
so these who needs the stopping can simply add this small option to
the corresponding typoscript, having the sliding over for the others
still in place.

It is suggested to add a new option ‘slide.stopOnDokTypes’ as a comma
sperarated doktype int list.

temp.traversefooter = COA
temp.traversefooter {
    stdWrap.ifEmpty.cObject = CONTENT
    stdWrap.ifEmpty.cObject {
        table = tt_content
        select {
            pidInList = this
            orderBy = sorting
            where = colPos = 1
        }

        # that's the magic for traversing
        slide = -1

        # stop on sysfolders like in v7 (this is the suggested option)
        slide.stopOnDokTypes = 254
    }
}
Author Stefan Bürk
Assigned to Stefan Bürk
Created 12/16/21, 10:13
Updated 06/21/24, 09:09
Epic
New Orphaned Backend User Interface

#98593 [UX] - Clear standards

This ticket is managed by the TYPO3 UX Team and is used to sort open UX tasks.
https://typo3.org/community/teams/user-experience-ux

The ticket contains tasks that can be summarized under the item “Clear standards” .
The focus is on tasks that contribute to help end users avoiding messing up instead of cleaning the mess.

  • give clear naming and labels
  • give clear roles for modules and action buttons
  • give components ready to use

Further Information¶
_To be added_

Author Riccardo De Contardi
Created 10/12/22, 17:25
Updated 06/20/24, 11:30
Feature
Accepted Orphaned Code Cleanup

#103072 Manage translation DB fields

Currently the TCA of TYPO3 knows these ctrl options to enable and manage translation behavior for tables:

- languageField (sys_language_uid by convention)
- transOrigPointerField (l10n_parent by convention, l18n_parent in tt_content)
- translationSource(l10n_source by convention)
- transOrigDiffSourceField (l10n_diffsource by convention, l18n_diffsource in tt_content)

Each of these have 2 purposes:

1. Enable translations or a related feature
2. Tell TYPO3 which DB field to use in queries

This by itself is a problem but the main question is whether the names of these DB fields need to be configurable at all.

There are recently a lot of consolidations and simplifications in TCA. The same could be applied here:

- Turn these options from string to bool, thus only enable/disable the feature. TYPO3 would then use fixed DB field names and thus fully manage these.
- Consolidate/merge these options with better and clearer names, e.g. 'enableTranslations' => true, 'trackTranslationDifferences' => true or similar.

Author Mathias Brodala
Created 02/07/24, 10:59
Updated 06/19/24, 21:01

Showing results 1251 to 1275 of 1561