Umbraco doesn't find my node

Questions
1

Context

  • Umbraco version 8.18.7
  • We can see the node in the node three in the backoffice, but when we click on it to access, umbraco doesn’t find my node and it throws this 404 error.
    image
    image830×854 10.7 KB
  • I already tried removing the Temp folder and restarting my webapp, rebuilding the index and cache.

Issue:

  • My node appears in the backoffice but I can’t access to it (all the actions are not allowed because it throws a 404 error when it tries to find it) and I received this error from Umbraco logs:
System.Web.Http.HttpResponseException: Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by the 'Response' property of this exception for details.
   at Umbraco.Web.WebApi.Filters.EnsureUserPermissionForContentAttribute.OnActionExecuting(HttpActionContext actionContext) in D:\a\1\s\src\Umbraco.Web\WebApi\Filters\EnsureUserPermissionForContentAttribute.cs:line 129
  • I checked the database and the node appears in all the principal tables. For some reason Umbraco can’t add it in the internal index because it considers it doesn’t exist.
    I would appreciate any help with this issue, thanks.
2

I’m not sure if it’s located in temp, but maybe try to delete the umbraco.config cache file?

3

That wouldn’t help, that is caching for the frontend.

I don’t know how to help here, I am assuming this was an upgrade from a different version? If so which version? On some occasions I’ve seen this problem after an upgrade. Check the Umbraco logs and server logs as well for related errors. It’s difficult to deduce something from the database content as you tried because a lot of different tables link things together to be able to display a node, so if one of the things it needs is missing you might get an error like this.

Anyway, check both logs first and see if you can see something wrong from there.

4

Yeah I know, it was a really long shot, although I’ve seen weird issues, also in the backoffice on older versions of Umbraco with a mismatch between frontend and backend. But I guess in most cases it was probably something in the backoffice that didn’t show on the frontend or something…

5

Hi Everyone, thanks for your replies, I already figured out how to solve it. I ran a sql script to switch into a past node version. The issue was that the current version of the node wasn’t linked to anything in the propetiesdatatype table. Thanks

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.