Error when adding a MoFo email to the l10n blog

RESOLVED FIXED

Status

Infrastructure & Operations
WebOps: Blogs
RESOLVED FIXED
6 months ago
5 months ago

People

(Reporter: tchevalier, Assigned: joeyk)

Tracking

Details

(Reporter)

Description

6 months ago
When an admin tries to add my MoFo email to get me an account in https://blog.mozilla.org/l10n/, it says that the email doesn’t exist.

This happened with my current MoFo credential: theo@mozillafoundation.org (which exists)

Could it be that the instance expects a MoCo email?
(Reporter)

Comment 1

5 months ago
Hey Paul, sorry if I’m pinging the wrong person, would it be something you can look into, or would that be someone else?

Thanks!
Flags: needinfo?(pmac)
Hey Theo. Unfortunately I don't have any special blog access and I'm not sure who does. I know Craig Cook works on the blog themes quite a bit, but I'm not sure if he's one who could help with a more back-end issue like this. Hopefully someone from Webops can point you in the right direction.
Flags: needinfo?(pmac)
(Reporter)

Comment 3

5 months ago
Thanks for the pointers, Paul!

@Shyam, would you be able to help identify someone who could take a look?

Many thanks!
Flags: needinfo?(smani)
(Assignee)

Updated

5 months ago
Assignee: nobody → jkrejci
(Assignee)

Comment 4

5 months ago
Hey Theo I couldn't find a user associated with your name or email account: theo@mozillafoundation.org

I added your user via the email above (check your email for instructions) and also added you as an Author on the l10n blog. 

Let me know if you have any trouble logging in. Thanks!

- Joey K
Flags: needinfo?(smani) → needinfo?(theo)

Updated

5 months ago
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/5322]
(Reporter)

Comment 5

5 months ago
Thanks Joey!

I’ve been able to log in successfully and change my password. I guess this bug can be closed
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Flags: needinfo?(theo)
Resolution: --- → FIXED
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/5322]
You need to log in before you can comment on or make changes to this bug.