Closed Bug 512894 Opened 16 years ago Closed 16 years ago

links to search results return "Firefox can't find the server at kb." error

Categories

(support.mozilla.org :: General, defect)

defect
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rose.foster-aoej0dru, Assigned: paulc)

References

()

Details

(Whiteboard: sumo_only newsearch urlhandling)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 Build Identifier: links on the search result page are malformed, [https://kb/Het+door+Firefox+gebruikte+e-mailprogramma+wijzigen?s=gmail] for example. Reproducible: Always Steps to Reproduce: 1.enter url [https://support.mozilla.com/tiki-newsearch.php?where=all&q=gmail&sa=] 2.click one of the search result links or the ask a support question instead link 3. Actual Results: go to error page Expected Results: go to correct page
This happens only when I am logged in. Search results are totally different when I log out and all links for searches returned are clickable. All addons are disabled.
Changing product to support.mozilla.com.
Component: www.mozilla.org → General
Product: Websites → support.mozilla.com
QA Contact: www-mozilla-org → general
I confirm seeing the problem as well using a 6/26 & 7/18 nightly builds. We both went thru our addons, and disabled them. Even as far as uninstalling some of them (like Adblock Plus) for example. The problem still persisted. You MUST be logged in to SUMO to see the problem. Please remember that, I kept forgetting. :/
I can't reproduce, even when logged in.
(In reply to comment #4) > I can't reproduce, even when logged in. I take that back; Admin accounts work fine, but Contributor accounts give the behavior Noah and bretttt describe.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → 1.3
Is there any reason why searches should be different for contributors or regular users? Also I think this was working before so I suspect this may have to be bumped to IT.
Severity: normal → critical
If I log in as a Contributor, I still cannot reproduce. Is this specific to a build of Firefox (trunk)?
Maybe it's a specific DB slave?
Cilias, not specific to a trunk build as Brett is using a official 3.5.1. Take a gander at his UA in comment 0. :P I had a feeling it had something to do with accounts belonging to specific groups as Ricmacas couldn't reproduce it. So I found that funny.
I think let's wait and see if newsearch rewrite fixes this.
Target Milestone: 1.3 → 1.4
Assignee: nobody → paul.craciunoiu
Depends on: 501880
Now that newsearch is on stage, can we reexamine this?
OS: Windows XP → All
Hardware: x86 → All
Target Milestone: 1.4 → 1.4.1
Target Milestone: 1.4.1 → 1.5
Since we didn't land the newsearch rewrite, we need to address this ASAP, ie: 1.4.1.
Target Milestone: 1.5 → 1.4.1
Attached patch v1Splinter Review
I __cannot wait__ to rewrite the entire search. It is so ridiculously confusing :(
Attachment #404335 - Flags: review?(james)
No longer depends on: 501880
Comment on attachment 404335 [details] [diff] [review] v1 Seems to be working for me. I'm a little curious how this was falling through.
Attachment #404335 - Flags: review?(james) → review+
r52789 (trunk only)
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Verified FIXED. Litmus: https://litmus.mozilla.org/show_test.cgi?id=9560 Please commit to production, thanks!
Status: RESOLVED → VERIFIED
r52795 (prod) / r52796 (fennec) In case fennec wish to use search before we sync, they shouldn't have this problem.
Should this be Tiki upstreamed, or do we wait for the new(er) search?
Whiteboard: sumo_triage
Definitely wait.
Whiteboard: sumo_triage → sumo_only newsearch urlhandling
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: