Showing results 1426 to 1450 of 1561

Feature
Accepted Orphaned Install Tool

#96652 Reduce amount of weak matches in Extension Scanner

Scenario

Just as an example, analyzing ext:bootstrap_package in the Extension Scanner results in a bunch of weak matches concerning calling method ->error – which happens since TYPO3\CMS\Core\TypoScript\Parser\TypoScriptParser->error is configured to be reported. Attached screenshot shows a bunch of false-positives (for $this instead of expected TypoScriptParser).

The scope of this issue is to reduce the amount of weak matches that do not consider the proper instance type when invoking methods.

Investigation in using PhpStan

It seems to be possible to resolve those symbols and their type with PhpStan (using a custom rule and basically their Scope object), however there are some aspects that make it difficult for the Extension Scanner:

  • all used/called classes need to be available or to be stubbed
  • this requirement raises memory consumption (had to raise limits to 96M for a single file to be analyzed)
  • invoking standalone scans another PHP class seems to be difficult (but somehow still possible)

Investigation in extending current custom PHP Parser

In order to keep track of types that are exposed in a particular variable (or class property, or array-dim, or return-type of another function/method call, …) an own call-graph and scope needs to be maintained. It is just relevant for this feature to fetch the class-type (if any), not the actual value to keep memory consumption low.

In particular the Extension Scanner would first have to scan all symbols, maintain the call-graph and scope and then start analyzing symbols and compare them with corresponding configuration files. That’s some work…

General question

Concerning potential implications of using another tool, the main question is, whether the Extension Scanner shall stay accessible via Install Tool in browser, or whether that component is supposed to be a development tool that is invoked via CLI only.

—-

Author Oliver Hader
Created 01/26/22, 11:09
Updated 01/27/22, 13:11
Feature
New Orphaned Site Handling, Site Sets & Routing

#84187 Add possibility to change links inside a recursive copy of a pagetree

For links to subpages of a tree it would be cool to define that those links will be treated relatively. Currently they still link to the original pid. But it would be nice to copy them “relative” to the newly copied pagetree.

Author Stefan Neufeind
Created 03/09/18, 17:22
Updated 01/26/22, 10:25
Feature
New Orphaned Linkvalidator

#96447 Linkvalidator concept & open decisions

Before proceeding, it would be good to have a concept, a plan and a roadmap. In order to achieve that a number of things need to be decided:

Priority

  • decide how to do the link checking, also decide about throttling external link checking and / or using link target cache and exclude list
  • address current problems: e.g. content which is not rendered is checked (e.g. bodytext in plugins)

Open decisions

software architecture / structural / refactoring

  • split up classes
  • separate general API which can be moved to core and functionality specific to linkvalidator
  • look at reference index (sys_refindex) which also contains references (e.g. page links), and there is a lot of overlap in functionality

configuration

  • make more configurable, e.g. make it possible for extensions to use lowlevel API but create their own module
  • rethink usage of TSconfig

Testing

  • more tests, acceptance tests missing, test coverage low

