February 2025 - Koha-bugs - lists.koha-community.org

[Bug 37016] New: SIP2 renew shows old/wrong date due
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '25

18 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37016 Bug ID: 37016 Summary: SIP2 renew shows old/wrong date due Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org This was reported by a library running 23.11.03. Sometimes when patrons do renewals via SIP2, the old due date is reported as the new due date. But everything else looks OK, including the staff view and "my profile", which shows the right due date. It looks like this only happens some of the time, or for some patrons, but I have not been able to figure out what the difference is there. I do think I have spotted the problem, though. C4::Circulation::AddIssue() has this code: 1552 my $issue; ... 1571 # find which item we issue 1572 my $item_object = Koha::Items->find({ barcode => $barcode }) 1573 or return; # if we don't get an Item, abort. 1574 my $item_unblessed = $item_object->unblessed; 1575 1576 my $branchcode = _GetCircControlBranch( $item_object, $patron ); 1577 1578 # get actual issuing if there is one 1579 my $actualissue = $item_object->checkout; 1580 1581 # check if we just renew the issue. 1582 if ( $actualissue and $actualissue->borrowernumber eq $patron->borrowernumber 1583 and not $switch_onsite_checkout ) { 1584 $datedue = AddRenewal( 1585 { 1586 borrowernumber => $patron->borrowernumber, 1587 itemnumber => $item_object->itemnumber, 1588 branch => $branchcode, 1589 datedue => $datedue, 1590 lastreneweddate => 1591 $issuedate, # here interpreted as the renewal date 1592 } 1593 ); 1594 $issue = $item_object->checkout; 1595 } We get the $item_object on line 1572. Then we get the active issue/loan/checkout from the $item_object on line 1579. Renewal is done on line 1584 (and testing shows $datedue has the right date due there). But then we update $issue with the active issue/loan/checkout from the same $item_object as earlier, which has not been updated, and contains stale data, including the original date due. I was able to quickfix this by replacing line 1594 with this: my $updated_item_object = my $item_object = Koha::Items->find({ barcode => $barcode }); $issue = $updated_item_object->checkout; But I am far from confident that this is a good fix, so opinions are welcome! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 26653] New: Allow editing of item notes on moredetail.pl with circulation permission
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '25

18 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26653 Bug ID: 26653 Summary: Allow editing of item notes on moredetail.pl with circulation permission 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If a user has circulation permissions, they can edit the lost/damaged/withdrawn statuses of an item on moredetail.pl (the items tab in the catalog). However, they cannot edit the public and non-public notes for that item. Those notes are only editable on this if one also has edit_items permission, which opens up a lot more actions. I feel the editing of these notes from moredetail should also fall under circulation permissions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31603] New: Add search option for plugin page
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '25

18 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31603 Bug ID: 31603 Summary: Add search option for plugin page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be great to add a search box on this page /plugins/plugins-home.pl to allow users to search the installed plugins. Steps to recreate go to administration click on manage plugins -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 15789] New: Split borrowers permission into create/edit
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '25

18 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15789 Bug ID: 15789 Summary: Split borrowers permission into create/edit Change sponsored?: Seeking cosponsors Product: Koha Version: master Hardware: All URL: http://devs.bywatersolutions.com/projects/fine-overrid es/ OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Goal: Add ability to control if an individual staff user can override checkout restriction based on noissuescharge Work to be done: 1) Add new permission allow_fine_override 2) Set new permission for existing staff members with setting for AllowFineOverride 3) Remove use of AllowFineOverride, replace with use of new permission allow_fine_override Looking for sponsors here: http://devs.bywatersolutions.com/projects/fine-overrides/ -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 36975] New: Allow MarcModificationTemplates to change the record source for a batch of records
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '25

17 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36975 Bug ID: 36975 Summary: Allow MarcModificationTemplates to change the record source for a batch of records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be nice to be able to set the record source for a whole set of records (from a search result or a report). Best way to do it seems to permit the "BatchRecordModification Tool" to change the record source value. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 22861] New: Add ability to turn on/off the display of a public list
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '25

17 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22861 Bug ID: 22861 Summary: Add ability to turn on/off the display of a public list Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- Libraries use the Public List feature a lot for patrons to see them on the OPAC. It would be very nice to allow staff to disable/enable these public lists -as the Course Reserve module does -as needed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 19917] New: Holds for self registered patrons
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '25

17 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19917 Bug ID: 19917 Summary: Holds for self registered patrons Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 There needs to be a switch in place that does not allow a hold to be triggered if the hold is for a patron in the self registered category. Our library workflow: * Allows self registered patrons to place a couple of holds. * Doesn't assign an automatic card number. * Prints specialized hold slips * Allows self pickup Ideally, we would want the preference to not trigger the hold if the self registration category is in use on the patron with the hold, and a message to come up asking staff to go ahead and assign a card number, or something to that effect. Right now, when the hold is triggered, the slip comes out wrong because there is data missing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 38580] New: Correct the descriptions of the Babelthèque system preferences
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '25

17 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38580 Bug ID: 38580 Summary: Correct the descriptions of the Babelthèque system preferences Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Documentation 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: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de In the Enhanced content chapter, the descriptions for Babeltheque_url_js and Babeltheque_url_update don't match what is in the interface. These changes date back to bug 25630 (20.11), so nothing new or that we need to keep in the context of the "one manual". Maybe check the other sysprefs affected by bug 25630 to make sure they are correctly represented in the manual. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 20575] New: Auto-renewals to use current patron category when renewing as opposed to when item was issued.
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '25

17 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20575 Bug ID: 20575 Summary: Auto-renewals to use current patron category when renewing as opposed to when item was issued. Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Increasing the functionality of the Auto=-renewal process to have Koha look at the circulation and fine rule table at time of renewal instead of keeping the same circ and fine rules when the item was issued. If a patron category has been changed during when an item has been checked out the patron, this is not reflected in the auto-renewal process. For example, if a student is allowed to auto renewal items but they are changed to a different patron category who can not auto-renewal-Koha will still allow the auto-renewal given the rules were set when the item was checked out. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 36205] New: Plugins should be able to create permissions
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '25

16 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36205 Bug ID: 36205 Summary: Plugins should be able to create permissions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Some plugins expose additional functionality that should only be exposed to users with permission to access them. We could perhaps allow plugins to add sub-permissions to the existing 'plugins' flag to facilitate this? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10