Issue Bug Closed

#92974Re-import of website with form partially fails

Matthias Druske 12/02/20, 13:06 updated 11/13/26, 18:38

Description

I may have found a bug in TYPO3 (10.4.10). It seems, when you export a page (as XML file) with a form content element (inlcuding a form plug-in and included yaml-file) and try to import it, the plug-in file is not found. That’s because the used persistaceIdentifier should be 1:path/formfilename.form.yaml, but instead it is 1: followed by the uid of the yaml-file in the sys_file table. The website and yaml-file are properly* re-imported, the correct persistaceIdentifier is also listed in the plug-in dropdown list (and can be successfully chosen manually after import), but for some reason it is set to the wrong one described above, which is listed as well. If I had to import a website with many forms, it would be extremly troublesome to edit them all manually.

*as far as importing works anyway. There are other points I find strange about imports (such as the missing site configuration), but that’s not the issue at hand.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 3

  1. Simon Gilli commented and changed category status New Accepted <span data-processor="relativetime" data-value="2021-08-27T13:02:53+00:00" > 08/27/21, 13:02 </span>

    Can confirm this bug with the ext:introduction. Looks like the SoftRef parser does / can not correctly resolve the realtion on import. So far I have this issue with v10 and v11, not tested with v9 and below.

  2. Georg Ringer commented and changed status Accepted Closed <span data-processor="relativetime" data-value="2026-11-13T18:38:05+00:00" > 11/13/26, 18:38 </span>

    The problem only occurs for form definitions stored as YAML files in a file mount (e.g. 1:/form_definitions/foo.form.yaml). On import, the soft reference of the plugin’s persistenceIdentifier is resolved to the imported sys_file record and the value is rewritten to 1:<uid> instead of the file identifier, so the form is not found afterwards.

    File-based form storage was deprecated in v14.2 (see Deprecation: #108653) and the FileMountStorageAdapter is gone in main. Form definitions are now stored in the form_definition table (referenced by uid) or are delivered by extensions (EXT: paths). Both cases are handled correctly by the soft reference parser, so the affected setup no longer exists in main.

    Forms of existing file-based installations can be moved to database storage with the upgrade wizard “Migrate file-based forms to database storage”, which also removes the need to export/import YAML files via file mounts.