Posts: 2
Joined: Aug 2012
Reputation:
0
Hello,
Had the same error as you guys but the code didn't match what was shown. To fix it I went to line 801 and just commented it out. It looks like this, "#data = re.findall('flashvars="(.*?)"', data)" with no parenthesis.
I guessed what to comment out as it was the same code you guys said to add (I never did add it, this was already there). Save code. Restart XBMC. Works fine so far. Hope this helps someone.
Posts: 1
Joined: Sep 2012
Reputation:
0
Guys, i've been doing all the above and nothing worked.
I'm running Eden with 3.1.0
modifying YouTubePlayer.py etc.
But I've found a thing that worked. Turn off the Firewall!!!!!!
[/align]
Posts: 508
Joined: Aug 2010
How I solved this on Mac:
uninstalled the plugin
cd ~/Library/Application Support/XBMC/userdata/addon_data
rm -rf plugin.video.youtube/
reinstalled the plugin
configured plugin settings again
Posts: 2
Joined: Oct 2012
Reputation:
0
Turning off the firewall worked for me too!! (nothing else on this thread did). Doesn't seem like a great solution though, does anybody know what port specifically to open?
Posts: 17
Joined: Oct 2012
Reputation:
0
Same here! Any solution other thab complete shut off?
Posts: 4
Joined: Dec 2011
Reputation:
0
Ive had this error for months now and Ive tried everything to solve it. It just doesnt work. Same thing with Vimeo, havent worked for ages either. Im curious to know why these havent been removed. Would be awesome if someone would want to start a new plugin project for Youtube since current one didnt even work well when it was usable. I know this is open source and complaining is contra-productive - but the functionality of this plugin is probably very central to the success of XBMC and currently these plugin only serve to harm XBMC and give it a bad reputation. I myself has been thinking about ditching XBMC for this very reason, men but I still like it and I would rather continue using it.
Posts: 6,339
Joined: Jul 2010
Reputation:
116
artrafael
Team-XBMC Forum Moderator
Posts: 6,339
See link in post #27 above for current discussion/status/fixes regarding this add-on.