This is not a good solution for me. Have you tried this with collection types with fields that are non localized? Meaning fields that should be the same for all localization.
In my case, I have a bunch (eg, images that should be shared accross all localizations). So, if I move forward with your suggestion, I end up loosing all values on fields that are not localized, and it’s very frustrating. I’ll expand the steps you outlined:
- with the content manager go to the content type for which you want to duplicate the content for another language
- make sure a non-localized field exists on that collection type
- select the language on the drop down list in the right side
- click right away on save
**** Note how you already loosed data on non-localized fields from the original language **** - the “fill in from another locale” appears
- click on it
- localized fields (the remaining ones) will be copied over to the new language
—> Conclusion: Data is lost
Anyone experiencing the same? I’m currently on strapi 4.14.4
Thanks