Bug 12923 - How to add player in new skin?
: How to add player in new skin?
Status: RESOLVED DUPLICATE of bug 13174
Product: MySqueezebox.com
Classification: Unclassified
Component: Web UI
: MySB
: PC Other
: P1 normal (vote)
: INXS
Assigned To: Weldon Matt
:
Depends on: 13174
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-17 17:53 UTC by Dan Evans
Modified: 2009-09-08 09:23 UTC (History)
5 users (show)

See Also:
Category: Task


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Evans 2009-07-17 17:53:52 UTC
I do not see anywhere that allows me to add a new player once I'm logged in.
Comment 1 Weldon Matt 2009-07-17 18:09:15 UTC
There will be a "blank" case, where no squeezebox players are attached (not designed yet - please refer to the site map), that will provide some instruction.  As an option, we can make that option persistent in the left nav and call it "add a player."

Having said that, the only thing to go here, really, is instructions (basically telling users how to go to their device and log in or create an account).  All players, including ip3k, are going to require a login or account creation during setup. Disconnecting a player will log you out on the player itself.  

The PIN method is going away AFAIK.  This was discussed with Dean and engineering weeks and weeks ago and I've yet to hear any instructions/constraints to the contrary. 

Finally, it should be added that, since all new users will be required to create an account on-device, few users are going to run into this case - you'd have to either create an account on the site without having set up a device, or disconnect your player(s) deliberately from SN.

Players that are in the account, but disconnected, will still show up in the left-hand tab area, but there will be a "disconnected" message provided with some explanation.
Comment 2 Dan Evans 2009-07-20 13:26:29 UTC
Thanks Matt.  If I understood you though you did not mention the case where I own 1 Squeezebox with an existing account and I want to add my newly purchased second player to the same account.  If all players, including IP3K, will require I enter an account & password *on the player* then I suppose that takes care of that.  But...  

I'd feel more at ease hearing that that is indeed the plan.  If there's any doubt, or any reversals, we will need the above case added to the site.
Comment 3 Weldon Matt 2009-07-20 13:37:39 UTC
Of course.  

That IS indeed the plan.

There may, however, be some odd edge cases we haven't considered yet (at least I'm trying to assume there will be, for the sake of caution).

For example, what happens if a user hasn't upgraded their firmware to 7.4 for whatever reason.  I don't know enough about the technical issues to know if this could happen or not...
Comment 4 Michael Herger 2009-07-21 01:32:26 UTC
> That IS indeed the plan.

We're talking about entering username/password on the old players, like Boom, Transporter etc., right?
Comment 5 Andy Grundman 2009-07-21 04:33:51 UTC
Yes, that will replace the PIN.
Comment 6 James Richardson 2009-08-03 09:26:33 UTC
Dan/Matt can you guys please meet regarding this issue, to make sure there is a user friendly plan in place.
Comment 7 Chris Owens 2009-08-03 09:27:38 UTC
*** Bug 13182 has been marked as a duplicate of this bug. ***
Comment 8 Weldon Matt 2009-08-05 15:37:16 UTC
I think this was resolved in yesterday's call - we are forcing upgrades to 7.4 on all devices, and players will be added exclusively by singing into SN accounts on the player(s).  This will affect all players, including ip3k, I believe Andy has already built most or all of the functionality.

- A separate but related issue was discussed in that meeting in terms of how we can more gracefully help users once they've upgraded to 7.4.  But that's not the issue being discussed here.

- Bug 13174 already exists in terms of tracking the design of the page that will explain to users how to connect additional players.

Resolving as duplicate of 13174, which is the final piece of this IMHO...

*** This bug has been marked as a duplicate of bug 13174 ***