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

[Bug 32675] New: Cannot add a guarantor when there is a single quote in the guarantor attributes
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '24

04 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32675 Bug ID: 32675 Summary: Cannot add a guarantor when there is a single quote in the guarantor attributes 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: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It's impossible to select a guarantor when there is a single quote in the guarantor attributes. This patch allows to add a guarantor even if there is a single quote in guarantor attributes. Test plan 1. Find two patrons: - Patron 1 = guarantee - Patron 2 = guarantor 2. In the patron 2 account, add a single quote in one of the "Alternate address" or "Contact information" fields (like the "Address" field) for example type «L'Aqueduc» in the field and save 3. Edit the patron 1 and click on "Add guarantor" 4. Search for the patron 2 5. Click on "Select" --> Nothing happens 6. Apply the patch 9. repeat step 3, 4 and 5 10. Now Patron 2 is added as guarantor -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 32233] New: Cannot add a guarantor when patron attributes have certain characters
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '24

04 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32233 Bug ID: 32233 Summary: Cannot add a guarantor when patron attributes have certain characters 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. Setup a patron attribute 2. Setup an authorized value category and link it to the new patron attribute 3. Make sure the new authorized value category has a code like 'Driver's License'. 4. Make sure that patron has been give that value in the patron attribute. 5. Now try to link a child account to that borrower. Nothing happens but you will see a console error like: JSON.parse: unterminated string at line 1 column 892 of the JSON data -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 35332] New: gulp po:update (may) generates incorrect Koha-messages.pot
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '24

04 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35332 Bug ID: 35332 Summary: gulp po:update (may) generates incorrect Koha-messages.pot Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: translate.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 35079 >From bug 35079 comment 9, this is still valid. [11:13:51] Error: Command failed: msgmerge --backup=off --no-wrap --quiet -F --update misc/translator/po/de-DE-messages.po misc/translator/Koha-messages.pot misc/translator/Koha-messages.pot:11:35: syntax error misc/translator/Koha-messages.pot:11: keyword "n" unknown misc/translator/Koha-messages.pot:12: end-of-line within string msgmerge: found 3 fatal errors at ChildProcess.exithandler (node:child_process:419:12) at ChildProcess.emit (node:events:513:28) at ChildProcess.emit (node:domain:552:15) at maybeClose (node:internal/child_process:1091:16) at Socket.<anonymous> (node:internal/child_process:449:11) at Socket.emit (node:events:513:28) at Socket.emit (node:domain:552:15) at Pipe.<anonymous> (node:net:321:12) at Pipe.callbackTrampoline (node:internal/async_hooks:130:17) [11:13:51] 'po:update' errored after 31 s It's really hard to debug as it happens randomly. It's either coming from the merge of the header or 2 processes writing into the same file at the same time The problem is always the same, the extract of the strings generates line 11 of Koha-messages.pot with an extra quote: "Content-Transfer-Encoding: 8bit"\n" instead of "Content-Transfer-Encoding: 8bit\n" And so the update of the .tt fail because msgmerge fail to read the .pot file. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35079 [Bug 35079] Add option to gulp tasks po:update and po:create to control if POT should be built -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 28267] New: Koha-common package upgrade problem from 20.05.xx to 20.11.04-1
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '24

