Breaking: #87009 - Use multiple translation files by default in EXT:form

See forge#87009

Description

All translationFile options in EXT:form setup and form definitions have been renamed to translationFiles.

The following default translation files are now registered at index 10 in all locations:

  • EXT:form/Resources/Private/Language/locallang.xlf

  • EXT:form/Resources/Private/Language/Database.xlf

Impact

Extending form setup or form definitions with additional translation files does not require adding the default translation files anymore.

The option translationFile does not work anymore and must be migrated to translationFiles.

Opening and saving a form with the form editor once also performs the migration of the corresponding form definition and makes it permanent.

Affected Installations

All installations which use EXT:form and its translationFile option.

Migration

In your custom form configuration, migrate the single value translationFile option to the multi value translationFiles option.

Given that all default translation files of EXT:form are registered at index 10 it is recommended to use a higher index for custom translation files.

Single file

Before:

translationFile: path/to/locallang.xlf

After:

translationFiles:
  20: path/to/locallang.xlf

Multiple files

Before:

translationFile:
  10: EXT:form/Resources/Private/Language/locallang.xlf
  20: path/to/locallang.xlf
  25: path/to/other/locallang.xlf

After:

translationFiles:
  20: path/to/locallang.xlf
  25: path/to/other/locallang.xlf