June 2023 - Koha-bugs - lists.koha-community.org

[Bug 28560] New: Slash with non-ascii library code breaks various things
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28560 Bug ID: 28560 Summary: Slash with non-ascii library code breaks various things 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: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com == Test plan == create a library with code ko/ha and another with Ä/A A. 1. Try to hold from the OPAC with delivery to ko/ha 2. => ERROR: Internal error: incomplete hold request. (odd, nothing in all the logs, just a happy HTTP request returning 200) B. 1. Staff interface 2. set library: Ä/A (the slash isn't enought to cause issues) 3. transfer item to any another library 4. => Broken FK constraint at /usr/share/perl5/Exception/Class/Base.pm line 88 Oddly it works with ko/ha C. 1. Staff interface 2. set library: Ä/A (the slash isn't enought to cause issues) 3. checkout an item 4. => Broken FK constraint at /usr/share/perl5/Exception/Class/Base.pm line 88 Oddly it works with ko/ha D. 1. Staff interface 2. set library: NOT Ä/A 3. checkout an item 4. set library: Ä/A 5. partron page => checkout tab => show checkouts 6. try to check in 7. => it's loads for ever 8. => logs: Broken FK constraint at /usr/share/perl5/Exception/Class/Base.pm line 88 9. refresh page 10. The item has actually been checked in. (not sure if DB is in a consistent state) E. Same but use the check in tab of the search box, next to the Koha logo -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 28521] New: [OMNIBUS] Replace svc scripts
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28521 Bug ID: 28521 Summary: [OMNIBUS] Replace svc scripts 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: jonathan.druart+koha(a)gmail.com Replace "svc" scripts with REST API calls -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 28506] New: Editing purchase suggestion with no library or item type does not save edits
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28506 Bug ID: 28506 Summary: Editing purchase suggestion with no library or item type does not save edits Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Enter a purchase suggestion in the staff client with just a title - no library or document type 2. Edit the purchase suggestion and add publisher or ISBN, etc and save. 3. Notice that the changes are not saved. 4. Edit the record to add publisher and document type and save. 5. On the purchase suggestion summary screen, see that the item type was added, but publisher was not. 6. Edit the purchase suggestion again and see that the document/item type does not show. 7. Add publisher and select a library and save. 8. All data is updated, but the purchase suggestion gets moved to Status Unknown. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 28485] New: LOCK_DIR missing in koha-install-log
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28485 Bug ID: 28485 Summary: LOCK_DIR missing in koha-install-log Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Bug 25109 added installation var LOCK_DIR. It is missing in koha-install-log -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 28471] New: koha-dump --schema-only does not work with mysqldump 8
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28471 Bug ID: 28471 Summary: koha-dump --schema-only does not work with mysqldump 8 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 26947 With focal mysqldump: Couldn't execute 'SELECT COLUMN_NAME, JSON_EXTRACT(HISTOGRAM, '$."number-of-buckets-specified"') FROM information_schema.COLUMN_STATISTICS WHERE SCHEMA_NAME = 'koha_kohadev' AND TABLE_NAME = 'account_credit_types';': Unknown table 'COLUMN_STATISTICS' in information_schema (1109) But adding --column-statistics=0 (like suggested over the web) will break the command when run with a lower version mysqldump: unknown variable 'column-statistics=0' Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26947 [Bug 26947] kohastructure.sql should be updated for each release -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 28446] New: Fix encoding of OverDrive content on Your summary, OverDrive Account
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28446 Bug ID: 28446 Summary: Fix encoding of OverDrive content on Your summary, OverDrive Account Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: magnus(a)libriotech.no Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org Created attachment 121377 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=121377&action=e… Screenshot of bad encoding If you have borrowed a book from OverDrive it will show on "Your summary", on the "OverDrive Account" tab. The display includes the title and description, but this text is encoded wrong, see attached screenshot. It looks like the fix is to use to_json instead of encode_json in the call to output_with_http_headers in opac/svc/overdrive: output_with_http_headers $cgi, undef, to_json($data), 'json', $status_line; I will submit a patch for this once my customer has verified it does not break anything else. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 28436] New: Cache relatively static info that is used often and on many pages (instead of fetching from DB)
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28436 Bug ID: 28436 Summary: Cache relatively static info that is used often and on many pages (instead of fetching from DB) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org We should try to cache (Koha::Cache) some of the most common info that is used on many of our OPAC and intranet pages in order to prevent making very slow SQL queries. E.g. I can cut the load time of biblio detail.pl page by several seconds by just storing the Koha::Template::Plugin::Branches::GetName results in cache/RAM (when the bib has around 1000 items). Similar caching should be done for Koha::Template::Plugin::Categories::GetName, and so on. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 28432] New: When refunding lost fees we should not include voided payments [20.11 and below]
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28432 Bug ID: 28432 Summary: When refunding lost fees we should not include voided payments [20.11 and below] Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, testopia(a)bugs.koha-community.org Depends on: 22435, 27971, 28421 +++ This bug was initially created as a clone of Bug #28421 +++ To recreate: 1 - Mark an item lost 2 - Add a manual lost fee for that barcode to a patron (or checkout before #1 and ensure a fine will be charged when marked lost) 3 - Pay the fee 4 - Void the fee 5 - Pay the fee 6 - Checkin the item 7 - The patron has a credit for twice the fee The problematic code appears to be in _FixAccountForLostAndReturned: my $credits_offsets = Koha::Account::Offsets->search({ debit_id => $accountline->id, credit_id => { '!=' => undef }, # it is not the debit itself type => { '!=' => 'Writeoff' }, amount => { '<' => 0 } # credits are negative on the DB }); We count both the payment and the voided payment Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22435 [Bug 22435] account_offset types should be codes not descriptions https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27971 [Bug 27971] The VOID method should be updated to respect double-entry accounting https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28421 [Bug 28421] When refunding lost fees we should not include voided payments -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 28425] New: repeted strings in Pootle's units
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28425 Bug ID: 28425 Summary: repeted strings in Pootle's units Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: translate.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: e.betemps(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hello, When translating, I saw repeted strings. As I don't know if these repetitions are right or bugs, I ask here for two of them. -> Most popular titles &rsaquo; %s%s%sKoha online%s catalogMost popular titles https://translate.koha-community.org/fr/21.05/translate/fr-FR-opac-bootstra… Is the ending "Most popular titles" right" or do we have to delete it ? -> %s%s%s%sKoha online%s%sKoha online%s catalog &rsaquo; Your messaging settings https://translate.koha-community.org/fr/18.11/translate/fr-FR-opac-bootstra… A "Koha online" seems to be redundant, doesn't it ? have a nice day, Manu. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 28397] New: Bib level call number browse
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28397 Bug ID: 28397 Summary: Bib level call number browse Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl While the item level call number browse is very helpful, it would also be very helpful to be able to browse bib records using the bib level call number. It could run off the system preference defined for itemcallnumber. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1