mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: cosmetic bug #560
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf#560
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @skyzuma on GitHub (Jul 31, 2022).
Describe the issue
if i upload books with "vol XX" and open the editor window > match > search > the series tag shows as "#X" instead of (my) "#XX" ... its possible to detect what sequence the folder have? So "Vol 1" can detect as series "#X" and "Vol 01" can detect as series "#XX" ... i cant use quick match, cause of all my files will moved with "#X" to other location instead of "#XX" and if u use the normal match, i need to deselect or edit the series sequence ...
Steps to reproduce the issue
upload an folder with Vol XX instead of Vol X
Audiobookshelf version
2.1.1
How are you running audiobookshelf?
Docker
@advplyr commented on GitHub (Jul 31, 2022):
There was a request to remove the leading 0 https://github.com/advplyr/audiobookshelf/issues/562
I don't really understand the issue you are having with quick match. Quick match shouldn't have anything to do with the series volume number.
@skyzuma commented on GitHub (Jul 31, 2022):
but with manual matching ... maybe this can be solved with an option in the setting ....
@advplyr commented on GitHub (Jul 31, 2022):
I still don't know what you mean, manual matching? I'm trying to understand what the problem is with not having a leading 0.
@skyzuma commented on GitHub (Jul 31, 2022):
like this
and it is ONLY a cosmetic bug like i sayd
@advplyr commented on GitHub (Jul 31, 2022):
Did you update that so it shows as "Book 3" for the volume number? That doesn't seem right if the match result returned with that volume number.
The volume number returned from the match is exactly how it is stored in audible. I don't think modifying the results from audible will be a good idea. Some users may want it to update to match audible instead of the volume number they have with leading zeros.
@skyzuma commented on GitHub (Jul 31, 2022):
thats why i suggested with an option in the settings and i think its the best options for all ... i know many ppl to use this like me :)
@advplyr commented on GitHub (Aug 20, 2022):
This is not going to be implemented at this time, perhaps sometime in the distant future we add a setting for volume number format but this runs into issues when not dealing with numbers.