July 2024 - Koha-bugs - lists.koha-community.org

[Bug 37259] New: Upgrade database error -24.05.01
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '24

05 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37259 Bug ID: 37259 Summary: Upgrade database error -24.05.01 Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: vivek.yadava(a)pnguot.ac.pg QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 168526 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=168526&action=e… Error Web installer › Updating database structure Update errors : Upgrade to 23.06.00.061 [13:50:36]: Bug 29002 - Add bookings table ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 5 at /usr/share/koha/lib/C4/Installer.pm line 741 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #113 from David Nind <david(a)davidnind.com> --- Thanks Thibaud! I'm still getting this error for steps 5 and 6: DBIx::Class::Row::store_column(): No such column 'has_priority' on Koha::Schema::Result::CirculationRule at /kohadevbox/koha/Koha/Object.pm line 81 at /usr/share/perl5/DBIx/Class/Exception.pm line 77 I thought that it may be because when running dbic, it ends with this: Dumping manual schema for Koha::Schema to directory ./ ... DBIx::Class::Schema::Loader::make_schema_at(): Checksum mismatch in './/Koha/Schema/Result/CourseItem.pm', the auto-generated part of the file has been modified outside of this loader. Aborting. If you want to overwrite these modifications, set the 'overwrite_modifications' loader option. However, I get that as well running dbic without the patch. So maybe an issue with KTD? I also tried running dbic --force - I no longer got the error at the end when running dbic, however the error for steps 5 and 6 still occurs. Testing notes so far (using KTD): 1. Clone the rules that apply to all libraries to Centerville. 2. Edit the Centerville All All rule to change both "Current checkouts allowed" and "Current on-site checkouts allowed" to 3. 3. For the "Standard rule for all libraries", change both "Current checkouts allowed" and "Current on-site checkouts allowed" to 2. 4. With the library set to Centerville, check out three items to Mary. Try to check out a fourth item - you get a message: Please confirm checkout Too many checked out. 3 checked out, only 3 are allowed. Maximum checkouts calculated from the circulation rule for Item type: All item types Patron category: All patron categories Library: Centerville Yes, check out (Y) No, don't check out (N) 4. Change the library to Midway and try to check out another item - you get this message: Please confirm checkout Too many checked out. 3 checked out, only 2 are allowed. Maximum checkouts calculated from the circulation rule for Item type: All item types Patron category: All patron categories Library: All libraries Yes, check out (Y) No, don't check out (N) 5. Apply the patch 6. Update the database: updatedatabase 7. Run dbic: dbic 8. Clear the cache: flush_memcached 9. Restart everything: restart_all 10. Clear your browser cache. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35386] New: Renewals via the API are recorded using the branch of the API account used
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35386 Bug ID: 35386 Summary: Renewals via the API are recorded using the branch of the API account used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com CC: tomascohen(a)gmail.com When renewing items via the API Koha records the branch of the renewal as the branch of the account that is signed in to the API. For outside service (Aspen, Communico) they may have a single API account that represents all user interactions. While this behavior may not be technically incorrect, it should be configurable like OpacRenewalBranch - allowing the library to decide which branch is recorded in the statistics table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 36505] New: Cannot update patron attributes via PUT reuqst on Patrons endpoint
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36505 Bug ID: 36505 Summary: Cannot update patron attributes via PUT reuqst on Patrons endpoint Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com CC: tomascohen(a)gmail.com According to our docs, you can include an array of patron attributes on a patrons PUT request: https://api.koha-community.org/Development.html#tag/patrons/operation/updat… When testing I sent: {"category_id":"PT","library_id":"CPL","surname":"Ballard","extended_attributes":[{"extended_attribute_id":"1","type":"SHOW_BCODE","value":"0"}]} And I got an error: [2024/04/03 17:27:40] [ERROR] PUT /api/v1/patrons/21: unhandled exception (Koha::Exceptions::Object::PropertyNotFound)<<No property extended_attributes for Koha::Patron>> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 33036] New: REST API: Merge biblio records
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33036 Bug ID: 33036 Summary: REST API: Merge biblio records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliothek(a)th-wildau.de CC: tomascohen(a)gmail.com Related to the ongoing development of biblios API, what about an endpoint to merge existing biblios including items and acquisition data as the intranet already offers. Possible params should be - biblionumber_to_remain that remains - biblionumber_to_merge which will be merged into biblionumber_to_remain - optional MARCXML that represents the remaining biblio If no MARCXML is delivered the merge should take the MARCXML from the remaining biblio as reference. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 76

[Bug 34082] New: Cut some redundancy in OPAC JavaScript string translations
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34082 Bug ID: 34082 Summary: Cut some redundancy in OPAC JavaScript string translations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 34035 A few templates in the OPAC still define a string in one place and then use the string in another. If the string is used only once I don't think it's necessary to separate the definition from the use. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34035 [Bug 34035] Move translatable strings out of opac-bottom.inc: Tags -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 36443] New: Add
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36443 Bug ID: 36443 Summary: Add Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 36739] New: Unable to delete a budget
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36739 Bug ID: 36739 Summary: Unable to delete a budget Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I'm unable to delete a budget that has no funds, even with superlibrarian privileges. To recreate: 1. Go to Administration > Budgets 2. Click New budget 3. Enter a start and end date, a name and an amount (For the test, I entered April 1st, 2024 to April 30, 2024, named the budget "April", and gave it an amount of 100) 4. Click Save 5. Go to Inactive budgets 6. Click Actions next to the budget and choose the Delete option 7. Click Yes, delete 8. Go to Inactive budgets --> The budget is still there -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 35062] New: addbiblio: Allow a framework plugin to add class to prevent submit during ajax call
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35062 Bug ID: 35062 Summary: addbiblio: Allow a framework plugin to add class to prevent submit during ajax call Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I have a plugin that does a REST API call wrapped in an ajax construct: jQuery.ajax({ rest api stuff }).done(function() ...).fail(function() ...); Rapidly clicking Save (while the ajax is triggered by the Change event) lets the plugin shortly show an error before the form submits. Which is obviously undesirable. If we would replace this in addbiblio.tt: var onOption = function () { - return Check(); + if ( $('.plugin-blocks-submit').length==0 ) return Check(); } We can conditionally and temporarily block submittal. When the change event of the plugin fires, I add class plugin-no-submit to the html element involved. In the done and fail functions I remove the class again from the element. This effectively works. While several other approaches in addbiblio failed. (Removing the event handler is just too late.) This is a one-liner that will do the job. On bug 34860 I will still submit a ISBN/ISSN plugin using this class that will demonstrate its use. In the meantime this is a harmless check. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 36151] New: Update leaflet.js to current version
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '24

04 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36151 Bug ID: 36151 Summary: Update leaflet.js to current version 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: domm(a)plix.at QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Koha comes with leaflet.js 1.0.3 which is quite old. We need a current leaflet for Bug 31652, so we propose to upgrade to the current version 1.9.4 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26