[V15-RC2] URL to document types in settings occasionally gets stuck on /root and it won't show content

[BernadetGoey]

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

15.0.0-rc2

Bug summary

I'm reporting this buy for the 15.0.0 RC but I've noticed it's also the case in V14.

This is probably a pretty obscure bug, but I've noticed that occasionally when I opened my document type, which entirely exists of compositions, that it wouldn't open the first available content tab and just show 'Add group', as if the document type had no fields.

Specifics

I've made a screen recording since it happens occasionally, but often enough that I'm able to replicate it. It appears that the URL to the document type occasionally changes to /root instead of /tab/content and then it won't show the expected results.

You'll notice in the screen recording that initially the 'Content' tab of the '_Content' composition doesn't open and at the end it doesn't open for the 'Example Document Type' either.

Umbraco.-.Google.Chrome.2024-10-21.16-46-14.mp4

Steps to reproduce

1. Create a composition
2. Create a new document type
3. Add the composition to the document type
4. Switch between opening the document type and the composition, it'll eventually break

Expected result / actual result

I would expect for the first available tab with content in it to be opened when I click a document type.

---

This item has been added to our backlog AB#45479

[github-actions]

Hi there @BernadetGoey!

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

[nielslyngsoe]

Hi @BernadetGoey Thanks a lot for spotting this specific issue, and well described.
I have made a fix, it will be part of 15.2.
#17716

Thanks