Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

15.1.1: Loosing data saved in a label & unable to Publish node #17889

Closed
warrenbuckley opened this issue Jan 3, 2025 · 2 comments
Closed

15.1.1: Loosing data saved in a label & unable to Publish node #17889

warrenbuckley opened this issue Jan 3, 2025 · 2 comments
Labels

Comments

@warrenbuckley
Copy link
Contributor

warrenbuckley commented Jan 3, 2025

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

15.1.1

Bug summary

When saving a content node that contains a Label (string) property that varies by culture and is required
Upon publish then the value of the Label is removed 🙈 and an error is displayed that the node can not be published.

Specifics

No response

Steps to reproduce

Please follow along with this video for reproduction steps

Issue_17889_Loosing-Data-In-Labels-Unable-To-Publish.mp4

Document Type Setup

  • Set the document type to allow at root
  • Make the document type vary by culture

Properties

  • Title (Required & Varies by Culture) - Initially set as textbox
  • Override Title (Varies by Culture) - Textbox
  • Visible - (NON Variant) - True/False

Next steps

  • Create some test nodes with data stored in the title property
  • Modify the doctype that the title property is to a Label (string)
  • Navigate back to test content and update another property & attempt to publish

Expected result / actual result

That my document continues to publish with the modified change and the value stored in the label is not lost

Copy link

github-actions bot commented Jan 3, 2025

Hi there @warrenbuckley!

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

@NguyenThuyLan
Copy link
Contributor

Hi @warrenbuckley , thank you for reporting this issue.
It appears to be duplicate of issue #16615
Since the root cause of this bug seems to be the same, I will mark this issue as a duplicate so we can consolidate our discussions and updates in one place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants