mirror of
https://github.com/koel/koel.git
synced 2026-04-25 16:56:02 +03:00
[GH-ISSUE #2098] [Bug]: GET /api/users/{user} route defined by apiResource is unimplemented, causing 500 error #1095
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#1095
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 @WangYihang on GitHub (Sep 12, 2025).
Original GitHub issue: https://github.com/koel/koel/issues/2098
Originally assigned to: @phanan on GitHub.
Read the Troubleshooting guide.
Reproduction steps
indexmethod, which is implemented).This confirms the environment is running and the token is valid for interacting with
UserController.showmethod. Use any user ID, e.g., '1'.Expected behavior
Actual behavior
The server returns a
500 Internal Server Errorpage. The response body contains the fatal error:Logs
Koel version
v7.15.0
How did you install Koel?
Official Docker image
Additional information
@phanan commented on GitHub (Sep 12, 2025):
This is not a bug. The route is simply not defined, because there's no use for it.
@WangYihang commented on GitHub (Sep 12, 2025):
You're right, it's not a functional bug since the endpoint isn't an intended feature.
The issue is a technical one:
Route::apiResourcestill registers the public route, but calling it causes a 500 fatal error instead of a cleaner response like a 404. This can be problematic for API clients and automated tools.A simple fix that perfectly aligns the code with your intent is to explicitly list only the implemented methods:
This removes the problematic route and prevents the 500 error. I can submit a quick PR for this one-line change if you'd like.
Thanks!