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

[Bug 32093] New: cleanup_database.pl bg-jobs parameter should be bg-days
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32093 Bug ID: 32093 Summary: cleanup_database.pl bg-jobs parameter should be bg-days 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The help says: --bg-days DAYS Purge all finished background jobs this many days old. Defaults to 1 if no DAYS provide d. The script checks: 'bg-jobs:i' => \$background_days, We should use bg-days -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 32248] New: t/00-checkdatabase-version.t should be removed
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32248 Bug ID: 32248 Summary: t/00-checkdatabase-version.t should be removed Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 25078 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25078 [Bug 25078] Update DB process - wrap each DBRev inside a transaction and better error handling -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 32224] New: Add cypress to the yarn commands
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32224 Bug ID: 32224 Summary: Add cypress to the yarn commands 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+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Either I am missing something obvious, or we need to add cypress to the scripts of package.json With /kohadevbox/node_modules only (ie. without $SYNC_REPO/node_modules), I cannot run yarn run cypress run `cypress run` is working with an adjusted PATH (see https://gitlab.com/koha-community/koha-testing-docker/-/issues/313#note_117…) but I think both should work. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 32240] New: api/erm_users.t fails if checkouts exist
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32240 Bug ID: 32240 Summary: api/erm_users.t fails if checkouts exist Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Test Suite Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 32030 DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Cannot delete or update a parent row: a foreign key constraint fails (`koha_kohadev`.`issues`, CONSTRAINT `issues_ibfk_1` FOREIGN KEY (`borrowernumber`) REFERENCES `borrowers` (`borrowernumber`) ON UPDATE CASCADE) at /kohadevbox/koha/Koha/Object.pm line 234 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32030 [Bug 32030] Electronic resource management (ERM) -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 31937] New: cleanup_database locked a large number of patrons
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31937 Bug ID: 31937 Summary: cleanup_database locked a large number of patrons Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The first run of cleanupdatabase after the upgrade to 21.11 did indeed cleanup a lot ;) It seems that this statement my $expired_patrons = Koha::Patrons->filter_by_expiration_date({ days => $lock_days })->search({ login_attempts => { '!=' => -1 } }); works different than before. It must have selected patrons that had an empty dateexpiry in 20.11 ? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 32089] New: build_holds_queue should optimize transfers to the hold pickup location rather than the patron home library
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32089 Bug ID: 32089 Summary: build_holds_queue should optimize transfers to the hold pickup location rather than the patron home library Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 31557 The logic used in build_holds_queue is all based on the item location and the patron's home branch, on the assumption that the patron will be picking the hold up at their home branch. That's going to be correct often, but not always. We should instead look at the hold pickup location, reserves.branchcode. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31557 [Bug 31557] Add ability for holds queue builder to prioritize either matching a patron's home library to the item's home or holding library -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 27035] New: Shows the number of results in a facet
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27035 Bug ID: 27035 Summary: Shows the number of results in a facet Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: ivan.dziuba(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org After searching, the number of results for facets is not displayed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 30243] New: When OPACSuggestionMandatoryFields includes branchcode the dropdown should default to an empty value
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30243 Bug ID: 30243 Summary: When OPACSuggestionMandatoryFields includes branchcode the dropdown should default to an empty value Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When OPACSuggestionMandatoryFields includes branchcode the dropdown should default to an empty value which will force the user to make a choice regarding branchcode. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 32249] New: When OPACSuggestionMandatoryFields includes branchcode the dropdown defaults to patron home branch
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32249 Bug ID: 32249 Summary: When OPACSuggestionMandatoryFields includes branchcode the dropdown defaults to patron home branch Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: catrina(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 144003 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144003&action=e… OPACSuggestionMandatoryFields defaults to patron home branch When testing for documentation of Bug 30243 in 22.05, the branchcode dropdown defaults to patron home branch instead of an empty value. OPACSuggestionMandatoryFields includes branchcode OPACSuggestionUnwantedFields does NOT include branchcode Save all OPAC preferences On the OPAC, select "New Purchase Suggestion" In the form, Library defaults to patron's home branch instead of an empty value. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 30812] New: subfield 9 deleted if no other data is available
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '22

17 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30812 Bug ID: 30812 Summary: subfield 9 deleted if no other data is available Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl DNB exports the ISBN with dashes in 020$9, which we import via SRU while cataloguing. Therefore we added a subfield 9 to field 020. But when 020 contains no data except the dashed ISBN in $9, the value of $9 is deleted. I assume this is caused by some special cases needed to delete the koha_id of an authority (which is often stored in $9). To reproduce: * Go to a framwork, field 020, add a subfield 9, visible in tab 0, OPAC, Intranet and edito * Go to a book, edit it, enter something in 020$a and 020$9, save * The values are stored * Edit again, remove the value from 020$a, save * the value from 020$9 is gone, too I can maybe take a look tomorrow to try to figure out what's happening.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3