Bug 8030 - Don't display Rhapsody channels that are unavailable
: Don't display Rhapsody channels that are unavailable
Status: CLOSED FIXED
Product: MySqueezebox.com
Classification: Unclassified
Component: Rhapsody
: Prod
: PC All
: P1 normal (vote)
: Falco
Assigned To: Andy Grundman
:
Depends on: 7779
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-01 12:01 UTC by Mark Miksis
Modified: 2009-09-08 09:13 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Miksis 2008-05-01 12:01:11 UTC
About half of the Rhapasody channels are available for free and the rest require a paid account.  When browsing (via SC, SBC or SB) and signed in with a free-only account, all of the channels are listed including the ones I'm not allowed to play.  If I try to play one of the premium channels, it errors with "Rhapsody Error: Unable to retrieve track for channel".  These channels should not be listed if they can't be played.

Observed today on 7.2, but I think it's always been this way.
Comment 1 James Richardson 2008-05-01 13:23:56 UTC
Fletch:

Yes, it has always been that way with the "free" accounts.

Maybe we should change the message to read "This is premium account content" or something like that.
Comment 2 Mark Miksis 2008-05-01 14:19:17 UTC
(In reply to comment #1)
> Yes, it has always been that way with the "free" accounts.

Is there a technical reason why they can't be removed?  Or is this intentional to promote the Rhapsody paid content?

> Maybe we should change the message to read "This is premium account content" or
> something like that.

At the least, it would be nice if there were some visual indication of which channels are playable and which are not without first having to select "play".

Comment 3 James Richardson 2008-05-05 09:41:20 UTC
Chris to investigate with Rhapsody.

Which Account types are we going to support?  Pay, Free, RHAP-25 ???
Comment 4 Andy Grundman 2008-07-16 19:16:32 UTC
This can be handled entirely on SN, so changing product.
Comment 5 Chris Owens 2008-08-11 09:57:41 UTC

*** This bug has been marked as a duplicate of bug 7779 ***
Comment 6 Andy Grundman 2008-10-30 09:05:30 UTC
Fixed in QA branch.
Comment 7 James Richardson 2008-12-05 10:14:43 UTC
Verified fixed in (sv) r5231/r24205
Comment 8 James Richardson 2008-12-15 12:24:10 UTC
This bug has been fixed in the latest release of SqueezeNetwork!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.