link checking

  • when / how to do the link checking (e.g. due full check via scheduler, do “on-the-fly” checking when content is changed, e.g. via hook, do immediate (synchronous) checking or asynchronous etc.)
  • external links: throttle checks to reduce excessive checking of external sites (which may lead to site being blocked), #89287
  • external link target cache to store result of checks
  • exclude / ignore list of external link targets (URL) to exclude “false positives” (URLs that are checked as broken but are not broken) from link checking, #85127, #92822
  • figure out reasons for “false positives” and try to reduce them, #85006
  • address problem of content which is not rendered in FE and / or not editable in Backend is checked nonetheless. This content should not be checked for broken links, and if not editable, clicking the pencil will result in error, e.g. * pages.url if doktype != 3 * content which will not be rendered due to l18n_cfg * content which will not be rendered because in hidden gridelement * content.bodytext where bodytext not used due to ctype / list_type (e.g. plugins) * translated (connected mode), original content hidden, #95195
  • some things not checked, e.g. shortcut pages
  • decide what are links, “soft references”, references etc. and what linkvalidator should cover (e.g. shortcut pages are redirects, not links, file references are not (necessarily) links. In TYPO3 this is sometimes not clearly defined what is what and terms used ambiguously. See #92542, #83835

scheduler

  • BUG (regression): no longer possible to enter several pids in scheduler, see #90848
  • FEATURE: if no start pid is given, use all start pids from sites configuration (see brofix)

GUI

  • move list to separate module?
  • add pagination (see brofix)
  • add sorting (see brofix)
  • add filtering (see brofix)
  • declutter list? – currently contains a lot of text, e.g. full page path (even if editor is working in a mountpoint)
  • add buttons to jump to the page or open page layout
  • open buttons to recheck a specific broken link?

email report

  • email report: what is relevant? E.g. in brofix a number of links in general is calculated and a percentage of broken links / total links is calculated.
  • create email reports for editors (which show only the pages / content they have access to, as in the BE module)
Author Sybille Peters
Created 01/01/22, 11:15
Updated 01/01/22, 11:15
Bug
New Orphaned Form Framework TYPO3 CMS 11

#96435 Apply rate limiter to mail forms

In order to limit sending forms again and again (which can be automated e.g. by using Selenium or similar techniques), sending out a particular form should be rate-limited (available since TYPO3 v11).

Author Oliver Hader
Created 12/27/21, 18:09
Updated 12/27/21, 18:09
Feature
New Orphaned DataHandler aka TCEmain

#92874 RFC: When activating a record from outside the TCA view check for missing required fields

Say you create a new page in the page tree and don’t go into the edit mode but immediately activate it via the context menu. You then have an invalid page activated. In the worst case it breaks the frontend at some point.

In my opinion it would be neat to have this process being secured by a check for missing mandatory fields. Should there be it fails with a proper response.

This would apply for any kind of record. I am not sure to which category it belongs, so I stick to Miscellaneous.

Depending on how this is implemented one could create a Widget which lists invalid record throughout the TYPO3 instance as well. For example when you import pages during a relaunch which had a different format.

Author Alex Nostadt
Created 11/19/20, 10:20
Updated 12/17/21, 14:33
Bug
New Orphaned TYPO3 CMS 10

#96290 ActionController->forward does not work when targetting another extension

I have a created some extensions for our instance of Typo3.

There is among other things a core extension that implements:
- a base controller: SelectedSiteController
- a template: Resources/Private/SelectedSite/DisplayNoSelectedPageWarning.html

The purpose of SelectedSiteController is to be inherited by other extensions which have a BE module needing a website (a page) to be selected in the page tree.

I’ve got two other extension which have a controller inheriting this base class SelectedSiteController

This class SelectedSiteController acts as a middleware before any action and get the currently selected website (page), or, if no page is currently selected, should display a basic template showing a ‘Please select a website’ message.

The SelectedSiteController class looks like this:

class SelectedSiteController extends ActionController
{
    protected function callActionMethod() {
       // looking for the current website
       // ...

       if(!$selectedWebsite) {
           $this->forward('displayNoSelectedPageWarning', 'SelectedSite', 'MyCoreExt');
       }

       parent::callActionMethod();
    }

    protected function displayNoSelectedPageWarningAction() {}
}

Then, I have this class in another extension :

class MyController extends SelectedSiteController {
    // various actions
}

If I don’t precise the extension in the ‘forward’ method, the child controller look for the template DisplayNoSelectedPageWarning.html in its own extension.

But if I define it explicitly, I’ve got this error:

(1/2) #1278450972 TYPO3\CMS\Extbase\Reflection\Exception\UnknownClassException

Class does not exist. Reflection failed.
in /var/www/typo3/public/typo3/sysext/extbase/Classes/Reflection/ReflectionService.php line 125
Author Olivier Massot
Created 12/08/21, 15:16
Updated 12/08/21, 15:16
Bug
New Orphaned File Abstraction Layer (FAL) TYPO3 CMS 10

#95330 'behaviour' => 'allowLanguageSynchronization' ignored on pages

We use “pages” with an own doktype as news pages, with an own model and repository (similar to the blog extension).

On translated pages, the TCA option ‘behaviour’ => ‘allowLanguageSynchronization’ is ignored, the sys_file_reference is always in default language 0, even if the translation behaviour is set to “custom value”.

The l10n_parent value of the translated values in sys_file_processedfile is always 0 – we tried to set the l10n_parent manually in database, then the translation of our FAL field works as expected (tried with custom fields and also with media field on plain TYPO3).

(this behaviour only happens on pages – tt_content is everything fine)

Author David Hoeckele
Created 09/23/21, 13:44
Updated 12/06/21, 14:11
Bug
Under Review Orphaned Backend JavaScript TYPO3 CMS 11

#93270 BroadcastMessage.fromData() is not idempotent

If BroadcastMessage is recreated using BroadcastMessage.fromData() it does not retain the original object structure. This is because BroadcastMessage.fromData() nests the entrire data (which includes a payload property itself) into another wrapping payload property.

Given following JavaScript code (executable in a Browser console in a window of the TYPO3 Backend):

window.require(['TYPO3/CMS/Backend/BroadcastMessage'], ({BroadcastMessage}) => {
  const bm1 = new BroadcastMessage('component', 'eventName', {foo: 'bar'})
  // Create bm2 from bm1, as if bm1 has been sent via broadcastchannel
  const bm2 = BroadcastMessage.fromData(bm1)
  console.log('bm1', bm1.payload)
  console.log('bm2', bm2.payload)
})

The expected result/output is that payload contains the same value for both BroadcastMessage instances:

bm1 {foo: "bar"}
bm2 {foo: "bar"}

While it actually is:

bm1 {foo: "bar"}
bm2 {payload: {foo: "bar"}}

BroadcastMessage.fromData() should be fixed to be idempotent, while keeping backwards compatibility (to existing event-subscribers) by doing the “additional” payload wrapping in BroadcastMessage.createCustomEvent. The “good” thing is, that BroadcastMessage isn’t used directly by subscribers, it is transformed into a CustomEvent, therefore this can be fixed without breaking BC.

Author Benjamin Franzke
Created 01/12/21, 06:35
Updated 11/29/21, 14:03
Feature
Author Oliver Hader
Created 08/31/21, 13:46
Updated 11/29/21, 14:02
Feature
Under Review Orphaned Content Rendering

#93450 ContentObjectRenderer: allow TypoScript select object without any constraint of uidInList or pidInList

Current state

A TypoScript select object must have at least one constraint of uid or pid – configured via properties uidInList and pidInList

Feature proposal

Allow to completely disable the pid_uid constraint on purpose in ContentObjectRenderer.

10 = CONTENT
10 {
   table =
   select {
      uidInList = 0
      pidInList = 0
   }
}

Motivation

Get records from a m:n-relation where you already know the uids of one side.
Tables respresenting m:n-relations do not have a field named uid – instead they have uid_local and uid_foreign.

As a current work-around you must pre-fill pidInList with all pids of the entire database to make this work:

pidInList.data = leveluid : 0
recursive = 99

Example code taken from tt_content.menu_categorized_content

tt_content.menu_categorized_content =< lib.contentElement
tt_content.menu_categorized_content {
    templateName = MenuCategorizedContent
    dataProcessing {
        10 = TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor
        10 {
            table = tt_content
            selectFields = tt_content.*
            groupBy = uid
            pidInList.data = leveluid : 0
            recursive = 99
            join.data = field:selected_categories
            join.wrap = sys_category_record_mm ON uid = sys_category_record_mm.uid_foreign AND sys_category_record_mm.uid_local IN(|)
            where.data = field:category_field
            where.wrap = tablenames='tt_content' and fieldname='|'
            orderBy = tt_content.sorting
            as = content
        }
    }
}

Code base

TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer – L6078-L6081

        // If not uid and not pid then uid is set to 0 - which results in nothing!!
        if (!$pid_uid_flag) {
            $constraints[] = $expressionBuilder->eq($table . '.uid', 0);
        }
Author Ayke Halder
Created 02/05/21, 18:30
Updated 11/29/21, 13:15
Bug
New Orphaned Caching TYPO3 CMS 10

#90840 Custom Caching Configuration silently keeps the options-Array

Hello folks,

when using the new caching configuration UI in v10 in the configuration presets area, one can crash a site.

This happens depending on the configuration you activate before setting a custom configuration. For the sake of simplicity let’s just have a look at the pages cache.

If you activate the Typo3DatabaseBackend, this is a part of what is written into the LocalConfiguration.php:

                'pages' => [
                    'backend' => 'TYPO3\\CMS\\Core\\Cache\\Backend\\Typo3DatabaseBackend',
                    'options' => [
                        'compression' => 1,
                    ],
                ],

If you activate the FileBackend, this will be written instead:

                'pages' => [
                    'backend' => 'TYPO3\\CMS\\Core\\Cache\\Backend\\FileBackend',
                    'options' => [
                        'compression' => '__UNSET',
                    ],
                ],

Note that the compression is unset here. If you now insert a custom configuration, e.g. APCuBackend, you end up with this:

                'pages' => [
                    'backend' => 'TYPO3\\CMS\\Core\\Cache\\Backend\\ApcuBackend',
                    'options' => [
                        'compression' => '__UNSET',
                    ],
                ],

This is fine, unless you had the Typo3DatabaseBackend active beforehand, which leads to this:

                'pages' => [
                    'backend' => 'TYPO3\\CMS\\Core\\Cache\\Backend\\ApcuBackend',
                    'options' => [
                        'compression' => 1,
                    ],
                ],

This will cause errors, because the ApcuBackend can not use compression.
So if your custom configuration breaks the site or not depends on the configuration you had before switching it, since the options-Array is only updated when you use the preconfigured cache-backends.

I marked this as a feature, since I think that people who use a custom configuration will most likely use the AdditonalConfiguration or directly edit the LocalConfiguration.php anyway (as stated in the hints in the configuration presets).
But if you only want to “try out” different caching backends using the UI, you might end up with a broken configuration (and errors on the site / the backend).

I think it would be useful to always unset the compression (and more options, depending on the capability of other cache backends). This way, the configuration also might not be perfect, but at least it would not cause errors.

cheers,

Hannes

Author Hannes Strangmeier
Created 03/26/20, 12:42
Updated 11/25/21, 20:55
Feature
New Orphaned Backend User Interface

#90825 link to an explicit language of a page - usability issue

This is a kind of follow-up of ticket #22113

It is currently possible (TYPO3 9.5.14 and 10.4.0-dev) to link to an explicit language version of a page with the following procedure:

Prerequisites

1) At least an additional language (e.g. with ID=1) and some translated pages
2) If you want to use the RTE, enable the “additional parameter selector” with the TSConfig

