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

[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 28922] New: Vendor search has poor performance when system has many vendors
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '23

11 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28922 Bug ID: 28922 Summary: Vendor search has poor performance when system has many vendors 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 In acquisitions our search does a 'contains' search on vendor name We then loop through the vendors and lookup the baskets We then lookup the groups for each basket we found It would be nice if we could fetch all the info needed in one call to the DB and possibly add paging -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 12762] Paginate baskets view in acquisitions
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '23

11 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12762 Jonathan Druart <jonathan.druart+koha(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=28922 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 31720] New: Output of export_borrowers with all fields cannot be imported
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '23

11 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31720 Bug ID: 31720 Summary: Output of export_borrowers with all fields cannot be imported Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz You used to be able to use the output of export_borrowres for patron import in Koha, but it looks like the file now contains some fields like 'description' with the patron category description, that cannot be used in patron import. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 30151] New: branchcode should always be in PatronSelfRegistrationBorrowerMandatoryField
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30151 Bug ID: 30151 Summary: branchcode should always be in PatronSelfRegistrationBorrowerMandatoryField Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org branchcode should always be in PatronSelfRegistrationBorrowerMandatoryField See Bug 29795 comments -- You are receiving this mail because: You are watching all bug changes.

1 5

[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 13093] Allow/Don't allow holds on items with set statuses
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13093 --- Comment #3 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I think settings would work, yes. Also this would allow for migrations without changing behaviour. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 11420] Patron preference to restrict staff from changing location
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11420 --- Comment #7 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Christopher Brannon from comment #6) > (In reply to Katrin Fischer from comment #5) > > We do now have this permission: > > Allow staff to change logged in library (loggedinlibrary) > > What version? Not seeing it in 22.11. Correct, it's a 23.05 feature: Bug 30624 - Add a permission to control the ability to change the logged in library -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 13165] Don't trigger holds when patrons have already reached limit of checkouts
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13165 --- Comment #6 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- I think that it should be up to the system admin to implement, not how complicated we might think it is for the patron. If a library can communicate this well, it would be worth it. It could simply be communicated at the time the hold is being placed like a warning: "Please note that holds are not filled if you have reached the limit of your library's checkouts." Maybe we could even have something that would display checkout limits, if any. It should be up to the library whether this would be implemented or not, leaving it to the library as to whether a patron's holds can be filled if their checkout limits have been reached. As is, a patron gets notified that they have a hold, and they go to pick it up, only to find out that they can't check it out until they return something. They probably are not prepared with this dilemma, and have to return home to get something to return so they can claim their hold. With a new option, they are not even eligible or notified until they are under the limit. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0