Properties shared across cultures are not editable once populated

[ewuski]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

13.2.2

Bug summary

With a multilingual setup (for example 3 languages) some properties of the content are shared (not varied by culture).
Once they become populated, it is not possible to edit them even in the default language.

The following message appears when hovering on the property editor:

{property name} is shared across all languages.

{property name} can be any property name over which I am hovering.

It happens to all shared (not varied by culture) properties of all observed doc type.

Specifics

We have 3 languages setup as per the screenshot:

Then, we have a page with some properties varied by culture:

For example, the last property above Estimated time, is shared across all cultures.

Once it is populated in more than one language version, it is impossible to edit it in any language - see below:

Polish:

English (UK):

French:

We can still edit it if we only have one language version of the page added - see below:

Estimated price is editable on the only language version of the page:

Checked Chrome 129.0.6668.91 & Firefox 132.0.2.

As far as I remember, this issue didn't happen before. Possibly in one of the previous versions of Umbraco as after migrating from version 7 we upgraded from 9 to 10 and then to version 13.

Steps to reproduce

Add multiple languages to the site as per the above description.
Make a doc type varied by culture.
Make some properties varied by culture and others not.
Add a content page and populate the shared property.
Add another language version of the same page.
Observe the result.

Expected result / actual result

The shared property should be editable in the default language content version.

[github-actions]

Hi there @ewuski!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