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

[Bug 26639] New: Turn auto_savepoint ON
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26639 Bug ID: 26639 Summary: Turn auto_savepoint ON Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org We have been adding transactions a lot lately, and we have just found that we are expecting a behaviour that is not the one we have. Take a look at the code posted on bug 26518 comment 7. If we turn auto_savepoint on, we will get the behaviour we expect. This patch has been initially attach on bug 21684 comment 2, but then dropped. See also https://metacpan.org/pod/distribution/DBIx-Class/lib/DBIx/Class/Manual/Cook… -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 26529] New: Holds rules enforced incorrectly when not set at library level
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26529 Bug ID: 26529 Summary: Holds rules enforced incorrectly when not set at library level Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major 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 To recreate: 1 - Set ReservesControl to item home library 2 - confirm your circ rules allow holds at both the All Libraries and library-specific levels 3 - confirm Default checkout, hold and return policy is totally unset at both the All Libraries and library-specific levels 4 - place a hold on an item at Branch A for pickup at Branch A 5 - check item in, confirm hold triggers 6 - cancel hold 7 - go to Default checkout, hold and return policy for Branch A 8 - enter 1 for Total current checkouts allowed, save that with no other values entered 9 - re-place hold, confirm no error when placing hold 10 - check item in, hold does not trigger 11 - set Hold policy and Hold pickup library match at to Any Library at All Libraries level 12 - confirm hold still doesn't capture set Hold policy and Hold pickup library match at to Any Library for Branch A 13 - confirm hold now captures If these rules aren't set at the branch level we should be falling back to All Libraries. If they're not set anywhere, we should be assuming holds are allowed is the circ rules allow them. Starting from default testing docker data, this is what my db shows at step 7: MySQL [koha_kohadev]> select * from circulation_rules; +----+------------+--------------+----------+-------------------+------------+ | id | branchcode | categorycode | itemtype | rule_name | rule_value | +----+------------+--------------+----------+-------------------+------------+ | 1 | NULL | NULL | NULL | maxissueqty | 5 | | 2 | NULL | NULL | NULL | maxonsiteissueqty | 5 | +----+------------+--------------+----------+-------------------+------------+ And this is what it shows at step 8: MySQL [koha_kohadev]> select * from circulation_rules; +----+------------+--------------+----------+--------------------------+------------+ | id | branchcode | categorycode | itemtype | rule_name | rule_value | +----+------------+--------------+----------+--------------------------+------------+ | 1 | NULL | NULL | NULL | maxissueqty | 5 | | 2 | NULL | NULL | NULL | maxonsiteissueqty | 5 | | 8 | CPL | NULL | NULL | patron_maxissueqty | 1 | | 9 | CPL | NULL | NULL | returnbranch | | | 10 | CPL | NULL | NULL | hold_fulfillment_policy | | | 11 | CPL | NULL | NULL | patron_maxonsiteissueqty | | | 12 | CPL | NULL | NULL | max_holds | | +----+------------+--------------+----------+--------------------------+------------+ I cannot recreate this on master. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 35416] New: Advanced editor interface hang when trying to edit an existing catalogue record
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35416 Bug ID: 35416 Summary: Advanced editor interface hang when trying to edit an existing catalogue record Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: iming(a)rosewoodfarm.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 159288 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=159288&action=e… Screenshot Advanced editor interface hang when trying to edit an existing catalogue record. No problem editing using the standard editor. Switched to Advanced editor, you then get an egg timer with "Loading, please wait ..." message. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 20755] New: Allow separate email configuration for acq emails
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20755 Bug ID: 20755 Summary: Allow separate email configuration for acq emails Change sponsored?: --- Product: Koha Version: master 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 At the moment the emails in acuisistion (claims and orders) are sent with the email address of the librarian that triggers the sending. This is not practical in all cases for several reasons and it would be nicer if a general acquisition team email could be used. The development should allow to configure the email on library level with a from, replyto and returnpath address similar to the branchemail and it's options. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 34149] New: Syndetics cover images don't load in staff interface detail page in other images services are enabled
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34149 Bug ID: 34149 Summary: Syndetics cover images don't load in staff interface detail page in other images services are enabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 1. Turn on Syndetics 2. Set AmazonCoverImages to show 3. Go to a record detail page that has a Syndetics image but no Amazon image. In KTD I am using bib 181. 4. The image never loads. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 31575] New: Missing warning for holds where AllowHoldPolicyOverride can be used to force a hold to be placed
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31575 Bug ID: 31575 Summary: Missing warning for holds where AllowHoldPolicyOverride can be used to force a hold to be placed 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If some holds are overridable, and AllowHoldPolicyOverride is enabled, Koha used to "flag" each holdable item to let librarians know the hold could not normally be placed. In 22.05 up to current master as of this writing, no warning is displayed. Test Plan: 1) Set one circ rule to allow 0 holds 2) For Library A, set "Hold pickup library match" to "item's hold group" 3) Enable AllowHoldPolicyOverride 4) Set ReservesControlBranch to "item's home branch" 5) Create a record with an item for Library A, one for Library B, and one for Library C This should create a scenario where A's item cannot be held, and B and C's items must be overridden 6) Note you get the "Cannot place hold" but can place those holds anyway without a "warning" sign -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 35433] New: mark some strings as read-only
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '23

30 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35433 Bug ID: 35433 Summary: mark some strings as read-only Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: translate.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We could propagate a "do not translate this string!" flag up to Weblate. We only need to have a "#, read-only" line before the msgid https://docs.weblate.org/en/latest/admin/checks.html#custom-checks Which kind of strings would we want to mark as such? I have not tested yet but I would be willing to investigate if we have the need for it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '23

30 Nov '23

1 0

[Bug 34014] New: There is no way to fix records with broken MARCXML
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '23

30 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34014 Bug ID: 34014 Summary: There is no way to fix records with broken MARCXML Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl See bug 29697 and bug 23846 Koha currently catches an exception if the view is degraded in order to allow the staff to know there is a problem with the record. However, if the staff user tries to edit the record, we simply throw the exception and there is no way to recover. In other places we use StripNonXmlCharacters to get past encoding issues. We should do the same in the record editor. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 60

[Bug 33662] New: Improve visibility of acq advanced search
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '23

30 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33662 Bug ID: 33662 Summary: Improve visibility of acq advanced search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, oleonard(a)myacpl.org With the new staff design we now require 3 clicks to get to the advanced search in the acquisition module: * Switch to Orders search tab * Open additional options * Click on Advanced search link That's one click more than in earlier versions and it makes it hard to find the page in general. In the serials module we have opted to display the search form right on the start page, which got some positive feedback already. In acq the space is more limited, because we show the budgets/funds summary table. Maybe we could add a link to advanced search in the first section (vendor search) or the sidebar navigation? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25