367500 - get SeaMonkey 1.1 users redirected to a working dictionaries page

Status: RESOLVED FIXED

(SeaMonkey :: General, defect)

Description

[Robert Kaiser]

SeaMonkey 1.1 shipped with the "get more dictionaries" URL pointing to https://addons.mozilla.org/en-US/seamonkey/1.1/dictionaries/ as this was a variant that was discussed earlier on in the URL discussions and actually has been working when the "correct" URL, http://en-US.add-ons.mozilla.org/en-US/seamonkey/1.1/dictionaries/ still has not been working yet.

Unfortunately we didn't check that page enough to see that it had not been update to the new-style list the "correct" one is being redirected to, and, what's even worse, "next results" is broken on that page as well.

Because of this, we'd be very glad if either the "next results" link there would be corrected to work, or even better, if this one hardcoded URL would be redirected to the same place as the "correct" URL.

Sorry, this bascially has been my fault, but unfortunately we have shipped that way now so I can't correct it on the SeaMonkey side any more.

Comment 1

[Robert Kaiser]

On Remora, this URL results in a 404 - could we get it redirected the same way that https://addons.mozilla.org/en-US/seamonkey/dictionaries/ (i.e. the same URL just without the version number) gets redirected to the correct dictionaries list?

Comment 2

[Mike Shaver (:shaver emeritus)]

Is this still an issue?  I lost track of it, sorry.

Comment 3

[Robert Kaiser]

Yes, as comment #1 says this is still an issue... actually, with Remora it is even more so as we currently get a 404 on that URL.

Comment 4

[Mike Shaver (:shaver emeritus)]

OK, I'll see what I can do.  I presume that the next Seamonkey 1.1.x update will have the fix, though, so maybe that's soon enough?

Comment 5

[Robert Kaiser]

We haven't checked any fix in yet, but it might be a good idea...

Comment 6

[Robert Kaiser]

Ah, and just as I pressed "commit" on this comment, I realized why I didn't check in a change:
In SeaMonkey, those URLs are in L10n files, and L10n is frozen on branch. Additionally, the existing localizations probably have the olde and wrong URL in their 1.1. language packs, which should work for the whole 1.1.x series.

Comment 7

[Mike Shaver (:shaver emeritus)]

I'm not sure that I agree that the wrong URL "should work" forever.  Are you really saying that whoever makes the rules for l10n on the branch for seamonkey won't permit you to fix a URL that is a 404, so that it can point at something correct?  That seems a little pointless, as change control policies go...

Is it at least fixed on trunk?  Then you can bake the change for a while and ask whoever it is that prefers purity over working products to grant you an exception.

(What would you do if you found an entity error in an l10n file that broke another feature?)

Comment 8

[Robert Kaiser]

That bad policy guy is... myself, actually.

Now that this is a 404 since Remora, I think it's probably best to fix it on branch. This won't fix any locales having a wrong URL though, as we don't have locales in CVS (yet).
And of course, it won't fix people who are still using 1.1 or 1.1.1 (1.1.2 will be released soon, in sync with FF 2.0.0.4, though).

On trunk this should have been fixed for a long time now, so no problem there.

Comment 9

[Mike Shaver (:shaver emeritus)]

Sounds great.  You're going to use redirect-farm links like we do in Firefox and TB, I presume, so other locales will be able to go to the right places on the site as they come on line on AMO?

I _think_ I'm moving this to the right place, apologies if not.

Comment 10

[Robert Kaiser]

I'll fix the en-US branch code side, but I think we still want the additional redirect for the old, wrong URL for those that still have it.

We're using the same style of URLs as usually done with urlformatter, but we don't actually use the urlformatter on branch yet (we do on trunk), so we need to hardcode this to https://en-US.add-ons.mozilla.org/en-US/seamonkey/1.1/dictionaries/ 

Comment 11

[Robert Kaiser]

OK, checked in the URL change to all three (!) locale files that need this change on branch, so 1.1.2 (en-US) will ship with the corrrect URL.

Still need to figure out what to do about 1.1. and 1.1.1 users (do we care enough?) and locale packs.

Comment 12

[Robert Kaiser]

OK, new locale packs should be corrected, I sent out a notice to L10n people, and 1.1.2 is fixed as well. From what I see here, we'll probably just leave remaining 1.1(.1) users out in the cold and hope for them to upgrade to a version that has the correct URL.