mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #1983] [Bug]: Visiting Favorites playlist page bugging out songs and Home plays after release upgrades #1048
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#1048
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 @Jacob-Noah on GitHub (Jul 1, 2025).
Original GitHub issue: https://github.com/koel/koel/issues/1983
Originally assigned to: @phanan on GitHub.
Read the Troubleshooting guide.
Reproduction steps
Expected behavior
I expect likes and page changes to function as intended. Changing pages should not permanently affect the client state of all songs.
Actual behavior
The bug(s) described in reproduction steps. I will capture a gif:
It is not shown in the gif, but after returning out of the Favorites page, if examining any known-liked song, it will be shown as not yet liked/favorited.
Logs
No logs were produced by this bug in Laravel or the browser client. I will attach the last logs produced anyway even though they are unrelated.
Koel version
7.7.1
How did you install Koel?
Official Docker image
Additional information
@phanan commented on GitHub (Jul 1, 2025):
Oh true what the heck haha. Thanks for reporting this bug, I'll take a look!
@phanan commented on GitHub (Jul 1, 2025):
Fixed and will be in the next release ;)