Bug 13182 - Need a flow to register pre-7.4 players with the new mysb.com system
: Need a flow to register pre-7.4 players with the new mysb.com system
Status: CLOSED INVALID
Product: MySqueezebox.com
Classification: Unclassified
Component: Web UI
: MySB
: PC Windows XP
: P1 normal (vote)
: INXS
Assigned To: Weldon Matt
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-31 23:38 UTC by Mickey Gee
Modified: 2009-10-05 16:43 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mickey Gee 2009-07-31 23:38:07 UTC
The user interface of mysb.com does not have a way for a user with pre-7.4 firmware, such as a Controller or a SB Classic, from entering the player PIN to activate the player. I would not expect every user to update to 7.4, and a legacy way must be created to allow those user to do this.
Comment 1 Andy Grundman 2009-08-01 04:33:22 UTC
Ugh...please don't. :(

Mickey this problem only affects Jive, not ip3k players, by the way.
Comment 2 Weldon Matt 2009-08-01 14:46:30 UTC
Since, by definition, the PIN only applies in cases where you're registering the device with SN, we should prompt users at that point to upgrade to 7.4.  We probably do this on the "empty player/add a player" screen I'm working on for SN.

It happens.  Sometimes you've got to drop some legacy support in the interest of everyone's sanity...
Comment 3 Andy Grundman 2009-08-01 15:11:59 UTC
Yeah, players will get upgraded prior to any PIN screen.
Comment 4 Chris Owens 2009-08-03 09:27:38 UTC

*** This bug has been marked as a duplicate of bug 12923 ***
Comment 5 Weldon Matt 2009-08-03 09:43:41 UTC
If we force-update users to 7.4, which currently is the plan according to Andy (and I don't disagree we should do it), then this bug becomes invalid.
Comment 6 James Richardson 2009-10-05 16:43:14 UTC
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.