Bug 23498 - [18.11] Broken links to bibs when placing holds on multiple records and a hold exists on at least one record
Summary: [18.11] Broken links to bibs when placing holds on multiple records and a hol...
Status: RESOLVED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: 18.11
Hardware: All All
: P5 - low trivial (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-22 21:31 UTC by Jason Robb
Modified: 2023-12-08 21:27 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Screenshot of broken link (57.49 KB, image/png)
2019-08-22 21:31 UTC, Jason Robb
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Robb 2019-08-22 21:31:22 UTC
Created attachment 92441 [details]
Screenshot of broken link

When placing holds on multiple records at once from a list of search results in the staff client, if one of the selected records already has a hold, the "Confirm Holds" page where you choose a patron will list each record and the existing holds. The links to the bib records on that page are incomplete.

To replicate the issue:
1. Run a search that gives multiple results
2. Place an individual hold on the first record
3. Repeat the search
4. Use the check boxes to select 2 or more records, including the record with a hold
5. Click 'Place Hold' at the top of the results
6. The next page should have a box to search for the patron, and list out the records you selected and any holds on those records. Hover over the title of the record and notice that the URL for each is lacking a bib number at the end.
Comment 1 Katrin Fischer 2019-11-03 22:33:45 UTC
I just tested this on master, but the display of information there is quite different. On 18.11 I can confirm the bug, suspecting a problem in the template.
Comment 2 Katrin Fischer 2023-12-08 21:27:35 UTC
18.11 is no longer maintained and this appears to be fixed in current versions.