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

[Bug 30107] New: When editing a desk, the currently logged in library is selected
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '22

02 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30107 Bug ID: 30107 Summary: When editing a desk, the currently logged in library is selected Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Instead of showing the library the desk was added to, on editing a desk, it always shows the library the user is currently logged in as preselected. Requires UseCirculationDesks to be activated. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 30346] New: Editing circ rule with Overdue fines cap (amount) results in data loss
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '22

02 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30346 Bug ID: 30346 Summary: Editing circ rule with Overdue fines cap (amount) results in data loss Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Similar to bug 29610, when editing a rule that has an Overdue fines cap (amount) the data in that field is lost. Duplicating/copying a rule with an Overdue fines cap amount does not bring that value over either. To recreate: --Create a circulation rule with a value in "Overdue fines cap (amount), or edit an existing rule to add it -Save the new (or edited) rule. -Edit the same rule again to change any other field. Note that "Overdue fines cap (amount)" is now blank -Save your edited rule - "Overdue fines cap (amount)" will save as blank. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 28717] New: NewsLog doesn't work
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '22

02 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28717 Bug ID: 28717 Summary: NewsLog doesn't work Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The logging for News items added in Bug 26205 is broken. This was caused by Bug 22544 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 63

[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 30863] New: Deleting a patron message - selecting cancel option deletes message
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '22

01 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30863 Bug ID: 30863 Summary: Deleting a patron message - selecting cancel option deletes message Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When deleting a message for a patron's account, selecting the "Cancel" button deletes the message. To replicate: 1. Add a message to a patron's account (Patrons > find and view a patron record > select "Add message" > enter some details > select "Save"). 2. Select "Delete" next to the message. 3. A message box is shown with "Are you sure you want to delete this message? This cannot be undone.". Options are "Cancel" and "OK". 4. Select OK - the message is deleted, as expected. 5. Repeat steps 1-3. 5. Select Cancel - the message is deleted, when it shouldn't be! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[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 30805] New: Missing default value on import_records.marxml_old
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '22

01 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30805 Bug ID: 30805 Summary: Missing default value on import_records.marxml_old Change sponsored?: --- Product: Koha Version: 20.11 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 20144 We fixed a ton of missing default values on bug 20144, I believe this one might be another to fix: import DBD::mysql::st execute failed: Field 'marcxml_old' doesn't have a default value [for Statement "INSERT INTO import_records (import_batch_id, record_sequence, marc, marcxml, record_type, encoding, z3950random) We see this error in an older version after the latest Debian update with a new MariaDB version, but in master we still have: `marcxml` longtext COLLATE utf8mb4_unicode_ci NOT NULL, Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20144 [Bug 20144] Test suite is failing with new default SQL modes -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1