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

[Bug 29184] New: Warn from chargelostitem when no replacement cost set for item
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29184 Bug ID: 29184 Summary: Warn from chargelostitem when no replacement cost set for item 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - Create a new item with no replacement cost set 2 - Check the item out to a patron 3 - Mark the item lost 4 - Note in plack-intranet-error.log: [2021/10/06 12:43:26] [WARN] Use of uninitialized value $replacementprice in numeric gt (>) at /kohadevbox/koha/C4/Accounts.pm line 114. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 27802] New: Set focus for cursor on first input field when adding a cash register
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '22

31 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27802 Bug ID: 27802 Summary: Set focus for cursor on first input field when adding a cash register Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When adding a new cash register, the focus is not on the first input field requiring an additional click. To test: - Turn on the UseCashRegisters system preference - Go to administration > cash registers - Click on 'new cash register' - Verify you can't type into the 'Name' input field without clicking into it first -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 27081] New: Notes missing from lost items report column configuration
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '22

31 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27081 Bug ID: 27081 Summary: Notes missing from lost items report column configuration Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The last column of the lost items report - "notes" is missing from the table configuration pull down in 20.05.05. Couldn't test in master yet. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 28708] New: fr-CA localization file
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '22

31 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28708 Bug ID: 28708 Summary: fr-CA localization file 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 I saw some other languages had localization files for specific system preferences. I had my own file before, but now I can share most of it (some things are specific to our organization). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 18440] New: tmp_holdsqueue should have a timestamp
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '22

28 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18440 Bug ID: 18440 Summary: tmp_holdsqueue should have a timestamp Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If the holds queue builder doesn't run for some reason (cron job disabled, or job crashes), it's not possible to tell when the last entry was made in tmp_holdsqueue. It would be very nice to have a timestamp available for this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 25994] New: Make Hold Queue page show when the cron was last run
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '22

28 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25994 Bug ID: 25994 Summary: Make Hold Queue page show when the cron was last run Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 18440 suggests adding a timestamp to tmp_holdsqueue so one can see when an entry there was generated. Once we've done that, it'd be great to add a big clear "This queue was generated at XX/XX/XXXX XX:XX" message to the top of the page. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 27341] New: Performance 21.05 - Omnibus
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '22

28 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27341 Bug ID: 27341 Summary: Performance 21.05 - Omnibus Change sponsored?: --- Product: Koha Version: unspecified 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 -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 22983] New: New default local NotoSans font copy lackck glyphs for (some) Roman letters with diacritics
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '22

28 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22983 Bug ID: 22983 Summary: New default local NotoSans font copy lackck glyphs for (some) Roman letters with diacritics Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Created attachment 90054 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=90054&action=ed… NotoSans rendered incorrectly (missing) for Polish letters The patches of Bug 20554 introduced a new pretty NotoSans font family as basic font for OPAC. A decision was taken to serve the font files from Koha installation, not from Google font API. Unfortunately, the copy of the font files in Koha lacks non-standard (probably those outside iso 8859-1 set?) accented Roman letters (among others, Polish). As a result the user is presented with the page which is--typographically--hard to accept (cf. attached screenshot -- Windows 10, Chrome 74.0.3729.169; BTW, on my Android 9 everything seems to be OK -- probably thanks to the local, system copy of the font?). Possible solutions could be: 1) update the Koha copies of the font files with the up-to-date version 2) let css get the font from Google font API (href="https://fonts.googleapis.com/css?family=Noto+Sans&display=swap") Can be tested--for instance--with Polish letters: ACELNOSZZ ĄĆĘŁŃÓŚŻŹ acelnoszz ąćęłńóśżź -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 26832] New: Elasticsearch mappings export should use UTF-8
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '22

27 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26832 Bug ID: 26832 Summary: Elasticsearch mappings export should use UTF-8 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com Script misc/search_tools/export_elasticsearch_mappings.pl allows to export current search engine configuration into a YAML file. This export should use UTF-8 encoding, like other exports. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 22323] New: cronjob runreport.pl CSV encoding issue
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '22

27 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22323 Bug ID: 22323 Summary: cronjob runreport.pl CSV encoding issue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Target Milestone: --- Cronjob runreport.pl runs SQL reports and can export as CSV. This export needs to be UTF-8 encoded. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15