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

[Bug 35543] New: Error message when upgrading from 23.05 to 23.11
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '23

12 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35543 Bug ID: 35543 Summary: Error message when upgrading from 23.05 to 23.11 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: vctrzuniga(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Hello, I was finishing the upgrade on our catalog from 23.05 to 23.11 via the web interface this evening when I got the following error message: ===== Updating database structure Update errors : Upgrade to 23.06.00.007 [22:25:29]: Bug 34029 - Extend datatypes in biblioitems and deletedbiblioitems tables to avoid import errors ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: BLOB/TEXT column 'publishercode' used in key specification without a key length at /usr/share/koha/lib/C4/Installer.pm line 741 Updated biblioitems.place to text ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: BLOB/TEXT column 'publishercode' used in key specification without a key length at /usr/share/koha/lib/C4/Installer.pm line 741 Updated deletedbiblioitems.place to text ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: BLOB/TEXT column 'publishercode' used in key specification without a key length at /usr/share/koha/lib/C4/Installer.pm line 741 ===== I checked both tables and the column is there: ========= mysql> show columns from biblioitems; +-----------------------+--------------+------+-----+-------------------+-----------------------------------------------+ | Field | Type | Null | Key | Default | Extra | +-----------------------+--------------+------+-----+-------------------+-----------------------------------------------+ | biblioitemnumber | int | NO | PRI | NULL | auto_increment | | biblionumber | int | NO | MUL | 0 | | | volume | longtext | YES | | NULL | | | number | longtext | YES | | NULL | | | itemtype | varchar(10) | YES | MUL | NULL | | | isbn | longtext | YES | MUL | NULL | | | issn | longtext | YES | MUL | NULL | | | ean | longtext | YES | MUL | NULL | | | publicationyear | mediumtext | YES | | NULL | | | publishercode | varchar(255) | YES | MUL | NULL | | | volumedate | date | YES | | NULL | | | volumedesc | mediumtext | YES | | NULL | | | collectiontitle | longtext | YES | | NULL | | | collectionissn | mediumtext | YES | | NULL | | | collectionvolume | longtext | YES | | NULL | | | editionstatement | mediumtext | YES | | NULL | | | editionresponsibility | mediumtext | YES | | NULL | | | timestamp | timestamp | NO | MUL | CURRENT_TIMESTAMP | DEFAULT_GENERATED on update CURRENT_TIMESTAMP | | illus | varchar(255) | YES | | NULL | | | pages | varchar(255) | YES | | NULL | | | notes | longtext | YES | | NULL | | | size | varchar(255) | YES | | NULL | | | place | text | YES | | NULL | | | lccn | longtext | YES | | NULL | | | url | mediumtext | YES | | NULL | | | cn_source | varchar(10) | YES | | NULL | | | cn_class | varchar(30) | YES | | NULL | | | cn_item | varchar(10) | YES | | NULL | | | cn_suffix | varchar(10) | YES | | NULL | | | cn_sort | varchar(255) | YES | | NULL | | | agerestriction | varchar(255) | YES | | NULL | | | totalissues | int | YES | | NULL | | +-----------------------+--------------+------+-----+-------------------+-----------------------------------------------+ 32 rows in set (0.00 sec) mysql> mysql> show columns from deletedbiblioitems; +-----------------------+--------------+------+-----+-------------------+-----------------------------------------------+ | Field | Type | Null | Key | Default | Extra | +-----------------------+--------------+------+-----+-------------------+-----------------------------------------------+ | biblioitemnumber | int | NO | PRI | 0 | | | biblionumber | int | NO | MUL | 0 | | | volume | longtext | YES | | NULL | | | number | longtext | YES | | NULL | | | itemtype | varchar(10) | YES | MUL | NULL | | | isbn | longtext | YES | MUL | NULL | | | issn | longtext | YES | | NULL | | | ean | longtext | YES | MUL | NULL | | | publicationyear | mediumtext | YES | | NULL | | | publishercode | varchar(255) | YES | MUL | NULL | | | volumedate | date | YES | | NULL | | | volumedesc | mediumtext | YES | | NULL | | | collectiontitle | longtext | YES | | NULL | | | collectionissn | mediumtext | YES | | NULL | | | collectionvolume | longtext | YES | | NULL | | | editionstatement | mediumtext | YES | | NULL | | | editionresponsibility | mediumtext | YES | | NULL | | | timestamp | timestamp | NO | MUL | CURRENT_TIMESTAMP | DEFAULT_GENERATED on update CURRENT_TIMESTAMP | | illus | varchar(255) | YES | | NULL | | | pages | varchar(255) | YES | | NULL | | | notes | longtext | YES | | NULL | | | size | varchar(255) | YES | | NULL | | | place | text | YES | | NULL | | | lccn | longtext | YES | | NULL | | | url | mediumtext | YES | | NULL | | | cn_source | varchar(10) | YES | | NULL | | | cn_class | varchar(30) | YES | | NULL | | | cn_item | varchar(10) | YES | | NULL | | | cn_suffix | varchar(10) | YES | | NULL | | | cn_sort | varchar(255) | YES | | NULL | | | agerestriction | varchar(255) | YES | | NULL | | | totalissues | int | YES | | NULL | | +-----------------------+--------------+------+-----+-------------------+-----------------------------------------------+ 32 rows in set (0.01 sec) mysql> ========= I also looked at the code from file '/usr/share/koha/lib/C4/Installer.pm' on line 741 (last line) which is displayed below: ====== try { 736 my $schema = Koha::Database->new->schema; 737 $schema->txn_do( 738 sub { 739 $db_rev->{up}->( { dbh => $schema->storage->dbh, out => $outfh } ); 740 } 741 ); ====== A quick Google search took me to this page: https://stackoverflow.com/questions/1827063/mysql-error-key-specification-w… Based on the response, it has something to do with converting (or attempting) the data type for this particular column. The response from the link above says the varchar data type on the column should have an explicit character limit which it seems to have it set, from the show columns statement above. Any help would be greatly appreciated. Thanks, Victor -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 32578] New: Wildcard searches do not work with asterisk
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '23

12 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32578 Bug ID: 32578 Summary: Wildcard searches do not work with asterisk Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: estherm(a)sodaspringsid.com QA Contact: testopia(a)bugs.koha-community.org This bug is split off from bug 32491 and this is what I reported there: Prior to our upgrade to 22.05, we could do searches like 2913*3456 and have it return results. After the upgrade this no longer works. The % wildcard appears to work in the search example above. However the % as a wildcard is odd when compared with how other search indexes work. Most major search engines use either an asterisk or a question mark. The same is true with searching indexes at Ancestry or Family Search. The asterisk replaces multiple characters and the question mark replaces a single character. Most of our staff is accustomed to using an asterisk and trying to adapt to a different nomenclature and keyboard position has proven difficult. Since the asterisk worked prior to 22.05, it would be nice to return that functionality. Also Lucas Gass reported: This also effects wildcard searches. Previously you could search for a cardnumber like '2913*' and that would return all patrons with cardnumbers starting with '2913'. Now it tries searching for the exact match '2352*' and returns nothing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 35551] New: Customize checkin messaging for bundle items
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '23

12 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35551 Bug ID: 35551 Summary: Customize checkin messaging for bundle items Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kkperry(a)hagerstowncc.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When checking in an individual item that is part of a bundle, we currently get a dialog button "Remove from bundle." We would like to be able to hide this and/or customize the text and function for this button. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 11300] Add a new authority linker which searches for authority links on a Z39.50 server.
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '23

