Localized entries are not migrated correctly - _localization_links tables missing values in inv_* fields

strapi / migration-scripts

Collection of Strapi Migration scripts

58 stars 58 forks source link

Localized entries are not migrated correctly - _localization_links tables missing values in inv_* fields #71

Closed sarsonj closed 1 year ago

sarsonj commented 1 year ago

Bug report

Required System information

Node.js version: 14.2
Source Strapi version: 3.6.10
Target Strapi version: 4.5.1
Source Database: mysql
Target Database: mysql
Operating system: Linux
Which script are you running: v3-sql-v4-sql

Describe the bug

I run data migration from 3.6.10 version to latest 4.5.1. The migration finished, but for localized entries no links were correctly created. The _localization_links tables are not empty, but the _inv field is always null. Like:

sarsonj commented 1 year ago

I made analyzation what is happening and the problem is, that in the original 3.x version table, the link to translated content field is named "blog-article_id". The migrateItem method in migrateFields.js converts this field to the same blog_articleid. I am not sure, when naming convention changes, looks like newer version are using related prefix.

Screenshot of 3.x table:

martincapek commented 1 year ago

Hi, this should be fixed in #73 and happens due to the Strapi update. Can you please test it and confirm it works?

derrickmehaffy commented 1 year ago

fixed by: https://github.com/strapi/migration-scripts/pull/73