I have an issue where an item is being duplicated in my content tree:
Selecting either version of the node shows it to have the same id.
What could be causing this?
I have cleared my browser cache, so that's not an issue, I even ran the api call directly: ../umbraco/backoffice/UmbracoTrees/ContentTree/GetNodes?id=1287&application=cont and that contains the duplicate, so not a local caching issue.
I have had a look in the umbracoNode table, the node only appears once.
I have had a look in the cmsContent table, the node only appears once.
I have also had a look in the cmsDocument table where it show there to be 2 published versions of the node, though only 1 shows as being newest. One version of the node in this table shows with a different documentUser, I assume this has something to do with the issue?
How do I go about fixing this, assuming anyone knows? Trying hard to avoid breaking anything on the first day back after new year :-)
Well, in the end I update the cmsDocument table to have only the latest version of the node as published. This appears to have fixed the issue for me now. Hopefully this will help someone else.
Duplicate content item in content tree
Guys,
I have an issue where an item is being duplicated in my content tree:
Selecting either version of the node shows it to have the same id.
What could be causing this?
I have cleared my browser cache, so that's not an issue, I even ran the api call directly: ../umbraco/backoffice/UmbracoTrees/ContentTree/GetNodes?id=1287&application=cont and that contains the duplicate, so not a local caching issue.
I have had a look in the umbracoNode table, the node only appears once. I have had a look in the cmsContent table, the node only appears once.
I have also had a look in the cmsDocument table where it show there to be 2 published versions of the node, though only 1 shows as being newest. One version of the node in this table shows with a different documentUser, I assume this has something to do with the issue?
How do I go about fixing this, assuming anyone knows? Trying hard to avoid breaking anything on the first day back after new year :-)
Thanks in advance..
Mark
Well, in the end I update the cmsDocument table to have only the latest version of the node as published. This appears to have fixed the issue for me now. Hopefully this will help someone else.
is working on a reply...