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

[Bug 17160] New: Foreign key constraint for message_transports is too loose
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '19

16 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17160 Bug ID: 17160 Summary: Foreign key constraint for message_transports is too loose 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I think this is the probable cause for Bug 13171. http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=installer/data/my… The message transports definition -- -- Table structure for table `message_transports` -- DROP TABLE IF EXISTS `message_transports`; CREATE TABLE `message_transports` ( `message_attribute_id` int(11) NOT NULL, `message_transport_type` varchar(20) NOT NULL, `is_digest` tinyint(1) NOT NULL default '0', `letter_module` varchar(20) NOT NULL default '', `letter_code` varchar(20) NOT NULL default '', `branchcode` varchar(10) NOT NULL default '', PRIMARY KEY (`message_attribute_id`,`message_transport_type`,`is_digest`), KEY `message_transport_type` (`message_transport_type`), KEY `letter_module` (`letter_module`,`letter_code`), CONSTRAINT `message_transports_ibfk_1` FOREIGN KEY (`message_attribute_id`) REFERENCES `message_attributes` (`message_attribute_id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `message_transports_ibfk_2` FOREIGN KEY (`message_transport_type`) REFERENCES `message_transport_types` (`message_transport_type`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `message_transports_ibfk_3` FOREIGN KEY (`letter_module`, `letter_code`, `branchcode`) REFERENCES `letter` (`module`, `code`, `branchcode`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; Has `message_transport_types` (`message_transport_type`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `message_transports_ibfk_3` FOREIGN KEY (`letter_module`, `letter_code`, `branchcode`) REFERENCES `letter` (`module`, `code`, `branchcode`) ON DELETE CASCADE ON UPDATE CASCADE The foreign key contstraints `module`, `code`, `branchcode` do *NOT* uniquely identify a row in the letter table, because message_transport_type may vary. Therefore, a deletion *any* message transport type will delete *all* rows matching `module`, `code`, `branchcode`. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 18097] New: It is possible to create unusable category codes (ccode) due to field length mismatch
by bugzilla-daemon＠bugs.koha-community.org 12 Dec '19

12 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18097 Bug ID: 18097 Summary: It is possible to create unusable category codes (ccode) due to field length mismatch Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The column items.ccode is 10 characters long. It references authorised values of the type CCODE. The maximum length of an authorised value is 80 characters long. If a CCODE is created with a value greater than 10, when it is stored for the item it will be truncated and become either a) an invalid ccode or b) match a different ccode! The solution should be to increase the items.ccode column from varchar(10) to varchar(80). This really goes for all columns that could possibly store an authorised value. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 18428] New: Duplicate key error in old_reserves table.
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '19

11 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18428 Bug ID: 18428 Summary: Duplicate key error in old_reserves table. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I'm not exactly sure how we got ourseleves into this situation, but one of our libraries is getting the following error when trying to check in an item that is on hold: DBD::mysql::st execute failed: Duplicate entry '39' for key 'PRIMARY' [for Statement "INSERT INTO `old_reserves` ( `biblionumber`, `borrowernumber`, `branchcode`, `cancellationdate`, `expirationdate`, `found`, `itemnumber`, `itemtype`, `lowestPriority`, `notificationdate`, `priority`, `reminderdate`, `reserve_id`, `reservedate`, `reservenotes`, `suspend`, `suspend_until`, `timestamp`, `waitingdate`) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )" with ParamValues: 0='11198', 1='693', 2='CFOT', 3=undef, 4=undef, 5='F', 6=undef, 7=undef, 8='0', 9=undef, 10=0, 11=undef, 12='39', 13='2017-04-13', 14='', 15='0', 16=undef, 17='2017-04-13 06:19:29', 18=undef] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1832. DBIx::Class::Storage::DBI::_dbh_execute(): Duplicate entry '39' for key 'PRIMARY' at /usr/share/koha/lib/Koha/Object.pm line 120 This is analogous to bug 18242 for old_issues. I wonder if we need to do the same thing for the deleted* tables. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 17774] New: Acquisitions module getting internal server error when adding orders to basket - a case of barcode not autoincrementing (?)
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '19

11 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17774 Bug ID: 17774 Summary: Acquisitions module getting internal server error when adding orders to basket - a case of barcode not autoincrementing (?) Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: eugenegf(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org In a new Koha 16.11 instance, when adding orders to basket with the following system preferences: a) AcqCreateItem = placing an order b) autoBarcode is set to generated in the form <branchcode>yymm0001. c) plack enabled d) 952$o has plugin 'barcode.pl' A barcode is not filled up (just clicked 'Add item' button) during adding of items since it is implicitly stated in the interface: "The autoBarcode system preference is set to hbyymmincr and items with blank barcodes will have barcodes generated upon save to database." However, when the order is being saved, I am getting internal server error. So, I have to click the Back button to go back to what I'm doing. And when I returned to the "add orders to basket" interface, and then click save to finish the transaction, I am able to finish the transaction, however, I now get two items ordered, first one with only the title and the second one has the title and the patron who suggested the material (see http://koha.1045719.n5.nabble.com/file/n5913371/acqui_internal_server_error…) Tried this in another server with same database, however I'm getting "Software error: DBIx::Class::Storage::DBI::_dbh_execute(): Column 'itemnumber' cannot be null at /usr/share/koha/lib/Koha/Acquisition/Order.pm line 68" But when brought to the Basket no., I can see the order. Delving into the plack-error message in the first server: No existing hbyymmincr barcodes found. Reverting to initial value. at /usr/share/koha/lib/C4/Barcodes/hbyymmincr.pm line 62. DBD::mysql::st execute failed: Duplicate entry 'DLSU-D16120002' for key 'itembarcodeidx' [for Statement "INSERT INTO items SET biblionumber = ?, biblioitemnumber = ?, barcode = ?, dateaccessioned = ?, booksellerid = ?, homebranch = ?, price = ?, replacementprice = ?, replacementpricedate = ?, datelastborrowed = ?, datelastseen = ?, stack = ?, notforloan = ?, damaged = ?, itemlost = ?, withdrawn = ?, itemcallnumber = ?, coded_location_qualifier = ?, restricted = ?, itemnotes = ?, itemnotes_nonpublic = ?, holdingbranch = ?, paidfor = ?, location = ?, permanent_location = ?, onloan = ?, issues = ?, renewals = ?, reserves = ?, cn_source = ?, cn_sort = ?, ccode = ?, itype = ?, materials = ?, uri = ?, enumchron = ?, more_subfields_xml = ?, copynumber = ?, stocknumber = ?, new_status = ? " with ParamValues: 0="4911", 1='4911', 2="DLSU-D16120002", 3='2016-12-14', 4=undef, 5="DLSU-D", 6=undef, 7=undef, 8='2016-12-14', 9=undef, 10='2016-12-14', 11=undef, 12=0, 13=0, 14=0, 15=0, 16=undef, 17=undef, 18=undef, 19=undef, 20=undef, 21="DLSU-D", 22=undef, 23=undef, 24=undef, 25=undef, 26=undef, 27=undef, 28=undef, 29="lcc", 30='', 31=undef, 32=undef, 33=undef, 34=undef, 35=undef, 36=undef, 37=undef, 38=undef, 39=undef] at /usr/share/koha/lib/C4/Items.pm line 2119. DBD::mysql::st execute failed: Column 'itemnumber' cannot be null [for Statement "INSERT INTO `aqorders_items` ( `itemnumber`, `ordernumber`) VALUES ( ?, ? )" with ParamValues: 0=undef, 1='45'] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1832. And the second server's intranet error log snippet: [Wed Dec 14 18:15:55.903548 2016] [cgi:error] [pid 19570] [client 112.198.75.180:54634] AH01215: [Wed Dec 14 18:15:55 2016] addorder.pl: " with ParamValues: 0="4914", 1='4913', 2="DLSU-D16120002", 3='2016-12-14', 4=undef, 5="DLSU-D", 6=undef, 7=undef, 8='2016-12-14', 9=undef, 10='2016-12-14', 11=undef, 12=0, 13=0, 14=0, 15=0, 16=undef, 17=undef, 18=undef, 19=undef, 20=undef, 21="DLSU-D", 22=undef, 23=undef, 24=undef, 25=undef, 26=undef, 27=undef, 28=undef, 29="lcc", 30='', 31=undef, 32=undef, 33=undef, 34=undef, 35=undef, 36=undef, 37=undef, 38=undef, 39=undef] at /usr/share/koha/lib/C4/Items.pm line 2119. I feel that the barcode is not auto-incrementing (but I don't know why it isn't) as I see in the first server the same barcode 'DLSU-D16120002' is showing up several times, and this is supposed to be incremented. I also see that this barcode is already used by another item. A discussion of this is in http://koha.1045719.n5.nabble.com/Acquisitions-module-internal-server-error… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 16655] New: ERROR ON HOLIDAYS
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '19

05 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16655 Bug ID: 16655 Summary: ERROR ON HOLIDAYS Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: hblancoca(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Hi, I created holidays for vacation period, if i borrow a book on staff inferface have no problems,but if so the same over SIP2 protocol do no take the holidays defined. For example: humberto blanco can borrow book for 8 days. If checkout from staff interface in 2016-06-03 has no problem and the date_due take all my holidays (2016-07-25); but if I do the same process over 3m selfcheck machine the date_due is (2016-06-11) Really appreciate your help to solve this issue Humberto, -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 17826] New: Allow extended patron attributes to be sent in arbitrary SIP2 fields
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '19

03 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17826 Bug ID: 17826 Summary: Allow extended patron attributes to be sent in arbitrary SIP2 fields Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Some libraries need to be able to send additional patron data from the extended patron attributes in made up SIP2 fields for the patron information and patron status responses. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 17768] New: spinelabel.css should be user editable.
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '19

02 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17768 Bug ID: 17768 Summary: spinelabel.css should be user editable. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The quick-label CSS file is currently part of the Koha distribution, stored at koha-tmpl/intranet-tmpl/prog/en/css/spinelabel.css. This means that users who use package Koha cannot change the styling of the quick slips without resorting to javascript. I would suggest that koha-tmpl/intranet-tmpl/prog/en/css/spinelabel.css be a default, but that we can change this via syspref. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 16887] New: Entering a bad date in 'Koha out on loan' field sets items.onloan to 0000-00-00.
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '19

28 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16887 Bug ID: 16887 Summary: Entering a bad date in 'Koha out on loan' field sets items.onloan to 0000-00-00. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To re-create 1/ Go to Circulation->Fast Cataloging 2/ Add a biblio record 3/ On Add Items screen, enter a space in 'Koha out on loan' (and enter item type of course). Save the item. 4/ items.onloan will be set to 0000-00-00. ... I'm not certain whether or not this is specific to the fast add framework. Note that this causes upstream issues with search -- any item that has items.onloan set to 0000-00-00 will cause an internal server error on the search results page, with the following error in plack.error.log: Can't locate object method "ymd" via package "dateonly" (perhaps you forgot to load "dateonly"?) at /usr/share/koha/li b/Koha/DateUtils.pm line 223. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 17526] New: OPAC lists require a sortfield
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '19

27 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17526 Bug ID: 17526 Summary: OPAC lists require a sortfield Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Using the OPAC, going into the public lists, I click one of them and get DBIx::Class::Storage::DBI::_dbh_execute(): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ASC LIMIT 10) `me` JOIN `biblio` `biblionumber` ON `biblionumber`.`biblionumber' THis is because the sortfield is empty and creates a SQL like GROUP BY ASC LIMIT 10. Missing the group by. In the intranet list, there's a default usage of 'title' that makes it all work. TESTING: 1) just create a public list with no sortfield. - virtualshelves.category = 2 - virtualshelves.sortfield = '' 2) click on the list in the OPAC's public list. Boom! -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 17851] New: Add elasticsearch config to koha-conf.xml
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '19

26 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17851 Bug ID: 17851 Summary: Add elasticsearch config to koha-conf.xml Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Following the Elasticsearch installation instructions from: https://wiki.koha-community.org/wiki/Elasticsearch the <elasticsearch> config seems to be missing. This patch adds interactive Elasticsearch-questions to the Makefile.PL to configure ES. -- You are receiving this mail because: You are watching all bug changes.

1 25