Project

General

Profile

Actions

Bug #92046

closed

forms migrateTranslationFileOptions seems not to work

Added by Kevin Ditscheid over 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Won't have this time
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2020-08-19
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Remote Sprint

Description

I have several form definitions with custom translation files defined in

TYPO3:
  CMS:
    Form:
      prototypes:
        standard:
          formEditor:
            translationFile:

for example, but it is not automatically migrated to translationFiles like the migrateTranslationFileOptions function in TYPO3\CMS\Form\Controller\FormEditorController is suggesting. Instead I have to add the translationFiles setting in addition to keeping the old setting for backwards compatibility.

Actions #1

Updated by Björn Jacob over 2 years ago

  • Sprint Focus set to Remote Sprint
Actions #2

Updated by Mathias Brodala over 2 years ago

  • Status changed from New to Closed
  • Priority changed from Should have to Won't have this time

Yes, the runtime migration only affects form definitions, not form setup.

The form setup cannot be migrated automatically since it is out of scope for the form editor.

Actions

Also available in: Atom PDF