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

[Bug 3150] Move emails for sending cart and list contents into notices tool
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3150 --- Comment #15 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Yup... What Joubu has said is just a longer way of saying what I said in my comment :) so glad we're all agreed. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8976] Default sequence of subfields in cataloguing editor
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8976 --- Comment #21 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I agree with Jonathan in that we should never change the sequence of subfields in an existing bibliographic record - imported or already in Koha. MARC requires some subfields to be in a specific sequence that is not alphabetical or easy to guess. I am not sure how the item forms are build in several places - only that the ones in acq and serials are "different" and have not all features from the frameworks. Maybe worth checking those for a separate bug. But I think this one here aims mostly at bibliographic and authority records? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25097] New: Add option to message_queue to allow for only specific sending notices
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25097 Bug ID: 25097 Summary: Add option to message_queue to allow for only specific sending notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The message_queue.pl currently will send all the messages queued up. It would be nice to have some control over which messages are to be sent. Example: We have libraries who only wanted to send 'hold notices' but not overdue, advance notice, etc during the covid-19 quarantine. And some that were the opposite - turn off hold notices, but send other generated notices. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 12430] Relevance ranking should also be used without QueryWeightFields system preference
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12430 --- Comment #93 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- It's likely that the tests should just expect undef instead of '' But better ask for confirmation ^_^ -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12430] Relevance ranking should also be used without QueryWeightFields system preference
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12430 --- Comment #92 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- Test plan works in 19.11.x but automated test doesn't [1] (t/Search/buildQuery.t) It works in 20.05.x Here is maybe the place to looks in the code. Does anyone understand the difference there or somewhere else that affect $limit_desc and $limit? 20.05.x: https://gitlab.com/koha-community/Koha/-/blob/8a9553c4ae62aa05d7d3529806d8f… 19.11.x: https://gitlab.com/koha-community/Koha/-/blob/608512179cf8f354ca76bab32e874… [1] Failed test: kohadev-koha@ec7b568b5d3d:/kohadevbox/koha$ prove t/Search/buildQuery.t t/Search/buildQuery.t .. 1/10 # Failed test 'Limit is correct' # at t/Search/buildQuery.t line 92. # got: undef # expected: '' # Failed test 'Limit desc is correct' # at t/Search/buildQuery.t line 94. # got: undef # expected: '' # Looks like you failed 2 tests of 13. # Failed test 'test weighted autotruncated' # at t/Search/buildQuery.t line 107. # Failed test 'Limit is correct' # at t/Search/buildQuery.t line 130. # got: undef # expected: '' # Failed test 'Limit desc is correct' # at t/Search/buildQuery.t line 132. # got: undef # expected: '' # Looks like you failed 2 tests of 13. # Failed test 'test* weighted autotruncated' # at t/Search/buildQuery.t line 144. # Failed test 'Limit is correct' # at t/Search/buildQuery.t line 167. # got: undef # expected: '' # Failed test 'Limit desc is correct' # at t/Search/buildQuery.t line 169. # got: undef # expected: '' # Looks like you failed 2 tests of 13. # Failed test 'test weighted not-autotruncated' # at t/Search/buildQuery.t line 181. # Failed test 'Limit is correct' # at t/Search/buildQuery.t line 316. # got: undef # expected: '' # Failed test 'Limit desc is correct' # at t/Search/buildQuery.t line 318. # got: undef # expected: '' # Looks like you failed 2 tests of 13. # Failed test 'one and two weighted autotruncated' # at t/Search/buildQuery.t line 330. # Looks like you failed 4 tests of 10. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25583] New: When ClaimReturnedLostValue is not set, the claim returned tab doesn't appear
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25583 Bug ID: 25583 Summary: When ClaimReturnedLostValue is not set, the claim returned tab doesn't appear 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When you add a 'claimed returned' to an item, but ClaimReturnedLostValue is not set, the "Claims" tab won't display and cause some confusion. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 26946] New: Limit size of cash register's name on the UI
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26946 Bug ID: 26946 Summary: Limit size of cash register's name on the UI Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Staff Client Assignee: martin.renvoize(a)ptfs-europe.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 23321 If you create a new cash register with a "long" (not that long actually) name, the submit form fails with: 2020/11/06 09:56:19] [WARN] DBD::mysql::st execute failed: Data too long for column 'name' at row 1 [for Statement "INSERT INTO `cash_registers` ( `branch`, `description`, `name`, `starting_float`) VALUES ( ?, ?, ?, ? )" with ParamValues: 0="CPL", 1="<script>alert("â¤");</script>", 2="<script>alert("â¤");</script>", 3="0.00"] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1836. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23321 [Bug 23321] Add 'cash registers' to the accounts system -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 12430] Relevance ranking should also be used without QueryWeightFields system preference
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12430 Victor Grousset/tuxayo <victor(a)tuxayo.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to oldstable |Pushed to oldoldstable Version(s)|21.05.00,20.11.01,20.05.07 |21.05.00,20.11.01,20.05.07, released in| |19.11.13 --- Comment #91 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- Backported to 19.11.x branch for 19.11.13 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 16067] New: Koha::Cache, fastmmap caching system is broken
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16067 Bug ID: 16067 Summary: Koha::Cache, fastmmap caching system is broken 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: abl(a)biblos.pk.edu.pl QA Contact: testopia(a)bugs.koha-community.org After Bug 11998, fastmmap caching system implementation in Koha::Cache ceased to work properly. If fastmmap is enabled (= environment variable CACHING_SYSTEM is set to 'fastmmap'), any CGI script call causes the following error: Use of uninitialized value $db_name in concatenation (.) or string at /home/koha/devkohaclone/Koha/Database.pm line 73. Use of uninitialized value $db_host in concatenation (.) or string at /home/koha/devkohaclone/Koha/Database.pm line 73. DBI connect('database=;host=;port=','',...) failed: Access denied for user 'koha'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1249 DBIx::Class::Storage::DBI::dbh(): DBI Connection failed: Access denied for user 'koha'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1253. at /home/koha/devkohaclone/Koha/Database.pm line 90 To reproduce on command line: 0) ensure that you have fastmmap perl module installed (libcache-fastmmap-perl in debian) 1) export CACHING_SYSTEM=fastmmap 2) export GATEWAY_INTERFACE=1 3) try to run this simple script: #!/usr/bin/perl use Modern::Perl; use C4::Biblio; GetMarcStructure(); -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 26336] New: Cannot import items if items ignored when staging
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26336 Bug ID: 26336 Summary: Cannot import items if items ignored when staging Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When staging marc records you have the option to process or ignore items. If you choose to ignore you can change the option after staging, however, items are not processed unless they are parsed in initial staging To test: 0 - Check the count of import_items SELECT COUNT(*) FROM import_items; 1 - Import a marc file with items , process the items 2 - Check the count of import items, it has increased 3 - Stage the file again, do not process items 4 - Count of import_items has not increased 5 - Manage the stage batch, process items and reapply 6 - Check the count of import_items, no change 7 - Import the file, no items are processed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17