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]: RSS-feed for podcasts does not include Subtitle-field #2776

New Issue
Open
opened 2026-04-25 00:10:32 +02:00 by adam · 0 comments
adam commented 2026-04-25 00:10:32 +02:00
Owner
Copy Link
Copy Source

Originally created by @satosti on GitHub (May 17, 2025).

What happened?

If the user opens an RSS-Feed in Audiobookshelf (podcast page → three-dot menu → "Open RSS Feed"), the feed is missing the metadata stored in the Subtitle-field of each episode in ABS. This would usually be stored in an <itunes:subtitle> or <itunes:summary> element. Currently it is stuck in ABS and not shared over the created feed.

What did you expect to happen?

I expected the opened RSS-feed to include all metadata stored in ABS for each episode, including the Subtitle-field.

Steps to reproduce the issue

  1. open the page of any stored podcast in Audiobookshelf
  2. confirm that the podcast's episodes have text stored in their Subtitle-field in ABS
  3. open the three-dot menu of the podcast and click "Open RSS Feed" → "Open Feed"
  4. open the created feed's link in your browser
  5. search for the contents of the Subtitle-field of any episode

Audiobookshelf version

v2.22.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

Not sure if this is considered a bug, but it means that the (potentially edited) metadata stored in the Subtitle-field of each episode is currently stuck in ABS and can't be exported/shared by opening an RSS-feed.

Originally created by @satosti on GitHub (May 17, 2025). ### What happened? If the user opens an RSS-Feed in Audiobookshelf (podcast page → three-dot menu → "Open RSS Feed"), the feed is missing the metadata stored in the Subtitle-field of each episode in ABS. This would usually be stored in an `<itunes:subtitle>` or `<itunes:summary>` element. Currently it is stuck in ABS and not shared over the created feed. ### What did you expect to happen? I expected the opened RSS-feed to include all metadata stored in ABS for each episode, including the Subtitle-field. ### Steps to reproduce the issue 1. open the page of any stored podcast in Audiobookshelf 2. confirm that the podcast's episodes have text stored in their Subtitle-field in ABS 3. open the three-dot menu of the podcast and click "Open RSS Feed" → "Open Feed" 4. open the created feed's link in your browser 5. search for the contents of the Subtitle-field of any episode ### Audiobookshelf version v2.22.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 ```shell ``` ### Additional Notes Not sure if this is considered a bug, but it means that the (potentially edited) metadata stored in the Subtitle-field of each episode is currently stuck in ABS and can't be exported/shared by opening an RSS-feed.
adam added the bug label 2026-04-25 00:10:32 +02:00
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#2776
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?