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

"Not Found" Error Appears Briefly When Navigating to Content Section #18671

Open
okadriu opened this issue Mar 13, 2025 · 1 comment
Open

"Not Found" Error Appears Briefly When Navigating to Content Section #18671

okadriu opened this issue Mar 13, 2025 · 1 comment
Labels

Comments

@okadriu
Copy link

okadriu commented Mar 13, 2025

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

15.3.0-rc2 (also present in 15.2.3)

Bug summary

When navigating to the Content section in the Umbraco backoffice, an error message appears briefly before the content loads. The message displayed is:

"Not found, The requested route could not be found. Please check the URL and try again."

After a few seconds, the correct content loads as expected. This seems to be a UI issue where the error is shown too early instead of a proper loading state.

Specifics

  • Happens when clicking on the Content section in the backoffice.
  • Tested in Chrome, Edge, and Firefox – issue occurs in all browsers.
  • Attached is a screenshot of the error.

Image

Steps to reproduce

  1. Log into the Umbraco backoffice.
  2. Click on the Content section.
  3. Observe that a "Not Found" error briefly appears before the actual content loads.

Expected result / actual result

Expected Result:

  • Instead of an error message, a loading indicator should be displayed while fetching content.
  • The "Not Found" message should only appear if the content actually does not exist, rather than appearing temporarily during the loading process.

Actual Result:

  • The "Not Found" message appears incorrectly before the content loads, leading to confusion.
Copy link

Hi there @okadriu!

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