`page` field not visible in translation

[ursbraem]

Hi

It's thought as a feature, but it can be a bug.

In tx_powermail_domain_model_field the page field (the parent fieldset of this field) is defined as only visible in Lang=0.

'displayCond' => 'FIELD:sys_language_uid:<=:0',

But sometimes, this value is not filled in in localised records.

Or, you want to move a field from one page to another.
I don't see how the translation relation would be updated automatically.

Shouldn't this field be visible in all languages?

[ursbraem]

PS: I've now just overridden it in the TCA

// Show 'tx_powermail_domain_model_field.page' in all languages
// (override 'displayCond' => 'FIELD:sys_language_uid:<=:0',)
unset($GLOBALS['TCA']['tx_powermail_domain_model_field']['columns']['page']['displayCond']);

[mschwemer]

Hi

I had a look at it.

IMHO it does not make sense at all to edit the field record on its own, neither in the default language nor in the translation.

This should always happen within the edit of a form. For editors I usually do not display powermail pages and fields. Admins, and system maintainers should know what they do.

Had a look at the git history. It was introduced in Feb. 2017, when the l10n_mode noCopy was removed from core. Commits:

• 5d49be5
• 5191060

So I think it is save to remove the display cond.

[ursbraem]

Thank you!