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

[Bug 15678] New: Make pickup branch editable on holds tab on circulation/patron detail screens
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15678 Bug ID: 15678 Summary: Make pickup branch editable on holds tab on circulation/patron detail screens Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 9528 added a pickup at column to the holds tab on the circulation/patron detail screens. Liz Rea mentioned, "it should be editable without deleting and re-adding the reserve." I'm filing a new bug with that suggestion. That would be quite useful to have. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 17669] New: Add purging temporary uploads to cleanup_database
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '20

07 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17669 Bug ID: 17669 Summary: Add purging temporary uploads to cleanup_database Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org 17501 will start a move to Koha::Objects. On top of that we should add this one. -- You are receiving this mail because: You are watching all bug changes.

1 74

[Bug 17831] New: Item Search fails on custom subject search field
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '19

20 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17831 Bug ID: 17831 Summary: Item Search fails on custom subject search field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If I add an Item Search Field: Name: Subj Label: Subj Head MARC field: 650 MARC subfield: a Auth values: N/A I get an error when doing the item search: DBD::mysql::st execute failed: Unknown column 'bibliosubject.subject' in 'where clause' [for Statement " SELECT SQL_CALC_FOUND_ROWS items.* FROM items LEFT JOIN biblio ON biblio.biblionumber = items.biblionumber LEFT JOIN biblioitems ON biblioitems.biblioitemnumber = items.biblioitemnumber LEFT JOIN biblio_metadata ON biblio_metadata.biblionumber = biblio.biblionumber WHERE 1 AND (bibliosubject.subject like ?) AND biblio_metadata.format = 'marcxml' AND biblio_metadata.marcflavour = ? ORDER BY title ASC LIMIT ?, ? " with ParamValues: 0="juvnile%", 1='MARC21', 2=0, 3=20] at /home/vagrant/kohaclone/C4/Items.pm line 2798. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 16688] New: RenewSerialAddsSuggestion - suggestions not showing up, note not saved
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '19

16 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16688 Bug ID: 16688 Summary: RenewSerialAddsSuggestion - suggestions not showing up, note not saved Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When renewing a serial subscription with RenewSerialAddsSuggestion set to active, an entry is added to the suggestions table in Koha. The status is "ASKED" and the biblionumber is column is set to the existing record. But the suggestion isn't shown in the acquisition module - it cannot be found using the search options in suggestions, it doesn't show in the pending tab. Because the status is "ASKED", there is no way to create an order for it. When renewing the subscription, there is a note field you can fill out "for the librarian to process the order" - but this information is not stored in suggestion table and seems to be lost. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[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 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