MigrationStep: Add support for changing CultureSpecific

Vote:
 

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.

#182911
Sep 29, 2017 15:55
Vote:
 

like a migration step for the content type itself?

#183109
Oct 05, 2017 13:44
Vote:
 

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.

#183114
Edited, Oct 05, 2017 14:03
Vote:
 

Hey Johan,

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:

https://bitbucket.org/LHutz/removedculturespecificattribute/overview

Kind regards,

#184684
Nov 02, 2017 10:37
Vote:
 

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.

#184687
Nov 02, 2017 10:53
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.