RTE.default.buttons.link.queryParametersSelector.enabled = 1

Procedure

1) Open the “link wizard” on the [header_link] field or using the RTE
2) On the “additional parameter selector” write “&L=1“
3) Select the appropriate target page

This works,but it has some usability flaws:

1) on the select link wizard you have to write &L=1 (for example) inside the “Additional link parameters” field so the editor must know what parameter is needed and its syntax
2) on the select link wizard, you must write &L=1 inside the “Additional link parameters” field before choosing the page, or the wizard popup will close and the procedure must be repeated.
3) If you click on some other page on the tree in the wizard window, the parameter field will become empty
4) the editor must know beforehand that the target page is translated

I set this issue as “feature”, feel free to change it if needed.

Author Riccardo De Contardi
Created 03/24/20, 21:44
Updated 11/25/21, 10:37
Bug
Under Review Orphaned TYPO3 CMS 8

#86147 Prevent updating unchanged fields in DataMapProcessor

Given:

- a table with some additional IRRE relations and fields with TCA configuration [‘behaviour’][‘allowLanguageSynchronization’] enabled
- open a record from the given table
- save it without any changes

Expected:

- saving an untouched record should not update any other record as nothing has changed

Actual:

- related records are updated even without any changes
- fetching related records recursively (parents, siblings, relations) takes very long and may result in a “maximum execution time” error

