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

[Bug 19233] New: Add ability to send itemnumbers in report results to batch modification
by bugzilla-daemon＠bugs.koha-community.org 26 Dec '19

26 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19233 Bug ID: 19233 Summary: Add ability to send itemnumbers in report results to batch modification Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 21316] New: Adding controlfields to the ACQ framework causes issues when adding to basket
by bugzilla-daemon＠bugs.koha-community.org 23 Dec '19

23 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21316 Bug ID: 21316 Summary: Adding controlfields to the ACQ framework causes issues when adding to basket Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - Export your default framework 2 - Import it into the ACQ framework 3 - Attempt to add to a basket from an existing record 4 - Internal server error: Control fields (generally, just tags below 010) do not have subfields, use data() at /home/vagrant/kohaclone/acqui/neworderempty.pl line 295. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[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 21172] New: Warning in addbiblio.pl - Argument "01e" isn't numeric in numeric ne (!=)
by bugzilla-daemon＠bugs.koha-community.org 19 Dec '19

19 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21172 Bug ID: 21172 Summary: Warning in addbiblio.pl - Argument "01e" isn't numeric in numeric ne (!=) 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(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Argument "01e" isn't numeric in numeric ne (!=) at /home/vagrant/kohaclone/cataloguing/addbiblio.pl line 507. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 21667] New: Advanced Editor - advanced search - result set is lost after repeated clicks on “next” button
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '19

18 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21667 Bug ID: 21667 Summary: Advanced Editor - advanced search - result set is lost after repeated clicks on “next” button Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: carnold(a)dgiinc.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 81173 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=81173&action=ed… results are lost after multiple “Next” buttons are pushed In the advanced cataloging editor, search for author “Shakespeare” and sort by "ISBN" results are lost after multiple “Next” buttons are pushed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[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 20808] New: I cant install Koha on Ubuntu 18.04 LTS (Bionic Beaver) - Unmet dependences
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '19

16 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20808 Bug ID: 20808 Summary: I cant install Koha on Ubuntu 18.04 LTS (Bionic Beaver) - Unmet dependences Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.messina(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hello, I am installing Koha on Ubuntu 18.04 LTS Bionic Beaver (Fresh Installation). However, I have experienced the following error when I run "sudo apt-get install koha-common" The following packages have unmet dependencies: koha-common : Depends: libmarc-charset-perl but it is not installable Depends: libmarc-xml-perl but it is not installable E: Unable to correct problems, you have held broken packages. Workaround: sudo apt-get install libmarc-record-perl sudo apt-get install libxml-sax-perl wget http://ftp.br.debian.org/debian/pool/main/libm/libmarc-charset-perl/libmarc… wget http://ftp.br.debian.org/debian/pool/main/libm/libmarc-xml-perl/libmarc-xml… sudo dpkg -i libmarc-charset-perl_1.35-2_amd64.deb libmarc-xml-perl_1.0.3-1_all.deb sudo apt-get install koha-common -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 21685] New: Name our exceptions consistently
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '19

13 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21685 Bug ID: 21685 Summary: Name our exceptions consistently Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Few examples of inconsistencies: * Koha::Exceptions::WrongParameter Koha::Exceptions::BadParameter * Koha::Exceptions::CannotDeleteDefault Koha::Exceptions::Patron::FailedDelete * Koha::Exceptions::Account::IsNotCredit Koha::Exceptions::Password::Invalid => IsNotCredit vs NotCredit => IsNotValid vs Invalid vs NotValid * Koha::Exceptions::DuplicateObject Koha::Exceptions::Object::DuplicateID It would be good a write a guideline and adapt existing occurrences. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[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