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

[Bug 21714] New: Unable to view vendor with strict_sql_modes enabled
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '18

30 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21714 Bug ID: 21714 Summary: Unable to view vendor with strict_sql_modes enabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org With strict_sql_modes enabled it is not possible to view a vendor detail page, instead the following error is displayed: Can't use an undefined value as an ARRAY reference at /usr/lib/x86_64-linux-gnu/perl5/5.24/DBI.pm line 2088. After some digging around, the error seems to be being generated when this query is run: https://github.com/PTFS-Europe/koha/blob/master/C4/Acquisition.pm#L719 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 21724] New: Koha::Logger for gather_print_notices.pl
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '18

30 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21724 Bug ID: 21724 Summary: Koha::Logger for gather_print_notices.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: olli-antti.kivilahti(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org gather_print_notices.pl has no loggability, and silently ignores errors. Also the Mime::Lite is deprecated. Add some logging to gather_print_notices.pl for possible post mortem analysis and try to guess possible error/exception conditions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '18

30 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 --- Comment #118 from David Gustafsson <glasklas(a)gmail.com> --- I could also squash all the changes and add a new updated "To test", anyone has some input on this? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '18

30 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 --- Comment #117 from David Gustafsson <glasklas(a)gmail.com> --- Pushed the schema changes and followed the convention in Bug 19482. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '18

30 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 --- Comment #116 from David Gustafsson <glasklas(a)gmail.com> --- Created attachment 81621 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=81621&action=ed… Bug 14957: DO NOT PUSH Schema changes -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '18

30 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 --- Comment #115 from David Gustafsson <glasklas(a)gmail.com> --- (In reply to Cori Lynn Arnold from comment #114) > Applied fine, but there were runtime errors: > > 5. You should see a new link "MARC field permissions" in the "Catalog" > section under "Koha administrtion". > --> Link Changed to "MARCMergeRules" > > 7. Next to the page heading ("Manage MARC field permissions") there is a > button with a question mark, click this r more information about the > rule system. > --> Link labeled "MARC merge rules" > --> Page throws error > "DBIx::Class::Schema::source(): Can't find source for MarcMergeRule at > /home/vagrant/kohaclone/Koha/Objects.pm line 341 > at /usr/share/perl5/DBIx/Class/Exception.pm line 77" > > --cori lynn Regarding the commit message I'm a little bit confused about how to handle. If I edit the commit message for the first commit it no longer reflect the changes for that commit, on the other hand the "To test" is partly outdated, so perhaps it should have been rewritten in the "Bug 14957 - Refactor and fix tests and documentation"-patch. It seems the local help feature has been removed in Bug 19817, so work is needed to move it into the manual instead? Regarding the "DBIx::Class::Schema::source()" I think you need to run the "misc/devel/update_dbix_class_files.pl" script to regenerate the Schema-files, as those are not to be included in the patch. Perhaps there is a convention to include them an attachment anyway, see if I can find an example of such a bug. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '18

30 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 Cori Lynn Arnold <carnold(a)dgiinc.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #114 from Cori Lynn Arnold <carnold(a)dgiinc.com> --- Applied fine, but there were runtime errors: 5. You should see a new link "MARC field permissions" in the "Catalog" section under "Koha administrtion". --> Link Changed to "MARCMergeRules" 7. Next to the page heading ("Manage MARC field permissions") there is a button with a question mark, click this r more information about the rule system. --> Link labeled "MARC merge rules" --> Page throws error "DBIx::Class::Schema::source(): Can't find source for MarcMergeRule at /home/vagrant/kohaclone/Koha/Objects.pm line 341 at /usr/share/perl5/DBIx/Class/Exception.pm line 77" --cori lynn -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15032] [Plack] Scripts that fork (like stage-marc-import.pl) don't work as expected
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '18

30 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15032 --- Comment #36 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- (In reply to David Cook from comment #35) > (In reply to Tomás Cohen Arazi from comment #34) > > This is worth discussing in koha-devel, and IRC meeting or Marseille, but I > > think we should have a job queue in the lines of what David proposes. And I > > would add maybe the use of ZeroMQ to possibly notify other services. > > I agree about opening up the discussion in another forum like koha-devel, > IRC, or Marseille. > > I'm intrigued by the use of ZeroMQ. How do you see that working, Tomás? When > I first started thinking about background processing, I thought using a > message queue would be a good idea. Since then, I've used an embedded > ActiveMQ with the Fedora repository a bit, but that publishes notifications > about record changes. Celery uses a message queue for sending out tasks and > then it can use a backend like Redis for storing task results. > > I think if we use a database for a job queue, that would replace the message > queue? Or are you meaning using a message queue for notifying other services > like an indexer that there are imported records to index? I need to implement a way to hook record/item updates so changes are pushed to an external service. Ideally through the use of plugins so a more generic job queue was the first thing to consider. Then if we replace (say) rebuild_zebra.pl -d with this, we should add a way to inject new 'tasks' derived from this events (so a record update should trigger a zebra/ES indexing step, and also look for things (plugins) that would require actions. It felt simpler if it just sent broadcast messages through a socket to any service listening there. I like ZeroMQ because it doesn't need a server, you just use your own service. So, one event => multiple actions. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10442] Remove references to non-standard "error" class
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '18

30 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10442 Andrew Isherwood <andrew.isherwood(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #78413|0 |1 is obsolete| | --- Comment #14 from Andrew Isherwood <andrew.isherwood(a)ptfs-europe.com> --- Created attachment 81615 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=81615&action=ed… Bug 10442: Remove references to non-standard "error" class The CSS for <div class="error"> is obsolete and should not be used. This patch removes the definition from the main CSS file and corrects instances of its use in the templates to the standard <div class="dialog alert">. To test: - In Acquisitions -> Late orders, locate an order from a vendor which doesn't have an email address. Selecting that order and clicking "Claim" should trigger an error dialog, "This vendor has no email." It should be styled correctly. - With AcqCreateItem set to "when placing an order," add to an existing order using the "From a new (empty) record" option. Add two items with identical barcodes and submit the form. A error should show at the top of the page. - With AcqCreateItem set to "when receiving an order," receive an order and add two items with identical barcodes. Submitting the form should trigger an error message at the top of the page. With the remaining cases I don't know how to trigger the errors in question, so a visual check of the changes may be required: - Administration -> Funds -> "You are not authorized to modify this fund" - Administration -> Search engine configuration (/admin/searchengine/elasticsearch/mappgings.pl) -> Various modification errors. - With the AutoEmailOpacUser preference set to "send," adding a patron without an email address can trigger an error, "This member has no email." - With plugins enabled, and installed, there are error messages displayed under various circumstances. Signed-off-by: Andrew Isherwood <andrew.isherwood(a)ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10442] Remove references to non-standard "error" class
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '18

30 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10442 Andrew Isherwood <andrew.isherwood(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0