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

[Bug 29572] New: Receipt of issue on expired subscription should follow serialsadditems value
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29572 Bug ID: 29572 Summary: Receipt of issue on expired subscription should follow serialsadditems value Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Koha will allow receipt of an issue on an expired subscription. Bug 29188 already exists to suggest we should no longer allow that. I'd be fine with preventing receipt of issues on expired subscriptions entirely, but for the moment Koha allows it. In 20.05 and earlier, Koha would correctly follow the serialsadditems when receiving an issue on an expired subscription. In 21.05, Koha will not create an item when receiving an item on an expired subscription, even if serialsadditems=1. It allows the receipt, but does not present the Add Item form. If we're not preventing this receipt entirely, we should make it work entirely. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 14237] Allow bibs to be added to course without items
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14237 Jonathan Druart <jonathan.druart+koha(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|enhancement |new feature -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 29568] New: Are your Google servers down
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29568 Bug ID: 29568 Summary: Are your Google servers down Change sponsored?: --- Product: Koha Version: 21.05 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: windikartika376(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Assuming you are a Google client and confronting issues with your Google account since Google servers down then you are at the perfect spot. Some of the time this issue settle following a couple of moments or hours and here and there it might require a few days. Try not to stress you can resolve these issues without help from anyone else by follow some straightforward advances. https://www.contactcustomerservice.co/blog/google-outage/ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 29563] New: Version 21.05.05 is missing database update
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29563 Bug ID: 29563 Summary: Version 21.05.05 is missing database update Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org The increment to 21.05.05 was done in these two commits: https://git.koha-community.org/Koha-community/Koha/commit/d4f60deeb7f157177… https://git.koha-community.org/Koha-community/Koha/commit/ba30e76d1a08ef84e… But these commits do not update the database, only Koha.pm. Here is what it usually looks like: https://git.koha-community.org/Koha-community/Koha/commit/b17cf65633107306b… So if you check out the 21.05.05 tag, Koha.pm says: $VERSION = "21.05.05.000"; But the last DB update in installer/data/mysql/updatedatabase.pl is this: $DBversion = '21.05.04.003'; if( CheckVersion( $DBversion ) ) { $dbh->do( q{ INSERT IGNORE INTO systempreferences (variable, value, options, explanation, type) VALUES ('CreateAVFromCataloguing', '1', '', 'Ability to create authorized values from the cataloguing module', 'YesNo') }); NewVersion( $DBversion, 29137, "Add system preference CreateAVFromCataloguing"); } -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 29485] New: selenium/administration_tasks.t is failing randomly
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29485 Bug ID: 29485 Summary: selenium/administration_tasks.t is failing randomly 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: 19185 Since bug 19185, and Koha_Master running the tests after t/db_dependent/selenium/01-installation.t is ran, t/db_dependent/selenium/administration_tasks.t is failing randomly with: 12:32:59 koha_1 | STRACE: /usr/share/perl5/Try/Tiny.pm:123 in Selenium::Remote::Driver::catch {...} 12:32:59 koha_1 | /usr/local/share/perl/5.28.1/Selenium/Remote/Driver.pm:361 in Try::Tiny::try 12:32:59 koha_1 | (eval 1710):1 in Selenium::Remote::Driver::__ANON__ 12:32:59 koha_1 | (eval 1712):2 in Selenium::Remote::Driver::__ANON__ 12:32:59 koha_1 | /usr/local/share/perl/5.28.1/Selenium/Remote/Driver.pm:1340 in Selenium::Remote::Driver::_execute_command 12:32:59 koha_1 | /usr/local/share/perl/5.28.1/Selenium/Remote/Driver.pm:1340 in (eval) 12:32:59 koha_1 | /kohadevbox/koha/t/lib/Selenium.pm:170 in Selenium::Remote::Driver::find_element 12:32:59 koha_1 | t/db_dependent/selenium/administration_tasks.t:188 in t::lib::Selenium::click I don't recreate it locally. The screenshot of the failure shows that the screen is still on the authorised value list view. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19185 [Bug 19185] Web installer and onboarding tool selenium test -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 29264] New: SIP config allows use of non-branchcode institution ids causes workers to die without responding
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29264 Bug ID: 29264 Summary: SIP config allows use of non-branchcode institution ids causes workers to die without responding Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If is entirely possible to create an SIP institution whose ID does not match a valid branchcode in Koha's SIP config. In fact, Koha's example SIP config contains an example of this ( kohalibrary / kohalibrary2 ). If a SIP login uses an institution with an id that doesn't match a valid branchcode, everything will appear to work, but the SIP worker will die anywhere that Koha gets the branch from the userenv and assumes it is valid. The repercussions of this are that actions such as the checkout message simply die and do not return a response message to the requestor. At the very least, we should output a warning to the SIP log. I think we should strongly consider disallowing institution ids in the SIP config that do not match valid branchcodes. In this scenario, attempting to start the SIP server should result in a error message with the SIP server exiting immediately. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 1993] Task Scheduler Needs Re-write
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '21

23 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1993 Marjorie Barry-Vila <marjorie.barry-vila(a)collecto.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marjorie.barry-vila@collect | |o.ca -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 29558] New: Tabbing through item editor no longer works
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '21

