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

[Bug 37351] New: Using checkboxes on circ/aitingreserves.pl does not add them to cancellation list after changing to Page 2 or more of DataTable
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37351 Bug ID: 37351 Summary: Using checkboxes on circ/aitingreserves.pl does not add them to cancellation list after changing to Page 2 or more of DataTable Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cj.lynce(a)westlakelibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Steps to reproduce *Note for these steps to work, you must have enough holds waiting to necessitate a 2nd page of holds in circ/waitingreserves.pl 1. Log in to staff client 2. Place items on items for borrowers 2-1 Place enough holds as noted above 2-2 Trap holds for borrowers 3. Open Circulation->Holds Awaiting Pickup (circ/waitingreserves.pl) 4. Click a checkbox for one or mroe holds Note->The 'Cancel selected (0)' button changes to 'Cancel selected (1)', etc. 5. Cancel selected Holds using the (Cancel selected (#) button) 6. Confirm Cancellation 7. Wait for background processes to complete, then verify holds are cancelled. 8. Return to Open Circulation->Holds Awaiting Pickup (circ/waitingreserves.pl) 9. Ensure button shows "Cancel selected (0)" 10. Click "Next >" to navigate to page 2 of holds 11. Click a checkbox for one or more holds Note->The 'Cancel selected (0)' button DOES NOT increase as boxes are selected. 12. Cancel selected Holds using the (Cancel selected (#) button) 13. Confirm Cancellation 14. Wait for background processes to complete, then verify holds are cancelled. Note-> Holds were not cancelled The same behavior is reflected in the Holds waiting past their expiration date (Holds with cancellation requests not tested) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 38148] New: Unable to place OPAC holds and holds to pull list is empty
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38148 Bug ID: 38148 Summary: Unable to place OPAC holds and holds to pull list is empty Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This is due to Bug 29087, see comment 39 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 29087] New: Holds to pull list can crash with a SQL::Abstract puke
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29087 Bug ID: 29087 Summary: Holds to pull list can crash with a SQL::Abstract puke 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: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Opening the holds to pull list page can crash with the following logged error: SQL::Abstract::puke(): [SQL::Abstract::__ANON__] Fatal: SQL::Abstract before v1.75 used to generate incorrect SQL when the -NOT IN operator was given an undef-containing list: !!!AUDIT YOUR CODE AND DATA!!! (the upcoming Data::Query-based version of SQL::Abstract will emit the logically correct SQL instead of raising this exception) at /usr/share/koha/lib/Koha/Objects.pm line 145 I've traced this to Koha::Holds->get_items_that_can_fill(). Among other things, this routine fetches a list of item types that cannot fill holds, i.e., cases where the 'holdallowed' rule value is 'not_allowed'. However, if your default rule is to not allow holds, the @hold_not_allowed_itypes list will end up including an entry whose value is undef. When passed to the item query, doing the -not_in filter on itype will result in the crash listed above. A quick fix might be to filter out undef from that list. That will fix the crash, but could lead to incorrect results if the default policy is to deny holds for all item types except for ones that are going to be specifically permitted. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 56

[Bug 36985] New: 880 sub fields are not handled correctly in BuildSummary
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36985 Bug ID: 36985 Summary: 880 sub fields are not handled correctly in BuildSummary Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Mana-kb Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com CC: alex.arnaud(a)biblibre.com The variable 'subfields_to_report' is global in this function, and used for any 88x field, and picks up the last used subfields but really it should use the values from the field it is linked to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 35989] New: Searching Geographic authorities generates error
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35989 Bug ID: 35989 Summary: Searching Geographic authorities generates error Change sponsored?: --- Product: Koha Version: 23.11 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: rcooper(a)inceptlabs.com.au QA Contact: testopia(a)bugs.koha-community.org 1) Search Authorities from the main view (/cgi-bin/koha/authorities/authorities-home.pl) 2) From Authority type drop down select Geographic Name 3) Leave the search field blank 4) Run the search 5) The following error is returned : Error: Unmatched [ in regex; marked by <-- HERE in m/^[ <-- HERE ]$/ at /usr/share/perl5/MARC/Field.pm line 643. Notes: This also happens when searching for a or Australia, but not when searching for Japan When searching using the Authority Search pop-up, an Error 500 is returned. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 36815] New: Add the option to 'Reset to default' in the notices editor
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36815 Bug ID: 36815 Summary: Add the option to 'Reset to default' in the notices editor Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 15278 It would be nice to have the option to reset to the default notice text from the UI. This would allow for a reset to catch changes at upgrades or a reset for when you've installed a translation after the fact. I imagine a preview before reset might be helpful too? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15278 [Bug 15278] [Omnibus] Port default slips and notices from bespoke syntax to Template Toolkit -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 69