12 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11300 Salah Ghedda <salah.ghedda(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |salah.ghedda(a)inlibro.com --- Comment #68 from Salah Ghedda <salah.ghedda(a)inlibro.com> --- Rebased -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11300] Add a new authority linker which searches for authority links on a Z39.50 server.
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '23

12 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11300 Salah Ghedda <salah.ghedda(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #155603|0 |1 is obsolete| | --- Comment #67 from Salah Ghedda <salah.ghedda(a)inlibro.com> --- Created attachment 159742 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=159742&action=e… Bug 11300: (Fix) Fixing the authority linking -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11300] Add a new authority linker which searches for authority links on a Z39.50 server.
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '23

12 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11300 Salah Ghedda <salah.ghedda(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #155602|0 |1 is obsolete| | --- Comment #66 from Salah Ghedda <salah.ghedda(a)inlibro.com> --- Created attachment 159741 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=159741&action=e… Bug 11300: Add a new authority linker which searches for authority links on a Z39.50 server. This patch adds a Z39.50 Linker which searches for authority links on a remote server. If a matching authority is found, it's imported in the local database for linking with the current biblio record. If no matching authority was found on the remote server, the Linker falls back to a local authority search. Configuration : * The option "Z39.50 Server" is added to the LinkerModule preference. You must choose this to use the new Linker. * The preference LinkerZ3950Server is required and specifies which server to use for linking. It must contain the "name" of the server, as defined in the z3950servers table. * You can set the "local_first" option in the LinkerOptions preference to force the Linker to search for authorities in the local database first. If no local authority match was found, the Linker falls back to a remote Z39.50 search. Sponsored-by: CCSR ( http://www.ccsr.qc.ca ) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7972] GUI for Crons
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '23

12 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7972 Chris Rowlands <chris.rowlands6(a)nhs.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chris.rowlands6(a)nhs.net -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35544] New: No translation is required
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '23

12 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35544 Bug ID: 35544 Summary: No translation is required Change sponsored?: --- Product: Koha Version: master 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: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org %s/cgi-bin/koha/opac-registration-verify.pl?token=%s -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 25770] New: vars loggedinusername and loggedinusernumber should be replaced by use of logged_in_user in templates
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '23

12 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25770 Bug ID: 25770 Summary: vars loggedinusername and loggedinusernumber should be replaced by use of logged_in_user in templates 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 Since all templates have the current loggedin user as logged_in_user var (a Koha::Patron object), vars loggedinusername and loggedinusernumber should be replaced in templates. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 35534] New: Wrong encoding of reports exported in tab format
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '23

12 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35534 Bug ID: 35534 Summary: Wrong encoding of reports exported in tab format 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: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Reports exported in csv are encoded in unicode. In tab they are encoding in ANSI. If a record contains unicode characters, this is problematic. Maybe linked to https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=45501&action=di… ? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2