U4-8891 - Oops: this document is published but is not in the cache (internal error)

Created by Tito 23 Aug 2016, 09:24:30 Updated by Vidar Solberg 24 Feb 2017, 12:54:35

Your report will have a greater chance of being addressed if you can give us clear steps to reproduce the issue, please answer the following questions in as much detail as possible: What did you do? Upgrade from 7.4.3 to 7.5

What actually happened? Everything seems ok but only 3 level nodes are in the cache. From level 3 to a deeper level nodes are published but not in the cache. Only under one node, everything under other nodes its right. XML Data integrity is ok in developer section. Republishing entire site or delete umbraco.config does not solve the problem, only resaving the nodes solves temporary as deleting umbraco.config it returns to nodes not in cache. Note this is a very large site over 42.000 nodes published.

Comments

Tito 05 Sep 2016, 16:00:38

Still happens updating from 7.4.3 to 7.5.3


Vidar Solberg 24 Feb 2017, 12:54:35

I don't know if this is relevant to this issue, but after an upgrade from 7.1.8 to 7.5.10 I got the message "''This document is published but is not in the cache''" instead of the URL in the ''Link to document'' on a content node (Properties tab in the backoffice). (The frontend only site/page gave the message ''The resource you are looking for has been removed, had its name changed, or is temporarily unavailable''.)

The problem in my case was that on this node's parent node (== top level site) the node {{id}} was repeated in the {{path}} column in the database table {{umbracoNode}}. So a potensial loop. :-o

||id||trashed||parentID||nodeUser||level||path||...|| |1122|False|-1|0|4|-1,'''1122''',1123,1215,'''1122'''|...| |1123|False|1122|0|2|-1,1122,1123|...|

Changing to this fixed the issue (note ''level'' too): ||id||trashed||parentID||nodeUser||level||path||...|| |1122|False|-1|0|1|-1,1122|...| |1123|False|1122|0|2|-1,1122,1123|...|

I assume that this problem has been caused by moving nodes in an older version. And depending on node level and the code running, this may appear different.

The following SQL will give you these kind of problem nodes, so it's easy to check. :-) select * from umbracoNode where path like '%' + convert(varchar(5), id) + '%' + convert(varchar(5), id) + '%'

-Vidar


Priority: Critical

Type: Bug

State: Submitted

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 7.5.0, 7.5.3

Due in version:

Sprint:

Story Points:

Cycle: