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

[Bug 10517] koha-restore fails to create mysqluser@mysql_hostname so zebra update fails
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10517 --- Comment #18 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- > 2) Remove the instance completely using `koha-remove`. I'm having an issue here. Maybe it's my dev environment. root@4dfd0fcc251b:kohadevbox$ koha-remove kohadev Removing Koha instance kohadev [ ok ] Stopping Plack daemon for kohadev:. userdel: user kohadev-koha is currently used by process 1005 /usr/sbin/deluser: `/usr/sbin/userdel kohadev-koha' returned error code 8. Exiting. Using koha-disable doesn't help. There are still starman and apache processes running that are from the unix user of the instance. Could there be anything more to do before removing the instance? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10517] koha-restore fails to create mysqluser@mysql_hostname so zebra update fails
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10517 Victor Grousset/tuxayo <victor(a)tuxayo.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |victor(a)tuxayo.net --- Comment #17 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- For some reason comment 15 doesn't have the test plan. But it turns out the patch has a test plan. Here it is, to remove confusion and help discussing it: Subject: [PATCH] Bug 10517: Use `DROP USER IF EXISTS` and remove ` || true`. When restoring a Koha instance, and the database user does not exist, an error is shown, although it is prevented from stopping the script by ` || true`. This patch removes the ` || true` guard, and rather uses `DROP USER IF EXISTS` which does exactly what one would expect, without confusing error messages, whether the user existed or not. To test: 1) Assume your Koha instance is called `asdf`. 1) Export the Koha instance using `koha-dump`. 2) Remove the instance completely using `koha-remove`. 3) Import it again using `koha-restore`. 4) No error should be shown, and the import should work. There was NO user to drop, therefore `DROP USER IF EXISTS` did nothing. 5) A database user called `koha_asdf` should exist, and have all privileges on the database of the same name. 6) Remove the instance again using `koha-remove`. 7) Now create a database user in MySQL called `koha_instance` where instance is the name of your dumped koha instance. 8) Import your koha instance again using `koha-restore`. 9) Again, no error should be shown, and the import should work. There WAS a user to drop, therefore `DROP USER IF EXISTS` dropped the user before creating a new one. 10) Again, a database user called `koha_asdf` should exist, and have all privileges on the database of the same name. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25264] New: Add ability to process phone notifications without Talking Tech
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25264 Bug ID: 25264 Summary: Add ability to process phone notifications without Talking Tech 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We have a partner that would like to use Twilio for phone notifications. The problem is that our phone notifications are Talking Tech-centric, and the way our TT is engineered is odd to say the least. We specifically don't create the notices in Koha, but have TT create them instead. I think it would be good to have a system preference that allows phone notices to act in a 'normal' manner so to speak much like email and sms notices. Future outbound calling systems could then just be plugins that handle phone notices while Koha handles email and sms. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 23986] New: Batch Record Deletion does not remove records from search index
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23986 Bug ID: 23986 Summary: Batch Record Deletion does not remove records from search index Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com To test: - create a bib record - perform a search that returns a list of results including your record - delete record via batch record delete tool - repeat your search, observe that record still appears in results - click deleted title in search results, get "The record you requested does not exist" error -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 7947] 440/490 Koha Mapping
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7947 --- Comment #47 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- Nice work everyone! Pushed to master for 20.05 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7947] 440/490 Koha Mapping
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7947 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to master Version(s)| |20.05.00 released in| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23290] XSLT system preferences allow administrators to exploit XML and XSLT vulnerabilities
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23290 didier <didier.gautheron(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |25373 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25373 [Bug 25373] Bug 23290 Security fix break all XSLT entities -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25302] New: The indentations should be in accordance with the Coding guidelines.
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25302 Bug ID: 25302 Summary: The indentations should be in accordance with the Coding guidelines. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: timothy_alexis.vass(a)ub.lu.se QA Contact: testopia(a)bugs.koha-community.org Simply put, the indentations are inconsistent. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 25304] New: Some of the mark needs to be corrected
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25304 Bug ID: 25304 Summary: Some of the mark needs to be corrected Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: timothy_alexis.vass(a)ub.lu.se QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 7317] Add an Interlibrary Loan Module to Circulation and OPAC
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7317 --- Comment #219 from David Cook <dcook(a)prosentient.com.au> --- (In reply to David Cook from comment #218) > Why would you need to replace a null byte with a semicolon (;)? > > It seems to me that email addresses should be separated by a comma? Actually, looking at https://metacpan.org/release/Mail-Sendmail/source/lib/Mail/Sendmail.pm#L334, it seems that Mail::Sendmail doesn't care about separators. It just iterates through a string looking for valid email addresses... yikes... -- You are receiving this mail because: You are watching all bug changes.

1 0