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

[Bug 24424] New: Advanced editor - interface hangs as "Loading" when given an invalid bib number
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24424 Bug ID: 24424 Summary: Advanced editor - interface hangs as "Loading" when given an invalid bib number Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: carnold(a)dgiinc.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The Advanced Editor hangs with "Loading, please wait" message when given an invalid bib number /cgi-bin/koha/cataloguing/editor.pl#catalog/55555 https://paste.pics/e7c7e4956dfa888b13b54332472df066 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 32696] New: Recalls can inadvertently extend the due date
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32696 Bug ID: 32696 Summary: Recalls can inadvertently extend the due date Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If an item is due sooner than the recall due date interval then placing a recall on it can inadvertently extend the book's due date, possibly causing the recalling patron to receive the item later than they would otherwise. To recreate the issue: - turn on recalls with UseRecalls and scaffold out the minimal circulation rules needed to use the feature - set the recall due date interval to 7 days or any other arbitrary period - check out an item to one patron & set the due date to be before the recall due date interval will have elapsed (e.g. the next day) - as a second patron, place a recall on the item in question Actual behavior: the item's due date is extended to the current date plus the recalls due date interval. Desired behavior: the item's due date should stay the same so the recalling patron doesn't face an additional delay in obtaining it. The logic is that the new due date should be either the existing due date or the current date plus the recall due date interval, whichever is sooner. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 30493] New: Pending archived suggestions appear on intranet home page
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30493 Bug ID: 30493 Summary: Pending archived suggestions appear on intranet home page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org If suggestions are archived before their status is changed to something other than "Pending", they still appear on the intranet home page and the acquisitions home page as suggestions to be managed. 1. Go to Acquisitions > Suggestions 2. Click on New purchase suggestion 3. Fill in the form (title only is fine) 4. Click on Submit your suggestion 5. Go to the home page (click the Koha logo) --> Notice it says that there is 1 pending suggestion 6. Go to Acquisitions --> Notice it says that there is 1 pending suggestion 7. Go to Suggestions 8. Click on the up arrow to the right of the Edit button and choose Archive --> There are no more pending suggestions 9. Go to the home page (click the Koha logo) --> Notice it says that there is 1 pending suggestion 10. Go to Acquisitions --> Notice it says that there is 1 pending suggestion -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 30715] New: Terminology: Logs should use should use staff interface and not intranet for the inrerface
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30715 Bug ID: 30715 Summary: Terminology: Logs should use should use staff interface and not intranet for the inrerface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org When logs are enabled and an action is performed in the staff interface, it is displayed in the log interface column as "Intranet". This should be displayed as "Staff interface", as per the terminology guidelines: https://wiki.koha-community.org/wiki/Terminology#I To reproduce: 1. Any action logged by the staff interface should show this in the log viewer. 2. Example: . Enable logs for cataloging (enabled by default in koha-testing-docker) (CataloguingLog system preference). . For a record, change the shelving location for any item to something else. . Check the logs (Tools > Additional tools > Log viewer then Submit). . The interface column shows that the change was made in the "Intranet". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 30372] New: Patron self registration: Extended patron attributes are emptied on submit when mandatory field isn't filled in
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30372 Bug ID: 30372 Summary: Patron self registration: Extended patron attributes are emptied on submit when mandatory field isn't filled in 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Testing bug 30120 I noticed that when you lave a mandatory extended patron attribute (or possibly another mandatory field) empty, all values already entered in extended attributes will be removed when clicking submit. To test: - Activate patron self registration without email verification - Create several patron attributes as visible and editable in the OPAC, make one mandatory - Register as a new patron from the OPAC - Fill in all required fields but the extended attribute - Submit - Verify that the contents of the other extended attribute fields have been removed and you are forced to re-enter -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 33849] New: Duplicate patron warning resets borrowers branch if different than logged in user's branch
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33849 Bug ID: 33849 Summary: Duplicate patron warning resets borrowers branch if different than logged in user's branch Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When entering a new patron, if the patron's home library is not the same as the logged-in library of the user + the patron is flagged as a possible duplicate, the patron's home library reverts to the logged in user's library. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 33205] New: (Bug 28268 follow-up) Method call inside quotes
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33205 Bug ID: 33205 Summary: (Bug 28268 follow-up) Method call inside quotes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com CC: ere.maijala(a)helsinki.fi Bug 28268, in Koha::MetadataRecord::Authority::get_all_authorities_iterator, introduced a warning: warn "Something went wrong reading record for authority $row->authid: $@\n"; But a method cannot be called from within quotes in Perl - extrapolation does not work for functions/methods. So, if something really goes wrong, this line of code produces a warning like: Something went wrong reading record for authority Koha::Schema::Result::AuthHeader=HASH(0x55cf7e0d0958)->authid: Empty String at /usr/share/perl5/MARC/File/XML.pm line 450. which is not very informative -- authid is missing. Proposal: $row->authid should be placed outside of the quotes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 27198] New: Sync marc21-retrieval-info-auth-dom.xml with retrieval-info-auth-dom.xml
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27198 Bug ID: 27198 Summary: Sync marc21-retrieval-info-auth-dom.xml with retrieval-info-auth-dom.xml Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au ./debian/templates/marc21-retrieval-info-auth-dom.xml is out-dated and should be synchronized with ./etc/zebradb/retrieval-info-auth-dom.xml The main issue is that the XML retrieval syntax is wrong which prevents a person from using the Zebra special retrieval elements documented at https://software.indexdata.com/zebra/doc/special-retrieval.html -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 33457] New: Improve display of fund users when the patron has no surname
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33457 Bug ID: 33457 Summary: Improve display of fund users when the patron has no surname Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When a patron is added to a fund as user and they have no surname, null is displayed instead: * Go to administration > funds * Edit fund * Click 'Add users' * Select a user, only staff users will be searchable * In the sample database, choose cardnumber 42 * After adding the user, the name displays as: null koha -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 32477] New: Batch Item Modification Columns
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32477 Bug ID: 32477 Summary: Batch Item Modification Columns Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com 22.05 has created issues with the columns in Batch item modification. There are 2 different issues that we have observed. 1- Unselecting "Source of classification or shelving scheme" removes that column on the current page. However, going back to the batch item modification tool to run a new batch makes the "holds" column disappear. 2- Unselecting some columns on the current screen hides that column. However, when we run a new batch item modification, the column shows up again while the box is still unchecked. Checking the box now behaves as a hide instead of show. Both problems get resolved when "show all" is used. But that means we have to constantly revert back to show all before running any further batch item modifications or the columns will be wrong. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35