EPG123 GUI Not Picking Up Changed Channel

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html
Post Reply
bryankennedy2

Posts: 27
Joined: Sat Sep 08, 2012 1:45 pm
Location:

HTPC Specs: Show details

EPG123 GUI Not Picking Up Changed Channel

#1

Post by bryankennedy2 » Thu Oct 13, 2016 2:28 am

Background: The local ABC affiliate in my town (central Illinois) changed, going from WHOI to WEEKDT2. Seeing as how both zap2it and SchedulesDirect were both showing the old WHOI listing (and, therefore, the wrong shows), I send in a ticket to SchedulesDirect to get it resolved. I received an e-mail yesterday evening that the servers had been updated (ticket 14304):

7 WMBD
8 WEEK2SD <-
10 WEEK

899 MC50
906 WEEKDT
907 WHOIDT2
908 WEEKDT2 <-
910 WYZZDT
912 WMBDDT
913 WGNA

However, when I go into the GUI, including on a non-production WMC system (i.e. the computer I'm typing this on now), the new channel name (WEEKDT2) is not appearing - only the old information and station ID.

Is there anything I can do in EPG123 to get it to reflect the new station ID?

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#2

Post by garyan2 » Thu Oct 13, 2016 3:32 am

If it is not in the GUI, then it is not on the SD-JSON server yet. The GUI does not cache the lineups or channels, so what you see is what is current from SD.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

bryankennedy2

Posts: 27
Joined: Sat Sep 08, 2012 1:45 pm
Location:

HTPC Specs: Show details

#3

Post by bryankennedy2 » Thu Oct 13, 2016 4:57 am

Yeah, hold off on this. It looks like it was updated for the XML, but not the JSON (my fault when I sent in the trouble ticket). SD is looking into it. I'll post back if something strange is still going on.

bryankennedy2

Posts: 27
Joined: Sat Sep 08, 2012 1:45 pm
Location:

HTPC Specs: Show details

#4

Post by bryankennedy2 » Thu Oct 13, 2016 11:53 pm

Following up on this - everything is good. XML was updated, JSON wasn't. Thanks to SD for getting things squared away!

Post Reply