New Collection Bug

[sbourdon]

Hello,

If a user with no right to manage collections tries to create a new one, an endless spinning wheel will stay on screen after hitting «OK».

To reproduce, access any «Movie» library (using an account with no right to manage collections), hit «Collections» at the top, click on the «+» sign (New Collection), fill in the form and hit «OK».
A spinning wheel will appear and stay on-screen until you move to another page.

I guess the best thing to do would be to hide the «+» sign on the «Collections» page for users without appropriate rights.  

Found using the portable version of Jellyfin 10.10.5 under Windows, accessed with Edge.


Thank you for your time and support!

[TheDreadPirate]

How have you configured this user to prevent them from managing collections?

Also, if you've recently made changes to the user's server access you will need to clear that user's browser cache. It is possibly caching the old UI elements that user no longer has access to. So they still have the prompt, but don't actually have permission. Refresh the browser cache and that user should no longer have "add to collection" as an option.

[sbourdon]

Hello,

Thank you for your reply.
Unfortunately, I've tested that user's account on another browser (never used to access Jellyfin before) and the «Add to collection» option was still available.
Isn't that the case on your side?

SyncPlay is also deactivated for that user and, as expected, that option is masked.
It ain't the same for collection management, though...

Thank you for your time!

[TheDreadPirate]

Can you replicate the issue then share your full jellyfin log via privatebin.net?

[TheDreadPirate]

Is this user allowed to manage the server?

And can you provide screenshots of the user's configuration screens?

[theguymadmax]

Yeah, I see what you're saying and can easily replicate it. This seems to be an issue with the web UI, so I’d recommend raising it on the Jellyfin-web repository. Unfortunately, there's not much we can do to troubleshoot, as it's related to the UI design, and the fix would need to be made on the repo itself.