-
Notifications
You must be signed in to change notification settings - Fork 20
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
Request tab no reappear #41
Comments
+1 for this, I'm no longer able to login to my jellyseer inside the requests tab after setting it up. @ToMattBan any idea on this ? |
Good catch @MultiMadjik. I'm going to take a look at that. Never really had noticed it before. About being unable to login, @sureshfizzy I tried some things here and it seems related to "max number of devices" setting. |
Still not able to do that.. i checked on web and i get this, Am i missing something ? myjellyseerip:port/api/v1/auth/me:1 Failed to load resource: the server responded with a status of 401 () FYI: Jellyseer is working when i connect to it directly |
401 is an error code about unauthorized access. |
surprisingly I couldn't find /api/v1/auth/jellyfin so i believe there are no errors on it. and regarding the 401, i'm able to login to my jellyseer from web though, it's just I can't login from the requests tab inside my jellyfin. |
Same here @ToMattBan. After entering a library, it doesn't reappear, and after pressing home as well. |
@sureshfizzy can you open another issue about the login stuff? Let's keep this one about the tab not reappearing. As soon as I got some (prob later today or tomorrow) time I will take a look on the issues. |
@ToMattBan thanks for agreeing to take a look. Also, wanted to get this to your attention, this doesn't play well with the featured content bar, and also, doesn't seem to render well on a mobile device as well. Edit: Managed to sort it and got the slideshow only on the home tab, and removed it from appearing in the request tab, but still there is the issue of the entire tab vanishing on navigating anywhere+rendering+even I cannot login now to jellyseer 🫣. |
Sure, thanks :) |
Also @ToMattBan I had to set the width and height to vw and vh values as somehow the calc is messing the entire thing up (on desktop and phone both) |
@MakD Which browser/client are you using? About the tab vanishing, @MultiMadjik @sureshfizzy I found why it was happening. I edited the instructions, can you test it please? You can see the edited instructions here: It fixed for me, hope it fixes for you too |
@ToMattBan official android client. I changed the width calc to harcoded 98vw and that works for now. The only issue will be getting the reversed proxied url to open, which I have searched heaven and hell but couldn't get my hands around. Tried different caddy variation ls as well ( I'm not that client with caddy setup, so🤷). Only thing I came across is it needs a modded setup of jellyfin-web I guess. Even though I posted a query in the jellyseerr discord let's see if they address that. |
@ToMattBan Typo in the index.html code bit |
Thanks @MakD |
@ToMattBan it's still disappearing for me. So one part is solved. When I am in any library and press home, the button is there, but if I just press back, it doesn't render |
Gonna look at that @MakD |
@ToMattBan please test this I guess solved it
Edit: ARRRRGH... So
|
hahaha yeah @MakD Every way to come back to home have it's own behaviour, and this is making me crazy hahahaha. When I get some more time, I will come back to this nightmare hahahaha |
Thanks @MakD and @ToMattBan for your job, it resolve a part of the problem for me :) Hoever, the new CSS script are fixed also, I haven't screen problem anymore. |
Is it working on 10.10.3? It has created the tab, but shows nothing. Nevermind. I had not put http://. |
Hello 🙂
First, congratulations to this awesome job!
Last day, I put the request tab button and it's works
Sadly, the tab as no longer work when I switch to a library or another's in the website
I do refresh the page to see again the request tab
Can you have any ideas?
Thanks for advance!
The text was updated successfully, but these errors were encountered: