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

[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 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 28966] New: Holds queue viewer too slow to load for large numbers of holds
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28966 Bug ID: 28966 Summary: Holds queue viewer too slow to load for large numbers of holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We have a partner processing thousands of holds per day, per branch. At this number of holds, the script loads very slow if it manages to load at all. The primary slowdown is the individual fetch of the patron for each hold to be displayed. If we prefetch those patrons, the entire script should load much faster. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 76

[Bug 25328] New: Date formatting from JS - Remove tz handling
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25328 Bug ID: 25328 Summary: Date formatting from JS - Remove tz handling Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com Depends on: 24455, 24980 After some discussion, I now believe timezone handling in JS is redundant, and should be removed. Dates that comes from the API are already converted to the corresponding timezone with dt_from_string, so there is no need for a second conversion here. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24455 [Bug 24455] Date formatting from JS https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24980 [Bug 24980] Date formatting from JS - use timezone only with dates with offset -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 19616] New: Formatted Contents Note (Marc 21 505), subfield g isn' t visible in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19616 Bug ID: 19616 Summary: Formatted Contents Note (Marc 21 505), subfield g isn't visible in the OPAC Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org The 505 field in Marc 21, Formatted Contents Note, includes subfield g "Miscellaneous information". According to the Marc 21 format for bibliographic data, it is used to record "volume, part, page numbering or other extent information such as dates". If you use it in Koha, this information isn't visible in the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 29905] New: Superlibrarians should be able to delete any patron messages
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29905 Bug ID: 29905 Summary: Superlibrarians should be able to delete any patron messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Superlibrarians are generally exempted from branch limits, they should be able to delete a message on a patron account left by any library regardless of AllowAllMessageDeletion syspref setting -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 25467] New: Improve performance of ViewPolicy filter
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25467 Bug ID: 25467 Summary: Improve performance of ViewPolicy filter Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Rather than looping through every field of every record, it might be better to determine which fields must be hidden, then deal only with those? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24261] New: Google openID Authethication drops requested url
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24261 Bug ID: 24261 Summary: Google openID Authethication drops requested url Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: mihai.bojonca(a)tcmi.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Hi everyone, i think this is a bug, we have setup access to catalog after login, we use 2 authentication methods, username and password or google openid, when a patron opens a direct link to an item and authenticates with username and password they get to the item itself however with openid they get redirected to the opac main page -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 25221] New: Imported records are not checked for accuracy
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25221 Bug ID: 25221 Summary: Imported records are not checked for accuracy Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When you create a new bib record, Koha checks if certain fields are filled out. When you import a bib record, Koha does not check if that record has those fields filled out. I would suggest that when a record is imported, it either needs to be taken immediately into editing so that Koha can catch issues, or it needs to be put into a quarantine state, and unusable anywhere in the system until it is edited and saved. When importing a bib for an order, since you are dealing with a single record, I could see how going straight into editing after importing could work. However, if you are importing bibs through an batch import tool, if the process isn't already checking for issues or missing fields, these items should be set in quarantine and require the cataloger to edit the record to remove it from quarantine. This process would address problems elsewhere in Koha where incomplete or compromised records cause an error in Koha or in a process that can't complete due to a faulty record. I'm not a cataloger, but this seems like a reasonable workflow for bringing outside records into your own system. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 24967] New: Allow final user to choose ordering column
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24967 Bug ID: 24967 Summary: Allow final user to choose ordering column Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: pascale.nalon(a)mines-paristech.fr QA Contact: testopia(a)bugs.koha-community.org It would be fine, if members of staff, who have not permissions to modify a SQL requests, but only to run them, could choose the column and the way (ASC or DESC) to order the pre-builded request -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1