Author Nicole Hummel
Assigned to Nicole Hummel
Created 09/04/18, 16:45
Updated 11/18/21, 10:46
Bug
New Orphaned TYPO3 CMS 10

#96000 Match behaviour of folderTree.altElementBrowserMountPoints to pageTree

So I’ve run into the case that a user with access to a restricted pagetree wants to link to a page outside of his area.
I happily discovered that the option
@options.pageTree.altElementBrowserMountPoints@
lets me replace the defined dbmount with whatever I want.

If I don’t want to replace my defined dbmounts but instead want to append some, I can enable the following option
@options.pageTree.altElementBrowserMountPoints.append@

Both of this is great!

I then checked if the same exists for the foldertree (if someone wants to link to a file outside of his assigned file folder).

The option
@options.folderTree.altElementBrowserMountPoints@
exists! Great!
However, unlike the pageTree version, this one only appends filemounts, it doesn’t replace them.
The append option doesn’t exist (I tried to set options.folderTree.altElementBrowserMountPoints.append = 0)

What is the reasoning for this different behaviour?
I feel like the default behaviour for folderTree.altElementBrowserMountPoints should be “replace” and “folderTree.altElementBrowserMountPoints.append” should be added for those who want it.

Author Marco H
Created 11/16/21, 17:17
Updated 11/16/21, 17:17
Bug
New Orphaned Workspaces TYPO3 CMS 8