23 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29558 Bug ID: 29558 Summary: Tabbing through item editor no longer works Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Libraries are reporting a change to the way you can use the TAB button in the item editor. Prior to 21.05, you could use the TAB key to move through the item editor, hit tab and it would confirm the highlighted/upper choice and go to the next field. You can't just tab to Not For Loan, hit O (for Ordered), and hit tab to select that and jump to collection code. You now have to click and/or use enter. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 19444] New: Automatic renewal script should not auto-renew if a patron' s record has expired
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '21

23 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19444 Bug ID: 19444 Summary: Automatic renewal script should not auto-renew if a patron's record has expired Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: janet.mcgowan(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently with the automatic_renewals.pl script, materials are still auto-renewed even if the patron's account has expired. The automatic renewals script has error conditions which prevent automatic renewals in these circumstances: $error eq 'too_many' or $error eq 'on_reserve' or $error eq 'restriction' or $error eq 'overdue' or $error eq 'auto_too_late' or $error eq 'auto_too_much_oweing' or $error eq 'auto_too_soon The error conditions should take into account the expiry date of borrower and not auto renew if the borrower's account has expired. For example adding a new error code such as 'borrower_expired' - or whatever convention achieves this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 17979] New: Fatal error when searching from addbooks.pl due to ISBN flaw
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '21

23 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17979 Bug ID: 17979 Summary: Fatal error when searching from addbooks.pl due to ISBN flaw Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If you're doing a "Cataloging Search" from /cgi-bin/koha/cataloguing/addbooks.pl, and you type in "1st to die", you'll see the following: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 5 at /<koha>/lib/C4/Breeding.pm line 107 The reason is that the string is 10 characters long and contains a digit, so Koha thinks it's an ISBN. But when it tries to normalize it, it fails, and instead Koha generates no data for the WHERE clause and then the SQL statement fails because it contains a WHERE without the actual clause. The code: if ($query) { # fill isbn or title, depending on what has been entered #u must do check on isbn because u can find number in beginning of title #check is on isbn legnth 13 for new isbn and 10 for old isbn my ( $title, $isbn ); if ($query=~/\d/) { my $clean_query = $query; $clean_query =~ s/-//g; # remove hyphens my $querylength = length $clean_query; if ( $querylength == 13 || $querylength == 10 ) { $isbn = $query; } } if (!$isbn) { $title = $query; } ( $countbr, @resultsbr ) = BreedingSearch( $title, $isbn ); } -- You are receiving this mail because: You are watching all bug changes.

1 27