Reply to thread

Message

<blockquote data-quote="KitanaiYatsu" data-source="post: 720324" data-attributes="member: 111411">Well... there are a number of things to report:1)&nbsp; The error message I was getting about a badly formatted xmltv.dtd file was related to the EOL character(s).&nbsp; The plugin appears to be expecting UNIX style EOL (new line) but my file contained DOS/Win style EOL (cr and nl).&nbsp; I used wget to d/l the latest version of the xmltv.dtd.&nbsp; When I compared the new file with my file, the only differences were the EOL character(s).2)&nbsp; Fixing the above, didn't resolve my problem though.&nbsp; The plugin is still reporting that it's found channel information, but isn't seeing the program information.&nbsp; I suspect this is due to channel name mapping, but will remain unresolved as you'll see in the next paragraph.3)&nbsp; In my case however, I was using conflicting plugins for the same EPG information, and those plugins were stepping on each other.&nbsp; The bottom line is... if you're able to get all the EPG info you need using one plugin, you should turn off all of the other EPG related plugins.&nbsp; If you need to use additional EPG related plugins to complete your info, you need to configure them so they don't step on each other.&nbsp; I was able to get all of my EPG data from the SchedulesDirect plugin, so I don't need WebEPG, or xmlTv.</blockquote>

[QUOTE="KitanaiYatsu, post: 720324, member: 111411"] Well... there are a number of things to report: 1) The error message I was getting about a badly formatted xmltv.dtd file was related to the EOL character(s). The plugin appears to be expecting UNIX style EOL (new line) but my file contained DOS/Win style EOL (cr and nl). I used wget to d/l the latest version of the xmltv.dtd. When I compared the new file with my file, the only differences were the EOL character(s). 2) Fixing the above, didn't resolve my problem though. The plugin is still reporting that it's found channel information, but isn't seeing the program information. I suspect this is due to channel name mapping, but will remain unresolved as you'll see in the next paragraph. 3) In my case however, I was using conflicting plugins for the same EPG information, and those plugins were stepping on each other. The bottom line is... if you're able to get all the EPG info you need using one plugin, you should turn off all of the other EPG related plugins. If you need to use additional EPG related plugins to complete your info, you need to configure them so they don't step on each other. I was able to get all of my EPG data from the SchedulesDirect plugin, so I don't need WebEPG, or xmlTv. [/QUOTE]

Verification