#82221 Copying records with "flex" fields containing FAL IRRE relations fails to move copies to new parent upon workspace publishing

Prerequisites:

  • Content element with flexform
  • At least one field of type “inline” wanting FAL references
  • A draft workspace

Reproduction, first symptom:

  • Switch to live workspace
  • Create an instance of the content type
  • Fill in at least one FAL relation, best two or more (count of relations is a symptom and having one single relation may confuse)
  • Switch to draft workspace
  • Copy the content element, does not matter where to
  • Observe first symptom: draft record’s “pi_flexform” column contains an incorrect FAL reference value (CSV list of UIDs, or single UID, instead of count). Placeholder record contains the correct FAL reference value (number of references). Copies of file relations in sys_file_reference have the correct uid_local value (pointing to the new, copied record).
  • Editing either the original or the copy of the parent record shows the expected relations (note 1)

Reproduction, second symptom:

  • Switch to the workspaces module
  • Perform publishing of all pending changes
  • Observe the second symptom: original record now has double the original file relations and the copy of the parent record has no file relations (uid_local of copies created in sys_file_reference now point to original instead of placeholder)
  • Both backend and frontend now display double relations for original record and no relations for copy of record (note 2).

Notes:

  • Note 1: The expected relations are resolved from the placeholder record which has the correct values, so the GUI shows these relations correctly but the DB data is corrupted.
  • Note 2: The incorrect values get set as part of the “publish workspace” step. The column is NOT in the list of shadow columns (but adding it makes no difference).

Solution:

The solution appears to be adding the UID of the newly created placeholder record as target UID in the substNEWwithIDs array in DataHandler. This one line of code causes both of the symptoms to disappear – the correct relationship UID is then read from the placeholder record and translated to the UID of the copy of the parent record. The code comment immediately outside the condition that checks if a placeholder was created even states that the UID gets recorded, but that currently is not the case. Adding the UID does exactly that.

Issue may exist as far back as TYPO3 7.6 but has been tested on 8.7 and master only. Both exhibit the same symptoms.

Author Claus Due
Created 08/28/17, 01:30
Updated 11/09/21, 22:05
Feature
New Orphaned Linkvalidator

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

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

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

#87982 Insert Records now only inserts records, if in the same language or if sys_language_uid = -1 - up to 8LTS it inserted records independent of sys_language_uid

Dear Ladies and Gentlemen,

up to 8LTS, when selecting the “Insert Records” content element, TYPO3 just did show the inserted records on the target page without any language check.
with 9LTS, “Insert Records” performs a language check requiring the source content to be either of the same sys_language_uid or of -1.
It is my opionion that this breaks compatibility and that the language check in this case should be removed.

Next week I will investigate the core together with my developers to find a solution.

Best regards,

Patrick

