TYPO3 Core

ext:news has a good solution for this: overrideFlexformSettingsIfEmpty

Perhaps we can do something similar in the core.

Another, related issue: there a quite a few TS constants which are never considered.

Sybille Peters wrote in #note-1:

ext:news has a good solution for this: overrideFlexformSettingsIfEmpty

Perhaps we can do something similar in the core.

Maybe the FAL solution for the alt text, caption and title should be standard behaviour with flexform settings. overrideFlexformSettingIfEmpty has the disadvantage that you can clear those settings (which would be a problem for e.g.g redirects if you can't override the TS setting).

Can confirm.

TypoScript settings are still overridden by flexform in TYPO3 11.5.13.

Updating some technical information:

\TYPO3\CMS\Extbase\Configuration\FrontendConfigurationManager::overrideConfigurationFromFlexForm is the one doing "the work".

as noted above: empty flexform values override whatever is there from TypoScript.

While this is wanted/needed for some settings, this is not the case for all settings, e.g. pages/pids.
But maybe there is even a usecase for this with pages/pids.

$GLOBALS['TYPO3_CONF_VARS']['FE']['checkFeUserPid'] is a config worth to mention.
Set it to false to work around this problem completely and allow all pids.

(T3-11)
One way to set via TypoScript is to remove the settings field from original flexform by overwriting the xml related to the tt_content.pi_flexform field
here an example
https://gist.github.com/einpraegsam/c16ba695a5e3d903c2a2f795d98bca71
In this way you can set different flexforms according to different conditions.
In my case, I needed to set the storage folders (pages) via TypoScript (by $constant), so I overwrote the FlexForm without the 'pages' field.
In my FlexForm, I removed 'settings.pages'
https://github.com/TYPO3/typo3/blob/ec00fb81a0f64050e37eb032fca7d28daaf6b3f8/typo3/sysext/felogin/Configuration/FlexForms/Login.xml#L46

Do we have a general issue for combining Flexform and TypoScript? Because I think there are several problems when you want to combine TypoScript and Flexform and it is not just the problem described here.

Yes we have a general issue for combining FlexForm and TypoScript.

I have the exact same problem with the login plugin since I switched to the Extbase-based version (instead of old pi1).

I want to dynamically configure the redirect after login and logout (redirectPageLogin and redirectPageLogout) but my TS is systematically overridden by the (empty) configuration coming from FlexForm, thus the plugin.

A solution that looks ok for that use case, but it would need extensive testing to ensure this has no side-effect would be to modify that line:

https://github.com/TYPO3/typo3/blob/main/typo3/sysext/extbase/Classes/Configuration/FrontendConfigurationManager.php#L339

that way:

- ArrayUtility::mergeRecursiveWithOverrule($frameworkConfiguration[$configurationPartName], $configuration[$configurationPartName]);
+ ArrayUtility::mergeRecursiveWithOverrule($frameworkConfiguration[$configurationPartName], $configuration[$configurationPartName], true, false);

For TYPO3 v10:

--- a/Classes/Configuration/FrontendConfigurationManager.bak.php    2022-12-05 15:29:19
+++ b/Classes/Configuration/FrontendConfigurationManager.php    2022-12-05 15:21:08
@@ -220,7 +220,7 @@
     {
         if (isset($configuration[$configurationPartName]) && is_array($configuration[$configurationPartName])) {
             if (isset($frameworkConfiguration[$configurationPartName]) && is_array($frameworkConfiguration[$configurationPartName])) {
-                ArrayUtility::mergeRecursiveWithOverrule($frameworkConfiguration[$configurationPartName], $configuration[$configurationPartName]);
+                ArrayUtility::mergeRecursiveWithOverrule($frameworkConfiguration[$configurationPartName], $configuration[$configurationPartName], true, false);
             } else {
                 $frameworkConfiguration[$configurationPartName] = $configuration[$configurationPartName];
             }

Can confirm on TYPO3 11.5.21 (noticed it during an upgrade from 8.7. to 11.5). It seems that it also leads to some status messages not being shown anymore (empty).

Also, don't know if this relates, but in the piBase-Version it was possible to use the password change form for a logged-in user. This is not the case anymore. Instead, the user is redirected to the "redirectPageLogin" page when clicking on the link to the password change form.

Xavier Perseguers wrote in #note-11:

A solution that looks ok for that use case, but it would need extensive testing to ensure this has no side-effect would be to modify that line:

https://github.com/TYPO3/typo3/blob/main/typo3/sysext/extbase/Classes/Configuration/FrontendConfigurationManager.php#L339

that way:

[...]

For TYPO3 v10:

[...]

This does not work for me for boolean fields. If TypoScript has defined settings.showPermaLogin = 1 and FlexForm has no config for this setting (= empty), the result for the setting is settings.showPermaLogin = 0, since the empty checkbox is saved with a 0 value to FlexForm.

I am currently trying to come up with a configurable solution for the problem in general (see #99976).

For v10 and v11, this problem can sadly not be fixed. For v12, extbase extensions can now use the new setting ignoreFlexFormSettingsIfEmpty to define FlexForm field, which will be ignored if either empty or zero. See #99976 for details.

FYI in case you reach this issue later on:

I created the "backport" for our own usage - since we need it in our projects as a bugfix. Feel free to use it in your v11 projects:

https://github.com/baschny/typo3/pull/1