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

[Bug 30987] New: Adding relationship to PatronQuickAddFields causes it to be added 2x
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30987 Bug ID: 30987 Summary: Adding relationship to PatronQuickAddFields causes it to be added 2x Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com While working on Bug 29303 I noticed a small problem. If you add relationship to the PatronQuickAddFields system preference it will be added to the quick form two times. It looks like it is due to some JS that is no longer needed: if ( $("#memberentry_guarantor").length ) { $("#memberentry_guarantor").appendTo("#quick_add_form"); } -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 34621] New: Patron import option to 'Renew existing patrons' 'from the current membership expiry date' not implemented
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34621 Bug ID: 34621 Summary: Patron import option to 'Renew existing patrons' 'from the current membership expiry date' not implemented Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On bug 27920 the interface got a new option to extend the patron's renewal from the current membership expiry date by setting the variable 'update_dateexpiry' to 'dateexpiry' The code in tools/import_borrowers.pl however only checks for value 'now': 127 update_dateexpiry => $update_dateexpiry ? 1 : 0, And in Koha/Patrons/Import.pm - we either use the value from the import file, or today's date: 176 my $expiration_start_date = $update_dateexpiry_from_today ? dt_from_string : $borrower{dateenrolled}; We should either implement or remove this option -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 23102] New: 404 errors on page causes SCI user to be logged out
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23102 Bug ID: 23102 Summary: 404 errors on page causes SCI user to be logged out Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Bug 18387, but for the SCI To recreate: 1 - Have something on the SCO page that won't load 2 - Add the self_checkin_module and self_checkout_module permissions to the AutoSelfCheck user 3 - Access the selfcheckout module https://yoursite.org/cgi-bin/koha/sco/sco-main.pl 4 - Sign in 5 - Click 'Finish' 6 - Yes to print a receipt 7 - You are asked to sign in again 8 - Repeat with the SCI module -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 65

[Bug 23296] New: Auto Renewal Notice does not use Library specific notices
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23296 Bug ID: 23296 Summary: Auto Renewal Notice does not use Library specific notices Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org All notices in Koha are created to be a default ALL libraries notice, however, with branch systems, there is also the ability to create a library specific notice that can be used instead. However, the notice AUTO_RENEWALS is not currently capable of being library specific - instead, the ALL Library Notice for AUTO_RENEWALS is the only one that Koha send. To adjust this, it would be recommended that a library specific notice like all the others in Koha can be created. Following circ control, would be the suggested way to go as with most notices in Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 35573] New: Koha is no correctly warning of overridden items when placing a hold if AllowHoldPolicyOverride
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35573 Bug ID: 35573 Summary: Koha is no correctly warning of overridden items when placing a hold if AllowHoldPolicyOverride Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If AllowHoldPolicyOverride is enabled we are not warning that items require override if there are valid pickup locations. Regressions caused by (me on) bug 30687 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 35129] New: REST API: _per_page=0 crashes on Illegal division by zero
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35129 Bug ID: 35129 Summary: REST API: _per_page=0 crashes on Illegal division by zero Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl CC: tomascohen(a)gmail.com >From IRC: [14:08] <marcelr> Nice /api/v1/patrons?_page=1&_per_page=0 just returns me a 500 (ISE) [14:09] <marcelr> not tested yet :) [14:10] <marcelr> [ERROR] GET /api/v1/patrons: unhandled exception (Mojo::Exception)<<Illegal division by zero at /usr/share/koha/Koha/REST/Plugin/Pagination.pm line 106.>> -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 35977] New: Display current date in Hold starts on date on opac-reserve
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35977 Bug ID: 35977 Summary: Display current date in Hold starts on date on opac-reserve Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: mirjam.vantieghem(a)etf.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This is related to bug #15652. If you enable AllowHoldDateInFuture (and its OPAC variant), you get an additional "Hold starts on date". It is possible to select the current date from the datepicker in the OPAC. If no date is selected, the default is the current date. However, it is not clear to the patron that the current date is selected by default, as the field is empty if no date has been selected from the datepicker. This caused confusion among some of our patrons. Therefore we use a custom patch to have the current date shown in the field "Hold starts on date". What Marcel de Rooy wrote in the related bug, also applies here: "Although it does not really make any difference if you leave the startdate empty or put the current date in it, we concluded that it still makes a psychological difference." -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53

[Bug 30717] New: Date format doesn't change in additem for dateaccessioned
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30717 Bug ID: 30717 Summary: Date format doesn't change in additem for dateaccessioned Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mengu(a)devinim.com.tr QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, After upgrade from 19.05 to 21.11.04 we got a problem with additem section. dateaccessioned area of additem doesn't seem correctly even we changed dateformat in systempreferences. I've removed the blank in the line var dateformat_pref = "[% Koha.Preference('dateformat') | html %]"; of calendar.inc -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 34823] New: Do not show item group drop-down if there are no item groups
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34823 Bug ID: 34823 Summary: Do not show item group drop-down if there are no item groups Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When EnableItemGroupHolds is activated, there is a "Request specific item group:" drop-down in the OPAC when placing a hold. However, this drop-down appears regardless of whether the record has item groups or not. I think this may be confusing for patrons. To replicate: 1. Enable EnableItemGroups and EnableItemGroupHolds 2. Go to the OPAC and log in as a patron 3. Go to any record that doesn't have grouped items and try to place a hold 4. Click on "Show more options" --> Note that there is an option to choose an item group with the only option being "Any item group" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 34663] New: Unimarc Default framework
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34663 Bug ID: 34663 Summary: Unimarc Default framework Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org New install Koha 23.05.02 Please correct in the Unimarc Default framework. subfields not in same tabs Not all subfields for the following tags are in the same tab (or marked 'ignored'). Code Description Tag Tabs in use Default framework 410 3,4 Default framework 411 3,4 Default framework 412 3,4 Default framework 413 3,4 Default framework 421 3,4 Default framework 422 3,4 Default framework 423 3,4 Default framework 424 3,4 Default framework 425 3,4 Default framework 430 3,4 Default framework 431 3,4 Default framework 432 3,4 Default framework 433 3,4 Default framework 434 3,4 Default framework 435 3,4 Default framework 436 3,4 Default framework 437 3,4 Default framework 440 3,4 Default framework 441 3,4 Default framework 442 3,4 Default framework 443 3,4 Default framework 444 3,4 Default framework 445 3,4 Default framework 446 3,4 Default framework 447 3,4 Default framework 448 3,4 Default framework 451 3,4 Default framework 452 3,4 Default framework 453 3,4 Default framework 454 3,4 Default framework 455 3,4 Default framework 456 3,4 Default framework 461 3,4 Default framework 462 3,4 Default framework 463 3,4 Default framework 464 3,4 Default framework 470 3,4 Default framework 481 3,4 Default framework 482 3,4 Default framework 488 3,4 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17