Source language files not migrated

Created on 10 March 2020, over 4 years ago
Updated 5 June 2023, over 1 year ago

I ran into a strange situation. The project I'm maintaining is DE / EN.

The node type whose fields I tried to migrate from file / image to media image / document is mostly created in DE and translated to EN. So i created the three migration files based on DE and translation in EN, but my final result is that only EN files are migrated, all German fields stay empty (also no entries with lang "de" in the database table).

It would be nice to have some documentation how to handle fields
- with shared translation ( ✨ How to migrate shared (language "und") images? Active )
- with different uploads in both languages

and if the _media field and the original field have to have the same translatability configuration.

As said in the other issue I guess it would be the best to keep the language behaviour 1:1 for file and media fields and OPTIONALLY handle special translation cases like creating a copy for different languages.

✨ Feature request
Status

Closed: won't fix

Version

2.0

Component

Code

Created by

πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡¦Ukraine HitchShock Ukraine

    Hi @stephenplatz
    Your case is possible only when the default content language can be diff from a site's default language.
    For example:
    - the site's default language is 'en'
    - you generated configs with a default language 'en'
    - the content's default language is 'fr' and it doesn't contain 'en' translation
    - in this case a media with a default langcode 'fr' should be created but it won't be cuz you don't have specified migration configs for that.

    To solve such an issue you need to have configs that will migrate 'fr' content as a default language (not as translation) and config for 'en' language as a translation.

    But also, the better solution that can fix the issue is to migrate all possible files on the first step (without language filter).
    We provided such a solution for that in another ticket https://www.drupal.org/project/migrate_file_to_media/issues/3321588#comm... ✨ Allow to avoid translation filtering Fixed

Production build 0.71.5 2024