The default bug view has changed. See this FAQ.

Update app.support.baseURL to point to support.mozilla.org

RESOLVED FIXED in Firefox 12

Status

()

Firefox
General
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: rrosario, Assigned: zpao)

Tracking

12 Branch
Firefox 12
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
SUMO just finished moving over to support.mozilla.org. Links to support.mozilla.com will redirect over, but the links in Firefox (Help->Firefox Help, for example) should be updated to avoid the 301 redirect.
This is just updating the app.support.baseURL preference to s/.com/.org/.

zpao, can you help us get this to the right place?
Summary: Update SUMO links: s/support.mozilla.com/support.mozilla.org/ → Update app.support.baseURL to point to support.mozilla.org
Created attachment 584799 [details] [diff] [review]
Patch v0.1

Are there any other changes that we should make to this pref while we're here? It seems that regardless of version & platform I'm just getting redirected to su.m.o/LOCALE/home?as=u. It looks like mobile uses sumo/mobile as it's base url.

Relatedly, make sure you file a bug for mobile as well if you haven't already.
Assignee: nobody → paul
Status: NEW → ASSIGNED
Attachment #584799 - Flags: review?(gavin.sharp)
The locale, platform, and version bits can be used to direct specific Firefoxes to specific articles for any particular topic. I think it's used in a couple of places, but not with the generic F1/Firefox>Help links.

I'll go file a mobile bug.
(In reply to James Socol [:jsocol, :james] from comment #3)
> I'll go file a mobile bug.

Filed bug 714123.
Attachment #584799 - Flags: review?(gavin.sharp) → review+
https://hg.mozilla.org/integration/fx-team/rev/a1388e9f3679
Whiteboard: [fixed-in-fx-team]
https://hg.mozilla.org/mozilla-central/rev/a1388e9f3679
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 12
You need to log in before you can comment on or make changes to this bug.