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

[Bug 21641] New: Software error when checking out an item with a charge associated with it
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '22

11 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21641 Bug ID: 21641 Summary: Software error when checking out an item with a charge associated with it Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When you try to check out an item with a charge associated with it the following error is thrown as the C4::Circulation->AddIssuingCharge() is executed: Undefined subroutine &C4::Circulation::getnextacctno called at /home/vagrant/kohaclone/C4/Circulation.pm line 3194 The getnextacctno function is in C4::Accounts. This module is in a use pragma at the top of C4/Circulation.pm -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 23222] New: Fix DISABLE/ENABLE plugin label in plugins home
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '22

11 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23222 Bug ID: 23222 Summary: Fix DISABLE/ENABLE plugin label in plugins home Change sponsored?: --- Product: Koha Version: master 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: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Fix bug introduced in bug 21073 When you install a plugin, it shows as disables, even though it's enabled in database. Before 21073 that flag was called "enabled", after that bug it is called "is_enabled", but tt was never updated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 24083] New: Koha should support "seen" vs "unseen" renewals
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24083 Bug ID: 24083 Summary: Koha should support "seen" vs "unseen" renewals Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When carrying out a renewal transaction Koha should check for both the maximum number of renewals allowed and also the number of unseen renewals. If it finds a value equal to or greater than the number of renewals already carried out against that loan, it prevents the renewal. The purpose of this is to prevent borrowers from continually renewing a book when they have, in fact, lost or misplaced it! When a renewal takes place via a method that doesn't require visible sight or possession of the item (e.g. OPAC, automatic renewal) then the number of unseen renewals for that item should be incremented. SIP2 renewals can be considered seen since they will require the physical item to be scanned. The number of allowed unseen renewals before a renewal is denied should be specifiable in the circulation rules. If a renewal is denied due to the unseen maximum having been reached, the flow should be the same as when a renewal limit has been reached, though with appropriate messages displayed to the user. It should be possible to override the denial in the same was as when a renewal limit is reached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 186

[Bug 23971] New: Add logging for basket relation actions
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23971 Bug ID: 23971 Summary: Add logging for basket relation actions 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: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Acquisitions currently creates no action_logs. Some of our customers are requesting the addition of logs. The first stage of this work is to add the following logging: 1. Who created a basket and when Basket number, Basket name, Creation date, Vendor name, Creator name 2. Who edited a basket and when Basket number, Basket name, Edited date, Vendor name, Editor name 3. Who approved a basket and when Basket number, Basket name, Approval date, Vendor name, Who approved 4. Who closed a basket and when Basket number, Basket name, Closed date, Vendor name, Who closed (all should include EDI order information) This bug is related to Bug 13325, which requests logging of fund related actions -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 187

[Bug 22244] New: Typo in Mana Knowledge Base message
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22244 Bug ID: 22244 Summary: Typo in Mana Knowledge Base message 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: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- There is a typo in the message "You haven't decided if you want to activate Mana Knowlede Base, please let us know by clicking" The word "Knowledge" is misspelt -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 22169] New: ill-requests.tt failing QA test
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22169 Bug ID: 22169 Summary: ill-requests.tt failing QA test Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Target Milestone: --- The id and class attributes on the body tag are causing: not ok 2 - <body> tag with id and class attributes # Failed test '<body> tag with id and class attributes' # at xt/tt_valid.t line 91. # Files list: # intranet-tmpl/prog/en/modules/members/ill-requests.tt: 16 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 21900] New: intranet_catalog_biblio_enhancements_toolbar_button plugin hook broken
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21900 Bug ID: 21900 Summary: intranet_catalog_biblio_enhancements_toolbar_button plugin hook broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Commit 1a0172a253e5432e5eef862768aaacb3463501f2 broke the display of buttons provided by plugins making use of the intranet_catalog_biblio_enhancements_toolbar_button hook. The addition of the html filter breaks the ability of the browser to parse the HTML provided by the plugin, the $raw filter needs to be used instead. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 21679] New: Software error when placing a hold on an item with a charge associated with it
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21679 Bug ID: 21679 Summary: Software error when placing a hold on an item with a charge associated with it Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When you try and place a hold on an item with a charge associated with it, the hold fails with the error: Undefined subroutine &C4::Reserves::getnextacctno called at /usr/share/koha/C4/Reserves.pm line 574. The getnextacctno function is in C4::Accounts. This is exactly the same issue as bug 21641 and should be resolved in the same way. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 20923] New: Merging backend status graph into main status graph incorrect use of grep
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20923 Bug ID: 20923 Summary: Merging backend status graph into main status graph incorrect use of grep Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com When the Illrequest object is being constructed, it consults the status graphs for enabled backends. These status graphs are then merged into the main graph in order to provide the full workflow for a request. As part of this process, the "next_actions" property is updated to reflect any new statuses. During this, a check is performed to determine if the status graph knows about the next status being declared by a backend status graph: if ( grep $prev_action, @core_status_ids ) { This is incorrect. According to http://perldoc.perl.org/functions/grep.html, the first parameter should be a block or expression, here we are passing a string. This malfunctions in so much as passing "REQ" with match twice in the following array [ "REQ", "REQREV" ], this is not what we would expect. The fix is to substitute the following line: if ( grep /^$prev_action$/, @core_status_ids ) { -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 20917] New: Improve email functionality relating to ILL requests
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20917 Bug ID: 20917 Summary: Improve email functionality relating to ILL requests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com The ILL module has the ability to send emails containing details of requests to "partner" libraries. This functionality, though currently in the core ILL code, is actually only required by the "FreeForm" backend. It is surfaced in the UI as a form containing an email template and a multi-select to select the partners who will receive the email. The email functionality offered by ILL, though functional, is lacking in some important respects, which this bug proposes addressing. Proposed enhancements, which are all inter-related, are: - Move emailing functionality from the core ILL module to the FreeForm backend where it is actually used - Email is sent independently of the Koha message queue, which is understood to be undesirable, this should be addressed - As such, there is no ability for users to specify a default message template, using the Notices and Slips module, this should be addressed - It is not possible for users to specify default "reply-to" addresses for all ILL related emails, currently the ReplyToDefault syspref is used, this should be addressed - No message notification is sent to nominated staff when a request is modified, this should be addressed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9