Bug 12784 - MySB.com is missing Account Settings Page
: MySB.com is missing Account Settings Page
Status: CLOSED FIXED
Product: MySqueezebox.com
Classification: Unclassified
Component: Web UI
: MySB
: PC Windows XP
: -- normal (vote)
: CAT
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-10 15:32 UTC by James Richardson
Modified: 2009-10-06 09:22 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 2009-07-10 15:32:24 UTC
There is no account settings page on the new MySB.com interface.

No way to change or modify the account name/password after creating the logon
Comment 1 Chris Owens 2009-07-13 09:54:13 UTC
Currently this works by clicking on your name.  Is it reasonable to have another way to get here?
Comment 2 Weldon Matt 2009-07-13 12:25:41 UTC
This is a pretty normal approach to linking to account settings.  

Having said that, this could easily be added to the site footer.  Let's see what our beta community has to say about it (if anything) in terms of problems.  If so, the language in the top-right can be adjusted to make things more clear (e.g. "Hi, Matt! | Account Settings | Log Out").
Comment 3 James Richardson 2009-07-14 13:24:55 UTC
changing version for tracking
Comment 4 James Richardson 2009-07-15 09:18:54 UTC
Assigning this to my self, I'll monitor this during the CAT testing to determine user feedback.
Comment 5 Weldon Matt 2009-07-15 12:07:04 UTC
I actually thought about this further and refactored the design... assigning to Michael.  New mockups are here with a hopefully clearer layout.

http://embargo.wiki.slimdevices.com/index.php/Mysqueezeboxdotcom#1_Home
Comment 6 Michael Herger 2009-07-22 06:47:20 UTC
change 6634
Comment 7 James Richardson 2009-10-06 09:22:30 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.