Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration fails to migrate correct references to localized entries #101

Open
axelferdinand opened this issue Nov 10, 2021 · 0 comments
Open
Labels
bug Something isn't working multisite

Comments

@axelferdinand
Copy link

In v2, a localized entry has the same ID as the default language. In v3, each entry has a unique ID. Great.

When migrating a multisite, all the localized entries get their own IDs. Great.

The entry with the default language and the localized entry is connected with origin. Great.

BUT: If you have an entry with a reference to another entry, let's say by linking to it using the fieldtype entries, and your entry has 3 languages, things start to get messy... In v2, the reference would be identical for all 3 languages (the link to the entry you're targeting, is the same for all 3 languages, using the same ID) Meaning, you wouldn't have to set localizable: true on fieldtypes such as entries.

In v3, however, you will need to open up the default language, do your linking to other entries, open up the second language, do another round of linking, and so on. For a migrated site with hundreds of pages, featuring 3 languages, with thousands of references to other pages, this is quite overwhelming..

Could the migrator handle this also? Please?

@jesseleite jesseleite added bug Something isn't working multisite labels Nov 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working multisite
Projects
None yet
Development

No branches or pull requests

2 participants