U4-5350 - Node Stored in Umbraco.config XML Cache With Wrong Document Type

Created by Nicholas Westby 13 Aug 2014, 22:09:43 Updated by Shannon Deminick 26 Jun 2017, 05:40:42

Really strange bug for you. Basically, a client was noticing some content missing from a page, and it turns out the reason for it is that I was using the API to scan for the content by document type, and Umbraco had somehow stored that node in the XML cache (umbraco.config) by the wrong document type.

See the attached screenshot of a WinMerge diff. The left file is the broken umbraco.config with the incorrect doctype. The right file is the umbraco.config that was generated after I deleted the broken umbraco.config and republished the entire site.

Note that the node ID matches between each config file (3533). The invalid doctype was CommunityOutreach and the valid doctype was LifestyleCategories. There was a sibling to that node that correctly had the doctype of CommunityOutreach, so maybe during a publish/move/sort/whatever operation there was some code that used that doctype rather than the correct one? For example, I could imagine the sort algorithm getting confused and picking the wrong node to assign the doctype from.

1 Attachments

Comments

Sebastiaan Janssen 14 Aug 2014, 05:26:43

Did you use the "Change documents type" option at all?


Nicholas Westby 14 Aug 2014, 15:06:37

Whoa, I didn't even know that was available in 7.1.4. I certainly didn't, though I suppose somebody else may have done that. If they did (and I don't see why they would), they'd have changed it back because it worked fine after I refreshed the cache. Also, looking at the audit trail, I don't see anything related to changing doctypes (though maybe that shows up as a save or publish operation... not sure).


Sebastiaan Janssen 14 Aug 2014, 15:57:06

:-) Possibly, would be great to check as it can produce the error you're experiencing (see: U4-5301).

If that's not it, then unfortunately it's going to be very hard to track this down without more details, maybe logs, maybe a better understanding of what people were doing in the backoffice exactly when this problem occurred, etc. I certainly haven't heard of this happening before, except from issue U4-5301.


Nicholas Westby 14 Aug 2014, 23:10:39

Not really sure how to check on that. I tried rolling back to each previous version, and the doctype never changed.

However, I then then did a "Change document type" myself just to see what would happen. Showed up in the audit trail as a save event. When I did a rollback it appears the rollback didn't change the doctype back to the previous doctype as I would expect. Seems like two new bugs (well, one is more of a usability issue), even if I can't figure out how to reproduce the primary bug I reported in this issue.

If we can't figure out what the issue is, perhaps we should first work on modifying the audit trail to more accurately show changes of document types? Or maybe some logging (publish events are written to umbracoTraceLog.txt, but nothing about change document type change events).


Shannon Deminick 26 Jun 2017, 05:40:43

Closing issue due to inactivity - see blog post for details https://umbraco.com/blog/issue-tracker-cleanup/


Priority: Major

Type: Bug

State: Closed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 7.1.4

Due in version:

Sprint:

Story Points:

Cycle: