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

[Bug 34696] New: Leaving on screen keyboard enabled breaks advanced editor
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34696 Bug ID: 34696 Summary: Leaving on screen keyboard enabled breaks advanced 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 To recreate 1. Edit catalog record in Advanced Editor 2. Turn on the on screen keyboard with ctrl-shift-k 3. Select keyboard layout for French-azerty-1 4. Hit enter at the end of a tag line to add a new tag. 5. Enter tag number at start of new line. 6. Hit tab twice to add indicator spaces. Entering tab twice for the indicator spaces fails as the indicator underscores does not appear. Also the tab space amount is incorrect as it adds too many spaces and bypasses the normal start point for the first delimiter. A delimiter can be added, but it is in the incorrect place and shows as red. Having the onscreen keyboard enabled while editing allows for quick insertion of diacritics. It would be expected that enabling the keyboard would not interfere with the ability to edit the record. The current work around is to enable the keyboard and layout to select the correct diacritic to insert and then disable it to continue editing the record. This can be problematic when multiple diacritics need to be inserted. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 34929] New: Allow automatic removal of users from ERM agreements and licenses
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34929 Bug ID: 34929 Summary: Allow automatic removal of users from ERM agreements and licenses Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: holly(a)bywatersolutions.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Currently users must be manually removed from agreements and licenses in the ERM module. It would be more efficient to have an option to remove a user from any ERM agreements or licenses they are connected to when the ERM permission is disabled on that user's account. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 34262] New: Merging duplicate patrons in succession is adding previously merged duplicate
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34262 Bug ID: 34262 Summary: Merging duplicate patrons in succession is adding previously merged duplicate Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Merging duplicate patrons in succession is adding previously merged duplicates into the merge options. To Recreate: 1. Self-register Patron A multiple times through the OPAC. 2. Self-register Patron B multiple times through the OPAC. 3. Search for Patron A and merge some of the duplicates. 4. Search for Patron B and select some of the duplicates. On the next screen selected Patron B duplicates will be shown as well as the previously merged account of Patron A. 5. Select a Patron B account as the surviving record and proceed to merge. Patron B accounts are merged to the surviving record as well as Patron A's account, causing Patron A to no longer exist. The current work around is to log out of the staff account and log back in. This seems to clear the session data and allow the proper selections to appear, minus the previously merged account. However, this is not practical when needing to merge a lot of accounts. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[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 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