04 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28267 Bug ID: 28267 Summary: Koha-common package upgrade problem from 20.05.xx to 20.11.04-1 Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: skaman.tx(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Our koha installation is on Debian 10. Upgrade challenges str specifically related to the outcome of the Debian package koha-common upgrade scripts. We are stuck at koha-common version 20.05.xx at this point. My latest attempt to upgrade to 20.11.04-1 resulted in the following three error messages. Is there any way to manually alter the correct table(s) to fix the database issues? I'm not sure what the "Failed to enable unit" message means. ---------------------------- Setting up koha-common (20.11.04-1) ... Installing new version of config file /etc/cron.daily/koha-common ... Installing new version of config file /etc/init.d/koha-common ... Installing new version of config file /etc/koha/SIPconfig.xml ... Installing new version of config file /etc/koha/apache-shared-intranet-plack.conf ... Installing new version of config file /etc/koha/apache-shared-intranet.conf ... Installing new version of config file /etc/koha/apache-shared-opac.conf ... Installing new version of config file /etc/koha/koha-conf-site.xml.in ... Installing new version of config file /etc/koha/log4perl-site.conf.in ... Installing new version of config file /etc/koha/plack.psgi ... Installing new version of config file /etc/koha/zebradb/etc/phrases-icu.xml ... Installing new version of config file /etc/koha/zebradb/etc/word-phrase-utf.chr ... Upgrading database schema for [database] ....... Upgrade to 20.06.00.031 done [10:19:38]: Bug 22789 - Add non_priority column on reserves and old_reserves tables DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs [for Statement "ALTER TABLE `items` ADD COLUMN `exclude_from_local_holds_priority` tinyint(1) default NULL AFTER `new_status`"] at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 22709. DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs [for Statement "ALTER TABLE `deleteditems` ADD COLUMN `exclude_from_local_holds_priority` tinyint(1) default NULL AFTER new_status`"] at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 22715. ...... Failed to enable unit: Unit /run/systemd/generator.late/koha-common.service is transient or generated. ---------------------------- NOTE: When I then run "/usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -a -z" in this post-upgrade state I get the following error for each biblio record: DBD::mysql::st execute failed: Unknown column 'me.exclude_from_local_holds_priority' in 'field list' [for Statement "SELECT `me`.`itemnumber`, `me`.`biblionumber`, `me`.`biblioitemnumber`, `me`.`barcode`, `me`.`dateaccessioned`, `me`.`booksellerid`, `me`.`homebranch`, `me`.`price`, `me`.`replacementprice`, `me`.`replacementpricedate`, `me`.`datelastborrowed`, `me`.`datelastseen`, `me`.`stack`, `me`.`notforloan`, `me`.`damaged`, `me`.`damaged_on`, `me`.`itemlost`, `me`.`itemlost_on`, `me`.`withdrawn`, `me`.`withdrawn_on`, `me`.`itemcallnumber`, `me`.`coded_location_qualifier`, `me`.`issues`, `me`.`renewals`, `me`.`reserves`, `me`.`restricted`, `me`.`itemnotes`, `me`.`itemnotes_nonpublic`, `me`.`holdingbranch`, `me`.`timestamp`, `me`.`location`, `me`.`permanent_location`, `me`.`onloan`, `me`.`cn_source`, `me`.`cn_sort`, `me`.`ccode`, `me`.`materials`, `me`.`uri`, `me`.`itype`, `me`.`more_subfields_xml`, `me`.`enumchron`, `me`.`copynumber`, `me`.`stocknumber`, `me`.`new_status`, `me`.`exclude_from_local_holds_priority` FROM `items` `me` WHERE ( `me`.`itemnumber` = ? )" with ParamValues: 0=1] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1836. error retrieving biblio 1 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 686. I understand this database error was previously affecting a different table and was addressed in bug 24986. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24986 Looks like a patch is needed to cure this one as well. I am not a programmer so turning to the bug list for help. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 94

[Bug 30777] New: stockrotationitems table could store additional information
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '24

04 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30777 Bug ID: 30777 Summary: stockrotationitems table could store additional information Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It would be very helpful if stockrotationitems had more information, especially when it was added to the rota. It might also be helpful to have when the last time it was moved by the stock rotation cron. If we could also have the remaining duration that would be great, but I also think would be trickier. Lisette -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 6416] koha-remove fails when dropping user
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '24

04 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6416 Jonathan Druart <jonathan.druart+koha(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |24383 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24383 [Bug 24383] koha-create doesn't restart / empty memcached causing installer fail -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 9725] Add support to notices for hourly loans
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '24

04 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9725 Ray Delahunty <r.delahunty(a)arts.ac.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |r.delahunty(a)arts.ac.uk --- Comment #1 from Ray Delahunty <r.delahunty(a)arts.ac.uk> --- In the meantime we are using the patron_emailer_pl functionality to send 'late' notices for hourly loans. For example when a laptop loaned for 5 hours goes late, the email is sent within a few minutes. OK it means running the emailer script often: */5 * * * * /usr/share/koha/bin/cronjobs/patron_emailer.pl --report 974 --notice ODUE_LAPTOP --module circulation --commit Better than nothing, I suppose. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 32162] New: erm_eholdings_packages_agreements does not have a primary key
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '24

04 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32162 Bug ID: 32162 Summary: erm_eholdings_packages_agreements does not have a primary key Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 32030 And TestBuilder.t is failing because of this. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32030 [Bug 32030] Electronic resource management (ERM) -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 26912] New: Expired staff accounts can still log in to Koha staff intranet
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26912 Bug ID: 26912 Summary: Expired staff accounts can still log in to Koha staff intranet Change sponsored?: --- Product: Koha Version: master 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We just discovered that staff accounts can be used for staff logins, SIP, API, etc even if they are expired. The question we don't have an answer to is; should this be allowed? We could prevent staff logins for expired accounts, or perhaps add a new 'enabled' column to explicitly enable/disable accounts from logging in to Koha. Right now, the only way to disable an account without deleting it is to remove user permissions, which may be non trivial if the account has complicated permissions and may need to be 'restored' in the future. What do you all think? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 34284] New: Customize the Accountlines Description: Lost Items
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34284 Bug ID: 34284 Summary: Customize the Accountlines Description: Lost Items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Similar to Bug 24865, it would be great if this could be expanded to include lost items with a separate notice. Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4