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

[Bug 36488] New: Flatpickr creates invalid date entries
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36488 Bug ID: 36488 Summary: Flatpickr creates invalid date entries 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I believe that in some conditions flatpickr creates invalid date entries that can be saved. To test: * Switch DateFormat to DD.MM.YYY * Go to the OPAC self registration form * Enter a date of 00.00.000 * It will show as: 30.12.00-1 in the input and can be saved We have seen something similar on bug 36466. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 34175] New: Unable to delete certain tags in basic editor
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34175 Bug ID: 34175 Summary: Unable to delete certain tags in basic editor Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When editing a biblio in the basic editor, it is not possible to delete certain tags. It is possible to delete subject tags such as 600, 650, etc. But it is not possible to delete a blank 007 despite the icon for delete tag being present. If leaving a blank tag has no impact, then the delete tag icon should be removed. Otherwise, the delete tag ability should be enabled. It is confusing for it to be present if the tag should not be deleted. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 34330] New: Saving while leaving 942 $c blank (required field) in fast cataloging causes random redirection
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34330 Bug ID: 34330 Summary: Saving while leaving 942 $c blank (required field) in fast cataloging causes random redirection Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To replicate 1. Ensure fast add framework has at least two required fields. 245 $a Title and 942 $c item type 2. Go to cataloging module and fast cataloging 3. Choose a title already existing in the system in order to trigger a duplicate warning. 4. Enter a title only and leave 942 $c blank 5. Get a Duplicate record suspected warning with the option to Yes, edit exiting items or No, save as new record. Select No, save as new record. >From here random things happen depending on the permissions of the patron. If the patron has full cataloging permissions it will open a new Add MARC record blank form, skipping the warning about a blank required field. If the patron only has fast cataloging permission it will log the patron out of the system. What should happen in both cases is a block with a warning that the 942 $c is blank. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 34361] New: Search by date for invoices to close gives Error
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34361 Bug ID: 34361 Summary: Search by date for invoices to close gives Error Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: dch(a)interleaf.ie QA Contact: testopia(a)bugs.koha-community.org Since 22.11, in invoices.pl, if you search by date and then select one or more invoices to Close, you get Error 500. Template process failed: undef error - The given date (01/10/2019) does not match the date format (iso) at /usr/share/koha/lib/Koha/DateUtils.pm line 205. The invoice(s) are actually closed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 34874] New: Patron card creator: When creating a new batch, input box and label overlap
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34874 Bug ID: 34874 Summary: Patron card creator: When creating a new batch, input box and label overlap Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: oleonard(a)myacpl.org When creating a new patron card batch, the label of the input box for cardnumbers overlaps with the input box itself. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 34777] New: koha-restore could use a db-only option
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34777 Bug ID: 34777 Summary: koha-restore could use a db-only option Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz It might be nice for some users to have a koha-restore that doesn't try to restore everything in /var/lib/koha and /etc/koha/ and only does the database. While I realise that it is very easy to zcat backup.sql | sudo koha-mysql site, it's an elegant thing to wrap that in koha-restore as an option. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 36558] New: The placement of the Select button in Search for patron pop up window (while adding a guarantor)
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36558 Bug ID: 36558 Summary: The placement of the Select button in Search for patron pop up window (while adding a guarantor) Change sponsored?: --- Product: Koha Version: 22.11 Hardware: PC OS: Windows Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: irina.halminen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org Created attachment 164570 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=164570&action=e… Screenshot of the search results showing the Select button When searching for a guarantor in the Search for patron pop up window the Select (a patron) button is on the far right. Depending on the screen resolution/browser zoom level, the button is some cases out of view (requires scrolling to the right). If it was moved to the far left (before the Card column), there wouldn't be issues with different displays or browser zoom levels, and it would be more accessible to use. Url: cgi-bin/koha/members/search.pl?columns=cardnumber,name,category,branch,dateofbirth,address-library,action The information shown in the screenshot is from an anonymized version of Koha. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 36893] New: Shibboleth Login not honouring branch selector
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36893 Bug ID: 36893 Summary: Shibboleth Login not honouring branch selector Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: ryan.henderson(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org A client of ours has recently installed Shibboleth SSO into their staff client. They have asked us to help honour the branch selector on the staff login screen but Shibboleth is ignoring this from what we can see and is only logging staff into their default branches. We think this would be a nice enhancement to the authentication module, to help people login to their requested branches. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 30303] New: Add ability to select which values to retain when merging patrons
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30303 Bug ID: 30303 Summary: Add ability to select which values to retain when merging patrons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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 merging two patron records, one simply picks one record to retain values from. It would be helpful to have an interface more like what we see when merging biblio records, where one can select values from either pre-merge record to be retained post-merge. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61

[Bug 28530] New: Allow configuration of floating limits by item type
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28530 Bug ID: 28530 Summary: Allow configuration of floating limits by item type 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 return policy is set to Item Floats, it's possible for patron usage patterns to result in an imbalance in the collection -- more DVDs end up at Branch A and more books at Branch B. This can be especially troublesome when a given branch has limited shelving for a specific item type. I'd like to see a mechanism by which libraries can define a maximum count of items per item type to be allowed to float at a given branch. So, following my example above, Branch A could say that DVDs float when checked in but only up to 1000 items. If a DVD is checked in at Branch A and would be the 1001st DVD there, it instead transfers away. When some DVDs get checked out or transferred away, new returns will again be allowed to remain at Branch A. Setting the float limit to zero for a given item type and branch would make that item type always transfer away from that branch. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 242