http://www.mozilla.org/my/firefox/ 302 FOUND -> http://www.mozilla.org/my/firefox/fx/ 301 Moved Permanently -> http://www.mozilla.org/en-US/my/firefox/fx/ 404 Not Found I've checked some other locales and realized there is more... http://www.mozilla.org/an/firefox/fx/ http://www.mozilla.org/an/firefox/new/ http://www.mozilla.org/az/firefox/fx/ http://www.mozilla.org/az/firefox/new/ http://www.mozilla.org/ms/firefox/fx/ http://www.mozilla.org/ms/firefox/new/ Those pages should be fallbacked to en-US if l10n is not ready.
Currently only /az/firefox/ is in question.
Locale: az / Azerbaijani
Summary: [l10n] Some locales of /firefox/ are 404 Not Found → [l10n] /az/firefox/ is 404 Not Found
We don't ship Azerbaijani yet (only on Aurora for now) and I remember Flod mentionned display issues on the site with this locale, pinging him to know more.
Yes, it's bug 991516. We should have a few key pages ready (home, new) waiting for that bug to be fixed.
(In reply to Francesco Lodolo [:flod] from comment #4) > Yes, it's bug 991516. We should have a few key pages ready (home, new) > waiting for that bug to be fixed. We are using http://l10n.mozilla-community.org/webdashboard/?locale=az page for choosing what to translate and our team working on translation in our github page. Pages home and new are ready, but some other critical pages remaining. We are getting 404 in https://www-dev.allizom.org/az/firefox/ And font problem in https://www-dev.allizom.org/az/ stays same.
So, bug is solved, and all critical pages are ready, waiting for new version to go live.
This is fixed on prod now, thanks. There are still a few untranslated strings on the webdashboard and pootle, but the scope of this bug was "nothing at all", and that's done.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.