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

[Bug 20074] New: Auth_subfield_structure changes hidden attribute
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '21

13 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20074 Bug ID: 20074 Summary: Auth_subfield_structure changes hidden attribute Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org >From bug 18811 comment40: It sounds like there is something else to fix: On a new DB: MariaDB [koha_kohadev]> select tagfield, tagsubfield, hidden from auth_subfield_structure where tagfield=551 and tagsubfield=9 and authtypecode="GEOGR_NAME"\G *************************** 1. row *************************** tagfield: 551 tagsubfield: 9 hidden: 1 Edit the subfields for GEOGR_NAME /admin/auth_subfields_structure.pl?op=add_form&tagfield=551&authtypecode=GEOGR_NAME Possible value for "Select to display or not"/hidden are -5 and 0, so "Show all" is displayed. Save without modifying anything: hidden is now '0'. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 25216] New: XSLT can only use HTTP not HTTPS URL.
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '21

12 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25216 Bug ID: 25216 Summary: XSLT can only use HTTP not HTTPS URL. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hi, At least on Debian libxml doesn't understand https, but only http or local files. It's an issue with more and more systems silently redirecting http to https. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 29186] New: Move reports result limit menu into toolbar
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '21

10 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29186 Bug ID: 29186 Summary: Move reports result limit menu into toolbar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Reports Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 125831 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=125831&action=e… Screenshot of the proposed change I propose to convert the HTML <select> for choosing the number of report results shown into a Bootstrap dropdown menu. See attached screenshot. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 28937] New: Use Flatpickr on circulation and patron pages
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '21

09 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28937 Bug ID: 28937 Summary: Use Flatpickr on circulation and patron pages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED 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 Depends on: 28928 Bug 28376 added Flatpickr for date and time-picker widgets, with the goal of replacing all usage of jQueryUI's datepicker widget. This bug will cover Flatpickr additions to these pages/files: includes/borrower_debarments.inc includes/calendar.inc includes/holds_table.inc circ/circulation.tt circ/overdue.tt circ/pendingreserves.tt circ/reserveratios.tt members/memberentrygen.tt members/moremember.tt reserve/request.tt prog/js/checkouts.js prog/js/holds.js Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28928 [Bug 28928] Minor follow-ups to Bug 28376 - Flatpickr introduction -- You are receiving this mail because: You are watching all bug changes.

1 41

[Bug 27708] New: Cannot create EDI order if AcqCreateItem value is not "placing an order"
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '21

09 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27708 Bug ID: 27708 Summary: Cannot create EDI order if AcqCreateItem value is not "placing an order" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: nugged(a)gmail.com Depends on: 23926 There was a regression in bug 23926 which causes EDI orders to give internal server error if AcqCreateItem syspref is set to something other than "placing an order." The code from patch "Bug 23926: Limit GIR segment to 5 pieces of info" (f9efa7a9) assumes in the line > branchcode => $item->homebranch->branchcode, that we have an Koha object but that is not true when AcqCreateItem is set to not create an item while placing the order. In that case we manually create hash representing item which has the key "branch" that contains the branchcode so the code "$item->homebranch->branchcode" doesn't work because it should be $item{branch}. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23926 [Bug 23926] In EDI Order limit GIR segment to five pieces of information -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 28057] New: Confusion of biblionumber and biblioitemnumber in request.pl
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '21

08 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28057 Bug ID: 28057 Summary: Confusion of biblionumber and biblioitemnumber in request.pl 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 We have seen issues on sites where biblionumber and biblioitemnumbers are not the same - we hit an ISE for missing itemypes for items on record B when placing a hold on record A biblionumber and biblioitemnumber are not guaranteed to be the same I don't understand what is happening around this code, but I am certain this is not right: 447 $items_any_available = ItemsAnyAvailableAndNotRestricted( { biblionumber => $biblioitemnumber, patron => $ patron }) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 26457] New: DB DeadLock when renewing checkout items
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '21

