Closed
Bug 615683
Opened 14 years ago
Closed 14 years ago
Link of some localized articles with their english parent is lost in Kitsune
Categories
(support.mozilla.org :: General, defect)
support.mozilla.org
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: scoobidiver, Unassigned)
Details
The link of some localized articles with their English parent is lost. It means that they are declared unstranslated in the localization dashboard. See: * https://support-stage.mozilla.com/fr/kb/Obtenir de l’aide sur Firefox 4 bêta that is a translation of https://support-stage.mozilla.com/en-US/kb/Get%20help%20with%20Firefox%204%20Beta * https://support-stage.mozilla.com/fr/kb/Poser%20une%20question that is a translation of https://support-stage.mozilla.com/en-US/kb/Ask%20a%20question
Comment 1•14 years ago
|
||
Do we know how many non-English articles there are after the import that lack an English parent?
Comment 2•14 years ago
|
||
These can be fixed through the django admin as they're found. We're out of time to generate a new wiki migration in time for the current push window.
Comment 3•14 years ago
|
||
Yeah, that was my thought, too. Would be good to know roughly how many we're talking about here though. (just these two? ten? hundreds?)
Comment 4•14 years ago
|
||
For what it's worth, the migration is trying really hard to figure out parent-child relationships, so I doubt this could be improved in the script any further.
Comment 5•14 years ago
|
||
In some cases it may have failed because there was already a translation of that document in that locale.
Comment 6•14 years ago
|
||
Still, my question was if it's possible to see how many non-English articles there are after a migration -- if it's just a handful, then there's no reason to worry about it, but if this happens to a lot (say, 50) articles, than it might be indicative of a bigger problem. Though, with just 13 minutes to go before we push, it might not make that big a difference anyway. We'll just have to make sure we connect them after the push.
Get help with Firefox 4 beta is just redirected to the main Firefox startpage since that's going to be our new Firefox 4 home page. I've fixed the linkage for the french Ask a question page so it should work now.
Reporter | ||
Comment 8•14 years ago
|
||
After the migration, "Installing Firefox" has been changed and it became "Untranslated" in every locales. I don't know if it is a different issue from the one in comment 0. https://support.mozilla.com/en-US/kb/Installing Firefox https://support.mozilla.com/fr/localization/untranslated
Comment 9•14 years ago
|
||
Cheng (or someone else), what's the procedure for linking pages back together? There's indeed something really strange going on with https://support.mozilla.com/en-US/kb/Installing%20Firefox because the language selector lists a LOT of languages, but no matter which one you select it keeps showing the English content.
Updated•14 years ago
|
Severity: normal → critical
Comment 10•14 years ago
|
||
Cc'ing Kadir in case you know how to connect localized articles to the English parent article.
Comment 11•14 years ago
|
||
Scoobidiver: This is same issue. You can search the lost article from search box. They are still there. for ja article: https://support.mozilla.com/ja/kb/Firefox のインストール expected to: https://support.mozilla.com/en-US/kb/Installing%20Firefox actual to: https://support.mozilla.com/ja/kb/%D0%9E%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%BD%D1%8F%20%D0%B4%D0%BE%20Firefox%2035
Comment 12•14 years ago
|
||
I've been connecting them via the admin. Can you please put things in http://etherpad.mozilla.org:9000/kb-sprint-admin-tasks (Section 2) and I'll be doing them throughout the day.
Reporter | ||
Comment 13•14 years ago
|
||
> I've been connecting them via the admin. Can you please put things in
> http://etherpad.mozilla.org:9000/kb-sprint-admin-tasks (Section 2) and I'll be
> doing them throughout the day.
Will this task file be used after KB sprint because I filed new tasks?
Comment 14•14 years ago
|
||
The connecting-them-through-the-admin solution has been working.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•