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

[Bug 25654] New: Making the Contact Section / Guarantor Section separate from the Contact details of the patron would be less confusing
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25654 Bug ID: 25654 Summary: Making the Contact Section / Guarantor Section separate from the Contact details of the patron would be less confusing Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 105490 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=105490&action=e… differences With the recent change of the Guarantors in Koha, the Contact section of the Patron Detail page (when editing) is confusing. Prior to 19.11, the Contact section was created for the Contact details of the Patron, phone, email, fax. Now in 19.11, the Guarantor (Non-Koha) has been added to the contact section, causing questions if this is the Guarantor's contact information or the primary patron's contact information. It would be nice if there could be a separation of the two areas in the Koha patrons form (memberentry.pl) Attaching an image of the before 19.11 and 19.11 contact section. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 32613] New: Can we add 'autocompletion' to our SQL reports editor?
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32613 Bug ID: 32613 Summary: Can we add 'autocompletion' to our SQL reports editor? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We're using CodeMirror for the SQL reports editor.. I wonder if there's a plugin or configuration option for that which supports basic autocompletion, similar to what is found on https://sqliteonline.com/, that we can impliment for Koha? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 9799] Prompt for due date for specific item types
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9799 Katie Bliss <kebliss(a)dmpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kebliss(a)dmpl.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 27096] New: Add option to message_queue to exclude specific letter codes
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27096 Bug ID: 27096 Summary: Add option to message_queue to exclude specific letter codes 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 25097 Bug 25907 allows one to set process_message_queue to only send notices with the specified letter codes. In some cases, it'd be hand to invert that and list notices to be excluded. So an exclude-list rather than an include-list. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25097 [Bug 25097] Add option to message_queue to allow for only specific sending notices -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 6428] refered column 'items.coded_location_qualifier' does not exist
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6428 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|Oldversions |--- --- Comment #40 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- I just stumble over this report anno 2023. I noticed in my data (empty) occurrences of $f in more_subfields_xml. And surprisingly, there is no mapping in my data from $f to items.coded_location_qualifier. So this leaves a theoretical issue: AFAICS the patches here did not check if there was a Koha to MARC mapping when adding the item field but assumed that it was there? Hence possible data in the xml field was lost when no mapping existed. But yes, if you do not use the field, no problem :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35501] New: Make koha-restore restore only files, not db
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35501 Bug ID: 35501 Summary: Make koha-restore restore only files, not db Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Use case: We have Koha instances on a number of different virtual servers, and databases on separate/dedicated servers. Sometimes we need to move an instance from one server to another, without doing anything about the database. It would be nice if we could copy a .tar.gz backupfile from the old server to the new server, and recreate the site on the new server with something like: sudo koha-restore --onlyfiles mykoha-<date>.tar.gz This is the opposite of bug 34777. :-) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 4875] koha-remove, koha-restore should have options similar to --request-db
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4875 Magnus Enger <magnus(a)libriotech.no> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |35502 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35502 [Bug 35502] [Omnibus] Rewrite koha-restore -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 15664] koha-restore: Allow database dump to be restored to another Koha instance
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15664 Magnus Enger <magnus(a)libriotech.no> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |35502 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35502 [Bug 35502] [Omnibus] Rewrite koha-restore -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 21769] New: koha-restore file-exists
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21769 Bug ID: 21769 Summary: koha-restore file-exists Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: Heinrich.Hartl(a)email.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz I have two virtual servers. vm-prod is running the production, vm-dev was created long ago as clone from vm-prod. Update procedures are always first tried using vm-dev and only then applied to vm-prod. So there is a lot of similarity between these two vm's. vm-prod and vm-dev are ubuntu 14.4 LTS, koha 16.11. I did hhl@koha-VM-dev:~ > sudo koha-remove library [sudo] password for hhl: Removing Koha instance library Stopping Zebra server for library * Stopping Koha indexing daemon for library [ OK ] * Restarting web server apache2 [ OK ] sudo koha-restore library-2018-10-25.sql.gz library-2018-10-25.tar.gz hhl@koha-VM-dev:~ > sudo koha-restore library-2018-10-25.sql.gz library-2018-10-25.tar.gz [sudo] password for hhl: ERROR: File exists: /var/lib/koha/library/ ERROR: File exists: /var/lib/koha/library/authorities/ ERROR: File exists: /var/lib/koha/library/authorities/register/ ERROR: File exists: /var/lib/koha/library/authorities/key/ ERROR: File exists: /var/lib/koha/library/authorities/tmp/ ERROR: File exists: /var/lib/koha/library/authorities/shadow/ ERROR: File exists: /var/lib/koha/library/biblios/ ERROR: File exists: /var/lib/koha/library/biblios/register/ ERROR: File exists: /var/lib/koha/library/biblios/register/sort100-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/dict-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort23-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/recdA-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort29-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/isambC-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort143-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort58-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort40-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/isambD-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort19-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/isambA-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort68-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/recdB-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort139-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort44-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/isambB-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort6-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/reci-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort11-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/gmatch-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort94-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort36-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort202-0.mf ERROR: File exists: /var/lib/koha/library/biblios/key/ ERROR: File exists: /var/lib/koha/library/biblios/tmp/ ERROR: File exists: /var/lib/koha/library/biblios/shadow/ ERROR: File exists: /var/lib/koha/library/plugins/ ERROR: File exists: /var/lib/koha/library/uploads/ ERROR 1396 (HY000) at line 1: Operation DROP USER failed for 'koha_library'@'%' Warning: You passed -x which is already the default and is now deprecated item-level_itypes set but no itemtype set for item (64339) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64342) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64334) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64344) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64348) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64343) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (65556) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64341) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64352) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64892) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (65581) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64337) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64338) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64596) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (61258) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. * Restarting web server apache2 [Fri Nov 02 15:16:48.516017 2018] [core:warn] [pid 19897] AH00111: Config variable ${instance} is not defined [Fri Nov 02 15:16:48.516171 2018] [core:warn] [pid 19897] AH00111: Config variable ${instance} is not defined [ OK ] hhl@koha-VM-dev:~ > I am confused - an error should stop a procedure I am pleased - the koha instance on vm-dev subsequently was running, a few simple tests succeeded I am afraid - there may be some serious malfunction not to be detected easily Where can a find an explanation for above messages? Are there activities required to resolve problems? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 35462] New: "savepoint_0 does not exist" when saving patron
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35462 Bug ID: 35462 Summary: "savepoint_0 does not exist" when saving patron Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When trying to save a new patron, clicking on "Save" sends me right back to the form for adding the new patron, but some of the information I entered is missing (at least firstname and cardnumber). There is no error message displayed. I see this in the logs: ==> /var/log/koha/konaturvard/plack-error.log <== DBIx::Class::Storage::DBI::mysql::_exec_svp_release(): DBI Exception: DBD::mysql::db do failed: SAVEPOINT savepoint_0 does not exist at /usr/share/koha/lib/Koha/Object.pm line 170 Patron creation failed! - DBIx::Class::Storage::DBI::mysql::_exec_svp_release(): DBI Exception: DBD::mysql::db do failed: SAVEPOINT savepoint_0 does not exist at /usr/share/koha/lib/Koha/Object.pm line 170 The code around /usr/share/koha/lib/Koha/Object.pm line 170 looks like this (in "sub store"): 169 try { 170 return $self->_result()->update_or_insert() ? $self : undef; 171 } The error "Patron creation failed!" comes from members/memberentry.pl: 424 ### Error checks should happen before this line. 425 $nok = $nok || scalar(@errors); 426 if ((!$nok) and $nodouble and ($op eq 'insert' or $op eq 'save')){ 427 my $success; 428 if ($op eq 'insert'){ 429 # we know it's not a duplicate borrowernumber or there would already be an error 430 delete $newdata{password2}; 431 $patron = eval { Koha::Patron->new(\%newdata)->store }; 432 if ( $@ ) { 433 # FIXME Urgent error handling here, we cannot fail without relevant feedback 434 # Lot of code will need to be removed from this script to handle exceptions raised by Koha::Patron->store 435 warn "Patron creation failed! - $@"; # Maybe we must die instead of just warn 436 push @messages, {error => 'error_on_insert_patron'}; 437 $op = "add"; This happens in two different instances on the same server, but not on other servers with similar setups. Koha version: 22.11.10-2 (Debian packages) OS: Ubuntu 18.04.6 LTS DB: 10.3.38-MariaDB-0ubuntu0.20.04.1-log Must be related to bug 26639, I guess. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8