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

[Bug 27015] New: Add filtering options to the pickup_locations routes
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27015 Bug ID: 27015 Summary: Add filtering options to the pickup_locations routes 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: tomascohen(a)gmail.com Based on bug 27002 and bug 26988, the route could be added filters as the routes will rely on resultsets, leveraging on our existing framework. This paves the way to using things like Select2 in a fancier way for the dropdown. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 22243] New: Advanced Cataloguer editor fails if the target contains an apostrophe in the name
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22243 Bug ID: 22243 Summary: Advanced Cataloguer editor fails if the target contains an apostrophe in the name 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.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- As the title, if a z39.50 target has an apostrophe in the name, the editor fails with an "Unexpected token" Javascript error. The array containing the targets is constructed then embedded in the page template and, since the string is enclosed in unescaped single apostrophes, things fall over. The fix is to replace ' in target names with ' -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 26956] New: Allow "Show checkouts/fines to guarantor" to be set without a guarantor saved
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26956 Bug ID: 26956 Summary: Allow "Show checkouts/fines to guarantor" to be set without a guarantor saved Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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 With AllowStaffToSetCheckoutsVisibilityForGuarantor and AllowStaffToSetFinesVisibilityForGuarantor set to Allow, one can only see the controls for these values in the patron record *after* the patron has been saved with a guarantor. That makes a frustrating 2-step process. We should be able to set those values regardless of whether or not there is currently a guarantor on the account. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 27099] New: Stage for import button not showing up
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27099 Bug ID: 27099 Summary: Stage for import button not showing up Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: eric.begin(a)inLibro.com QA Contact: testopia(a)bugs.koha-community.org Some of our clients report that the 'Stage for import' button disappeared in the Stage MARC records page. This problem seams to be related to Chrome 87. The button is still there, but hidden by the language bar at the bottom of the page. A temporary workaround is to add a margin to the <main> element in IntranetUserCSS In our case, we added main { margin-bottom: 50px; } The problem is also present on 20.05 No tested yet on master. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 27031] New: Update header.inc to use Koha plugin for intranetbookbag
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27031 Bug ID: 27031 Summary: Update header.inc to use Koha plugin for intranetbookbag Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org header.inc is still using the [% intranetbookbag %] instead of using Koha.Preference('intranetbookbag'). -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 26953] New: Phone & SMS transports always displayed in overdue status triggers and notices editor
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26953 Bug ID: 26953 Summary: Phone & SMS transports always displayed in overdue status triggers and notices editor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com While working on bug 25334, I noticed that even if a library is not using any phone transport, the phone column still shows on the overdue status triggers. A similar issue is prevalent in the notice editor. It would be nice if those things were hidden when no phone transport is set up. The same for SMS as well. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 27004] New: Deleting a staff account who have created claims returned causes problem in the return_claims table because of a NULL value in return_claims.created_by.
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27004 Bug ID: 27004 Summary: Deleting a staff account who have created claims returned causes problem in the return_claims table because of a NULL value in return_claims.created_by. Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: enica(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When a staff deletes another staff member's staff account and that particular account happens to have created return_claims, it creates a NULL value in the return_claims.created_by, causing a problem when another staff tries to resolve the claims. On the patron's account Claim tab, when one tries to resolve the claim, it will perpetually load without doing anything. Only way to fix is update the NULL value on the created_by and add a borrowernumber. Is there a way to transfer the claim to a different staff account? Should Koha allow the deletion of an account when there are still return_claims unresolved? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 26367] New: Warn in HoldsQueue if request itemtype set but request is not item specific
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26367 Bug ID: 26367 Summary: Warn in HoldsQueue if request itemtype set but request is not item specific Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 0 - set AllowHoldItemTypeSelection to 'Allow' 1 - Place a title level hold for a record with an item from Library A for delivery at Library A for a patron from Library A with an itemtype specified 2 - perl misc/cronjobs/holds/build_holds_queue.pl 3 - There are warns: Use of uninitialized value in hash element at /kohadevbox/koha/C4/HoldsQueue.pm line 523. Use of uninitialized value in string eq at /kohadevbox/koha/C4/HoldsQueue.pm line 523. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 26701] New: Deal with scripts in C4/SIP directory
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26701 Bug ID: 26701 Summary: Deal with scripts in C4/SIP directory Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com There are a number of Perl (and Python) scripts in the C4/SIP directory. These look like test scripts which shouldn't be on a production system. Perhaps we could relocate them to misc/ if we don't want to delete them. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 26950] New: Checkin failure messages are unclear or too specific
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26950 Bug ID: 26950 Summary: Checkin failure messages are unclear or too specific Change sponsored?: --- Product: Koha Version: master 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently checkins can fail for one of two known reasons: 1 - Duplicate issue ids 2 - Anonymous borrower configuration issues In the first case we refer to the 'data problems' or 'data corrupted' section of the about page. All errors are on the 'System information' tab and this is what we should mention In the second case we refer to the data problems section, but information is in another section on the tab. Additionally, during checkin we issue an 'Error' but on the about page we call it a 'Warning' we should upgrade to error and specify what is broken -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15