Bit of a strange one but after sorting a node a node representing a content page has vanished in our site.
It remained visible on the front-end and via backoffice search until the cache and indexes were rebuilt.
We tried to recreate it but the old node still exists in the database causing a name clash and appending the new node with a (1).
Has anyone encountered this before? Ideally any suggestions to restore the previous node would be preferred. I've tried changing the sort order in the database but that's not made any difference, the path, parentId, level and trashed values are all the same (excluding the ID at the end of the path) in the umbracoNode table so the problem must lie elsewhere.
I'm trying to reproduce the behavior if I can I'll raise a bug.
Looks like all the versions of this node in the CMS document table got marked as Latest > False - a new version had been created as User 0 but again Latest false.
I've set this to true and it seems to be OK now - hopefully I won't cause any
side effects.
Node missing following sort (7.5.11 in Azure)
Hi all,
Bit of a strange one but after sorting a node a node representing a content page has vanished in our site.
It remained visible on the front-end and via backoffice search until the cache and indexes were rebuilt.
We tried to recreate it but the old node still exists in the database causing a name clash and appending the new node with a (1).
Has anyone encountered this before? Ideally any suggestions to restore the previous node would be preferred. I've tried changing the sort order in the database but that's not made any difference, the path, parentId, level and trashed values are all the same (excluding the ID at the end of the path) in the umbracoNode table so the problem must lie elsewhere.
I'm trying to reproduce the behavior if I can I'll raise a bug.
Hi all,
Looks like all the versions of this node in the CMS document table got marked as Latest > False - a new version had been created as User 0 but again Latest false.
I've set this to true and it seems to be OK now - hopefully I won't cause any side effects.
I'll raise a bug for it.
is working on a reply...