[Bug 36732] New: Add detail to the language selection system preferences to highlight the important of ordering
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36732 Bug ID: 36732 Summary: Add detail to the language selection system preferences to highlight the important of ordering Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 33237 Order matters ;P You can order the enabled languages in these system preferences.. the OPAC one is particular important as the order alters both the picker options order, the tab display order for translated notices and most importantly the first option in the list is the 'default' language of the system and is applied to the includes in default notices. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33237 [Bug 33237] If TranslateNotices is off, us the default language includes in slips -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 36733] New: It would be good to have a 'Print/Message in language' option in the UI
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36733 Bug ID: 36733 Summary: It would be good to have a 'Print/Message in language' option in the UI Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 33237 Sometimes you want to print or email a notice in a different language to that of the Patron.. it used to be that you could quickly change you're interface language but that's no longer the case. We should add 'language' where appropriate to buttons that allow you to print or queue a message/notice. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33237 [Bug 33237] If TranslateNotices is off, us the default language includes in slips -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 33237] New: If TranslateNotices is off, use the interface language includes in slips
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33237 Bug ID: 33237 Summary: If TranslateNotices is off, use the interface language includes in slips Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N 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: frederic(a)tamil.fr Most of our clients use Koha in one language only (French) and their patrons are also all french-speakers. So they don't use TranslateNotices, since they don't need to print slips in different languages. However, if TranslateNotices is off, the translations for "includes" (in my specific example, account types), are not taken into consideration and print in English. Same if TranslateNotices is on, but the patron's language is Default. In those cases, shouldn't it use the interface language rather than just print in English? To replicate: 1. Install the other language (i used fr-CA here) 1.1. gulp po:update fr-CA ./misc/translator/translate install fr-CA 1.2. In Administration > Global system preferences, search for language and check the added language 2. Create a manual invoice in a patron's account and pay it 3. From the Transactions tab, click 'Print' next to the payment line --> On the printed slip, the title is "Payment receipt" (OK) 4. Switch interface to other language 5. Redo step 3 --> On the printed slip, the title is still "Payment receipt" (not ok) 6. In Administration > Global system preferences, enable TranslateNotices 7. Go to Tools > Notices and slips > ACCOUNT_CREDIT and copy the content of the letter into all the languages 8. Redo step 3 (you should still be in the other language interface) --> On the printed slip, the title is still "Payment receipt" (not ok?) 9. Edit the patron's account and change the preferred language to the other language 10. Redo step 3 --> On the printed slip, the title is "Paiement receipt" (OK) On step 3, the account type is in English in the English interface (OK) On step 5, the account type is in English in the other interface, with TranslateNotices off, I feel like the slip should take the interface into account in this case for the include... On step 8, TranslateNotices is on, but the patron's language is Default, I feel like this should also take into account the interface language... On step 10, TranslateNotices is on and patron language is set, these are currently the only settings which allow to have the accounttypes in the other language. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 90

[Bug 36708] New: Problems editing circ rules when 'Holds allowed (total)' value is greater than or equal to 0
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36708 Bug ID: 36708 Summary: Problems editing circ rules when 'Holds allowed (total)' value is greater than or equal to 0 Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If I edit a circulation rule with a value of 0 or higher in the 'Holds allowed (total)' column, Koha is populating the 'No automatic renewal after (hard limit)' with a date when it was/should remain blank for editing. Also, the value in 'Holds allowed (total)' isn't populating in the editing line. To replicate: -Find or create a circulation rule with a 'Holds allowed (total)' limit of 3 (or another number) and no value in 'No automatic renewal after (hard limit)' -Select to edit the rule, and note that 'No automatic renewal after (hard limit)' box in the editing line is now populated with a date -Note also that 'Holds allowed (total)' is empty in your editing line -If you save your edits without clearing the new 'No automatic renewal after (hard limit)' date, it will save as part of the rule. Also, 'Holds allowed (total)' will save as Unlimited unless you re-add your numerical value. This happened when I tested with multiple numbers including 0. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25