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

Console error when opening any item in the content tree: Cannot read properties of undefined (reading 'labelKey') #18408

Closed
stephen-sherman opened this issue Feb 21, 2025 · 2 comments
Labels

Comments

@stephen-sherman
Copy link

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

13.6.0

Bug summary

In Umbraco 13.6.0, opening any item in the content tree results in the following error being logged to the console: Cannot read properties of undefined (reading 'labelKey').

Likely related, the labels in the save and publish submenu (schedule, publish with descendants, and unpublish) disappear after performing any publish action.

Reproduced in multiple sites on Umbraco 13.6.0. Does not occur in Umbraco 13.5.3.

Image

Specifics

No response

Steps to reproduce

To see the error:

  1. Log in to the Umbraco back office
  2. Open the browser console
  3. Navigate to an item in the content tree

To see the disappearing publish submenu action labels:

  1. Save and publish, schedule, publish with descendants, or unpublish a content item
  2. Re-open the Save and publish submenu

Expected result / actual result

Expected:

  • No console error
  • Schedule, publish with descendants, and unpublish action labels remain visible

Actual:

  • Console error
  • Schedule, publish with descendants, and unpublish action labels show only "..."
Copy link

Hi there @stephen-sherman!

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

@AndyButland
Copy link
Contributor

Thanks for reporting @stephen-sherman but I think we have this one already, so I'll close as a duplicate of #18253. You should expect it resolved in 13.7, which is available now as a release candidate.

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