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

[Bug 24835] New: Bad PCDATA explodes search with a Software ERROR.
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24835 Bug ID: 24835 Summary: Bad PCDATA explodes search with a Software ERROR. Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: Lisa.Beinhoff(a)ttuhsc.edu QA Contact: testopia(a)bugs.koha-community.org Searching in the public library catalog for a record with bad PCDATA, causes the following error to appear: Software error: Invalid data, cannot decode object (id=75430, format=marcxml, schema=MARC21, decoding_error=':94: parser error : PCDATA invalid Char value 27 construction of the Metacarpal Hand -- 21. The Mutilated Wrist -- 22. Krukenberg ^ :94: parser error : PCDATA invalid Char value 27 struction of the Metacarpal Hand -- 21. The Mutilated Wrist -- 22. Krukenbergb2 ^') For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error. Error generated in staff view is: There is an error with this bibliographic record, the view may be degraded. Error: Invalid data, cannot decode object (id=75430, format=marcxml, schema=MARC21, decoding_error=':94: parser error : PCDATA invalid Char value 27 construction of the Metacarpal Hand -- 21. The Mutilated Wrist -- 22. Krukenberg ^ :94: parser error : PCDATA invalid Char value 27 struction of the Metacarpal Hand -- 21. The Mutilated Wrist -- 22. Krukenbergb2 ^') Editing the record and saving the bibliographic error seems to clear the error, for some unknown reason. But I need a way to identify the bad records, so they can be corrected. About 1 in 20 records in our databases is generating this error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 24799] New: add withdrawn status for issues
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24799 Bug ID: 24799 Summary: add withdrawn status for issues Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: mbarham(a)birzeit.edu QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com add new issue status 'withdrawn' or even connect it with authorized value, rather than hardcoded. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24796] New: No test coverage for getting translations from templates
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24796 Bug ID: 24796 Summary: No test coverage for getting translations from templates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr There are two different code paths for getting translatable strings out of templates: 1) extract_messages_from_templates() in LangInstaller.pm which handles js-files and the templates that use i18n.inc, 2) tmpl_process3.pl which uses misc/translation/xgettext.pl to parse and extract strings out of tt-files. The t/LangInstaller.t only tests the first one, there are no tests whatsoever for the second. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 24785] New: Search result column localization
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24785 Bug ID: 24785 Summary: Search result column localization Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: stephane.delaye(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org At the level of the localization column in search result, it would either be necessary to ignore itype of the items for the classification of the items in the available or unvailable html span or to change the titles of these html span. Because it is not fair to mix the concepts of availability and borrowability: a dictionarie who is not borrowable with the display not unavailable it's wrong: the items is on shelf, that's all. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 24761] New: Caching issues in scripts running in daemon mode
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24761 Bug ID: 24761 Summary: Caching issues in scripts running in daemon mode 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 16758 highlighted an issue on long running processes (daemons) with the L1 cache mechanism not being able to invalidate cache. The proposed and agreed solution there was to disable L1 cache for daemon scripts. But the bug only took care of rebuild_zebra.pl, leaving things like SIPServer for later. We should resume that work, and discussion. It clearly needs to be handled in a generic way on Koha::Script -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 24714] New: Include ISBN tag in search result items even if no in-built Enhanced Content service for cover images is used
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24714 Bug ID: 24714 Summary: Include ISBN tag in search result items even if no in-built Enhanced Content service for cover images is used Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: webi(a)runbox.com QA Contact: testopia(a)bugs.koha-community.org 3rd-party services commonly use ISBN for image links. This makes it easy to use UserJS to produce them from simple ISBN tags in the HTML. Currently though, one has to check e.g. Google Jackets, only to get them. This works, but also adds completely redundant loading. One solution: a simple unconditional (or conditioned by no Enhanced Content used - after the [% IF ( GoogleJackets ) %] etc. sections ) addition of SEARCH_RESULT.normalized_isbn in opac-results.tt; and corresponding .tt:s, for Intra etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 24687] New: Installation errors in Koha-common
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24687 Bug ID: 24687 Summary: Installation errors in Koha-common Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: jwboulier(a)sbcglobal.net QA Contact: testopia(a)bugs.koha-community.org Getting errors about unable to locate Koha configuration file koha-conf.xml at line 245. /usr/share/koha/lib/C4/Context.pm. (Repeated 4 times) Can't call method "config" on unblessed reference at /usr/share/koha/lib/Koha/Database/pm line 56. Setting up koha-common (19.11.02-1) ... failed to load external entity "/etc/koha/sites/jack/koha-conf.xml" Upgrading database schema for jack unable to locate Koha configuration file koha-conf.xml at /usr/share/koha/lib/C4/Context.pm line 245. unable to locate Koha configuration file koha-conf.xml at /usr/share/koha/lib/C4/Context.pm line 245. unable to locate Koha configuration file koha-conf.xml at /usr/share/koha/lib/C4/Context.pm line 245. unable to locate Koha configuration file koha-conf.xml at /usr/share/koha/lib/C4/Context.pm line 245. Can't call method "config" on unblessed reference at /usr/share/koha/lib/Koha/Database.pm line 56. dpkg: error processing package koha-common (--configure): installed koha-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: koha-common E: Sub-process /usr/bin/dpkg returned an error code (1) Using a Dell 7500, 6 core 48 Gig of ram, Mint 19.3 Cannot load any Koha software. Attempted a live DVD. Does not respond to the install software from the admin menu, Following instructions from the Live DVD. Why is this software so difficult to install? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 24678] New: Add missing search fields to Elasticsearch mappings
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24678 Bug ID: 24678 Summary: Add missing search fields to Elasticsearch mappings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi The Elasticsearch mappings.yaml file is still missing a lot of search fields compared to Zebra. For example Zebra has 264a and 264c separately indexed but Elasticsearch only has 264 indexed in one search field 'provider'. You can compare MARC21 search mappings with the files: - etc/zebradb/marc_defs/marc21/biblios/biblio-koha-indexdefs.xml - admin/searchengine/elasticsearch/mappings.yaml -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 24667] New: Displaying the Home Location of the Item from Search Results in Staff Client
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24667 Bug ID: 24667 Summary: Displaying the Home Location of the Item from Search Results in Staff Client Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some users would like to see the ability to change what is visible in the Location column when searching in the staff client. Currently, when a search is performed, on the brief result screen, the right-hand column is for the item's location. This location indicates where the item actually is, and not it's home location. Some users would like to have the ability to change this to see the home location of the item, not where the item currently is. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 24659] New: Improve Patron Notice Status options to be more clear to staff
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24659 Bug ID: 24659 Summary: Improve Patron Notice Status options to be more clear to staff Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: margaret(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When patron messaging preferences are selected not to send courtesy notices, and there is no email for them to be sent to, Koha generates a notice and marks it as failed. The case I'm specifically looking at involves Auto Renewal notices. These “failures” are visible in the Patron Notices Log and then general circulation staff sees “failed” and gets confused. Staff education is important, but we can make things easier for our users by clarifying these types of messages. Either we could skip making them, as determined the Patron messaging preferences, to find a better status term for these types of messages. "Not applicable" "Unsent" "Not required" "No emails selected" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2