February 2023 - Koha-bugs - lists.koha-community.org

[Bug 26471] New: Datatables js error on missing pdfmake.min.js.map
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '24

17 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26471 Bug ID: 26471 Summary: Datatables js error on missing pdfmake.min.js.map Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Seeing this error in the Firefox console on a page with a datatables table (e.g. admin/z3950servers.pl) Fout bij brontoewijzing: Error: request failed with status 404 Bron-URL: https://dev.rijkskoha.nl:28443/intranet-tmpl/lib/datatables/datatables.min_… Brontoewijzings-URL: pdfmake.min.js.map Compare with an older mention of this error from bug 15400: > I'm getting a different error that I'm not sure how to fix > > Source map error: Error: request failed with status 404 > Resource URL: > http://localhost:8081/intranet-tmpl/lib/datatables/datatables.min_19.1200060. > js > Source Map URL: pdfmake.min.js.map I am kind of lost in datatables land. It is a nightmare component imo. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 31181] New: Merge function does not include local copy images
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31181 Bug ID: 31181 Summary: Merge function does not include local copy images Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It seems that merge-from item local cover images are not merged to the merge-to entry. Is thie intentional or is it a bug? If intentinal there should be a warning to the user before the merge is performed, so that they may save the current images and re-locad them once the merging is complete. Are the images left in limbo, or are they deleted from the db once the merge is complete? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 26820] New: "Important" flag enforced only at subfield level
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26820 Bug ID: 26820 Summary: "Important" flag enforced only at subfield level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: - edit your framework so the 001 is set to Important at the tag level but not at the subfield level - create a new record in that framework, note that the 001 is not marked Important - edit framework, set it to Important on the @ subfield in the 001 - reload new record, see the 001 is now marked Important We're not doing anything with Important at the tag level, so let's not ask for it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 32183] New: Purchase suggestions for logged in patron - doesn't display suggestions made by everyone
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32183 Bug ID: 32183 Summary: Purchase suggestions for logged in patron - doesn't display suggestions made by everyone Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org If OPACViewOthersSuggestions is set to 'Show', for a logged in patron they can only see their own suggestions - not all suggestions as expected. This is working correctly on 22.05.x, but is not working on the current master. To replicate on the current master: 1. Set AnonSuggestions to 'Allow'. 2. Set OPACViewOthersSuggestions to 'Show'. 3. On the OPAC, when not logged in, add a purchase suggestion. 4. On the OPAC, log in as a patron and make a purchase suggestion. 5. Change OPACViewOthersSuggestions to "Don't show". 6. Under Your account > Purchase suggestions, you can only see your own suggestions (as expected). 6. Change OPACViewOthersSuggestions set to "Show". 7. Under Your account > Purchase suggestions, after the "Search for" input field there is a dropdown list with options: 7.1 Select "Suggested by me" and press "Go": the patron's own suggestion(s) are correctly shown. 7.2 Select "Suggested by anyone" and press 'Go': it DOESN'T show all suggestions. Identified when testing bug 20207. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 32256] New: self-checkout batch mode
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32256 Bug ID: 32256 Summary: self-checkout batch mode Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: ddaghita(a)mckinneytexas.org QA Contact: testopia(a)bugs.koha-community.org Please enable batch checkouts on self-checkout machines using koha self-checkout module (/cgi-bin/koha/sco/sco-main.pl?). We have patrons place one book at time on the RFID pad to self-checkout. We would ideally like patrons to stack five or more materials at a time so they checkout more efficiently all at once as it does on the koha staff side. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 105

[Bug 25375] New: Elasticsearch: Limit on available items does not work
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25375 Bug ID: 25375 Summary: Elasticsearch: Limit on available items does not work Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com Currently what this limit does is a filter on onloan:false This means that: - Any biblio with at least one checked out item will be hidden from the results, even if it has other available items - A biblio whose items are all lost, damaged, withdrawn or "notforloan" will not be hidden, but the results will show "X items, none available" -- You are receiving this mail because: You are watching all bug changes.

1 70

[Bug 27937] New: Date of birth entered without correct format causes internal server error
by bugzilla-daemon＠bugs.koha-community.org 12 Oct '24

12 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27937 Bug ID: 27937 Summary: Date of birth entered without correct format causes internal server error Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In 20.05 when a birthdate is entered in patron registration form (memberentry.pl) incorrectly, and save button is clicked, you receive an Internal Server Error and all the data is lost. To recreate: 1. Add new patron 2. Enter birthdate as 2/11/1986 3. Complete required fields 4. Save 5. Get ISE Yes, the text below the birthdate does specify MM/DD/YYYY but an incorrect entry should not cause all the data entered to be lost. Perhaps a warning instead that the birthdate format is incorrect? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 31330] New: Branchcode used for routing preview can be wrong
by bugzilla-daemon＠bugs.koha-community.org 11 Oct '24

11 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31330 Bug ID: 31330 Summary: Branchcode used for routing preview can be wrong Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Noticed when working on bug 31318, and discussed on IRC http://irc.koha-community.org/koha/2022-08-09#i_2443598 It seems that we adding/modifying the hold using the holdingbranch of the serial item published first. If no item is created (or no holdingbranch), we are using the subscription.branchcode Shouldn't we use the branchcode of the issue we previously created (if an item exist) instead of the first published one? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 26027] New: Add ability to let librarians know why higher priority holds were skipped
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26027 Bug ID: 26027 Summary: Add ability to let librarians know why higher priority holds were skipped Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com There are circumstances where higher priority holds are not trapped for a given item. These reasons range from requiring specific item or itemtype, to a hold being suspending, to a hold being given local holds priority. I think the best way to accomplish this would be to capture a list of the skipped holds and the reason for skipping them, then pass that to the template for display on the checkin screen when an item is trapped to fill a hold. This feedback would be especially useful if *none* of the holds were trapped for the given item. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 25809] New: Make claims returned claims visible in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '24

10 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25809 Bug ID: 25809 Summary: Make claims returned claims visible in the OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When an item is claimed returned, there isn't any place in the OPAC for the patron to see their claims. Could we add a claims tab to the patron account on the OPAC, mirroring what's on the staff side? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13