Label Value Clears Upon Publishing

[martinthogersen]

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

15.1.1

Bug summary

When publishing a page with a "Label Property Editor UI" (value type: String), the label's value is cleared. This issue may potentially affect all label types.

Please see the video below for a demonstration. Note that this error also occurs in Umbraco 14.3.1.

Specifics

No response

Steps to reproduce

1. Programmatically set the label value, for example:

var content = _contentService.GetById(...);
content.SetValue("usageCount", 1);
_contentService.Save(content);
_contentService.Publish(content, []);

2. Open Umbraco and verify that the value is correctly stored for "usageCount".
3. Publish the content.
4. Observe that the value is now removed.

Expected result / actual result

No response

[github-actions]

Hi there @martinthogersen!

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 🤖 🙂

[warrenbuckley]

Same report to my issue @martinthogersen
#17889 which got closed and pointed to
#16615

Hopefully @NguyenThuyLan can advise further

[kjac]

Hi @martinthogersen (and @warrenbuckley) 👋

Thanks a lot for reporting! I'm looking into all of these this week 😄

I'm going to close this one in favour of the other two which @warrenbuckley pointed out above. We assume the root cause is what @NguyenThuyLan added in this comment, so for the time being, all communication regarding this issue will be on #16615

[martinthogersen]

@warrenbuckley @kjac Thank you!