08 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26457 Bug ID: 26457 Summary: DB DeadLock when renewing checkout items Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, Since it's in a transaction ( https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20086 ) we are seeing deadlock when renewing checkout and items aren't renewed randomly. plack error DBD::mysql::st execute failed: Deadlock found when trying to get lock; try restarting transaction [for Statement "UPDATE issues SET date_due = ?, renewals = ?, lastreneweddate = ? WHERE borrowernumber=? AND itemnumber=?" with P SHOW ENGINE INNODB STATUS; ----------------------- LATEST DETECTED DEADLOCK ------------------------ 2020-09-14 11:09:55 0x7f69b85c0700 *** (1) TRANSACTION: TRANSACTION 19363996, ACTIVE 1 sec fetching rows mysql tables in use 4, locked 4 LOCK WAIT 7 lock struct(s), heap size 1128, 8 row lock(s) MySQL thread id 22449, OS thread handle 140092040718080, query id 38767706 localhost kohaadmin Updating UPDATE issues SET date_due = '2020-09-18 23:59', renewals = '1', lastreneweddate = '2020-09-14T11:09:54' WHERE borrowernumber='93697' AND itemnumber='999735' *** (1) WAITING FOR THIS LOCK TO BE GRANTED: RECORD LOCKS space id 476 page no 87 n bits 248 index PRIMARY of table `koha`.`issues` trx id 19363996 lock_mode X locks rec but not gap waiting Record lock, heap no 109 PHYSICAL RECORD: n_fields 18; compact format; info bits 0 0: len 4; hex 802713f6; asc ' ;; 1: len 6; hex 000000000000; asc ;; 2: len 7; hex 80000000000000; asc ;; 3: len 4; hex 80016e01; asc n ;; 4: len 4; hex 8008e784; asc ;; 5: len 5; hex 99a7397ec0; asc 9~ ;; 6: len 6; hex 43454e545245; asc CENTRE;; 7: SQL NULL; 8: SQL NULL; 9: len 1; hex 80; asc ;; 10: len 1; hex 80; asc ;; 11: SQL NULL; 12: len 4; hex 5f326b5e; asc _2k^;; 13: len 5; hex 99a6e20000; asc ;; 14: len 4; hex 80000000; asc ;; 15: SQL NULL; 16: SQL NULL; 17: SQL NULL; *** (2) TRANSACTION: TRANSACTION 19363999, ACTIVE 1 sec starting index read mysql tables in use 4, locked 4 4 lock struct(s), heap size 1128, 3 row lock(s) MySQL thread id 22450, OS thread handle 140092041332480, query id 38767702 localhost kohaadmin Updating UPDATE issues SET date_due = '2020-09-18 23:59', renewals = '1', lastreneweddate = '2020-09-14T11:09:54' WHERE borrowernumber='93697' AND itemnumber='583556' *** (2) HOLDS THE LOCK(S): RECORD LOCKS space id 476 page no 87 n bits 248 index PRIMARY of table `koha`.`issues` trx id 19363999 lock_mode X locks rec but not gap Record lock, heap no 109 PHYSICAL RECORD: n_fields 18; compact format; info bits 0 0: len 4; hex 802713f6; asc ' ;; 1: len 6; hex 000000000000; asc ;; 2: len 7; hex 80000000000000; asc ;; 3: len 4; hex 80016e01; asc n ;; 4: len 4; hex 8008e784; asc ;; 5: len 5; hex 99a7397ec0; asc 9~ ;; 6: len 6; hex 43454e545245; asc CENTRE;; 7: SQL NULL; 8: SQL NULL; 9: len 1; hex 80; asc ;; 10: len 1; hex 80; asc ;; 11: SQL NULL; 12: len 4; hex 5f326b5e; asc _2k^;; 13: len 5; hex 99a6e20000; asc ;; 14: len 4; hex 80000000; asc ;; 15: SQL NULL; 16: SQL NULL; 17: SQL NULL; *** (2) WAITING FOR THIS LOCK TO BE GRANTED: RECORD LOCKS space id 476 page no 425 n bits 1168 index issuesborridx of table `koha`.`issues` trx id 19363999 lock_mode X waiting Record lock, heap no 52 PHYSICAL RECORD: n_fields 2; compact format; info bits 0 0: len 4; hex 80016e01; asc n ;; 1: len 4; hex 8026df40; asc & @;; *** WE ROLL BACK TRANSACTION (2) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 58

[Bug 28668] New: typo in Koha Manual 21.05
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '21

07 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28668 Bug ID: 28668 Summary: typo in Koha Manual 21.05 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: e.betemps(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi, here is the original string (in faq.po) **Answer**: You probably need to set a default circulation rule in your␠:ref:`Circulation and fines rules <circulation-and-fines-rules-label>`. At the very least you will need to set a default circulation rule. his rule should be as standard rule for all libraries, 'All' itemtype', and 'All' patron category. That will catch all instances that do not match a specific rule. - I think a sentence (At the very least you will need to set a default circulation rule.) is useless because it only repeats the beginning of the string. - a "T" is missing : "This rule..." and not "his rule..." have a nice day, Manu. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 27673] New: Replace YAML with YAML::XS
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '21

07 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27673 Bug ID: 27673 Summary: Replace YAML with YAML::XS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Blocks: 26633 >From tht YAML pod: """ This module has been released to CPAN as YAML::Old, and soon YAML.pm will be changed to just be a frontend interface module for all the various Perl YAML implementation modules, including YAML::Old. If you want robust and fast YAML processing using the normal Dump/Load API, please consider switching to YAML::XS. It is by far the best Perl module for YAML at this time. It requires that you have a C compiler, since it is written in C. """ See also https://gitlab.com/koha-community/qa-test-tools/-/merge_requests/35 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26633 [Bug 26633] Add advanced editor for transfer limits -- You are receiving this mail because: You are watching all bug changes.

1 52

[Bug 17269] New: Library::CallNumber:: LC does not follow LC standards for Area Subarrangments of cataloged maps
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '21

06 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17269 Bug ID: 17269 Summary: Library::CallNumber::LC does not follow LC standards for Area Subarrangments of cataloged maps Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Library::CallNumber::LC is used to generate cn_sort for Library of Congress callnumbers. According to the LC document "Special Instructions and Tables of Subdivisions for Cartographic Materials", in the section 'Area Subarrangments' The document can be found at http://www.loc.gov/catdir/cpso/class_g.pdf; see page 6: "Regions and political divisions within a city or town may be classified with the use of a colon (:) followed by the number 2 or 3, indicating whether the subdivision is (2) geographic or (3) political and a Cutter number for the subdivision. Examples: G4364 California (map city and town number) .L8:2G7 Los Angeles, Griffith Park (classified as a region) G4114 Michigan (map city and town number) .E4:2M4 East Lansing, Michigan State University (classified as a region) G3804 New York State (map city and town number) .N4:3Q4 New York City, Queens (classified as a political division) " When I use Library::CallNumber::LC::Normalize(), 'G4364 .L8:2G7' and 'G4364 .L8' generate entirely different call numbers: Library::CallNumber::LC->normalize("G4364 .L8:2G7") => G4364 .L00008:00002G00007 Library::CallNumber::LC->normalize("G4364 .L8") => G4364 L8 If I'm reading the Library of Congress instructions instructions correctly, I believe that "G4364 .L8:2G7" should generate as "G4364 L8:2G7", which would sort after "G4364 L8", whereas "G4364 .L00008:00002G00007" sorts before "G4364 L8". I'm also filing a bug with the module maintainer: https://github.com/libraryhackers/library-callnumber-lc/issues/10 -- You are receiving this mail because: You are watching all bug changes.

1 8