Closed
Bug 365300
Opened 18 years ago
Closed 18 years ago
[mod_perl] Editing a saved search does not re-populate the search page
Categories
(Bugzilla :: Query/Bug List, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.0
People
(Reporter: alqahira, Assigned: LpSolit)
References
Details
Attachments
(1 file, 1 obsolete file)
3.98 KB,
patch
|
justdave
:
review+
|
Details | Diff | Splinter Review |
When I attempt to edit any of my saved searches (click "Edit Search" in the line-above-the-footer-table after running the search), instead of getting a Search page with all the parameters and values of my saved search pre-filled, I get a Search page which only has ";bug_file_loc_type" in the URL input :/
Trying to edit the search from the "Saved Searches" section of the Preferences results in the same failure.
Updated•18 years ago
|
Assignee: justdave → query-and-buglist
Severity: major → blocker
Component: Bugzilla: Other b.m.o Issues → Query/Bug List
OS: Mac OS X 10.3 → All
Product: mozilla.org → Bugzilla
QA Contact: reed → default-qa
Hardware: Macintosh → All
Summary: Editing a saved search does not re-populate the search page → [mod_perl] Editing a saved search does not re-populate the search page
Target Milestone: --- → Bugzilla 3.0
Version: other → 2.23.3
Updated•18 years ago
|
Flags: blocking3.0+
Comment 1•18 years ago
|
||
This is specific to running under mod_perl.... this showed up after we enabled mod_perl tonight. No clue why.....
Comment 2•18 years ago
|
||
see also bug 365293 - probably related.
Comment 3•18 years ago
|
||
I've deactivated mod_perl on production for the time being until we figure this out, this is too big a deal to leave it broken. mod_perl is once again active on bugzilla-test to give us somewhere to play.
Comment 4•18 years ago
|
||
OK, more information: this problem only exhibits itself in the combination of mod_perl and SSL. mod_perl on a cleartext http site works fine, without mod_perl on an https site works fine, mod_perl on an https site causes this problem. Just gets weirder and weirder.
Comment 5•18 years ago
|
||
Search page, after "edit search" from a buglist/search results, has same symptoms as comment 0 - values lost plus URL input contains ;bug_file_loc_type
Assignee | ||
Comment 6•18 years ago
|
||
This works on a non-mod_perl installation.
Attachment #249917 -
Flags: review?(justdave)
Assignee | ||
Comment 7•18 years ago
|
||
There was a missing $foundone = 1 in my previous patch, and so in some cases the query was overwritten by the default query.
Attachment #249917 -
Attachment is obsolete: true
Attachment #249920 -
Flags: review?(justdave)
Attachment #249917 -
Flags: review?(justdave)
Assignee | ||
Comment 8•18 years ago
|
||
OK, this seems to fix the problem on bugzilla-test, with mod_perl enabled.
Assignee | ||
Updated•18 years ago
|
Assignee: query-and-buglist → LpSolit
Comment 9•18 years ago
|
||
Comment on attachment 249920 [details] [diff] [review]
patch, v1.1
Yep, and as weird as it sounds, this appears to fix bug 365293 as well.
Attachment #249920 -
Flags: review?(justdave) → review+
Comment 10•18 years ago
|
||
For those following along, the PrefillForm() function was trying to decode the query string manually... and presumably we're doing something wrong. This patch changes it to use Perl's CGI module to do the decoding for us (we already do everywhere else in Bugzilla), which apparently knows how to deal with whatever edge case we're hitting in the CGI operation.
Updated•18 years ago
|
Flags: approval+
Assignee | ||
Comment 11•18 years ago
|
||
Checking in query.cgi;
/cvsroot/mozilla/webtools/bugzilla/query.cgi,v <-- query.cgi
new revision: 1.171; previous revision: 1.170
done
Checking in template/en/default/search/knob.html.tmpl;
/cvsroot/mozilla/webtools/bugzilla/template/en/default/search/knob.html.tmpl,v <-- knob.html.tmpl
new revision: 1.19; previous revision: 1.18
done
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 12•18 years ago
|
||
might this also have fixed bug 325123 and bug 339270?
Comment 13•18 years ago
|
||
(In reply to comment #12)
> might this also have fixed bug 325123 and bug 339270?
nope, neither of those is related.
You need to log in
before you can comment on or make changes to this bug.
Description
•