Author Daxboeck no-lastname-given
Created 03/22/19, 10:40
Updated 10/19/21, 19:05
Epic
Accepted Orphaned

#95690 Performance issues when hosting a large amount of websites, and optimizations propositions

Context

My company uses Typo3 to provide a website to each of our clients, meaning that we host around 3500 websites (i.e. around 120.000 pages) on a single Typo3 installation.

We’re now using Typo3 10.4. This installation is built with composer, uses php7.4 and mariadb 10.3, and is hosted on a dedicated apache server.

The general behaviour is really satisfying, but hosting that many websites and pages also presents some difficulties.
The main challenges we faced were about perfs.

First of all, the website configuration system introduced with Typo3 9 and implying one yaml file per website caused a huge performance loss. The time needed to parse 3500 files is really long, and opening the “Sites” backend module can last something like 30sec.

We also had to rise the php limit about the max number of files that it can maintain open at the same time.
The website and page resolution were also problematics. In their primitive form, they triggered one or two db query per site, meaning that each page displayed made around 7000 db queries each time! Not only the loading time was near to 6secs, but our hosting machine had some bad times…

We fixed these issues by:

  • rebuilding an inbase website configuration (we’ve got a ‘website’ table hosting those informations). The ‘pages’ table got a new foreign key linking it to this new table.
  • overriding the \TYPO3\CMS\Frontend\Middleware\PageResolver middleware to resolve the website first with one db query on this ‘website’ table, then
    a second query in the ‘pages’ table to find the suited page. From 7000 queries, we’re now to only 2.
  • also, xclassing the now named TYPO3\CMS\Core\Routing\PageSlugCandidateProvider class, precisely the getPagesFromDatabaseForCandidates method. the way this method is designed makes the while loop to call getSiteByPageId once for each page matching the given ‘slug’. But with 3500 websites, we’ve also got 3500 pages with the ‘/’ slug..

The last problems we could’nt solve at this time are related to the backend when accessed by the super-admin.
Because this admin can see all of the pages, sites, files, or users, the backend performances are really overstretched.

Reproducing and optimizing

I created a docker container reproducing the problem, and an extension that assemble the patches we made.
You can find it there: https://github.com/Opentalent/Typo3MultisitesOptim

The docker is based on the martinhelmich/typo3:10.4 container.

An extension (populate) provides CLI command to populate the DB with as many dummy websites as requested:

php /var/www/html/typo3/sysext/core/bin/typo3 ot:populate 3000

For those who possess a blackfire licence, it also ship a blackfire docker, allowing to profile the typo3 docker, with or without the optimization measures.

Last but not least, I ran two blackfire tests against this container on my machine. These tests were run with 3510 of thoses basic websites (=108810 pages), and all caches flushed before each test :

Author Olivier Massot
Created 10/18/21, 14:40
Updated 10/19/21, 06:22
Feature
New Orphaned Pagetree

#94080 Pagetree ShowNavTitle and selectTree

Hello,

in the User-Config with

