If we add [CultureSpecific] to a property that already has a value all language variants looses their values, except for the master language. It would be nice if there was support for migrating the value from the master language to all language variants.
like a migration step for the content type itself?
There is already migration steps for renaming properties and content types https://world.episerver.com/documentation/Class-library/?documentId=cms/10/93B6FD87. Content types doesn't make sense though, since you probably aldready have an ID on them, but changing the name of a property without loosing the value is nice. That's why it would be nice to handle the change of culture-specific properties as well.
I also ran into this problem a while back so I took the liberty of rebuilding the missing properties-plugin to a Removed Culture Specific attribute-plugin. Feel free to download it from here:
Thanks for sharing Lindy. But my case is the other way arround. I want to add CultureSpecific to properties without loosing any content on the language variants.