The default bug view has changed. See this FAQ.

remove en-US part from link in 'ready for localization' emails

VERIFIED FIXED in 2012-03-06

Status

support.mozilla.org
Knowledge Base Software
P3
normal
VERIFIED FIXED
5 years ago
5 years ago

People

(Reporter: atopal, Assigned: tgavankar)

Tracking

unspecified
2012-03-06

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: u=contributor c=wiki s=2012.4 p=1)

(Reporter)

Description

5 years ago
The ready for localization email says:

> To localize the document, click the following link, or paste it into
> your browser's location bar:
> 
> https://support.mozilla.org/en-US/kb/contributor-news-resources/translate

However with the en-US part left in, this is redirected to 
https://support.mozilla.org/en-US/kb/contributor-news-resources/edit

That's the English edit page and not useful to localizers. Please remove the en-US part from the URL
It should probably be go to this page instead: https://support.mozilla.org/kb/contributor-news-resources/locales ?
Whiteboard: u=contributor c=wiki s=2012.4 p= → u=contributor c=wiki s=2012.4 p=1
(Reporter)

Updated

5 years ago
Priority: -- → P3
(Assignee)

Comment 2

5 years ago
Top
Assignee: nobody → tgavankar
(Assignee)

Comment 3

5 years ago
Erm, I have no idea why that got posted while I was typing.

I meant to ask: Kadir, would you prefer simply removing the locale from the url, or should we go to /locales (as ricky mentioned)? Seems like locales would be the safer user path since they can select which locale to translate to, but then again it also has the one additional click. Opinions?
(Reporter)

Comment 4

5 years ago
Tanay, please go with what Ricky suggested, that is the safer option indeed.
(Assignee)

Comment 5

5 years ago
Done in https://github.com/mozilla/kitsune/commit/67a99b27
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2012-03-06
Verified updated article is ready for localization links in email notifications
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.