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

[Bug 34174] New: Saving RIS results to Error 505
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '23

02 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34174 Bug ID: 34174 Summary: Saving RIS results to Error 505 Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: eugenegf(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org When exporting records to RIS in the OPAC as well as in the administration panel, it results to Error 505. In plack-opac-error-log, we are getting this error: [2023/06/30 22:30:04] [WARN] print() on closed filehandle _GEN_51 at /usr/share/koha/opac/cgi-bin/opac/opac-export.pl line 166. [2023/06/30 22:30:04] [WARN] print() on closed filehandle _GEN_51 at /usr/share/koha/opac/cgi-bin/opac/opac-export.pl line 179. [2023/06/30 22:30:04] [WARN] seek() on closed filehandle _GEN_51 at /usr/share/perl5/CGI/Emulate/PSGI.pm line 34. Also in plack-intranet-error-log, when trying out to export to RIS a particular record: [2023/06/30 22:29:21] [WARN] print() on closed filehandle _GEN_38 at /usr/share/koha/intranet/cgi-bin/catalogue/export.pl line 84. [2023/06/30 22:29:21] [WARN] print() on closed filehandle _GEN_38 at /usr/share/koha/intranet/cgi-bin/catalogue/export.pl line 87. [2023/06/30 22:29:21] [WARN] seek() on closed filehandle _GEN_38 at /usr/share/perl5/CGI/Emulate/PSGI.pm line 34. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 6819] Don't offer cancel order links for received order lines on basket summary
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6819 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=34469 -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 6729] Block received order lines from editing
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6729 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=34469 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. You are the QA Contact for the bug.

1 0

[Bug 34469] New: Modifying an order line of a standing order will delete linked invoice ID
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34469 Bug ID: 34469 Summary: Modifying an order line of a standing order will delete linked invoice ID Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: blocker 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 modifying a received order line from a standing order, the invoice id in the order line will be emptied out, leaving you with an order line that is complete, but not linked to an invoice (= inconsistent state, data loss) This cannot be resolved in the GUI, since you can't 'cancel receipt' for this order line, since it's not linked to an invoice any more. The only way to fix things is with SQL. And there is no way to find out which invoice the order line was originally received in. To test: * Create basket as standing order with items added in cataloguing * Add an order line * Receive shipment * Go to the basket summary page, click on 'Modify' * Change the actual cost * Save * Verify that the invoice is now empty * In the database aqorders.invoiceid will be NULL -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 33346] New: Add Help link to Koha manual in ERM module
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33346 Bug ID: 33346 Summary: Add Help link to Koha manual in ERM module 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: catrina(a)bywatersolutions.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com All other pages/modules in Koha show the Help button hyperlinked to the relevant portion of the manual. This link is missing throughout the ERM module and should be added in. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 34955] New: One Koha manual (to rule them all)
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34955 Bug ID: 34955 Summary: One Koha manual (to rule them all) 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: aude.charillon(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The Documentation team, at our meeting on 27 September 2023, voted to move from one manual per Koha version to one manual for all versions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 35454] New: A bad RENEWAL notice breaks the ability to renew items
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35454 Bug ID: 35454 Summary: A bad RENEWAL notice breaks the ability to renew items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Have an errouneous template in your RENEWAL notice. For example this template is missing an [% END %]: [% UNLESS borrower.branchcode == "ABC" %] The following items have been renewed: ---- <<biblio.title>> ---- 2. Have RenewalSendNotice set to 'Send' 3. Make sure a patron has the 'Item checkout' messaging pref set. 4. Checkout some items to that patron and try to renew them. 5. Nothing happens. 6. Fix the notice by adding the missing [% END %] 7. Now you can successfully renew. Bad templates should not complete break the ability to renew items. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 27667] New: Display the number of non-indexed records
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27667 Bug ID: 27667 Summary: Display the number of non-indexed records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr On "About Koha" page are displayed the numbers of indexed biblios and authorities with ES. It could be great if we could have comparison with the number of records in the database to display the number of non-indexed datas. We could have on the same page something like : Indices: koha_robin_biblios (count: 834999 on 1056480 = 221481 missing) Or on the "System information" tab with the other "Data problems". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[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