August 2019 - Koha-bugs - lists.koha-community.org

[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 22907] New: Cannot add new suggestion with strict SQL modes turned on
by bugzilla-daemon＠bugs.koha-community.org 15 Dec '19

15 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22907 Bug ID: 22907 Summary: Cannot add new suggestion with strict SQL modes turned on Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Acquisitions Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- DBIx::Class::Storage::DBI::_dbh_execute(): Incorrect integer value: '' for column 'copyrightdate' at row 1 at /home/vagrant/kohaclone/C4/Suggestions.pm line 457 -- You are receiving this mail because: You are watching all bug changes.

1 32

[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

[Bug 23214] New: OPAC add ability to pay guarantees fines
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '19

11 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23214 Bug ID: 23214 Summary: OPAC add ability to pay guarantees fines Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Depends on: 20691 Blocks: 20211, 23213 Target Milestone: --- Add ability in OPAC to pay guarantees fines Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20211 [Bug 20211] Guarantor/Guarantee and payments ideas [OMNIBUS] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20691 [Bug 20691] Add ability for guarantors to view guarantee's fines in OPAC https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23213 [Bug 23213] OPAC check mimimum payment threshold from payment plugin -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 22427] New: Frequency Units do not accommodate a 2x a week frequency
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '19

11 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22427 Bug ID: 22427 Summary: Frequency Units do not accommodate a 2x a week frequency Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Target Milestone: --- When setting up a 2x a week serial, the frequency of 2x a week does not allow for correct Unit/Issues set up. Setting up a 2x a week frequency, 1. Unit = Week 2 Issues per Unit = 2 3. Units per Issue =.5 However, Koha does not accept a value of less than 1. Due to this, the frequency cannot be used as it is intended, Koha will predict the wrong frequency. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[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