starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Enhancement]: ABS cannot scan files which begin with a dot (Documentation) #2175

New Issue
Closed
opened 2026-04-25 00:04:38 +02:00 by adam · 3 comments
adam commented 2026-04-25 00:04:38 +02:00
Owner
Copy Link
Copy Source

Originally created by @ZLoth on GitHub (Aug 12, 2024).

Type of Enhancement

Documentation

Describe the Feature/Enhancement

For the following pages:

It should be noted on Linux hosts, a file or folder that begins with a dot is considered "hidden", and is not scanned in by audiobookshelf.

Why would this be helpful?

Just to understand my configuration... my main computer is a Windows computer, but the server which I use to host ABS is a TrueNAS SCALE (Linux) running ABS as a docker container. The title in question is located at https://www.audible.com/pd/And-Your-Ass-Will-Follow-Audiobook/B0CS1S6HXK , and the title begins with three dots. This file converted normally, but included the three dots at the beginning. However, *nix OS treats the leading period as a hidden file/folder, and ABS is unable to scan the file.

The workaround is simple: Just rename the file so that any leading dots are gone. The ABS database can hold the "true" title.

This is such a corner case that I don't think any code fix would be worth the trouble. I have several thousand audiobooks, and this is the only title with the issue. And the only reason I have it is because it is a free Audible "Plus" title

Future Implementation (Screenshot)

Not applicable.

Audiobookshelf Server Version

2.12.2

Current Implementation (Screenshot)

Not applicable.

Originally created by @ZLoth on GitHub (Aug 12, 2024). ### Type of Enhancement Documentation ### Describe the Feature/Enhancement For the following pages: * https://www.audiobookshelf.org/guides/book-scanner * https://www.audiobookshelf.org/docs#book-title-folder-naming * https://www.audiobookshelf.org/faq It should be noted on Linux hosts, a file or folder that begins with a dot is considered "hidden", and is not scanned in by audiobookshelf. ### Why would this be helpful? Just to understand my configuration... my main computer is a Windows computer, but the server which I use to host ABS is a TrueNAS SCALE (Linux) running ABS as a docker container. The title in question is located at https://www.audible.com/pd/And-Your-Ass-Will-Follow-Audiobook/B0CS1S6HXK , and the title begins with three dots. This file converted normally, but included the three dots at the beginning. However, *nix OS treats the leading period as a hidden file/folder, and ABS is unable to scan the file. The workaround is simple: Just rename the file so that any leading dots are gone. The ABS database can hold the "true" title. This is such a corner case that I don't think any code fix would be worth the trouble. I have several thousand audiobooks, and this is the only title with the issue. And the only reason I have it is because it is a free Audible "Plus" title ### Future Implementation (Screenshot) Not applicable. ### Audiobookshelf Server Version 2.12.2 ### Current Implementation (Screenshot) Not applicable.
adam added the enhancement label 2026-04-25 00:04:38 +02:00
adam closed this issue 2026-04-25 00:04:38 +02:00
adam commented 2026-04-25 00:04:39 +02:00
Author
Owner
Copy Link
Copy Source

@nichwall commented on GitHub (Aug 12, 2024):

I think items which begin with a dot should still be scannable by ABS.

Is this the same as https://github.com/advplyr/audiobookshelf/issues/3230? Not sure if your books didn't show up in the log at all or if you were getting the same error.

@nichwall commented on GitHub (Aug 12, 2024): I think items which begin with a dot should still be scannable by ABS. Is this the same as https://github.com/advplyr/audiobookshelf/issues/3230? Not sure if your books didn't show up in the log at all or if you were getting the same error.
adam commented 2026-04-25 00:04:39 +02:00
Author
Owner
Copy Link
Copy Source

@ZLoth commented on GitHub (Aug 13, 2024):

Looks to be the same. It was something that I had noticed, but when I remembered, the logs no longer existed. :(

@ZLoth commented on GitHub (Aug 13, 2024): Looks to be the same. It was something that I had noticed, but when I remembered, the logs no longer existed. :(
adam commented 2026-04-25 00:04:39 +02:00
Author
Owner
Copy Link
Copy Source

@ZLoth commented on GitHub (Sep 30, 2024):

@advplyr , @nichwall : Does this mean the online documentation won't be updated? That was the jist of this request (it's easy to do) rather than dealing with an extreme corner case that has a easy workaround.

@ZLoth commented on GitHub (Sep 30, 2024): @advplyr , @nichwall : Does this mean the online documentation won't be updated? That was the jist of this request (it's easy to do) rather than dealing with an extreme corner case that has a easy workaround.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2175
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?