Bug 21261

Summary: OpacResults XSLT does not honor OpacHiddenItems
Product: Koha Reporter: Caroline Cyr La Rose <caroline.cyr-la-rose>
Component: OPACAssignee: Owen Leonard <oleonard>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: minor    
Priority: P5 - low CC: r.delahunty, severine.queune
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:
Attachments: In OPACResults, the withdrawn item is shown
In OPACDetails, the withdrawn item does not appear

Description Caroline Cyr La Rose 2018-08-23 13:59:56 UTC
Created attachment 78096 [details]
In OPACResults, the withdrawn item is shown

In the case where a record has more than one item and one of them is supposed to be hidden as per opachiddenitems, the record appears in the results list and shows the supposedly hidden item.

Expected result: in the result list, the record should appear and show only the items not hidden

To reproduce :
1- Go to Administration > Global System Preferences
2- Search for opachiddenitems
3- Add the following value to the system preference: withdrawn: [1]
4- Click on "Save all OPAC preferences"
5- In the search bar, click on "Search the catalog"
6- Search for anything
7- Find a record with two (or more) items, OR
7a- Click on "Edit items"
7b- Add an item by filling in the form
8- Change withdrawn status (field 0) for one of the items, the other(s) must be available
9- Go to the OPAC
10- Do a search large enough to get a couple of results in addition to the record modified above
11- In the results list, available items appear in green and the withdrawn item appears in red
12- Go into the detailed record
13- The withdrawn item does not appear
Comment 1 Caroline Cyr La Rose 2018-08-23 14:00:34 UTC
Created attachment 78097 [details]
In OPACDetails, the withdrawn item does not appear
Comment 2 Katrin Fischer 2020-01-11 18:12:04 UTC

*** This bug has been marked as a duplicate of bug 21014 ***