Scheduled Tasks section not working since last JF updates

[raulo1985]

Hi:

Has anyone had this issue? It started happening since the last couple of jellyfin-web updates, and afaik, it only affects the scheduled tasks page. The play button to execute them works as expected, but when I try to set up any of them, it looks like the second screenshot. The "Task triggers" text appears above the previous page, and nothing happens when I press the + button.

It's not just a cosmetic or graphic glitch in my case, since nothing happens when pressing the + button I can no longer configure any scheduled task (and there are some that are enabled by default that I usually disable).

Any clue about the possible cause and how to solve it? Like previously said, apparently it only happens with the scheduled tasks section, I haven't found the same issue affecting other ones. And my setup is as standard as it can get, and no changes have been made besides updating Jellyfin.

Thanks in advance!

PS: I'm guessing it's a jellyfin-web issue, since it happens with all my clients (iOS, JMP, WebOS). And I already tried reinstalling the entire server from scratch and the issue persists.

[TheDreadPirate]

Your theme or custom CSS needs to be adjusted. All the clients you mentioned use jellyfin-web and apply the same CSS to their UIs.

[raulo1985]

Your theme or custom CSS needs to be adjusted.  All the clients you mentioned use jellyfin-web and apply the same CSS to their UIs.

But I've been using the same css setup for quite some time (no recent changes), and this started happening some days ago after a jellyfin-web update.

Do you know what should I look into my css? I don't know what could cause this behavior.

Thanks again

[theguymadmax]

Check this thread for responses to a similar question from two of the devs.

[raulo1985]

Your theme or custom CSS needs to be adjusted.  All the clients you mentioned use jellyfin-web and apply the same CSS to their UIs.

Hi. Apparently it isn't a css issue. I disabled my custom css and left it blank, and the issue persists. In other words, with or without css, the behavior doesn't change. Any idea about what could be causing this?

Check this thread for responses to a similar question from two of the devs.

Thanks for your reply, but as you can read in my reply to TheDreadPirate, it doesn't seem to be a css issue that's breaking jellyfin-web after the update. I reinstalled everything from scratch again (including the SO), this time without custom css and with all settings left at default, and it's still happening.

In my case it's an issue because I have the scheduled library scan disabled because it always creates some movie collections that I don't want there as collections. Since I can't disable it now, I have to delete those collections manually every day. Not ideal, but everything else works great.

FYI, I'm building jellyfin-web from source (master branch and following the instructions). I never had a problem before, and I've been doing that for some time. It just started happening since I would say a week or two, and still happens (last reinstall was made yesterday).

Thanks again.

[TheDreadPirate]

Why are you building from master? It is unstable and not meant for production use.

[theguymadmax]

FYI, I'm building jellyfin-web from source (master branch and following the instructions). I never had a problem before, and I've been doing that for some time. It just started happening since I would say a week or two, and still happens (last reinstall was made yesterday).

Well way to bury the lead. That said, I can replicate the issue and noticed that the scheduledtask.js file was updated last week. You should submit a bug report on the web repo. Just be sure to mention that you're using the master branch."

[raulo1985]

Why are you building from master?  It is unstable and not meant for production use.

Thanks for your reply. I know that master branch is not intended for production use, my main reason for building from it is if some day after an update the local intros plugin works again for me. I don't even know if jellyfin-web interacts in some way with the plugin, so I don't know if any change made to jellyfin-web source could have an impact on that regard, but I don't know what else to do. I created a thread about it and received some replies, but I was told it was a client issue but no advice on how to solve it. Another user said that he had issues with the plugin too, but apparently the thread is kind of dead now, and I ran out of ideas. I really want to use that plugin again, but haven't been able to make it work since 10.9. All I can do is to keep updating jellyfin-web and server to see if some day it gets fixed (I don't even know if it's a bug, I posted the logs but I don't understand why it's behaving like that). Going back to 10.8.13 is the only solution I've found, but I prefer to keep the server updated. Maybe it's a dumb reason to build from master branch, but since I ran out of ideas and apparently other users don't know how to help me with that, it's better than to try nothing 

FYI, I'm building jellyfin-web from source (master branch and following the instructions). I never had a problem before, and I've been doing that for some time. It just started happening since I would say a week or two, and still happens (last reinstall was made yesterday).

Well way to bury the lead. That said, I can replicate the issue and noticed that the scheduledtask.js file was updated last week. You should submit a bug report on the web repo. Just be sure to mention that you're using the master branch."

Sorry, I was sure I posted that info at my first post, indeed is crucial information. I re read it and realized I didn't mention it, my bad.

I'll try to report it as a bug. Recently a close relative of mine was diagnosed with cancer, so I currently don't have much spare time because of that (that's why it took me some days to reply. Sorry about that).

Thanks again