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

[Bug 21348] New: Add ability to export and import plugin data
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '24

26 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21348 Bug ID: 21348 Summary: Add ability to export and import plugin data Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We could possibly add a way to download a specific plugin's data from plugin_data in some arbitrary file format, and also add a facility to re-insert that data back into the plugin_data table. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 21309] New: Add flag to change password
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '24

23 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21309 Bug ID: 21309 Summary: Add flag to change password 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We should add a flag to patron accounts that, if checked, would require the patron to sign in to their account and change their password. This option could incorporate the following functionality: * Allow patron to sign in with old password then prompt for a new password. * E-mail patron notifying them with the need to change. * When active, it would block checkouts and sip authentication until done. * Anytime a password is changed in the account, whether staff side or opac, the change would clear the flag in the patron account. * Date of change should be time stamped. Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 26681] New: Clone the buttons for 'Add Item', 'Add & Duplicate' and 'Add Multiple Copies of this Item' to top of item form on additem.pl
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '24

23 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26681 Bug ID: 26681 Summary: Clone the buttons for 'Add Item', 'Add & Duplicate' and 'Add Multiple Copies of this Item' to top of item form on additem.pl Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Sometimes I only need to make a quick edit to an item record but then I have to scroll all the way down to the bottom of the form to click the add item/save button. It would be helpful if the 'Add Item', 'Add & Duplicate' and 'Add Multiple Copies of this Item' buttons that appear at the end of the form could also be included at the top of the form because it would save unnecessary scrolling and make cataloging more efficient. Our solution at the moment is to use this jQuery: $("#cat_additem.cat #addsingle").clone().insertAfter('#additema'); $("#cat_additem.cat #add_multiple_copies").clone().insertAfter('#addsingle'); $("#cat_additem.cat #f > fieldset.action").clone().insertAfter('#edititem'); -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 30052] New: When adding a 'New child record' the 773 field is not pre-populated in advanced editor
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '24

23 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30052 Bug ID: 30052 Summary: When adding a 'New child record' the 773 field is not pre-populated in advanced editor 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 To recreate: 1 - Enable Advanced Cataloging Editor 2 - Edit a record and confirm you are using, or switch to advanced editor 3 - From an existing record Click 'New->New child record' 4 - Fill in required fields and save 5 - Record is not linked to parent -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 29830] New: Superlibrarian unable to delete patron list
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '24

22 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29830 Bug ID: 29830 Summary: Superlibrarian unable to delete patron list Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: jendayi30(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I'm currently unable to delete patron lists that someone else has created even though I have superlibrarian privileges. I am able to delete patron lists that I originally created, but not patron lists that someone else has created. As superlibrarian, I should have the ability to delete all patron lists on our system, if needed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 20307] New: Language overlay for authorized values
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '24

21 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20307 Bug ID: 20307 Summary: Language overlay for authorized values Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement 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 Depends on: 14100 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14100 [Bug 14100] Add base to make item types, branch names, sysprefs values and authorised values translatable -- You are receiving this mail because: You are watching all bug changes.

1 145

[Bug 32202] New: Remove kohalib.pl from recall cronjobs
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '24

21 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32202 Bug ID: 32202 Summary: Remove kohalib.pl from recall cronjobs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Depends on: 29734 >From misc/cronjobs/recalls/expire_recalls.pl and misc/cronjobs/recalls/overdue_recalls.pl: +BEGIN { + # find Koha's Perl modules + # test carefully before changing this + use FindBin; + eval { require "$FindBin::Bin/../kohalib.pl" }; +} As Jonathan pointed out on bug 19532 this should not longer be used, as kohalib.pl has been removed with bug 28617. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29734 [Bug 29734] [OMNIBUS] Recalls for Koha -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 31368] New: Koha::Recalls->add_recall should throw exceptions
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '24

21 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31368 Bug ID: 31368 Summary: Koha::Recalls->add_recall should throw exceptions Change sponsored?: --- Product: Koha Version: unspecified 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It instead returns undef. We should change this and properly handle exception cases. One remarkable example is missing mandatory parameters. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 30292] New: Link recall to checkout
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '24

21 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30292 Bug ID: 30292 Summary: Link recall to checkout Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When patron biblio-level recall is issued, and an item/checkout combination is chosen to proceed with the actual checkout, we should store the checkout_id. This way we would avoid guessing the right checkout. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31369] New: Koha::Recalls->add_recall should validate there's a related checkout
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '24

21 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31369 Bug ID: 31369 Summary: Koha::Recalls->add_recall should validate there's a related checkout Change sponsored?: --- Product: Koha Version: unspecified 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I haven't really tried, but the code cleary relies on an $recall->checkout returning a Koha::Checkout object... Which shouldn't be taken for granted. The way it is constructed is fragile and makes the controller need to perform all the checks, that really belong here. It should probably throw an exception as well. Right now the code can generate a recall object (store it on the DB) and then explode because of the lack of the checkout. This also points to the need of a transaction. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3