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

[Bug 20664] New: Optimize retrieval of biblio and item data
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20664 Bug ID: 20664 Summary: Optimize retrieval of biblio and item data Change sponsored?: --- Product: Koha Version: master 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: ere.maijala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org There are several inefficiencies in the current process of retrieving biblios and embedding items in the MARC data. These affect especially batch processes such as exporting of records and the OAI-PMH provider. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 118

[Bug 12133] Guarantor requirements when registering a patron
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12133 Johanna Räisä <johanna.raisa(a)koha-suomi.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12133] Guarantor requirements when registering a patron
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12133 Johanna Räisä <johanna.raisa(a)koha-suomi.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #94538|0 |1 is obsolete| | CC| |johanna.raisa(a)koha-suomi.fi --- Comment #13 from Johanna Räisä <johanna.raisa(a)koha-suomi.fi> --- Created attachment 94544 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=94544&action=ed… Bug 12133: Add requirements for guarantor and guarantee Add three requirements when registering a new patron: - A child patron must have a guarantor. This is controlled by a new syspref ChildNeedsGuarantor. - A guarantor has to be a patron. This is controlled by a new syspref GuarantorHasToBePatron. - A guarantor cannot be a guarantee. Test plan: -Add child patron without guarantor or child patron with guarantee as guarantor succesfully. - Apply this patch. - Add a child patron with a guarantee as guarantor. Error is raised. - Turn syspref "ChildNeedsGuarantor" ON. - Add a child patron without a guarantor and error "Child needs a guarantor" is raised. - Add guarantor. Guarantor can either be existing patron or added with "Contact" section. Save without errors. - Turn syspref "GuarantorNeedsToBePatron" ON. - Form fields for "Contact" section aren't displayed and only existing patron can be added as guarantor. Signed-off-by: Johanna Raisa <johanna.raisa(a)gmail.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12133] Guarantor requirements when registering a patron
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12133 Emmi Takkinen <emmi.takkinen(a)outlook.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #94371|0 |1 is obsolete| | --- Comment #12 from Emmi Takkinen <emmi.takkinen(a)outlook.com> --- Created attachment 94538 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=94538&action=ed… Bug 12133: Add requirements for guarantor and guarantee Changed header of the patch. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 21028] New: www/history.t is failing on jenkins for Ubuntu 18.04
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21028 Bug ID: 21028 Summary: www/history.t is failing on jenkins for Ubuntu 18.04 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com, mirko(a)abunchofthings.net, nick(a)bywatersolutions.com, tomascohen(a)gmail.com t/db_dependent/www/history.t is failing with the following error on Ubuntu 18.04 (at least with the image from koha-testing-docker): koha_1 | # Failed test 'Cyrillic characters with umlauts show correctly on the history page.' koha_1 | # at t/db_dependent/www/history.t line 68. It is *not* an encoding issue, the problem is that history.txt is not found: Could not read the history.txt file. Please make sure <docdir> is correctly defined in koha-conf.xml. >From koha-conf.xml: <docdir>/usr/share/doc/koha-common</docdir> Indeed this location does not contain history.txt: root@95f30c756223:/kohadevbox/koha# ls /usr/share/doc/koha-common changelog.Debian.gz copyright I have no idea if it is a koha issue, a packaging issue, or a koha-testing issue. Does anyone has an idea? https://jenkins.koha-community.org/job/Koha_18.05_U18/14/consoleFull -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 23865] New: Throw exceptions from Koha::AuthUtils::is_password_valid
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23865 Bug ID: 23865 Summary: Throw exceptions from Koha::AuthUtils::is_password_valid Change sponsored?: --- Product: Koha Version: unspecified 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: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org Exceptions are currently thrown in Koha::Patron->set_password. We need to validate password (with exceptions) without wanting to set the password. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 13193] Make Memcached usage fork safe
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193 --- Comment #46 from Joonas Kylmälä <joonas.kylmala(a)helsinki.fi> --- (In reply to Katrin Fischer from comment #45) > (In reply to David Cook from comment #44) > > Any movement on this one? I'd really like to see this one move forward... > > It looks like it was pushed? It was reverted because the dependency is missing still. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13193] Make Memcached usage fork safe
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193 --- Comment #45 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to David Cook from comment #44) > Any movement on this one? I'd really like to see this one move forward... It looks like it was pushed? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13193] Make Memcached usage fork safe
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193 --- Comment #44 from David Cook <dcook(a)prosentient.com.au> --- Any movement on this one? I'd really like to see this one move forward... -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 18549] New: There should be a warning that logging out of Koha will leave browser session logged in to OAuth
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18549 Bug ID: 18549 Summary: There should be a warning that logging out of Koha will leave browser session logged in to OAuth Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org >From bug 16892 Nick: For CAS we have casLogout - can we have something similar here? I think disconcerting if a patron signs in via google, signs out of Koha and walks away leaving their google auth intact unintentionally Mark: This is the problem. If you have multiple tabs, let's say gmail in one, and Koha in the other. If Koha does a forced logout, then your gmail tab will be affected. This is the problem that is widely known. I was thinking of actually doing another bug to drop-down choose what kind of log out. Martin: A federated logout is actually pretty rare in my experience, though it is possible. As you say Mark, it 'feels' strange to the user that logging out of seemingly unrelated apps can have the knock on effect of logging out apps in other tabs that happen to share an aouth2 openid connect identity provider. On a related note, I'm not sure I saw any code out end to support such a federated logout triggered by another service in our end either... but perhaps I missed it ;) Nick: Perhaps if OAuth is activated just a note added that when you log out of Koha you may still be logged in via google? I agree a user with many tabs open may not expect this, but a patron using a shared machine in the library who signs in to place a hold or renew may never visit their email or expect that they have signed in to that. I think a pop-up when logging out to say "Hey, you are logged in to google, and they know lots of stuff about you" wouldn't hurt, who can say if it would help :-) Mark: Perhaps this type of discussion should happen on another bug report, as this bug has nothing to do with logging out. :) Also, yes, some sort of warning should be displayed, somewhere, somehow. Nick: It can happen here now :-) -- You are receiving this mail because: You are watching all bug changes.

1 22