search

CptDarling / xot-uzg

Automatically exported from code.google.com/p/xot-uzg
0 stars 0 forks source link

Error fetching channels for plugin #185

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When trying to run  XOT-Uzg v3.2.0b7 as a plugin, it will not start. When 
running it as a script there are no issues.

I attached the log file. THe error "Error fetching channels for plugin"  is at 
line 
327.

regards,

JW

Original issue reported on code.google.com by jwbaalbe...@gmail.com on 9 Mar 2010 at 10:05

Attachments:

GoogleCodeExporter commented 9 years ago 
Update to a more recent (but not to recent, januari or so) XBMC. August 2009 
builds are 
too old.

It was a known issue.

Original comment by basrie...@gmail.com on 9 Mar 2010 at 11:13

GoogleCodeExporter commented 9 years ago 
Bas, thanks for the reply.
but no can do, sorry..:-) this is the last version that XBMC for Xbox that 's 
working 
(almost) flawless for me.

Do you know what version of xot-uzg will work with older versions of xbmc? I've 
read 
somewhere version 3.2.0b5 should be ok?

thanks JW

Original comment by jwbaalbe...@gmail.com on 9 Mar 2010 at 11:47

GoogleCodeExporter commented 9 years ago 
I use a januari build of XBMC for Xbox and have  no problems.

Older versions of XOT won't work because channel updates are not backwards 
compatible. 

Try commenting line (# In front of the line) 159 in plugin. That is the line 
with 
logFile.debug(channelGUI.sortOrder)

Original comment by basrie...@gmail.com on 10 Mar 2010 at 7:04

GoogleCodeExporter commented 9 years ago 
Unfortunately, commenting that line didn't do the trick.
I'll try a newer version of XBMC when I have time. What build did you use? I 
had 
problems playing ISO and DVD with newer builds

Original comment by jwbaalbe...@gmail.com on 10 Mar 2010 at 9:55

GoogleCodeExporter commented 9 years ago 
you can't have gotten the same error. Post a logfile again.

Original comment by basrie...@gmail.com on 10 Mar 2010 at 10:04

GoogleCodeExporter commented 9 years ago 
no not the same error.  I tried some other stuff so I have to reproduce it. 
What I can 
remember the error was ow in line 162. Rest looked the same.

I will post a log file tomorrow.

Original comment by jwbaalbe...@gmail.com on 10 Mar 2010 at 10:09