Problem changing the powermailCleaner settings in flexform on content elements in connected language mode

[sypets]

Thank you for providing these extensions. I am generally very happy with powermail and powermail_cleaner. 👍

I have 2 connected powermail plugin content elements which were created a while ago:

1. uid=473754 default language
2. uid=473754, l18n_parent=473754 (connected mode)

I changed the setting for the element in default language in

"Data protectedion / Clean-up" :

before:
"Data is not stored in database"

after:
"Data will be cleaned after the specified deletion period"
"Clean-up period in days:" : 1

It was already a bit weird that the Flexform showed "Delete in 14 days" but the behaviour was "Do not save".

Now, I can't change it in the translated element in connected mode:

But the settings are missing in the flexform (if I look in tt_content.pi_flexform).

Also, in the FE I get the following information on the page with default lang, but not on translated page:

---

Update:

I think I can work-around this by removing the connection (l18n_parent), setting the deletion period in element with connected mode and then setting the language connection again. (that is not how it is supposed to work, in connected flexform the fields are not displayed, instead there is a different setting e.g. settings.flexform.powermailCleaner.deletionBehavior_l10n which is readonly and where the values of the original lang is displayed. It is correct that the fields are not saved to the flexform, it is not correct, that in the translated page the fields of the original lang are not used!

see https://github.com/in2code-de/powermail_cleaner/blob/typo3_13/Configuration/FlexForms/PowermailCleaner.xml

Versions

• TYPO3 v13.4.24
• powermail: 13.0.4
• powermail_cleaner: 13.0.1

Additional info

default lang pi_flexform has this part, pi_flexform of translated content element does not:

 <sheet index="powermailCleaner">
            <language index="lDEF">
                <field index="settings.flexform.powermailCleaner.deletionBehavior">
                    <value index="vDEF">deletionPeriod</value>
                </field>
                <field index="settings.flexform.powermailCleaner.deletionPeriod">
                    <value index="vDEF">1</value>
                </field>
                <field index="settings.flexform.powermailCleaner.informReceiversBeforeDeletion">
                    <value index="vDEF">0</value>
                </field>
                <field index="settings.flexform.powermailCleaner.deletionContact">
                    <value index="vDEF"></value>
                </field>
                <field index="settings.flexform.powermailCleaner.deletionDetails">
                    <value index="vDEF"></value>
                </field>
            </language>
        </sheet>

[sypets]

Update

The described workaround works for me as temporary solution 👍 (but it is not so great longterm as the editors maintain the powermail forms themselves and this makes it a bit tricky)

I don't recommend the previously described workaround. That is not how it is supposed to work: in the flexform in the connected translation (l18n_parent > =) the fields are not displayed, instead there is a different setting e.g. settings.flexform.powermailCleaner.deletionBehavior_l10n which is readonly and where the values of the original lang is displayed. It is correct that the fields are not saved to the flexform, it is not correct, that in the translated page the fields of the original lang are not used!

[typoworx-de]

I'm struggling with similar problem. For one of my forms in a TYPO3 actually upgraded to TYPO3 v13 I noticed in EN (localized form) the powermailCleaner settings (in FlexForm) are used with values from default language.

Never the less for some reason in FlexForm there are separated fields for l10n which actually implement their own l10n logic by having the original field plus field with "_l10n" in the fieldname:

• settings.flexform.powermailCleaner.deletionBehavior <> settings.flexform.powermailCleaner.deletionBehavior_l10n
• settings.flexform.powermailCleaner.deletionPeriod <> settings.flexform.powermailCleaner.deletionPeriod_l10n

Is there any reason for this workaround? Shouldn't TYPO3 core be able to handle this even with FlexForm Fields?

[typoworx-de]

I've noticed FlexForm behaviour in modern TYPO3 versions still behaves different than classic database TCA fields. I've proposed a fix for FormController which fixes the missing values for localized form records.

[sypets]

Is there any reason for this workaround? Shouldn't TYPO3 core be able to handle this even with FlexForm Fields?

@typoworx-de Is the mentioned problem in TYPO3 core the reason for this? Can you link to the issue in TYPO3 core if there is one? Or should we open one?

I am just wondering if we can find a clean and easy solution which will "just work" using core functionality. I don't have this problem with any other extensions but it might be that using flexform values from the default language content element is not so common.

If that is not possible I will check out your fix and hope the maintainers look at this too.

[typoworx-de]

@sypets have a look here f.e.:

• https://forge.typo3.org/issues/100993

  this is not possible and won't be build. flexform is already a not 100% feature set of TCA and adding l10n_mode into single fields of flexform would increase the complexity (+ potential errors) enormously.

• https://forge.typo3.org/issues/96673

This is an old story as FlexForm (XML) does not support every feature that native TCA (native database fields != XML Forms).

I often run into similar problem myself and have to figure out whether FlexForm supports it (in the meantime) or not.

[sypets]

Update: Additionally there seems to be a problem in the localized page with deletionDetails, see #27 by @typoworx-de

I must admit I initially did not check the localization behaviour of the additional fields like deletionDetails, deletionContact, informReceiversBeforeDeletionPeriod, because we usually do not use these.