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

[Bug]: Matched Covers lost #1786

New Issue
Closed
opened 2026-04-24 23:58:16 +02:00 by adam · 2 comments
adam commented 2026-04-24 23:58:16 +02:00
Owner
Copy Link
Copy Source

Originally created by @BumbleCast on GitHub (Mar 3, 2024).

Describe the issue

After upgrading to v.2.8 (deployed via docker), some of my Podcasts do not keep the covers after matching them.
The podcast is correctly identified and I save these changes (save & close). But as soon as a new episode is added, the Cover and all the other information is lost again. It before migrating to 2.8 (your maybe before migrating to the new DB structure).

I tried removing the podcast, and re-adding everything. It did not work.

2024-03-03 10_11_31-Audiobookshelf - Chromium
2024-03-03 10_11_47-Audiobookshelf - Chromium
2024-03-03 10_10_31-Audiobookshelf - Chromium

Steps to reproduce the issue

  1. Add podcast (I download them using a different program)
  2. Match podcast info to get Cover and other meta data
  3. Loose cover and data after adding an additional episode
  4. Rinse and repeat

Audiobookshelf version

2.8

How are you running audiobookshelf?

Docker

Originally created by @BumbleCast on GitHub (Mar 3, 2024). ### Describe the issue After upgrading to v.2.8 (deployed via docker), some of my Podcasts do not keep the covers after matching them. The podcast is correctly identified and I save these changes (save & close). But as soon as a new episode is added, the Cover and all the other information is lost again. It before migrating to 2.8 (your maybe before migrating to the new DB structure). I tried removing the podcast, and re-adding everything. It did not work. ![2024-03-03 10_11_31-Audiobookshelf - Chromium](https://github.com/advplyr/audiobookshelf/assets/112068435/df3f2e09-20e0-43c8-90d5-ce84483b0057) ![2024-03-03 10_11_47-Audiobookshelf - Chromium](https://github.com/advplyr/audiobookshelf/assets/112068435/06d1a69f-aa31-4c91-b365-d5664eb58aa0) ![2024-03-03 10_10_31-Audiobookshelf - Chromium](https://github.com/advplyr/audiobookshelf/assets/112068435/084e5d46-bcb3-4774-9ae8-ff9c70bb8f3f) ### Steps to reproduce the issue 1. Add podcast (I download them using a different program) 2. Match podcast info to get Cover and other meta data 3. Loose cover and data after adding an additional episode 4. Rinse and repeat ### Audiobookshelf version 2.8 ### How are you running audiobookshelf? Docker
adam added the bug label 2026-04-24 23:58:16 +02:00
adam closed this issue 2026-04-24 23:58:16 +02:00
adam commented 2026-04-24 23:58:17 +02:00
Author
Owner
Copy Link
Copy Source

@advplyr commented on GitHub (Mar 3, 2024):

Can you check the server logs to see if you are getting permission errors?

Assuming you don't have the server setting enabled "Store covers with item" the covers will be stored in your /metadata/items/<item id> folder. You can find the id of the podcast library item in the URL when you navigate to the podcast page.
One test you can do is find that folder and note that the cover is there, then add a new episode and see what happens to the cover. You can also watch the server logs when you do that and look for errors.

@advplyr commented on GitHub (Mar 3, 2024): Can you check the server logs to see if you are getting permission errors? Assuming you don't have the server setting enabled "Store covers with item" the covers will be stored in your `/metadata/items/<item id>` folder. You can find the id of the podcast library item in the URL when you navigate to the podcast page. One test you can do is find that folder and note that the cover is there, then add a new episode and see what happens to the cover. You can also watch the server logs when you do that and look for errors.
adam commented 2026-04-24 23:58:17 +02:00
Author
Owner
Copy Link
Copy Source

@BumbleCast commented on GitHub (Mar 5, 2024):

Can you check the server logs to see if you are getting permission errors?

Assuming you don't have the server setting enabled "Store covers with item" the covers will be stored in your /metadata/items/<item id> folder. You can find the id of the podcast library item in the URL when you navigate to the podcast page. One test you can do is find that folder and note that the cover is there, then add a new episode and see what happens to the cover. You can also watch the server logs when you do that and look for errors.

Thanks for the quick reply. I was indeed a permission error. I changed the permission before adding the new podcast episode and it works flawless now. Thanks!

@BumbleCast commented on GitHub (Mar 5, 2024): > Can you check the server logs to see if you are getting permission errors? > > Assuming you don't have the server setting enabled "Store covers with item" the covers will be stored in your `/metadata/items/<item id>` folder. You can find the id of the podcast library item in the URL when you navigate to the podcast page. One test you can do is find that folder and note that the cover is there, then add a new episode and see what happens to the cover. You can also watch the server logs when you do that and look for errors. Thanks for the quick reply. I was indeed a permission error. I changed the permission before adding the new podcast episode and it works flawless now. Thanks!
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 bug
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#1786
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?