XMLTV down again....

[Lester Jacobs]

Looks like zap2it once again made some website changes and XMLTV is down for the count. Hopefully the xmltv folks will have a fix shortly. They're usually pretty quick at reacting to stuff like this.

I will have an updated plugin available once the new xmltv binaries to correct the problem are published.

Cheers
Lester

[nicktripp]

Originally posted by Lester Jacobs
They're usually pretty quick at reacting to stuff like this.

Apparently so are you. Three cheers for Lester!

[shodge]

After looking at zap2it's site, it looks like snapstream is paying big bucks.... Advertisements.... Direct button for recording....

Prehaps they are purposely working towards messing up xmltv? I can not wait until November....

-Stan [my listings expire at Midnight...]

[hubick]

As posted by Robert Eden to the xmltv-devel mailing list:

http://alpha-exe.xmltv.org/

That links to a new .exe which works around the problem. Apparently the zap2it site returns an http 500 error code despite the fact the correct data is returned as normal. The above .exe ignores the server response code.

It sucessfully generated epgdata.xml for me. Now I just have to figure out how to convince the SaveTV plugin to suck it up :P

[robogeek]

hubick,

To get SageTV to import your listings manually, go to Setup-->Channel Setup, Press Enter twice, then press the Right Arrow key. Return to the Guide and presto... :D

Toggling one of the channels in the channel setup forces SageTV to refresh the guide data. It may take some time (a minute or two) for all of the guide data to be refreshed, but it works :cool:

[robogeek]

It might also be worth mentioning...Upgrading to the new xmltv.exe from v0.5.15 isn't a problem. But, if you upgrade to the new xmltv.exe from xmltv v0.5.14, you'll probably need the newest plugin by corykim. If you installed the new xmltv.exe and SageTV isn't importing the new guide data, download and install corykim's xmltv plugin. You can find it in this thread:

http://www.freytechnologies.com/forums/showthread.php?s=&threadid=1001

Scroll to the bottom of the thread and there is a post by corykim with a link to the new plugin :)

[hubick]

Thanks robogeek. I already have corykim's new plugin, and I tried the enter/enter trick... and it didn't work - I left it all night and still no listings. I had reconfigured the xmltv grabber (while attempting to get it working before), so I think that could have something to do with it. I just removed and recreated the source in SageTV, and that did the trick :P

[Lester Jacobs]

Originally posted by Lester Jacobs
Looks like zap2it once again made some website changes and XMLTV is down for the count. Hopefully the xmltv folks will have a fix shortly. They're usually pretty quick at reacting to stuff like this.

I will have an updated plugin available once the new xmltv binaries to correct the problem are published.

Cheers
Lester

Well the new xmltv binary as mentioned above does indeed fix the problem. It produces files identical to the 0.5.15 version so no new plugin is necessary; corykim's exiting xmltv plugin should do the trick. Therefore I will not be publishing a new plugin at this time.

I've successfully downloaded xmltv listings and updated SageTV without a problem.

Cheers
Lester

[pawn]

I wonder why I was unaffected?

I use XMLTV version 0.5.15 and the XMLTV Sage plugin you posted last time it went down a couple of months back.

My guide and XMLTV downloads kept pluggin' away without a glitch.

[Lester Jacobs]

Originally posted by pawn
I wonder why I was unaffected?

I use XMLTV version 0.5.15 and the XMLTV Sage plugin you posted last time it went down a couple of months back.

My guide and XMLTV downloads kept pluggin' away without a glitch.

Actually, it seems that the glitch was really zap2it's problem. The "fix" merely was a workaround for the glitch at zap2it. Zap2it independently fixed the glitch themselves after a couple of days,, therefore the pre-glitch xmltv binary once again resumed working.

Depending on the interval between your downloads, you may never have hit the problem.

Cheers
Lester