Issue transferring shared properties when language variants is enabled #249
Description
We have noticed an interesting workflow when transferring content that has culture variants enabled.
I created a content node that supports culture variants in only one language: i.e. en-GB, populated the fields, save and publish, then clicked transfer now.
Considering I only created the node in en-GB, I deselected all the other languages and executed the transfer. I was surprised to see that after transferring, none of the shared properties were deployed to the target environment, only the en-GB specific ones.
Reproduction
Bug summary
When culture variants are enabled, shared properties are not transferred unless all supported languages are included in the Umbraco Deploy transfer.
Specifics
- Umbraco Heartcore
- Google Chrome Version 132.0.6834.84 (Official Build) (arm64)
Steps to reproduce
- Enable multiple languages in the CMS
- Create a document type with language variants enabled
- Create some properties with language variants enabled, but some without (shared properties)
- Create a content node using the new document type in only 1 language. Populate all fields. Save and publish.
- Click transfer now to deploy the field to a target environment.
- Deselect ALL languages for the deployment, except for the one language you have populated. Transfer/Deploy the content
- Check the content in the target environment.
Expected result
I would expect all properties of the content node to be deployed to the target environment
Actual result
The shared properties are not deployed to the target environment.
Umbraco support have mentioned this is because if the shared properties were deployed, they would override the other languages that were not deployed, which could result in undesirable results. This makes sense, but it's not very intuitive for the end user. If this is not a defect, can the UX be improved?