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

[Bug 31010] New: BatchRevert does not deal with indexation correctly
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31010 Bug ID: 31010 Summary: BatchRevert does not deal with indexation correctly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org This bug came up during QA of bug 30822, we're not yet properly handling the batchRevert indexing jobs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31015] New: Remove option to clear pickup location selects on multi-holds page
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31015 Bug ID: 31015 Summary: Remove option to clear pickup location selects on multi-holds page Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When placing multiple holds at once, the various selects for pickup location have a little X at the far right next to the dropdown arrow. Clicking the X clears the field and allows for holds to be created with null pickup locations. We discovered the hard way that things like the holds queue completely break when there are null pickup locations lurking about. It also seems to prevent the holds tab on the patron account from loading. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31022] New: 400/404 actually returns 500
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31022 Bug ID: 31022 Summary: 400/404 actually returns 500 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com CC: martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com Not sure if I am missing something, but I don't manage to get a 400 with the syntax we are using all around our REST API code. return $c->render( status => 400, openapi => { error => "this is an error" } ); I am getting a 500 with, in Koha logs: [{"message":"Missing property.","path":"\/body\/errors"}] So yes, it is working with: return $c->render( status => 400, openapi => { errors => [ {message => 'this is an error'}] } ); But it's not at all what we are doing in our REST API module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 31070] New: [DOCS] Did you mean? section needs an update
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31070 Bug ID: 31070 Summary: [DOCS] Did you mean? section needs an update Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org The Did you mean? section in the administration chapter needs an update (https://koha-community.org/manual/22.05/en/html/administration.html#did-you…) Updates required include: - Updated screenshots - Remove important note about it only working in the OPAC - Add information about the LibrisSpellCheck plugin Related changes to the searching preferences page: - Punctuation and spelling - Link to administration > did you mean section Other changes: - Check whether any update to the OPAC page is required -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 31089] New: viewlog.pl needs better reference point for compare
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31089 Bug ID: 31089 Summary: viewlog.pl needs better reference point for compare Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Currently, viewlog.pl runs comparisons another log. This is okay if you have a previous entry in the log to compare it to (if your logs haven't been cleaned up or a good log exists before the change). It would be better, if the log had a copy of info before the change, and after. If that is the only log entry you select to compare, it will show you a before and after and highlight the changes. If you select a second log entry, then it would show you a comparison between the two entries. This would make the compare feature infinitely more useful. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 31099] New: [DOCS] Export data tool - setup so database and configuration data can be downloaded
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31099 Bug ID: 31099 Summary: [DOCS] Export data tool - setup so database and configuration data can be downloaded Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org Add information to the manual on how to set up Tools > Export data so that the database and configuration backups are enabled and shown. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 30729] New: Template toolkit comments are caught in the translatable strings
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30729 Bug ID: 30729 Summary: Template toolkit comments are caught in the translatable strings 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: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr I was checking the untranslated strings for 22.05 and noticed template toolkit comments are caught in the translatable strings. For example this string: %%] [%%# - category:␠ https://translate.koha-community.org/fr/22.05/translate/fr-FR-staff-prog.po… It comes from koha-tmpl/intranet-tmpl/prog/en/includes/patron-search.inc [%# Display a complex patron search form %] [%# - Search: <input> %] [%# You can then pass a list of filters %] [%# - branch: <select library list> %] [%# - category: <select patron category list> %] [%# - search_field: <select patron field list> %] [%# - search_type: <select "contain" or "start with"> %] -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 30757] New: The last two skips on Jenkins for Koha_ExternalContent_RecordedBooks.t
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30757 Bug ID: 30757 Summary: The last two skips on Jenkins for Koha_ExternalContent_RecordedBooks.t Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 30672] New: Special characters entered into circulation and fine rules causes errors
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30672 Bug ID: 30672 Summary: Special characters entered into circulation and fine rules causes errors Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration 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 Currently, Koha allows for special characters such as $ in the circulation and fine rule matrix. This causes errrors if a circulation rule has a $ in the fines/fees column. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 30665] New: Make order of emails in "first_valid_email_address" configurable
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30665 Bug ID: 30665 Summary: Make order of emails in "first_valid_email_address" configurable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment Koha::Patron->first_valid_email_address mandates a precedence of "email", then "emailpro", then "B_email". However, when "emailpro" was "Work email", a lot of people preferred to use it instead of "email" which was "Home email". The change of "email" to "Primary email" and "emailpro" to "Secondary email" was biased towards public and academic libraries, which left a lot of special libraries in the lurch. At the moment, I hard-code a change to first_valid_email_address to prefer emailpro, but it would be good if this was just straight-up configurable in core Koha. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5