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

Tree state not kept when navigating between sections #17554

Open
enkelmedia opened this issue Nov 17, 2024 · 1 comment
Open

Tree state not kept when navigating between sections #17554

enkelmedia opened this issue Nov 17, 2024 · 1 comment
Labels

Comments

@enkelmedia
Copy link
Contributor

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

15.0.0

Bug summary

Not sure if this is a bug or if this is intentional but I wanted to post this since I think that it is important.

When I'm working on a node in the content-section, navigating to the media section and then want to go back the tree is collapsed and the dashboards are shown, like this:

umb-tree-state

Not a big deal in the example but most of the real world websites that we work with will have at least 4-5 levels (sometimes more) so I would argue that this is a very nice feature for editors (and probably expected if they are used to Umbraco 13).

I can see that this is not a easy fix. If we keep the tree state when clicking on "Content" - how would someone be able to get back to the dashboards again? Maybe only load dashboards the 2nd time if clicking on the active section? Not sure.

Specifics

No response

Steps to reproduce

I think that the way Umbraco 13 works in these scenarios is the "right way", that means remembering the last document that was edited and loading this document + the tree.

Expected result / actual result

No response

Copy link

Hi there @enkelmedia!

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

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

1 participant