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

[Bug 29569] New: Want the cash.app/help number to check balance?
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29569 Bug ID: 29569 Summary: Want the cash.app/help number to check balance? 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 Want to get the number of the cash.app/help to check the balances then you have knocked on the correct door to get the number of cash app help desk to check the balance in the cash app account. you will easily get the number here because we made it so simple for you by placing a link here that will directly take you to that number which you want. But for this, you have to click the link. https://www.contactcustomerservice.co/cash-app -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28660] New: Self checkout is not automatically logging in
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28660 Bug ID: 28660 Summary: Self checkout is not automatically logging in Change sponsored?: --- Product: Koha Version: 21.05 Hardware: Other OS: Linux Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jhenderson(a)nsd.org QA Contact: testopia(a)bugs.koha-community.org The self-checkout is not automatically logging in with the staff username and password provided. Upon entering the URL for the self-checkout system, it is still prompting for the staff username and password. This a fresh install of Koha 21.05 on Debian 10. No errors during installation. Things I have done to ensure everything would work: - I have created a patron account with the self-check modules turned on for this patron and the username and password is listed in the system preferences under AutoSelfCheckAllowed, and that is turned to allow. - The selfcheck is enabled This is either a bug or something that I am not seeing -- You are receiving this mail because: You are watching all bug changes.

1 42

[Bug 11175] Show the parent record's component parts in the detailed views
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=29560 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 17775] New: blocker of bug 7172
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17775 Bug ID: 17775 Summary: blocker of bug 7172 Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: mnashbat(a)alfaisal.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Koha & ldap authentication fail authenticating new users when enabling plack, it works fine only if plack is desabled. Ldap authentication works fine with old registered users. -- You are receiving this mail because: You are watching all bug changes.

1 34

[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