January 2022 - Koha-bugs - lists.koha-community.org

[Bug 28872] New: AcquisitionLog, NewsLog, NoticesLog should use 1/0 for their values
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '22

02 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28872 Bug ID: 28872 Summary: AcquisitionLog, NewsLog, NoticesLog should use 1/0 for their values Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff Client 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 In system preferences, AcquisitionLog, NewsLog, and NoticesLog are all saving values of "on" and "off" when they should be "1" and "0." That means if you change any of these prefs and save new values you end up with errors on the About page: Warning System preference 'AcquisitionLog' must be '0' or '1', but is 'on'. Warning System preference 'NewsLog' must be '0' or '1', but is 'on'. Warning System preference 'NoticesLog' must be '0' or '1', but is 'on'. In a little preliminary testing, this seems to mean we default to ALWAYS logging acquisitions actions, even if it's set to "Don't log." I didn't check whether the other two are ending up on or off. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 26205] New: News Changes aren't Logged
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '22

02 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26205 Bug ID: 26205 Summary: News Changes aren't Logged Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 48

[Bug 29711] New: Release date not passed as ISO to about.tt
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '22

02 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29711 Bug ID: 29711 Summary: Release date not passed as ISO to about.tt Change sponsored?: --- Product: Koha Version: unspecified 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 When parsing the teams.yaml file, the release date is (correctly) parsed from epoch into a DateTime, but the $KohaDates filter expects 'iso' formatted dates, and stringifying the 'dt' object leads to non-comformant datetime format. To test: 1. On current master 2. Point your staff interface to the About page => FAIL: It explodes because of date formats -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 27043] New: Add to number_of_replicas and number_of_shards to index config
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '22

02 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27043 Bug ID: 27043 Summary: Add to number_of_replicas and number_of_shards to index config 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 With Elasticsearch 6 (>6.4), we have a warning on index creation : the default number of shards will change from [5] to [1] in 7.0.0 See https://github.com/elastic/elasticsearch/pull/30587 I propose to add number_of_shards in index config. Also add number_of_replicas that is better explicit. In case on only one node, it must be 0. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 23887] New: Add support for client-specified sort order in Z3950Responder
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '22

01 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23887 Bug ID: 23887 Summary: Add support for client-specified sort order in Z3950Responder Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: ere.maijala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl GenericSession doesn't currently handle sorting specified by the client. This needs to be added. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 29796] New: Cannot create new patron accounts
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '22

01 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29796 Bug ID: 29796 Summary: Cannot create new patron accounts Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: Linux Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: jhenderson(a)nsd.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hello, My Koha installation suddenly will no longer allow me to create patron accounts. The first prompt I receive is: "Something went wrong when creating the patron. Check the logs." When I open the plack-intranet-log I see this: [2022/01/04 20:42:19] [WARN] Patron creation failed! - {UNKNOWN}: DBIC result _type isn't of the _type Category at /usr/share/perl5/DBIx/Class/Storage/BlockRunner.pm line 130. at /usr/share/koha/lib/Koha/Patron.pm line 354 I am honestly stumped, I was not having this problem before and I haven't changed any settings that would have caused this. Thankfully, I can use the self-registration feature as a workaround right now until this can get fixed. I can provide additional details if needed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 28301] New: Add ability to force re-run of a particular DB update
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '22

01 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28301 Bug ID: 28301 Summary: Add ability to force re-run of a particular DB update Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When there are errors in the updates it would be nice to have a way to execute a single DB update easily -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 18283] New: Display improvements on report results - hide code and change wording
by bugzilla-daemon＠bugs.koha-community.org 31 May '22

31 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18283 Bug ID: 18283 Summary: Display improvements on report results - hide code and change wording Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 29283] New: Cannot delete basket with cancelled order for deleted biblio
by bugzilla-daemon＠bugs.koha-community.org 30 May '22

30 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29283 Bug ID: 29283 Summary: Cannot delete basket with cancelled order for deleted biblio Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: - have a basket with at least one order - click "Cancel order and delete catalog record", confirm cancellation of order and deletion of bib - click "Delete basket", confirm deletion - get error "Cannot insert order: Mandatory parameter biblionumber is missing at /kohadevbox/koha/acqui/basket.pl line 136. at /usr/share/perl/5.28/Carp.pm line 289" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 26630] New: Allow custom text for each library on Purchase Suggestion Page
by bugzilla-daemon＠bugs.koha-community.org 27 May '22

27 May '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26630 Bug ID: 26630 Summary: Allow custom text for each library on Purchase Suggestion Page Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It would be great if using the news tool we could set custom text at the top of the purchase suggestion screen based on the home branch of the patron. Currently I'm using jq to do this, but it would be nice if it was built in. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24