mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-03-02 22:46:56 -05:00
[Bug]: Custom metadata changes for all podcast episodes reset #3200
Labels
No labels
authentication
awaiting release
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/audiobookshelf#3200
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @D3r3k23 on GitHub (Sep 29, 2025).
What happened?
All custom metadata edits to a podcast get reset to the default from the RSS feed. I have noticed this happen before when I manually copy a file to the podcast directory. But this time, it happened when I manually downloaded an episode from the RSS feed.
The log is attached, and this is what I was doing when it happened:
The RSS feed downloaded a duplicate episode (The J. Burden Show Ep. 346 - AgNONsis) so I deleted both copies, then downloaded the episode manually from the RSS feed. Then after it downloaded, all the custom metadata edits to previous episodes were gone.
abs-log.json
What did you expect to happen?
Save metadata edits
Steps to reproduce the issue
Audiobookshelf version
v2.29.0
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
Unraid OS
@advplyr commented on GitHub (Oct 8, 2025):
Can you clarify what you mean by "custom metadata"? Are you referring to the RSS feed specifically or the changes were also reverted in the Abs web client?
All of that data is stored in the sqlite db
podcastEpisodestable. We don't have anything that would automatically apply a backup or revert a bunch of changes in the db.