November 2023 - 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 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 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 16959] New: E-mail alerts for saved searches
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '23

05 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16959 Bug ID: 16959 Summary: E-mail alerts for saved searches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org It would be nice if Koha allowed to send e-mails to patrons when a new record is created for a saved search. Examples: - New records are added within a specific call number range - New records where the title contains certain words It should be possible to set this up individually per patron. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 34850] New: MySQL 8 test suite output is full of warnings regarding mysql_native_password
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '23

05 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34850 Bug ID: 34850 Summary: MySQL 8 test suite output is full of warnings regarding mysql_native_password Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org "Plugin mysql_native_password reported: ''mysql_native_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'" -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 32448] New: Datatable filtering problem whith hidden column
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '23

05 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32448 Bug ID: 32448 Summary: Datatable filtering problem whith hidden column Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In biblio record details page for items table : When a column is hidden, the column filters seems have problem. Test plan for KTD : 1) Go to /cgi-bin/koha/catalogue/detail.pl?biblionumber=312 2) See that by default in items table columns 'Checkouts' and 'Renewals' (after 'Last seen') are hidden by default 3) Activate filters 4) Search in column 'Date accessioned' with '2', no results 5) Hide column 'Item type' 6) Search in column 'Collection' with 'e', no results Looks like the search is performed on next column. 7) Search in column 'Home library' with 'Reference', no line is filtered! -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 30406] New: Our DT tables not filtering on the correct column if hidden by default
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '23

05 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30406 Bug ID: 30406 Summary: Our DT tables not filtering on the correct column if hidden by default 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org To recreate, hide city_state for the cities table, create some cities and notice that using the "Country" column filter will actually filter on the hidden "State" column (the one on the left) Coming from bug 30063 comment 23 (point 5) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 35381] New: Add list_borrowers permission for viewing patron data
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '23

04 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35381 Bug ID: 35381 Summary: Add list_borrowers permission for viewing patron data Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, we need the "edit_borrowers" to view patron data, but this causes users to need an excessive level of permission to just view data. Let's add a "list_borrowers" subpermission so that a user can view the patron information but not add/update patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31025] New: Reports with too many params can exceed length limit of URI
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '23

04 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31025 Bug ID: 31025 Summary: Reports with too many params can exceed length limit of URI 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Our reports submit the form as a GET request - this is useful for saving links to report results, however, when using the <<Param|list>> feature, too much data can be submitted to the form and cause a 414 error: Request-URI Too Long The requested URL's length exceeds the capacity limit for this server. Apache/2.4.53 (Debian) Server at kohadev-intra.myDNSname.org Port 80 We should, optionally, submit large requests as 'POST' Dirty sample code: $("#rep_guided_reports_start textarea[id^='sql_params']").change(function(){ console.log('Garsh'); let param_length = 0; $("textarea[id^='sql_params']").each(function(index,value){ param_length += $(this).val().length; }); if( param_length > 900 ){ $("#rep_guided_reports_start form").attr('method','post'); $("#rep_guided_reports_start form input[type='submit']").after('<p>Too much params! Wil submit as post!</p>'); } }); -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4