I have Umbraco 4.5.2 installed (upgraded from Umbraco 4.5.1) and I cannot sort nodes under certain folders.
The steps to reproduce are
Right click on node, goto sort.
Sort the nodes
Hit Save
I have verified that the posted data is in the correct sort order: e.g. { "ParentId": 1063, "SortOrder": "1132,1131,1305,1311,1134,1135,1136,1137,1138,1140,1141,1142,1308,1309,1310,1317,1318,1319,1320,"}
The response is {"d":null}
When I check UmbracoLog in the database, I am getting the following exception:
umbraco.DataLayer.SqlHelperException: Umbraco Exception (DataLayer): SQL helper exception in ExecuteXmlReader ---> System.ArgumentException: The query didn't return a value.
at umbraco.DataLayer.SqlHelper`1.ExecuteXmlReader(String commandText, P[] parameters)
at umbraco.DataLayer.SqlHelper`1.ExecuteXmlReader(String commandText, IParameter[] parameters)
--- End of inner exception stack trace ---
at umbraco.DataLayer.SqlHelper`1.ExecuteXmlReader(String commandText, IParameter[] parameters)
at umbraco.cms.businesslogic.web.Document.importXml()
at umbraco.cms.businesslogic.web.Document.refreshXmlSortOrder()
at umbraco.presentation.webservices.nodeSorter.UpdateSortOrder(Int32 ParentId, String SortOrder)
I'm experiencing the same issue on v4.5.2 on .Net 4.0 on a site where I have to sort 100+ nodes - actually just sorting some of the last added nodes at the bottom of the list. I have reported the issue on CodePlex.
Sorry for not updating this thread with my findings, but I was able to make a little more headway into my issue.
The issue seems to be when a user needs to unpublish some content in the future and enters a "Remove at" date in the properties tab. After the date has passed, umbraco unpublishes the content, but in doing so, the data seems to get corrupted.
I noticed that the corrupted nodes have a "#" symbol in "Link to document" under the properties tab. If any content node has this invalid link, sorting does not work.
My fix for now is to clear the "Remove at date" save it and then hit the "Unpublish" button. This changes the "Link to document" to read "This item is not published". Once all the nodes have been cleaned, sorting starts working again.
Luckily we only have to do this once a month and do not have a lot of need for sorting so we are able to get by.
Thanks for the feedback. That actually seems to be another issue then, because in my issue I haven't worked with the automatic un-publishing of content. However there are unpublished nodes in the list of nodes that are being sorted, so there may be an issue if the documents to be sorted contains published and unpublished nodes. I'll try to look into that as soon as possible.
Any of you other guys having testet with an All Published list of documents?
@zak - maybe you can append your comments to my CodePlex issue/report?
@everybody else - if you are experiencing the same issue, please vote for it on Codeplex.
That is absolutely super. Will you guys add these comments to the CodePlex issue, so it can be sorted. I'll try publishing all documents in a test-solution tomorrow to verify if it solves my issue too :)
Same here, removing the "Remove at" date allows sorting to work correctly. I see the CodePlex issue is still open. Does that mean it will not be fixed in version 4.6?
FYI - the issue with sorting on content that was removed using the "Remove At" feature appears to be fixed in 4.6.1.
In 4.5.2 the document was never fully unpublished, it was removed from the cache but its Published flag was still set to true, which caused an exception in the sorting functions. I tested in 4.6.1 and it appears to unpublish properly now and sorting seems to be working.
I'm experiencing this same issue in umbraco 4.7.1 - we have over 25k content nodes... any idea how to determine which items may have a "remove at" date? many thanks in advance!
Umbraco content nodes not sorting
Hi all,
I have Umbraco 4.5.2 installed (upgraded from Umbraco 4.5.1) and I cannot sort nodes under certain folders.
The steps to reproduce are
{ "ParentId": 1063, "SortOrder": "1132,1131,1305,1311,1134,1135,1136,1137,1138,1140,1141,1142,1308,1309,1310,1317,1318,1319,1320,"}{"d":null}When I check UmbracoLog in the database, I am getting the following exception:
umbraco.DataLayer.SqlHelperException: Umbraco Exception (DataLayer): SQL helper exception in ExecuteXmlReader ---> System.ArgumentException: The query didn't return a value.
at umbraco.DataLayer.SqlHelper`1.ExecuteXmlReader(String commandText, P[] parameters)
at umbraco.DataLayer.SqlHelper`1.ExecuteXmlReader(String commandText, IParameter[] parameters)
--- End of inner exception stack trace ---
at umbraco.DataLayer.SqlHelper`1.ExecuteXmlReader(String commandText, IParameter[] parameters)
at umbraco.cms.businesslogic.web.Document.importXml()
at umbraco.cms.businesslogic.web.Document.refreshXmlSortOrder()
at umbraco.presentation.webservices.nodeSorter.UpdateSortOrder(Int32 ParentId, String SortOrder)
Any help will be greatly appreciated.
Thank you
-zak
Hi zak,
Did you ever get around to get this error solved?
I'm experiencing the same issue on v4.5.2 on .Net 4.0 on a site where I have to sort 100+ nodes - actually just sorting some of the last added nodes at the bottom of the list. I have reported the issue on CodePlex.
Cheers
Kim
I get the same errors - I voted for it on codeplex.
I ran into this issue as well, some weeks ago, but actually never got it working and forgot all about it.
Voted for the issue on Codeplex as well now.
/Kim A
Hi all,
Sorry for not updating this thread with my findings, but I was able to make a little more headway into my issue.
The issue seems to be when a user needs to unpublish some content in the future and enters a "Remove at" date in the properties tab. After the date has passed, umbraco unpublishes the content, but in doing so, the data seems to get corrupted.
I noticed that the corrupted nodes have a "#" symbol in "Link to document" under the properties tab. If any content node has this invalid link, sorting does not work.
My fix for now is to clear the "Remove at date" save it and then hit the "Unpublish" button. This changes the "Link to document" to read "This item is not published". Once all the nodes have been cleaned, sorting starts working again.
Luckily we only have to do this once a month and do not have a lot of need for sorting so we are able to get by.
-zak
Hi Zak,
Thanks for the feedback. That actually seems to be another issue then, because in my issue I haven't worked with the automatic un-publishing of content. However there are unpublished nodes in the list of nodes that are being sorted, so there may be an issue if the documents to be sorted contains published and unpublished nodes. I'll try to look into that as soon as possible.
Any of you other guys having testet with an All Published list of documents?
@zak - maybe you can append your comments to my CodePlex issue/report?
@everybody else - if you are experiencing the same issue, please vote for it on Codeplex.
Cheers
Kim
This is spot on !
My list contained a document that had been unpublished using the "remove at" method. Publishing the document made it possible to sort again.
So a little bug in the umbraco core here I guess.
Thanks for a quick feedback.
That is absolutely super. Will you guys add these comments to the CodePlex issue, so it can be sorted. I'll try publishing all documents in a test-solution tomorrow to verify if it solves my issue too :)
Thanks a lot in advance :)
Cheers
Kim
Hi guys,
After a test republishing all the content that I tried to sort, this actually also solved my issue. Thanks to zak for figuring out the problem.
Cheers Kim
Holy moly Zak! That actually works for me too.
Nice detective work :)
/Kim A
Same here, removing the "Remove at" date allows sorting to work correctly. I see the CodePlex issue is still open. Does that mean it will not be fixed in version 4.6?
Hi,
FYI - the issue with sorting on content that was removed using the "Remove At" feature appears to be fixed in 4.6.1.
In 4.5.2 the document was never fully unpublished, it was removed from the cache but its Published flag was still set to true, which caused an exception in the sorting functions. I tested in 4.6.1 and it appears to unpublish properly now and sorting seems to be working.
-Tom
I'm experiencing this same issue in umbraco 4.7.1 - we have over 25k content nodes... any idea how to determine which items may have a "remove at" date? many thanks in advance!
is working on a reply...