[Bug]: Expanding a subseries does not consider the subseries' order when displaying #900

New issue

Open

opened 2025-10-14 17:53:57 -06:00 by navan · 0 comments

navan commented

2025-10-14 17:53:57 -06:00

Owner

Originally created by @kknutsondesign on 12/13/2024

What happened?

For series that are settings and have multiple stories in them with no inherent order giving them a series number for the setting doesn't make much sense. The problem is that when viewing the parent series all the subseries' orders are disregarded.

What did you expect to happen?

Books with no series number could be shown after the ones that do and the remainder could be sorted by their subseries+series number to differentiate them.

Displaying the first letter of the subseries followed by the subseries number could make them distinct from the parent series they belong to.

Or a tag displaying the series name under the books like on the Skeumophic view or a box around the expanded series for normal view would separate them nicely.

When displaying books if no series number is found you could assign it a temp "series number" as a UID followed by the subseries number so the normal sorting handles grouping the books together (eg 1,2,3,4 of the subseries becomes 1234.1, 1234.2, 1234.3, 1234.4)

Steps to reproduce the issue

Have a book that is part of a subseries but with no series number for the parent series
View the parent series and enable expand subseries

Audiobookshelf version

2.17.5

How are you running audiobookshelf?

Windows Tray App

What OS is your Audiobookshelf server hosted from?

Windows

If the issue is being seen in the UI, what browsers are you seeing the problem on?

Firefox

Logs

No response

Additional Notes

No response

*Originally created by @kknutsondesign on 12/13/2024* ### What happened? For series that are settings and have multiple stories in them with no inherent order giving them a series number for the setting doesn't make much sense. The problem is that when viewing the parent series all the subseries' orders are disregarded. ![image](https://github.com/user-attachments/assets/d5f3108d-c674-4fcd-9a47-d6507dd90c2b) ![image](https://github.com/user-attachments/assets/0a0d1503-5322-4a11-9486-e0916f1672d0) ![image](https://github.com/user-attachments/assets/da38d85e-653e-45e2-83a9-ca1d59b99d58) ![image](https://github.com/user-attachments/assets/b81f1ba7-b1de-4884-be2e-d4cd37f4d80b) ![image](https://github.com/user-attachments/assets/cd67edf2-08ec-4753-bbdd-16c3e7e02725) ### What did you expect to happen? Books with no series number could be shown after the ones that do and the remainder could be sorted by their subseries+series number to differentiate them. ![subseries 1](https://github.com/user-attachments/assets/9609f64b-95bc-4c0b-ac97-330522c6a271) Displaying the first letter of the subseries followed by the subseries number could make them distinct from the parent series they belong to. ![subseries 3](https://github.com/user-attachments/assets/cde52b96-29c4-444b-98c7-0c1d2bca379e) Or a tag displaying the series name under the books like on the Skeumophic view or a box around the expanded series for normal view would separate them nicely. ![subseries 2](https://github.com/user-attachments/assets/f187c076-d643-497a-a919-9f8c5124c70f) When displaying books if no series number is found you could assign it a temp "series number" as a UID followed by the subseries number so the normal sorting handles grouping the books together (eg 1,2,3,4 of the subseries becomes 1234.1, 1234.2, 1234.3, 1234.4) ### Steps to reproduce the issue 1. Have a book that is part of a subseries but with no series number for the parent series ![image](https://github.com/user-attachments/assets/d5f3108d-c674-4fcd-9a47-d6507dd90c2b) 2. View the parent series and enable expand subseries ### Audiobookshelf version 2.17.5 ### How are you running audiobookshelf? Windows Tray App ### What OS is your Audiobookshelf server hosted from? Windows ### If the issue is being seen in the UI, what browsers are you seeing the problem on? Firefox ### Logs _No response_ ### Additional Notes _No response_