Closed Bug 784815 Opened 11 years ago Closed 10 years ago
bring back richer account settings preferences
With commit: https://github.com/mozilla/zamboni/commit/da4b035 there are some TODOs relating to commented out/removed settings fields. These will have to come back for desktop since users are pointed to that link in their actual emails. username, location, occupation, bio, homepage, and notifications are the now-missing fields
And the ability for users/admins to delete accounts.
Hardware: x86 → All
(In reply to Davor Spasovski [:dspasovski] from comment #0) > With commit: https://github.com/mozilla/zamboni/commit/da4b035 there are > some TODOs relating to commented out/removed settings fields. > > These will have to come back for desktop since users are pointed to that > link in their actual emails. In what emails?
I haven't seen these either but cvan mentioned users who receive certain (marketplace?) emails are told to visit the settings page to alter their email prefs. This might be a remnant from Addons but I don't know much more. We can ask cvan for more info when he gets back but otherwise we can proceed without an email preferences area for now so that it's not blocking the rest of the work.
Ah, the list of other fields confused me. Yes, there are links in most outbound emails to alter your notification preferences. This is bug 802379 (also waiting on UX). For this particular bug, let's just focus on the fields which aren't notifications: username, location, occupation, bio, homepage Maria: I think we can add fields easily enough, so this could be summarized with: (1) Do we want these fields? (2) is there anything special to putting them on the settings page?
Let's keep the amount of fields to a minimum for now. We (the design team) are planning to spend some time defining how the accounts should work for end-users and developers, how much overlap we need etc. I'm assuming we aren't in any huge rush with this? Q1 material?
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.