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

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

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23290 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=25381 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25086] New: OPAC Self Registration - Field 'changed_fields' doesn't have a default value
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25086 Bug ID: 25086 Summary: OPAC Self Registration - Field 'changed_fields' doesn't have a default value Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: OPAC Assignee: agustinmoyano(a)theke.io Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 23579 In OPAC's self registration, if PatronSelfRegistrationVerifyByEmail is set to Require, OPAC dies with the following error DBD::mysql::st execute failed: Field 'changed_fields' doesn't have a default value [for Statement "INSERT INTO `borrower_modifications` ( `branchcode`, `categorycode`, `date_renewed`, `dateenrolled`, `dateexpiry`, `dateofbirth`, `debarred`, `email`, `firstname`, `gdpr_proc_consent`, `password`, `surname`, `timestamp`, `verification_token`) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, current_timestamp, ? )" with ParamValues: 0="CPL", 1="S", 2=undef, 3=undef, 4=undef, 5=undef, 6=undef, 7="prueba2(a)algo.com", 8="algo", 9=undef, 10='E<rcyc6h<p', 11="prueba2", 12='aa165f462c22f414a2cd1081bace0921'] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1836. Seems it's because changed_fields doesn't have a default value, and cannot be null. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23579 [Bug 23579] error during web install: 'changed_fields' can't have a default value -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 25011] New: Add display of Production credits (MARC21 508) to staff detail page
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25011 Bug ID: 25011 Summary: Add display of Production credits (MARC21 508) to staff detail page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support 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: 13385 Bug 13385 added 508 to the OPAC XSLT detail page, but missed staff. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13385 [Bug 13385] RDA: 508 display in XSLT -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 25136] New: PatronSelfRegistrationLibraryList controls both self-reg and self-modification
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25136 Bug ID: 25136 Summary: PatronSelfRegistrationLibraryList controls both self-reg and self-modification Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The syspref PatronSelfRegistrationLibraryList describes itself as being about self-registration, but also limits the libraries available for patron self-modification. This presents a problem for libraries that want to corral their self-reg patrons into one library but allow full patrons to move between libraries. I've only confirmed this on 19.05. Master is currently doing something else weird on this syspref, which I'll file a bug for separately. This is part of a larger muddling of selfreg and selfmod that it'd be helpful to get untangled. See also bug 13188 for separating out the mandatory fields for the two pages. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 25139] New: POS explodes in error when trying to display older transactions
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25139 Bug ID: 25139 Summary: POS explodes in error when trying to display older transactions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Fines and fees Assignee: martin.renvoize(a)ptfs-europe.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When trying to display older transactions in the POS module, there is an error: Template process failed: undef error - The given date (12.04.2020) does not match the date format (iso) at /home/vagrant/kohaclone/Koha/DateUtils.pm line 168. at /home/vagrant/kohaclone/C4/Templates.pm line 122 URL: http://localhost:8081/cgi-bin/koha/pos/register.pl?trange_f=07.04.2020&tran… It looks like the dateformat is not handled correctly here. Dateformat is set to DD.MM.YYYY -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 9290] Restricting patron category for online purchase suggestion
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9290 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart(a)bugs.koha-c | |ommunity.org --- Comment #15 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Maybe we could reuse the existing suggestion system preference: Suggestion = if suggestions are available in staff OpacSuggestion = if suggestions are available in OPAC Or make it a pref with 3 entries: Allow suggestions in (OPAC and staff interface|in staff interface|not at all) Native speakers might do better at phrasing these. And maybe: OpacSuggestionValidCategories ? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 20728] New: Remove subroutines GetLastOrder*
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20728 Bug ID: 20728 Summary: Remove subroutines GetLastOrder* 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 Depends on: 20276 There are 2 subroutines from C4::Acquisition that could be removed: - GetLastOrderReceivedFromSubscriptionid - GetLastOrderNotReceivedFromSubscriptionid After bug 20726 only GetLastOrderReceivedFromSubscriptionid will be used (from acqui/neworderempty.pl) and this call could be replaced easily with Koha::Acquisition::Orders The code (+ tests) related to these 2 subroutines could then be removed. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20276 [Bug 20276] GetCourseItem is using the wrong call to get itemnumber -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 23914] New: SQL Server Version
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23914 Bug ID: 23914 Summary: SQL Server Version Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hea Assignee: chris(a)bigballofwax.co.nz Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: jonathan.druart(a)bugs.koha-community.org It would be really interesting to collect the sql server versions people are using in HEA. I'm interested to see what the adoption of MariaDB is and whether we can start adopting more recently introduced features from either MySQL or MariaDB (like CHECK constraints). -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 20370] Misleading comment for bcrypt - #encrypt it; Instead it should be #hash it
by bugzilla-daemon＠bugs.koha-community.org 05 May '20

05 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20370 Joy Nelson <joy(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to master |Pushed to stable Version(s)|20.05.00 |20.05.00, 19.11.06 released in| | CC| |joy(a)bywatersolutions.com --- Comment #5 from Joy Nelson <joy(a)bywatersolutions.com> --- backported to 19.11.x for 19.11.06 -- 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 --- Comment #19 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- (In reply to Martin Renvoize from comment #16) > I'm afraid we cannot yet use the 'IF EXISTS' syntax here as we are > maintaining support for Jessie up to the end of it's LTS date (2020-06-30). > I intend to drop support for that Debian version at the release of 20.05 (at > which time I believe we should also drop support for it from 19.11 at > 19.11.06 and 19.05 at 19.05.12). > > However, even once we have dropped such support, unless I am mistaken, > stretch is still stuck at MySQL 5.5 (though it recommends MariaDB instead. > As such, we'll need a clear deprecation of mysql 5.5 support outlined and > publicised before we can make this change. > > I am, however, pretty keen to take such an approach and drop 5.5 support > with this release and so this patch is 'on hold' for now. Is there an existing place like in the wiki that contains these info? Nothing more than you said, the current situation and future plans. -- You are receiving this mail because: You are watching all bug changes.

1 0