You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 25, 2022. It is now read-only.
Sorry in advance if the topic already came up earlier!
Currently, we are using the plugin to export collection data from one Strapi instance and importing it on another Strapi instance. But in order to make this work, we had to patch the contentChecker.js to not only match media and relation references by id, but also by the 'name' property of entities. (See my fork if interested).
The question is if there is maybe a plan to mark a single field as the unique identifier for the importer to match the correct relation and media references? Or maybe there is already a different solution for the problem.
Thanks in advance!
P.S. If you want to skype and talk about this issue, just pm me.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sorry in advance if the topic already came up earlier!
Currently, we are using the plugin to export collection data from one Strapi instance and importing it on another Strapi instance. But in order to make this work, we had to patch the contentChecker.js to not only match media and relation references by id, but also by the 'name' property of entities. (See my fork if interested).
The question is if there is maybe a plan to mark a single field as the unique identifier for the importer to match the correct relation and media references? Or maybe there is already a different solution for the problem.
Thanks in advance!
P.S. If you want to skype and talk about this issue, just pm me.
The text was updated successfully, but these errors were encountered: