(2015-08-19 19:31)lazyboy0172 Wrote: aha. We (well, you) may be on to something. Here's the pastebin: http://pastebin.com/dCkcZF3r
i especially found this interesting:
13:21:04 T:3408 NOTICE: Add Show Set Future Status:
it never asked what I wanted for that (it asked past shows, as does the sickbeard web interface when adding shows), though I'd imagine 'wanted' would be default if I'm adding a new show.
also 13:21:08 T:3408 NOTICE: Add Show Request:...status=skipped&future_status=&flatten_folders=False&initial=sdtv|sddvd...
in that it shows says status=skipped&future_status= with nothing before the next &...seems to agree with the error I was getting of 'expected string or buffer'. Sound right, or am I way off?
Oh, and to answer other questions: sickbeard is on same local computer as kodi, and show lists still work in the addon. I was able to look at ongoing shows and shows coming up in the next week just fine when launching the plugin itself.
Sorry but you are way off.
What you're seeing in the "future_status" is an option only available on SickRage, not on Sickbeard. I did the Pull Request to add that myself to the SickRage project. The SickRage devs made some changes to how handling the status of past and upcoming shows. Having it empty, and the equals being next to the next ampersand just means that there is no value, and sickbeard simply ignores it cause it isn't looking for it as an option anyway. I was aware of that.
What what we do see in the log this time is an error message from the sickbeard server itself. It's complaining about a "HTTP Error 500: Internal Server Error" just a few lines below where you were looking in the log. That indicates something going wrong in sickbeard when it tries to add a show. So you can try two things to try to figure out what that might be.
First add a show using the Web UI and then look at the log. See if you can find where it's adding the show, and any error messages.
Second, you can take the URL that the SickRage addon has compiled, and put that in the address bar of your browser, and see what the exact errors message(s) are that Sickbeard sends back. So this text here:
Copy and paste that line above into the browser address bar and see what the results are. If it works it will show json text that includes a "success" message. If it's Sickbeard that has a config issue you will see "HTTP Error 500: Internal Server Error" and likely some other text with detail.
Doing a Google search of sickbeard and 500 error, there are some forum entries that say it's related to some notifications that have been set up in Sickbeard that no longer work, or have bugs.
Let's see what these tests tell us.