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

[Bug 36435] New: Prevent warnings from interrupting koha-run-backups when deleting old backup files
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36435 Bug ID: 36435 Summary: Prevent warnings from interrupting koha-run-backups when deleting old backup files Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Since the changes at Bug 30627, sometimes backup files older than X days don't get deleted as they are meant to. In our case, this happens when: - koha-dump does not return a success status - because `tar -c` throws a warning "tar: var/log/koha/INSTANCENAME/opac-access.log: file changed as we read it" The new dump is created, but the warning is enough to interrupt koha-run-backups before it gets to deleting old backups. This causes excess backups to be stored and fills up the disk. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 38211] New: New biblio in non-Default framework opens in Default on first edit
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38211 Bug ID: 38211 Summary: New biblio in non-Default framework opens in Default on first edit Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, m.de.rooy(a)rijksmuseum.nl Depends on: 37947 Seems unlikely, but it does. Prior to the patch from bug 37947, there was the unnoticed bug 38168 - if you created a biblio in the framework SR and then edited it again, the Settings menu would say you were in the Audio Cassettes, CDs framework, but the fields and tags would say you were in Default (easy check in MARC21 is that 001 and 003 are hidden in frameworks other than Default, so if you see them in the editor you are in Default). With the patch from bug 37947, the first time you edit a newly-created record, the editor opens in Default and the Settings menu says it is in Default, then every time after that the editor opens in the correct framework and the Settings menu agrees. Steps to reproduce: 1. Cataloging - New record -> Audio Cassettes, CDs 2. Fill in the required fields and save 3. Switch to 'Normal', Edit - Edit record 4. Note that 001 and 003 are visible, and the Settings menu has a checkmark by Default 5. Click the browser Back button, then Edit - Edit record 6. Note that 001 and 003 are not visible, and the Settings menu has a checkmark by Audio Cassettes, CDs Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37947 [Bug 37947] Import from Z39.50 doesn't open the record in editor -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 38076] New: Librarians with only fast add permission can no longer edit or create fast add records
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38076 Bug ID: 38076 Summary: Librarians with only fast add permission can no longer edit or create fast add records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If a librarian does not have the editcatalogue permission, but does have the fast_cataloging permission, they should be able to add and edit fast cataloging records. Instead they are presented with a login screen and the message that they do not have sufficient permissions. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 37946] New: Double menu when clicking the caret in Z39.50 search
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37946 Bug ID: 37946 Summary: Double menu when clicking the caret in Z39.50 search Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When importing a record via Z39.50, you have the possibility of either clicking anywhere to get the Marc/Card/Import menu, or clicking the caret button next the the MARC button. Right now, if you click on the caret, both menus appear. To recreate: 1. Go to Cataloging 2. Click on New from Z39.50/SRU 3. Make a search in the library of congress server for anything (I searched for author: shakespeare) 4. Next to one of the results, click the caret button next to the MARC button --> Two MARC/Card/Import menus appear -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 37947] New: Import from Z39.50 doesn't open the record in editor
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37947 Bug ID: 37947 Summary: Import from Z39.50 doesn't open the record in editor Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging 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: m.de.rooy(a)rijksmuseum.nl When importing a record from Z39.50, normally choosing "Import" opens the record in the basic editor. However, the record is not opening. To recreate: 1. Go to Cataloging 2. Click on New from Z39.50/SRU 3. Make a search in the library of congress server for anything (I searched for author: shakespeare) 4. Click on one of the results and choose Import --> The basic editor appears, but not the record I tried this in KTD as well as a sandbox with the same result. I tried different records (all from LOC and all with author: shakespeare) but they all do the same thing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 37542] New: Patron search is incorrectly parsing entries as dates and fetching the wrong patron if dateofbirth in search fields
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37542 Bug ID: 37542 Summary: Patron search is incorrectly parsing entries as dates and fetching the wrong patron if dateofbirth in search fields Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com When parsing patron search we try to convert the input into a date for searching against dateofbirth if included in defaultpatronsearchfields This can lead to odd values being converted to incorrect dates. To recreate" 1 - Create a patron with dateofbirth 1994-07-27 2 - Add dateofbirth to DefaultPatronSearchFields 3 - In patron or checkout search, type a cardnumber like '2908800092528' 4 - Note the patron with that birth date is found in autocomplete 5 - Open the browser console (F12) 6 - In the network tab, find the last request (or just remove and add a digit) 7 - Copy the URL from that request and paste into a text editor 8 - Search for 'dateofbirth' 9 - See that the entry has been converted to 1994-07-27 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 37499] New: Remove global variables from addbiblio.pl
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37499 Bug ID: 37499 Summary: Remove global variables from addbiblio.pl Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Depends on: 37429 addbiblio.pl contains a number of global variables. Some if not all of them are state variables that have no business being globals. We should refactor to scope these variables appropriately. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37429 [Bug 37429] Can't edit biblio records anymore (empty form) in 24.05 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 37429] New: Can't edit biblio records anymore (empty form) in 24.05
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37429 Bug ID: 37429 Summary: Can't edit biblio records anymore (empty form) in 24.05 Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)zefanjas.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl While cataloging new books the edit / add biblio form is sometimes empty. This happens also when I want to edit an existing biblio or import one via Z.39.50. Sometime I can add 5-10 new items before it happens, sometimes it happens after every new record. The only "fix" right now for me is to do a `service koha-common restart`. The log files don't show any error. To reproduce the issue: 1. Open an existing biblio (detail.pl) 2. Click "Edit record" 3. Change the framework (no need to change any details) 4. Change the framework back to the original one (no need to save anything) 5. Go back to the biblio overview page (detail.pl) 6. Click "Edit record" again → mask / form is empty -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 37892] New: Patron category 'can be a guarantee' means that same category cannot be a guarantor
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37892 Bug ID: 37892 Summary: Patron category 'can be a guarantee' means that same category cannot be a guarantor Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com Bug 12133 changed the way that these categories work. Before hand, a single category could be set up, and two patrons in that category could be set to have a guarantor/guarantee relationship. In upgrades, we are seeing that if this relationship is preexisting, patrons are unable to return items as we throw an exception: "Child cannot be a guarantor" I understand preventing the same patron from being a guarantor and a guarantee, however, is it correct that the same category cannot? We either need to: 1 - Add an update to fix or warn of this existing condition 2 - Remove this restriction -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 93

[Bug 36822] New: When creating a new patron via C4::Auth_with_ldap inserts 0000-00-00 for invalid updated_on
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36822 Bug ID: 36822 Summary: When creating a new patron via C4::Auth_with_ldap inserts 0000-00-00 for invalid updated_on Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: betka(a)illinois.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Relevant versions: OS: Ubuntu 22.04 Koha: 23.11.04-4 MySQL: 8.0.36-0ubuntu0.22.04.1 When using Auth_with_ldap, new borrowers that are created via LDAP have an updated_on date of 0000-00-00 00:00:00. Guessing this may be related to comments in https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18016 May also be a side effect of explicitly declaring a default_value of \"current_timestamp" for updated_on in Koha/Schema/Result/Borrower.pm. (Guessing no one else is still using LDAP to create accounts) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 66