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

[Bug 17004] New: REST API: add route to authenticate patron
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17004 Bug ID: 17004 Summary: REST API: add route to authenticate patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: mail(a)jkozlovsky.cz QA Contact: testopia(a)bugs.koha-community.org Add API route to authenticate patron. This would be very useful for 3rd party applications, such as NCIP's LookupUser service or simpleSAMLphp IdP for eduGAIN. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 57

[Bug 22833] New: Don't let users cancel holds connected with ILLs
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22833 Bug ID: 22833 Summary: Don't let users cancel holds connected with ILLs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no Target Milestone: --- In the Swedish (Libris) ILL module, when a new ILL request is created, a record and an item (with a specific ILL itemtype) are also created. And a hold is created between the local patron that is waiting for the ILL and the local ILL item. This means that the ILL shows up as a regular hold when the patron logs into the OPAC. That in it self is OK, but the problematic thing is that patrons can cancel the holds connected with the ILL (maybe thinking that they are then also canceling the ILL request). Libraries would like to stop patrons from doing this. A couple of options come to mind: 1. Add a syspref that can take a list of itemtypes that should not be cancel'able by the patron in the OPAC 2. Add a boolean field like itetypes.let_patrons_cancel_holds_in_opac which defaults to 1 for existing itemtypes, but can be set to 0 to achieve the desired effect. 1 is more unobtrusive, 2 is probably cleaner in the long run? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 29583] New: error as its is asking for 7395 character length.
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29583 Bug ID: 29583 Summary: error as its is asking for 7395 character length. 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: mdigesh555(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 128057 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=128057&action=e… error as its is asking for 7395 character length In Koha platform patron creation password is showing error as its is asking for 7395 character length. Please check below the screen shot. Kindly, please resolve the issue as soon as possible. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 29527] New: Convert item tables from pre-loading all order data to ajax tables
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29527 Bug ID: 29527 Summary: Convert item tables from pre-loading all order data to ajax tables Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi With many items, a record takes age to display in OPAC (same issue in staff interface). This is a big issue for serials. Koha should fetch the record, display it, then fetch item data and display the table, with a pagination system. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 29398] New: Importing Authority Records without Renumbering
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '23

24 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29398 Bug ID: 29398 Summary: Importing Authority Records without Renumbering Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: cmkelleymls(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Problem: When authority records are import ("Stage MARC records for import"), each authority record is assigned a new record number instead of retaining its original record number as recorded in 001 $a. This links bibliographic records to the wrong authority records, and the only way to restore the original linkage is to manual change biblographic $9 with the new authority record 100 $a; or vice versa. So, for example, Clements, Samuel Langhorne old authority (before migration) #9742 new authority (after migration) #8665 100 1 $a Clements, Samuel Langhorne $e [author] $9 9742 245 10 $a Huckleberry Finn / $cMark Twain. ... The bib. record 100 $9 remains 9742 even though that authority record is now assigned to Shakespeare, William. When clicking on the link in the Huck Finn book, the link finds works by William Shakespeare instead. Enhancement request: Authority records 001 $a retain assigned 001 $a instead of being assigned a new authority record number. I have had limited success with building an authority record's 942 $c from the 100 $a, but a more comprehensive solution is in order. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 29384] New: Advance Notice and Overdue Missing (Default messaging preferences for this patron category) after upgrade from old database (ver 3.2)
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '23

24 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29384 Bug ID: 29384 Summary: Advance Notice and Overdue Missing (Default messaging preferences for this patron category) after upgrade from old database (ver 3.2) Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: saajith(a)seu.ac.lk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 127149 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=127149&action=e… Default Messaging preferences after database migration -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 29383] New: Vendors with lots of orders causes timeouts when receiving
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '23

24 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29383 Bug ID: 29383 Summary: Vendors with lots of orders causes timeouts when receiving 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Some of our libraries have noticed that when upgrading to Koha 20.11.x or higher, Koha will take a very long time and often eventually time out when attempting to receive orders from vendors with many (i.e. more than 100) open orders. To reproduce: 1. Have a vendor 2. Create a basket for that vendor 3. Add at least 100 orders to the basket and close it 4. Receive from the vendor 5. Add invoice details and continue 6. This is when the slowness or timeout will occur -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29371] New: Built-in offline circulation broken in SQL strict mode
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '23

