Sorting in library view does not lead to sorted results

[dakush]

What went wrong?

When I set sort criteria to "Author" or "Author(Surname)", the view is not sorted accordingly (both grid and list views). I'm attaching an screenshot with a section of the list.

How can we reproduce it?

1. Select a library
2. In "Sort order" select "Author" or "Author(Surname)"
3. The view doesn't sort the books alphabetically by author's names or surnames

What Build of Grimmory are you on?

Stable

Your setup

Server side: Grimmory v3.0.0 running on Docker
Client side: Tried on Chromium (desktop Arch linux) and Chrome (Android)

Screenshots or error messages (optional)

Before submitting

• I've searched existing discussions and this hasn't been reported yet
• I've reviewed this report and have completed it as fully as I can

[QueenOfRavens]

I'm also having this issue. Here's a screenshot of the top of my full book catalogue

[afairgiant]

I'm also having an issue, the sort by series number has them in a random order.

[imnotjames]

I'm also having an issue, the sort by series number has them in a random order.

I cannot replicate this. Can you give more information? I have multiple items in multiple series & they all seem to sort by number correctly.

[aecreekmore]

I am having this issue as well. I have multiple magic shelves sorted by random, but instead they are sorting by author. Also my default sort (series name, series number, title) is sorting in what seems to be a random order.

[obviouslyallie]

Created issue #797

[ListerD000169]

Having a similar issue with Series Name/Series Number sorting. That's my default sort and the series numbers are not sorting properly on the All Books page or when filtered by a specific series on the side bar. Screenshot showing an example filtered on Discworld. You can see the numbers are all over the place. This happens with every series I've tried (probably around a dozen a looked at). For me, it does seem to be the combination of Series Name with a sub sort of Series Number.

[imnotjames]

This is fixed in nightly and will be in the next release.

[imnotjames]

This is fixed in 3.1.0