options.pageTree.showNavTitle = 1
I can use the nav title instead of the page title for the rendering. When using a selectTree (https://docs.typo3.org/m/typo3/reference-tca/master/en-us/ColumnsConfig/Type/Select/Tree/Index.html) the page title is rendered and not the nav title. The selectTree should also consider this option.
Best would be to make this more flexible and

But i think if the option is set for the user globale the selectTree should also consider this setting.

Thanks and kind regards,
Harald

Author varioous OG
Created 05/06/21, 14:29
Updated 10/14/21, 07:08
Task
New Orphaned Backend API TYPO3 CMS 10

#95621 Initial sorting of added assets

There is inconsistency in behaviour when adding assets, two buttons next to each other, if editor choose Add media file (from server) images are sorted ascending, but if editor choose Select & upload files images are sorted randomly.

This is non breaking as for now you never know in what order images will be added.

https://app.slack.com/client/T024TUMLZ/D01CZBWMHV1

Author Zeljko Debeljuh
Created 10/13/21, 08:11
Updated 10/13/21, 08:11
Task
New Orphaned Security TYPO3 CMS 10

#95559 Make authentication warnings configurable

Following TYPO3_CONF_VARS should be configurable:

  • ['BE']['warning_email_addr'] (possible already)
  • ['BE']['warning_period'] (new, time in seconds >= 0, 0 means always)
  • ['BE']['warning_max'] (new, integer >= 0, 0 means always)
Author Oliver Hader
Assigned to Oliver Hader
Created 10/11/21, 10:42
Updated 10/11/21, 10:42
Bug
New Orphaned Import/Export (T3D) TYPO3 CMS 11

#95007 Checking the file checksum on export or import may fail due to sanitizers

The calculated file checksums of the exported sys_file records in a TYPO3 export dump – made via EXT:impexp – may not match the actual checksum of the exported file, since the checksum is calculated before the file is copied to the export folder, and the checksum may change during this copying process. The copy process is done by GeneralUtility::upload_copy_move , which applies arbitrary sanitizers (e.g. SVG sanitizer) under the hood. One solution would be to recalculate the checksum after the file is copied.

The same applies for the import: During import the sanitizers may change the file content and make the final checksum test fail. It has to be checked, if this test should rather raise a notice than an error on failure, or if the test can be modified to still ensure validity.

Author Alexander Nitsche
Created 08/26/21, 13:35
Updated 09/17/21, 13:43
Bug
New Orphaned DataHandler aka TCEmain TYPO3 CMS 10

#90939 DataHandler: Existing pages are not moved into newly created pages

I suspected from the documentation https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/Typo3CoreEngine/Database/Index.html that this should work:

$data = [
    'pages' => [ 
        'NEW_IT' => [
            'pid' => 1,
            'hidden' => false,
            'title' => 'IT',
        ],
        591 => [
            // this is not set
            'pid' => 'NEW_IT', 
            // but this is set
            'title' => 'I am a child of IT', 
        ],
    ]
];

Yet it creates the new page but only sets the property ‘title’ on page 591. Page 591’s ‘pid’ is not changed.

@Stefan Bürk has done a tremendous job in verifying that from TYPO3 8-10 and also finding that the DataHandler explicitly disallows that (https://stackoverflow.com/a/61000253/2819581)

The question is if either
a) documentation should be amended
b) DataHandler can be fixed

Author Jonas Eberle
Created 04/03/20, 09:53
Updated 09/14/21, 09:50
Bug
New Orphaned TYPO3 CMS 10

#91291 FlexForm - Value of field is string instead of array

Hello everyone,

I’m currently working on a Extension with FlexForms and stumbled onto something.

Issue:
Accessing $config[‘row’][‘settings.*’] of other flexform settings in itemsProcFunc results in a string instead of an array while using a display condition in some cases.

Description:
I created a FlexForm with two selectSingleFields Board and List. Both fields get their values from itemsProcFunc. The List*-Select relies on a displayCond that requires *Board to be set. Board has an onChange reload property to reload the FlexForm that then shows List.
Code here:
https://github.com/Crontis/trello_integration/blob/master/Configuration/FlexForms/ShowCardsOnList.xml

In the List*-ItemsProcFunc I access the value of *Board. In some cases, like during the creation of a new content element with this plugin and flexform, the value of Board equals a string. In other cases, like editing an existing plugin, the value of Board equals an array with a single value.
Code here:
https://github.com/Crontis/trello_integration/blob/master/Classes/Backend/ItemsProcFunc.php

This seems to be an issue with the differentiation of columns into new or edit in FormDataProvider\TcaFlexProcess. In some occasions List will be an editColumn where Board is a newColumn. In this case Board will not be resolved at the time List is interpreted, which results in a string instead of an array.

I’m not too familiar with the handling of FlexForms but this does seem like a bug?

Author Markus Kugler
Created 05/04/20, 14:46
Updated 09/10/21, 14:33
Bug
New Orphaned Backend User Interface TYPO3 CMS 10

#95049 Wrong default values of excluded localized fields

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

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

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

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

Author Christian Toffolo
Created 08/31/21, 09:29
Updated 08/31/21, 09:29

Showing results 1426 to 1450 of 1561