24 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29371 Bug ID: 29371 Summary: Built-in offline circulation broken in SQL strict mode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com, testopia(a)bugs.koha-community.org Depends on: 29255 If Koha is in strict SQL mode and you try to Synchronize -> Download records in the built in offline circulation interface the process will fail: CGI::Compile::ROOT::kohadevbox_koha_offline_circ_download_2epl::get_data(): DBI Exception: DBD::mysql::st execute failed: 'koha_kohadev.borrowers.cardnumber' isn't in GROUP BY at /kohadevbox/koha/offline_circ/download.pl line 84 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29255 [Bug 29255] Built-in offline circulation broken with SQL error -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 29357] New: "Results" in the results browser is untranslatable (intranet)
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '23

24 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29357 Bug ID: 29357 Summary: "Results" in the results browser is untranslatable (intranet) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N 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: frederic(a)tamil.fr Hi all! I'm a bit skeptical about this one. I can't find a bug about it, and I can fathom that if it is indeed untranslatable, no one has opened one yet/noticed it ?! I doubt myself... When you are viewing a record from a list of results, a results browser appears above the biblio menu. The "Results" in that browser seems untranslatable. I found it in koha-tmpl/intranet-tmpl/prog/js/browser.js To find it: 1- In the staff interface, make a search for something vague enough that it will give you a couple of results ("cat" is usually good ;) ) 2- Click on the title of one of the results to access the biblio details page 3- On the left hand side, there should be a results browser, with "Results" and a back arrow and forward arrow This is the "Results" that is not translatable. I looked for it in fr-CA-staff-prog, fr-CA-messages and fr-CA-messages-js. Caroline -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 29353] New: Auth API tests can fail
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '23

24 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29353 Bug ID: 29353 Summary: Auth API tests can fail Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I usually run `qa` with --run-tests as root. Tests are setting SessionStorage=tmp so you end up with root only permissions on the tmp directory: root@kohadevbox:koha(master)$ ls -l /var/lib/koha/kohadev/tmp/ drwxr-xr-x 2 root root 4096 Oct 28 12:02 cgisess_koha_kohadev And some REST API auth tests fail: t/db_dependent/api/v1/auth.t ........................... # Failed test '403 Forbidden' # at t/db_dependent/api/v1/auth.t line 75. # got: '401' # expected: '403' # Failed test 'exact match for JSON Pointer "/error"' # at t/db_dependent/api/v1/auth.t line 75. # got: 'Session has been expired.' # expected: 'Authorization failure. Missing required permission(s).' # Looks like you failed 2 tests of 20. t/db_dependent/api/v1/auth.t ........................... 1/3 # Failed test 'under() tests' # at t/db_dependent/api/v1/auth.t line 108. t/db_dependent/api/v1/auth.t ........................... 3/3 # Looks like you failed 1 test of 3. t/db_dependent/api/v1/auth.t ........................... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/3 subtests t/db_dependent/api/v1/auth_authenticate_api_request.t .. 1/5 # Failed test '200 OK' # at t/db_dependent/api/v1/auth_authenticate_api_request.t line 131. # got: '401' # expected: '200' # Failed test 'The 'koha.user' object is defined in the stash' # at t/db_dependent/api/v1/auth_authenticate_api_request.t line 134. # Failed test 'userenv set correctly' # at t/db_dependent/api/v1/auth_authenticate_api_request.t line 137. # got: undef # expected: '141' # Failed test 'exact match for JSON Pointer ""' # at t/db_dependent/api/v1/auth_authenticate_api_request.t line 154. # Structures begin differing at: # $got->{error} = 'Session has been expired.' # $expected->{error} = 'Authentication failure.' # Looks like you failed 1 test of 3. # Failed test 'logged-out tests' # at t/db_dependent/api/v1/auth_authenticate_api_request.t line 157. # Looks like you planned 8 tests but ran 6. # Looks like you failed 4 tests of 6 run. # Failed test 'cookie-based tests' # at t/db_dependent/api/v1/auth_authenticate_api_request.t line 160. t/db_dependent/api/v1/auth_authenticate_api_request.t .. 4/5 # Looks like you failed 1 test of 5. t/db_dependent/api/v1/auth_authenticate_api_request.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/5 subtests -- You are receiving this mail because: You are watching all bug changes.

1 3