Search results paging does not work after using Search Results button in staff client

Bug #1126545 reported by Kathy Lussier
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
2.3
Fix Released
Medium
Unassigned

Bug Description

Evergreen version: 2.3.3

Take the following steps:

1. Perform a catalog search in the staff client that results in more than one page of search results.
2. Click on the title for one of those results.
3. Use the Search Results button (not the link) to return to the results list.
4. Try to navigate to another page of search results. You'll get a blank screen.

When I hover over Debug on the blank screen, the URL displays as "url: oils://eg/opac/results?query=harry%20potter;qtype=keyword;locg=1;_adv=1;page=1." There is no "remote" at the beginning of the URL.

Revision history for this message
Simon Mai (simonmai) wrote :

Tested and confirmed the above issue with ver 2.3.1.

Revision history for this message
Simon Mai (simonmai) wrote :

The problem is at the return URL. When you click on Search Results button, the result page will be at:
oils://remote//eg/opac/results?bool=and;bool=and;bool=and;qtype=keyword;qtype=title;qtype=author;contains=contains;contains=contains;contains=contains;query=computer;query=;query=;locg=2;pubdate=is;_adv=1oils

The wrong thing is "//" between "remote" and "eg" in the above URL. It should be only ONE "/" between them.

The right link must be like this:
oils://remote/eg/opac/results?bool=and;bool=and;bool=and;qtype=keyword;qtype=title;qtype=author;contains=contains;contains=contains;contains=contains;query=computer;query=;query=;locg=2;pubdate=is;_adv=1oils

Easy to test this with TPAC:
Good link, get result after navigating to another page: http://ecrld.mnpals.net/eg/opac/results?fi%3Aitem_type=&query=computer&qtype=keyword&locg=1
Bad link with //eg, get nothing after navigating to another page: http://ecrld.mnpals.net//eg/opac/results?fi%3Aitem_type=&query=computer&qtype=keyword&locg=1

I tried to find out how to fix this URL, but I couldn't. Sorry about that. Hopefully someone else can solve this issue soon.
Simon.

Ben Shum (bshum)
Changed in evergreen:
milestone: none → 2.4.0-beta
importance: Undecided → Medium
status: New → Confirmed
Ben Shum (bshum)
Changed in evergreen:
milestone: 2.4.0-beta → 2.4.0-rc
Revision history for this message
Bill Erickson (berick) wrote :

I found the culprit, thanks to Simon's research.

Fix pushed to working => user/berick/lp1126545-tpac-staff-return-to-results

tags: added: opac pullrequest
Revision history for this message
Jason Etheridge (phasefx) wrote :

Thanks guys, tested, pushed to master. Not in a position to test 2.3, though I'm sure it'll work.

Revision history for this message
Ben Shum (bshum) wrote :

Confirmed to work in a 2.3 environment. Picked to rel_2_3 too.

Changed in evergreen:
status: Confirmed → Fix Committed
Ben Shum (bshum)
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.