Bugzilla – Bug 10874
Play Button doesn't always work
Last modified: 2009-10-05 16:44:25 UTC
Clicking on the 'play' button via the WEB UI will not always work. This happens no matter which service I am selecting. I have tried Internet Radio and Music Services (new and old) Clicking the play button will always stop and empty the current play list for the selected player Clicking on the play button will intermittently start the new playlist. To Repo: Test.SN Browse > Music Service > select any service > Drill down till you see 'play' icon Click on the play icon: notice what happens to the selected player (boom in my case)
This is happening on (falco) Prod.SN as well
Might be related to the NP box changes.
Hmm... prod and test are so different, I wonder whether there's another issue. BTW: I've been playing a number of channels this morning, and all was fine. You're talking about the play button on the streams, not the big play button in the player control?
Yes, when browsing a stream, the little '>' button in front of "+"
Fixed in r5730.
Marking SqueezeNetwork bugs as closed. The latest version, r5879/r25112 should have fixed this issue. If you still experience the listed problem please feel free to reopen the bug.
This has come up in Heart again FireBug gives the following error when clicking the 'play' icon on the Web UI nc.opml is not a function playPlaylist(4)2# (line 42) onclick(click clientX=330, clientY=484)DAR%2BDN...56Q%3D%3D (line 2) [Break on this error] nc.opml('play', obj.url);
This error happens when clicking on the "+" key nc.opml is not a function addPlaylist(6)2# (line 49) onclick(click clientX=350, clientY=423)ldvjKG5b...UHg%3D%3D (line 2) [Break on this error] nc.opml('add', obj.url); May be related or even the same bug
Go to Deezer > Top Charts... errors happen there if you go one more level > France (or any other) then the error does NOT happen
change 6231 - temptative fix for nc.opml. Please give it a try.
I see this when the Play 'works' ===================================================================== {"params":["00:04:20:16:01:ea",["playlist","play","deezer://2718610.mp3","Dance With Somebody (Radio Version) by Mando Diao from Dance With Somebody"]],"error":null,"method":"slim.request","id":1,"result" :{}} ===================================================================== I see this when the Play 'fails' ===================================================================== {"params":["00:04:20:16:01:ea",["playlist","play",null]],"error":"Bad params!","method":"slim.request" ,"id":1,"result":null} =====================================================================
Andy - this sounds as if the OPML feed used wasn't correct, or misinterpreted by the opml.tt template. This issue is not a JS issue. The JS just does report that it doesn't get the data it's expecting.
I have now seen the same error on Prod.sn, when trying to play a newly created Pandora station. Instead of the 'play' icon, I see the > icon to 'play' the new station. The same error is seen when clicking on this > icon.
> I have now seen the same error on Prod.sn, when trying to play a newly created > Pandora station. Instead of the 'play' icon, I see the > icon to 'play' the > new station. The same error is seen when clicking on this > icon. IMHO this is an all different bug which should be reported separately. Or do you see any JS error? It rather looks as if the link next to the > wasn't a link to play the stream, but a "browse" type link.
The issue is related to the data delivered to the template. Instead of a playlist url it's delivering the playlist itself as a json object. { status => "OK", topChart => { chart => [ { country => "France", iso => "FR", track => [ { album => [{ id => 265374, name => "Like A Hobo" }], artist => [{ id => 162248, name => "Charlie Winston", smartPlay => 0 }], cover => "http://static.deezer.com/images/cover_big/35/e9/35e98981b4132322d8d396b3ab4dfe14.jpg", duration => 219, "format" => { aac_96 => 1, flv_128 => 1, mp3_128 => 1 }, name => "Like A Hobo", track_id => 2745929, }, { album => [ { id => 215333, name => "Doll Domination (International Version)" }, ], artist => [{ id => 83, name => "The Pussycat Dolls", smartPlay => 1 }], cover => "http://static.deezer.com/images/cover_big/a6/09/a609161f6b88da5945a30065c2d2f90f.jpg", duration => 225, "format" => { aac_96 => 1, flv_128 => 1, mp3_128 => 1 }, name => "I Hate This Part", track_id => 2149886, },
Moving bugs to next release so they don't get lost
This issue should be fixed when the new Web Control is implemented
James - I'd consider this fixed. Please re-open if you still see this issue in the new web remote control. Thanks!
This bug has been fixed in the latest release of MySqueezebox.com (formally known as SqueezeNetwork)! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.