New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sorting by Published column in a Listview does not order the items correctly #13301
Comments
I can take a look at this later today |
Oke, this is a lot more work than I had thought.
and then returns the ordering in the last column. A 1 if it is published or a 0 if it isn't. However, it currently shows a 1 if it was ever published and a 0 if it has never been published. And since then I've been lost. The results of the query shows version ids that aren't even the current one, but still thinks that it is published. I think the whole query needs to have some rework here. |
Fixed in #13474, thanks again for the detailed description 😄 |
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
10.3.1, 9.5.4, 8.18, 8.12
Bug summary
If you use a Listview and unpublish content, or publish content that was previously unpublished, the Listview will be unable to sort the content by the "Is Published" Column. Instead of ordering the content by published or unpublished, it will sort the content items by their previous publish status.
Specifics
No response
Steps to reproduce
Steps to reproduce:
At this point you should be able to sort the content by the Is Published column with no issue:
Expected result / actual result
When you try to sort the content in the Listview based on the "Is Published" column, you would expect the published content to be grouped together and for unpublished content to be grouped together such as this:
However, when you try to sort by this column after the steps above, it seems that the content is still sorted by its previous publish status which leaves the content sorted randomly:
This item has been added to our backlog AB#24049
The text was updated successfully, but these errors were encountered: