-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Button not showing up #23
Comments
Hi, do you have some jellyfin logs for me after startup of the server? |
Hi, I haven't thought of looking in the logs, but you're right !
I added the write permissions for "others" on index.html, and after restarting the server, I can see the button, thanks ! I'm wondering if there is a proper way to do that ? I'm running Jellyfin in a docker compose environment (based on https://hub.docker.com/r/linuxserver/jellyfin ), but the entire /usr/share/jellyfin directory is under root:root permissions |
Yeah, it is a bit tricky with so many different systems. As far as i know, Jellyscrub had the same problem in the past. |
I use jf installed on debian. The button was not displayed either. After giving write permissions to other users to the file index.html . (after restarting the server) A series selection button has appeared. It may be worth adding this information, that most likely the lack of a button is caused by a lack of access rights and changing them can help. Therefore, the problem now refers to the discussion of the problem, where it is unclear what to do to make the button appear. And after this discussion, it became immediately clear what needs to be done to make the button work. |
Yes, I tried to describe it in the readme. |
Hi,
I installed the latest plugin version (1.2.1.0), on Jellyfin 10.9.7, but the button is not showing up in the player. I tried on Firefox, Chrome, Brave, and tthe Android Jellyfin app, I just can't see it. I rebooted Jellyfin multiples times, even the docker container, but it doesn't work.
Could anyone help ? Thanks !
The text was updated successfully, but these errors were encountered: