#58491Impexp lacks support of keeping or setting new uids of lost relations
Description
- have translated records
- export page with all translated content
- do not export the sys_language record, because it got duplicated on import
- all sys_language_uid fields will have a lost relation to the sys_language record
On importing such export all sys_language_uid fields are set to 0
and so all translated records are on default language.
Idea to solve this: on importing there should be a list of records with corresponding uids where from other record fields a lost relation is set to. There you choose to force the old uid (import on the same instance) or to set a alternative one (import on other instance).
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 7
-
Marc Bastian Heinrichs changed TYPO3 Version
6.27 <span data-processor="relativetime" data-value="2015-06-18T13:47:39+00:00" > 06/18/15, 13:47 </span> -
Marc Bastian Heinrichs changed tracker
TaskFeature <span data-processor="relativetime" data-value="2015-06-18T13:48:14+00:00" > 06/18/15, 13:48 </span> -
Anja Leichsenring changed Sprint Focus On Location Sprint <span data-processor="relativetime" data-value="2016-01-08T11:22:48+00:00" > 01/08/16, 11:22 </span>
-
Nicole Hummel changed Sprint Focus
On Location Sprint<span data-processor="relativetime" data-value="2016-05-09T15:22:21+00:00" > 05/09/16, 15:22 </span> -
Markus Klein changed parent task #72584 <span data-processor="relativetime" data-value="2018-02-28T12:21:32+00:00" > 02/28/18, 12:21 </span>
-
Benni Mack commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-06T07:42:09+00:00" > 11/06/26, 07:42 </span>Closing this issue, as the scenario no longer applies. The sys_language table was deprecated in v11.3 (#94165) and removed in v12.0. Languages now come from the site configuration, and the language field uses the TCA type language (#57082), a plain integer value rather than a relation to a database table. Impexp therefore no longer resets sys_language_uid to 0 because of a “lost relation”. For relations to other tables that aren’t part of the export, mark them as static relations on export, as suggested.
I think this issue was part of the original FAL / impexp assessment, so another reason for cleaning up.
Note. The described issue is easy to solve. Simply select sys_language as “static relation” on export.