Closed
Bug 1028441
Opened 11 years ago
Closed 11 years ago
My username ghostbar is not linked to my email address me at ghostbar.co
Categories
(developer.mozilla.org Graveyard :: Profiles, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: me, Unassigned)
Details
(Whiteboard: [specification][type:bug])
What did you do?
================
1. Tried sign-in with Persona me@ghostbar.co
What happened?
==============
1. Said I didn't had a profile so should create it, tried with my username ghostbar
2. Said ghostbar was already taken, tried to send an email for ghostbar and remember if I used another email but showed the page that says: 'The username ghostbar is not linked to any email address'
What should have happened?
==========================
Should have sent to any of my emails, be it joseluis at rivco.net, me at ghostbar.co or me at joseluisrivas.net
Is there anything else we should know?
======================================
I can confirm my identity with an email signed with my GPG key 0x13EC43EEB9AC8C43 which is inside the Debian keyring to add more trust to it.
Comment 1•11 years ago
|
||
There was no email address associated with the old MindTouch account (Last login was 2011-04-23).
So, I added your me at ghostbar dot com email address to the account. Persona sign-in should work for you now.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Just saw you added me ghostbar.com and it's ghostbar.co without the m.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
And tried to recover with username and said Mozilla Developer Network had ghostbar without email associated to it.
Comment 5•11 years ago
|
||
Oops, django admin interface thinks .co isn't a valid email address. :(
I updated it thru the python django shell now so it should work.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•