2013-11-26, 10:18
had the same issue yesterday evening, too. Suddenly plexbmc got scripting errors. Seems that auto update for Amber Skin 2.5 is responsible for that. After going back to Amber 1.x everything worked again.
(2013-11-26, 10:18)amberplex Wrote: had the same issue yesterday evening, too. Suddenly plexbmc got scripting errors. Seems that auto update for Amber Skin 2.5 is responsible for that. After going back to Amber 1.x everything worked again.
(2013-11-26, 12:01)pecinko Wrote:(2013-11-26, 10:18)amberplex Wrote: had the same issue yesterday evening, too. Suddenly plexbmc got scripting errors. Seems that auto update for Amber Skin 2.5 is responsible for that. After going back to Amber 1.x everything worked again.
Use updated version of PleXBMC with latest Amber. There's a info about it in Amber thread.
(2013-12-07, 22:28)wojeda Wrote:(2013-11-26, 12:01)pecinko Wrote:(2013-11-26, 10:18)amberplex Wrote: had the same issue yesterday evening, too. Suddenly plexbmc got scripting errors. Seems that auto update for Amber Skin 2.5 is responsible for that. After going back to Amber 1.x everything worked again.
Use updated version of PleXBMC with latest Amber. There's a info about it in Amber thread.
Yes! Yes! Thank You! I also had PleXBMC working beautifully under Transparency! Some guy mentioned on another thread that Amber had better integration so, there I go, just 10 minutes ago, tried it right away. Amber did not like it one bit, right away i got the dreaded script error. Then I said, fine! I'll go back to Transparency! But it is also broken there as well now. Script Error all over the place. I mean, what happened?
I even tried to go back to re-install the add-on through the "get more add-ons", and it's not even in the list anymore.
I am literally heart broken. That is what I get for fixing something is not broken.
(2013-12-08, 02:40)wojeda Wrote: OK, thanks pecinko. That may explain what happened to me. I am now gun shy and really don't want to try Amber again in fear that it'll break again.
Thanks
<setting id="discovery" type="enum" label="30004" lvalues="30053|30070" default="1" />
<setting id="discovery" type="enum" label="30004" lvalues="30053|30070" default="2" />