December 2021 - Koha-bugs - lists.koha-community.org

[Bug 29105] New: items responses do not respect effective_itemtype
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '22

15 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29105 Bug ID: 29105 Summary: items responses do not respect effective_itemtype 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: martin.renvoize(a)ptfs-europe.com The item objects we return from various items API routes do not respect the effective itype offerings. Example, itype is mapped directly from the item itype field to item_type.. it should check for effective itemtype and return the result of that. Similarly notforloan is mapped directly, but can depend on the effective itemtype. There are possibly others. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 20439] New: SMS provider sorting
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '22

14 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20439 Bug ID: 20439 Summary: SMS provider sorting Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On intranet memberentry.pl and on OPAC opac-messaging.pl the SMS provider drop-down is sorted in the order the provider was added rather than alphabetically by provider name - making it difficult for library staff and for borrowers to find providers not added in alphabetical order. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 20726] New: Display acquisition details on the subscription detail page
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '22

13 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20726 Bug ID: 20726 Summary: Display acquisition details on the subscription detail page Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Serials Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Bug 20365 will add the ability to create several pending orders on the same subscription. To make it clear we should add a history of the acquisition on the subscription detail page. -- You are receiving this mail because: You are watching all bug changes.

1 60

[Bug 28730] New: Add option to format AH field (due date) in SIP checkout response
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '22

12 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28730 Bug ID: 28730 Summary: Add option to format AH field (due date) in SIP checkout response Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org According to SIP2 spec on due date/AH: This date field is not necessarily formatted with the ANSI standard X3.30 for date and X3.43 for time. Since it is a variable-length field the ACS can send this date field in any format it wishes. Some machines pass this directly to the checkout receipt, we should be able to format as a due date -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 29420] New: 401 Unauthorized pages come back as 200 OK under plack
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '22

12 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29420 Bug ID: 29420 Summary: 401 Unauthorized pages come back as 200 OK under plack 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: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We have a use case where we define Aliases in Apache for things like some.koha.url/files that are .htpasswd protected. In 21.05 and later, 401 Unauthorized responses go through Koha and become 200 OK. We should make the 401 Unauthorized pages come back as 401 Unauthorized, so that browsers know what to do when BasicAuth is requested. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 26615] New: Koha 18.11.04.000 Upon clicking any tab after ligin or doing any function it displays error :session timed out please login again
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '22

12 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26615 Bug ID: 26615 Summary: Koha 18.11.04.000 Upon clicking any tab after ligin or doing any function it displays error :session timed out please login again Change sponsored?: --- Product: Koha Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: Muhammednajeeb(a)kannuruniv.ac.in QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Created attachment 111260 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=111260&action=e… Error report -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29051] New: Seen renewal methods incorrectly blocked
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '22

09 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29051 Bug ID: 29051 Summary: Seen renewal methods incorrectly blocked 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(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 24083 To recreate: 1 - turn on UnseenRenewals 2- confirm AllowRenewalLimitOverride is off 3- set your all/all rule to allow 1 unseen renewal, more than 1 regular renewal 4- check item out to patron, make sure you're following the all/all rule 5- renew item from OPAC as patron 6- confirm OPAC and intranet tell you next renewal must be at library but that you have renewals remaining 7- try to renew with the Renew Selected button in the Checkouts tab, you cannot select this checkout 8- try to renew with the Renew All button in the Checkouts tab, the item does not renew 9- try to check the item out to the patron again, get message "No more renewals possible" 10 - try to renew by putting the barcode in the big Renew box at the top of the page, get message "E Street shuffle : ( 1 ) has been renewed the maximum number of consecutive times without being seen by the library )" That leaves staff with no way to perform a Seen renewal and reset the count un Unseen renewals, which means the patron is stuck and the item must be returned, which makes this feature deeply flawed. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24083 [Bug 24083] Koha should support "seen" vs "unseen" renewals -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 28610] New: Elasticsearch 7 - hits.total is now an object
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '22

08 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28610 Bug ID: 28610 Summary: Elasticsearch 7 - hits.total is now an object Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: kevin.carnes(a)ub.lu.se In Elasticsearch 7 hits.total is now an object (https://www.elastic.co/guide/en/elasticsearch/reference/7.0/breaking-change…) The total is now in $result->{hits}->{total}->{value} instead of $result->{hits}->{total}. There is also $result->{hits}->{total}->{relation} which specifies if the value is exact or if it's a lower bound. So it's possible to say "Your search returned > 10000 results." You can always get an exact total by adding a track_total_hits parameter set to true when using the Elasticsearch search method (https://www.elastic.co/guide/en/elasticsearch/reference/7.0/breaking-change…) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 27436] New: Set focus for cursor to report name field when creating new SQL report
by bugzilla-daemon＠bugs.koha-community.org 07 Sep '22

07 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27436 Bug ID: 27436 Summary: Set focus for cursor to report name field when creating new SQL report Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy 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: barbara.johnson(a)bedfordtx.gov, gmcharlt(a)gmail.com, testopia(a)bugs.koha-community.org When adding a new SQL report you have to tab to or click the report name field. It would be more efficient to set the focus automatically by adding a "focus" class to the <input> -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 27193] New: Set focus for cursor to patron attribute type code input box when creating new patron attributes
by bugzilla-daemon＠bugs.koha-community.org 07 Sep '22

07 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27193 Bug ID: 27193 Summary: Set focus for cursor to patron attribute type code input box when creating new patron attributes Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When adding a new patron attribute type on patron-attr-types.pl you have to click in the patron attribute type code input box, which is a required field, so that you can enter text. It would be more efficient to set the focus for the cursor to always be in the patron attribute type code input box so that you could just begin typing and eliminate an extra click. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29