Bug 8788 - Gallery Sign up is not working properly
: Gallery Sign up is not working properly
Status: CLOSED FIXED
Product: MySqueezebox.com
Classification: Unclassified
Component: Web UI
: Test
: PC All
: P1 normal (vote)
: Coldplay
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-18 08:51 UTC by James Richardson
Modified: 2008-08-15 14:47 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Richardson 2008-07-18 08:51:49 UTC
Using the new gallery sign up wizard in Coldplay, creating a new account (never been on SN, never had associated service accounts) I find that the music service accounts are not being auto-created for me.

Sign up an email address that has never been on SN and has never had any music service.  After the registration process, check Accounts > music services tabs and notice that nothing has been signed up.

Make sure to select all music services during the sign up, and fill in all required fields.
Comment 1 James Richardson 2008-07-18 08:55:10 UTC
MP3Tunes & Slacker did get signed up

Pandora, Rhapsody, Sirius did not
Comment 2 Michael Herger 2008-07-18 09:58:52 UTC
change 4092 (and earlier) - Andy's already fixed this before I had a chance to look at it in detail (thanks!). Gender was all upper case while Pandora expected it lower case.

Subscriptions are working fine for me on my local installation. 

Please note that Sirius/Rhapsody will need a registered player. If you don't have any, the subscription will fail.

Lack of specs there's currently no feedback on the success of the various subscriptions. The results are stored in the user's prefs table. We'll have to think about some kind of presentation. Could you please open an enhancement about this and CC Brian & Marketing? Thanks!
Comment 3 James Richardson 2008-08-15 14:47:01 UTC
This bug is being closed since it was resolved for a version of SqueezeNetwork which is now released!

If you are still seeing this bug, please re-open it and we will consider it for
a future release.