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

Cannot switch to content tab on items after upgrading from 13 to 15 #18101

Closed
muradious opened this issue Jan 23, 2025 · 2 comments
Closed

Cannot switch to content tab on items after upgrading from 13 to 15 #18101

muradious opened this issue Jan 23, 2025 · 2 comments
Labels

Comments

@muradious
Copy link

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

15.1.2

Bug summary

After going through an upgrade from Umbraco 13 to the Latest on Umbraco Cloud, we have an issue where selecting any item with multiple tabs in the content tree the editor will jump to any other tab except Content. When clicking on the content tab, Umbraco underlines it, but does not switch to it.

I will include a screen record below

Specifics

In the content tree, go to any item with multiple tabs, it will default to any tab other than content, when clicking on it it will do nothing.

Steps to reproduce

Tab.Error.webm

Expected result / actual result

It should switch to the content tab with no issues

Copy link

Hi there @muradious!

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

@nul800sebastiaan
Copy link
Member

Thanks for the report, it's a bug we're aware of and working on, please subscribe to the related issue #17676 for updates.

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