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

[Bug 15708] New: Add ability to allow only items whose home/holding branch matches one of a group of libraries to fill a given hold
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '23

12 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15708 Bug ID: 15708 Summary: Add ability to allow only items whose home/holding branch matches one of a group of libraries to fill a given hold Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This enhancement will extend the functionality added in Bug 15532 using the library groups editor in Bug 15707 to allow not only holds from a single library match but a group of libraries that match. This will give much greater flexibility in defining what items should full what holds within a groups of libraries. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 16436] New: Allow action logs to be logged to the koha log file
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '23

11 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16436 Bug ID: 16436 Summary: Allow action logs to be logged to the koha log file 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be very useful if it were possible to log actions to a log file as well as to the database. With Koha::Logger we can give the option of sending those logs to a separate file, but by default they can go to the standard log files. They should also be off by default. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 16865] New: marking branchcode unwanted breaks self registration
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16865 Bug ID: 16865 Summary: marking branchcode unwanted breaks self registration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If you add branchcode to PatronSelfRegistrationBorrowerUnwantedField then self registration fails silently. The library and the user have no idea what happened. We should have an error and/or not let branchcode be added to that preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 17364] New: branchcode should not be allowed in BorrowerUnwantedField , PatronSelfRegistrationBorrowerUnwantedField
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17364 Bug ID: 17364 Summary: branchcode should not be allowed in BorrowerUnwantedField, PatronSelfRegistrationBorrowerUnwantedField Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com If branchcode is among the fields in BorrowerUnwantedField, saving the borrower record in members/memberentry.pl will generate an Internal Server Error because there is a foreign key constraint on borrowers.branchcode. To replicate the issue: 1/ Set the syspref BorrowerUnwantedField so that it contains branchcode 2/ Create a patron on members/memberentry.pl 3/ Save the patron, you will get "Internal Server Error". It follows that PatronSelfRegistrationBorrowerUnwantedField should not contain branchcode either -- it's necessary to create a record in the borrowers table, so we shouldn't be able to exclude it. Details for those who like that sort of thing: If you're watching the plack error logs,you'll see something like this: DBD::mysql::st execute failed: Cannot add or update a child row: a foreign key constraint fails (`koha_salinas`.`borrowers`, CONSTRAINT `borrowers_ibfk_2` FOREIGN KEY (`branchcode`) REFERENCES `branches` (`branchcode`)) [for Statement "INSERT INTO `borrowers` ( `address`, `address2`, `borrowernotes`, `cardnumber`, `categorycode`, `city`, `contactnote`, `country`, `dateenrolled`, `dateexpiry`, `dateofbirth`, `debarred`, `email`, `emailpro`, `fax`, `firstname`, `initials`, `mobile`, `opacnote`, `othernames`, `password`, `phone`, `phonepro`, `privacy`, `sex`, `sort1`, `sort2`, `state`, `surname`, `title`, `userid`, `zipcode`) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )" with ParamValues: 0="1234 MAIN ST", 1="", 2="", 3="TESTYTESTERSON", 4="STAFF", 5="Bradley, CA", 6="", 7="", 8='2016-09-27', 9='2024-12-27', 10=undef, 11=undef, 12="", 13="", 14="", 15="TESTY", 16="", 17="", 18="", 19="", 20='!', 21="555 555 1212", 22="", 23=1, 24="", 25="C", 26="", 27="", 28="TESTERSON", 29="", 30='testy.testerson', 31="93426"] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1832. DBIx::Class::Storage::DBI::_dbh_execute(): Cannot add or update a child row: a foreign key constraint fails (`koha_salinas`.`borrowers`, CONSTRAINT `borrowers_ibfk_2` FOREIGN KEY (`branchcode`) REFERENCES `branches` (`branchcode`)) at /usr/share/koha/lib/C4/Members.pm line 769 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44

[Bug 17842] New: Broken diacritics on records exported as MARC from cart on reimport
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '23

09 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17842 Bug ID: 17842 Summary: Broken diacritics on records exported as MARC from cart on reimport Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I have experienced this problem for a while now in different versions, but I am not quite sure what's going wrong: - Add a records with diacritics, such as German umlauts äüö to your cart - Download the record from the cart in MARC - Import the record into Koha using the staged MARC import - Verify that the MARC preview doesn't work in the staged MARC import table - Verify that the umlauts didn't import correctly When using the 'import record' feature in Rancor, the diacritics also appear broken, fields containing diacritics get cut off and other oddities happen. -- You are receiving this mail because: You are watching all bug changes.

1 63

[Bug 17620] New: Fix format of date/data-times in Swagger definition
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '23

04 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17620 Bug ID: 17620 Summary: Fix format of date/data-times in Swagger definition Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: hector.hecaxmmx(a)gmail.com, jonathan.druart(a)bugs.koha-community.org, lari.taskula(a)jns.fi, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com Depends on: 16276, 17607 Bug #17607 highlighted the lack of a defined format for date and date-time fields in our api responses. We should settle on a response form and validate it to ensure it's consistently given across the codebase. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16276 [Bug 16276] When automatically deleting expired borrowers, make sure they didn't log in recently https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17607 [Bug 17607] Fix patron definition in Swagger -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 17596] New: Simplify accounting UI in staff client
by bugzilla-daemon＠bugs.koha-community.org 03 Jul '23

03 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17596 Bug ID: 17596 Summary: Simplify accounting UI in staff client Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This bug is omnibus for our effort on simplifying accounting UI and workflow. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 16665] New: Add a staffadmin bar to the opac interface in order to edit the previewing record (MARC)
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16665 Bug ID: 16665 Summary: Add a staffadmin bar to the opac interface in order to edit the previewing record (MARC) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dimantonak(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Currently when a librarian previewing a record in the opac interface and wants to edit that record, has to go to the staff interface, search again for that record and edit it. It would be useful to add a staffadmin bar (IF a librarian is logged in) linking to the staff interface (cgi-bin/koha/catalogue/detail.pl?biblionumber=#) in order to edit the MARC record directly. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 17723] New: Using MySQL on external server - lack of documentation giving example
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17723 Bug ID: 17723 Summary: Using MySQL on external server - lack of documentation giving example Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: fooquency(a)gmail.com I am trying to create a Koha instance using MySQL on a remote server. https://wiki.koha-community.org/wiki/Debian#Create_a_Koha_instance states: "create a new file in its place containing the connection information for the server, in the form of a my.cnf file." but no example is given. I would assume this somehow allows specification of all of hostname, username and password, but it is entirely unclear currently how to do this. Could someone kindly add an example or give more details of what format exactly "the connection information" should be in? http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html has no mention of a password configuration for instance. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 17311] New: koha-common service should be restarted on upgrade
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '23

27 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17311 Bug ID: 17311 Summary: koha-common service should be restarted on upgrade Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net The upgrade process should restart the koha-common service. This is needed so Plack processes are restarted too and Koha version is reloaded (otherwise end users keep getting upgrade messages on the UI. Any other patched file will be reloaded (apache, zebra, etc). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19