Make that "Not Working"... Two different machines having this issue.
Medusa Info: | Branch: master Commit: 212cd1c8a350f2d5ca40f172ed5a227d9a5cb80f Version: 0.2.4 Database: 44.9
Python Version: | 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:53:40) [MSC v.1500 64 bit (AMD64)]
SSL Version: | OpenSSL 1.0.2j 26 Sep 2016
OS: | Windows-7-6.1.7601-SP1
Locale: | en_GB.cp1252
*What you did: Click on "ADD SHOW Or add existing shows
*What happened: Nothing!
*What you expected: Expected to add shows
*Logs: Debug enabled - No Errors Shown
```
What browser are you using? Try refreshing with Ctrl + F5
Just noticed the problem yesterday, by the way. Using Firefox ESR 52.5.3 (32-bit). Flushing browser cache not doing it. Two independent machines, same issue... Even reinstalled and configured fresh from windows executable.
Addendum--- Web pages not even rendering in IE 11.
@DrakeJones
Edit: My comment applies to the addendum as well.
Just use latest versions of chrome, ff or edge. Problem solved
Tail wags dog? I really appreciate what you’ve done with the project, but I like my current bowser and Medusa worked fine until a few days ago. Firefox ESR branch is supported by MIT ( Massachusetts Institute of Technology), is current, secure, and up-to-date. If it’s good enough for them, it’s good enough for me. I hate to do it, but I’ll think put Sickrage back in my line-up.
From: p0ps [mailto:[email protected]]
Sent: Monday, May 21, 2018 3:51 PM
To: pymedusa/Medusa
Cc: DrakeJones; Mention
Subject: Re: [pymedusa/Medusa] Add Shows Button No Working (#4229)
Just use latest versions of chrome, ff or edge. Problem solved
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/pymedusa/Medusa/issues/4229#issuecomment-390659472 , or mute the thread https://github.com/notifications/unsubscribe-auth/AF-CmNGTodO8TBJ5nWDLoIKQ5OJSlOaOks5t0sZBgaJpZM4UG4zV .https://github.com/notifications/beacon/AF-CmHV2Gb_iUD3bux6PJclQQpkZ_hQyks5t0sZBgaJpZM4UG4zV.gif
I was afraid you’d tell me to try a different browser… Can I just stick with the Medusa version that worked?
Here is the dev console image of the issue/error: https://imgur.com/a/3CCFLUE
I like my browser and plan to stick with it. The version of FF that I’m using is the long-term support version supported by MIT – not Mozilla. It is secure and up-to-date.
From: sharkykh [mailto:[email protected]]
Sent: Monday, May 21, 2018 2:34 PM
To: pymedusa/Medusa
Cc: DrakeJones; Mention
Subject: Re: [pymedusa/Medusa] Add Shows Button No Working (#4229)
@DrakeJones https://github.com/DrakeJones
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/pymedusa/Medusa/issues/4229#issuecomment-390641196 , or mute the thread https://github.com/notifications/unsubscribe-auth/AF-CmFxcAGAKA-qwHc5lh9HZ7HRz4KC_ks5t0rRPgaJpZM4UG4zV .https://github.com/notifications/beacon/AF-CmGpkhy2S3LVnE-BY2WCSBwjaOPz9ks5t0rRPgaJpZM4UG4zV.gif
@OmgImAlexis Seems to me like an issue with Frisbee or its dependencies, as I'm getting SyntaxError: invalid property id frisbee.min.js:1:14252 on page load.
You posted the error as screenshot. But its not readable
@p0psicles It is on desktop... here you go:

The version of FF that I’m using is the long-term support version supported by MIT – not Mozilla. It is secure and up-to-date.
@DrakeJones It's not truly up-to-date. You're using version 52.5.3, while 52.8.0 is the latest.
Edit: While it's a good thing to always update to the latest versions with browser, this didn't fix the issue. I'm trying to see what can be done.
Thank you very, very much for revisiting the issue.
Maybe related - trying editing preexisting shows via http://localhost:8081/home/editShow?indexername=tvdb&seriesid=XXXXX seems to be defaulting to global settings, not show-specific settings... I hope the frisbee update does it. This is really bumming me out.
@DrakeJones
Frisbee update won't affect editShow.
Can you check the dev console on that page too? (Already uninstalled FF...)
@DrakeJones
addShow: Should now be fixed for you in develop (or you can wait for the next version).editShow: I wasn't able to reproduce the issue.