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

[Bug 32481] New: Rabbit times out when too many jobs are queued and the response takes too long
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481 Bug ID: 32481 Summary: Rabbit times out when too many jobs are queued and the response takes too long Change sponsored?: --- Product: Koha Version: master 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We saw this happen several times - a library would queue up 6 batch modifications that would take roughly 6 minutes each. The jobs would process normally, until the 30 minute configured timeout would hit - then the remaining job would fail, and rabbit would disconnect and not reconnect, and jobs would pile up It seems that koha receives all of the jobs immediately, but only acknowledges when complete - so the final job was waiting over 30 minutes for acknowledgement and this caused issues -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 52

[Bug 33028] New: The decimal separator 'comma' and its consequences on the calculation of fines (crons)
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33028 Bug ID: 33028 Summary: The decimal separator 'comma' and its consequences on the calculation of fines (crons) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hello @ll, I hesitate between 'fines and fee' section or 'cron' so don't move it if you think that's better in cron section.. When currency format is set on FR commas are decimals separators but when cron like fines.pl try to calculate fines it's fails due to this format. I know there is a lot of discussion around this behavior and decimal separator by 'countries'.. like bug 12310 and bug 21507 but I would like to propose this patch to solve at least the behavior on the fine calculations related to cronjob 'fines.pl' which will use some circulation rules and therefore their formatting is important if you want to make calculations with -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 129

[Bug 34558] New: Update custom.sql for it-IT webinstaller
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '23

17 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34558 Bug ID: 34558 Summary: Update custom.sql for it-IT webinstaller Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: ztajoli(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With new developments about transaltion, the file ../installer/data/mysql/localization/it-IT/custom.sql needs an update. Today, when you install a 23.05 version with Italian setup (it-IT), you will see a warning about problems with Authorised values (AV). We need to fix it and update the file. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 33819] New: Accessibility: More description required in opac search breadcrumbs
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '23

17 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33819 Bug ID: 33819 Summary: Accessibility: More description required in opac search breadcrumbs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org A report carried out for the British museum by the Shaw trust has identified that the "Search results for" breadcrumb on the opac search results page is not descriptive enough and should include the page number to assist screen readers with understanding the page content. Currently the breadcumb is the same on every page and it needs to be more unique to the page content. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 26558] New: Guarantor information is lost when an error occurs during new account creation
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '23

17 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26558 Bug ID: 26558 Summary: Guarantor information is lost when an error occurs during new account creation Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce: 1. Create a new account but cause an error that will keep the account from saving (enter the wrong age for a category or give the patron a username that's already being used) 2. Search for and select a guarantor 3. Try to save the account and wait for the "The following fields are wrong. Please fix them." message 4. Note that the guarantor information is gone and you need to search for and select the guarantor again -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 33074] New: ReservesControlBranch not taken into account in opac-reserve.pl
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '23

17 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33074 Bug ID: 33074 Summary: ReservesControlBranch not taken into account in opac-reserve.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Hold requests Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In opac-reserve.pl there is this line: my $rule = GetBranchItemRule( $patron->branchcode, $type ); $patron->branchcode should be replaced by the result of GetReservesControlBranch Test plan: 1. Set system preferences: - Disable OPACAllowUserToChooseBranch - Set ReservesControlBranch to "item's home library" - Enable UseBranchTransferLimits - Set BranchTransferLimitsType to "item type" - Enable canreservefromotherbranches - Disable IndependantBranches 2. Create two libraries: ITEM_LIB and PATRON_LIB 3. Set circulation rules: - Remove all circulation rules (DELETE FROM circulation_rules) - Set a default rule that allow some holds and with "OPAC item level holds" = "force". Allow "on shelf" holds for easier testing. - In the rules for ITEM_LIB, under "Default checkout, hold and return policy", - set "Hold policy" to "From any library" - set "Hold pickup library match" to "item's home library" - In the rules for PATRON_LIB, under "Default checkout, hold and return policy", - set "Hold policy" to "From any library", - set "Hold pickup library match" to "any library" 4. In "Library transfer limits" disable all transfers from ITEM_LIB to PATRON_LIB for an item type (let's say "BOOK") 5. Create a biblio with an item: - item type must be the same as in previous step ("BOOK") - home branch and holding branch must be ITEM_LIB 6. Create a patron at PATRON_LIB, give it a password so it can log in. 7. Go to OPAC, and login with this patron 8. Try to place a hold for the new item. You should be allowed to place a hold, but when doing it, no holds will be created. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 34457] New: Add card number to hold details page
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '23

17 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34457 Bug ID: 34457 Summary: Add card number to hold details page 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: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Adding the patron's cardnumber to the Hold details page can help libraries verify whether they are placing the hold for the correct patron. Especially if they have several patrons with the same or similar name. /cgi-bin/koha/reserve/request.pl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 34511] New: Typo in manage_staged_records permission description
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '23

17 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34511 Bug ID: 34511 Summary: Typo in manage_staged_records permission description Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com While translating, I noticed there is a typo in the description of the manage_staged_records permission. All other permission descriptions are in the present tense, but this one is in the past tense. Managed staged MARC records, including completing and reversing imports (manage_staged_marc) For example, compared to Stage MARC records into the reservoir (stage_marc_import) To recreate: 1. Go to any patron record 2. Click More > Set permissions 3. Click Show details next to the Use all tools permission --> Notice all descriptions start with a present tense verb except Managed staged MARC records A simple slip of the finger! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 33395] New: Patron search results shows only overdues if patron has overdues
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '23

17 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33395 Bug ID: 33395 Summary: Patron search results shows only overdues if patron has overdues Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When you search for patrons, in the results table, there is a Checkouts column. If the patron has no checkouts, it shows 0 / 0 (0 overdues / 0 total checkouts). If the patron has checkouts but no overdues, it shows, for example, 0 / 1 (0 overdues / 1 total checkout). If the patron has only overdues, it shows, for example, only 1 in red (1 overdue ?? total checkouts?). If the patron has checkouts and overdues, it shows, for example, only 1 in red also (1 overdue ?? total checkouts?) It's like if there are overdues, the number of checkouts disappear. To replicate: 1. Make sure SpecifyDueDate is enabled 2. Have 4 patrons (I used 4 patrons with B last names to see them all in one go) 3. Checkout items as follows - Checkout 1 item normally to Patron A - Checkout 1 item to Patron B, specifying a due date in the past - Checkout 1 item normally and 1 item with a past due date to Patron C - Nothing to Patron D 4. Go to Patrons and search for the patrons, making sure there are more than one results --> In the results table, the Checkouts column is like this Patron A: 0 / 1 Patron B: 1 (red) Patron C: 1 (red) Patron D: 0 / 0 For Patron B, it should be (I think?) 1 / 1 For Patron C, it should be (I think?) 1 / 2 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 21812] New: When adding items while ordering, the quantity field should not look like it can be edited
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '23

17 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21812 Bug ID: 21812 Summary: When adding items while ordering, the quantity field should not look like it can be edited Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement 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 adding items during creating the order in acquisitions, the quantity field cannot be edited, you have to use the item form and table above for increasing and decreasing the amount of items ordered. This if often misunderstood in traning, in part because the input field looks like it can be edited, when it's actually read-only. It would be nice if this could be improved, maybe even with a hint to use the form above. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2