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

[Bug 37525] New: [SCO] Regression in 32256: "Return this item" doesn't show up despite SCOAllowCheckin being allowed
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '24

11 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37525 Bug ID: 37525 Summary: [SCO] Regression in 32256: "Return this item" doesn't show up despite SCOAllowCheckin being allowed Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: oliver.behnke(a)aei.mpg.de QA Contact: testopia(a)bugs.koha-community.org Created attachment 169856 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=169856&action=e… Patch to fix the regression There's a regression in bug 32256 and commit bb059abe respectively: https://gitlab.com/koha-community/Koha/-/commit/bb059abe90#a22dc682a84c4167… The refactoring of "renew" -> "c.renew" missed this line (at least), so the condition is never met. The attached patch should do. Thanks -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 14959] Support for Library Communications Framework (LCF)
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '24

11 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14959 --- Comment #3 from Magnus Enger <magnus(a)libriotech.no> --- (In reply to Jonathan Field from comment #2) > This feature has now been implemented as a plugin if anyone is interested in > it. > https://github.com/PTFS-Europe/koha-plugin-LCF Sorry, that URL gives a 404 error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 14959] Support for Library Communications Framework (LCF)
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '24

11 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14959 --- Comment #2 from Jonathan Field <jonathan.field(a)ptfs-europe.com> --- This feature has now been implemented as a plugin if anyone is interested in it. https://github.com/PTFS-Europe/koha-plugin-LCF -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 35402] Update the OPAC and staff interface to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '24

11 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 Pedro Amorim <pedro.amorim(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |38675 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38675 [Bug 38675] Switch provider dropdown options not styled properly -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 36487] New: Add an option to add new conditions for processing failure_code on members/notices.pl
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '24

11 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36487 Bug ID: 36487 Summary: Add an option to add new conditions for processing failure_code on members/notices.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: anni.rajala(a)turku.fi QA Contact: testopia(a)bugs.koha-community.org At the moment on borrowers notices.pl page there is a column "Delivery note" that displays the reason the delivery has failed. The reason is displayed based on the following conditions: [% IF ( QUEUED_MESSAGE.failure_code ) %] [% IF ( QUEUED_MESSAGE.failure_code == "INVALID_BORNUMBER" ) %]Invalid borrowernumber [% borrowernumber | html %] [% ELSIF ( QUEUED_MESSAGE.failure_code == 'NO_EMAIL' ) %]Unable to find an email address for this borrower [% ELSIF (matches = QUEUED_MESSAGE.failure_code.match('INVALID_EMAIL:(\w+)') ) %]Invalid [% matches.0 | html %] email address found [% borrowernumber | html %] [% ELSIF ( QUEUED_MESSAGE.failure_code == 'NO_FROM' ) %]Missing from email address [% ELSIF ( QUEUED_MESSAGE.failure_code == 'MISSING_SMS' ) %]Missing SMS number [% ELSIF ( QUEUED_MESSAGE.failure_code == 'DUPLICATE_MESSAGE' ) %]Message is duplicate [% ELSIF ( QUEUED_MESSAGE.failure_code == 'NO_NOTES' ) %]No notes from SMS driver [% ELSIF ( QUEUED_MESSAGE.failure_code == 'SENDMAIL' ) %]Unhandled email failure, check the logs for further details [% ELSIF ( QUEUED_MESSAGE.failure_code == "UNKNOWN_ERROR" ) %]Unknown error [% ELSE %]Error occurred while sending email. [% END %] [% END %] Sms providers might send back failure_codes outside that list. In those cases "Delivery note" -colum displays the text "Error occurred while sending email" which doesn't give the proper info for the librarian. If it would be possible to add your own ELSIF conditions, we could provide accurate information for the librarians dealing with the failed messages. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 38674] New: OPAC UNIMARC Authorities 340
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '24

11 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38674 Bug ID: 38674 Summary: OPAC UNIMARC Authorities 340 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org UNIMARC Authorities 340 __ $a Social activities: Dr. Alfred A. Dulzon is ... $b Labour activity: Assistant, Senior ... $c Education, qualifications: Doctor of technical sciences ... $c Areas of research activity: pulsed power... $d Publications: candidate dissertation ... $f 1960-2019 $p Contacts: ... Only one subfield (340$a) in the OPAC is output. What needs to be done to display the remaining subfields? https://koha.lib.tpu.ru/cgi-bin/koha/opac-authoritiesdetail.pl?authid=14209 Koha 24.05 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 16694] New: Limit SIP2 auth by patron attribute
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '24

10 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16694 Bug ID: 16694 Summary: Limit SIP2 auth by patron attribute Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: magnus(a)libriotech.no Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org In Scandinavia "more open" (Swedish: "Meröppet", Norwegian: "Meråpent") is a hot issue at the moment. What this means is that patrons can use their card and password/PIN to lock themselves into the library even when staff is not around. Typically, this means that patrons can get access to the library building from 7 am to 11 pm, even if the library is only staffed from 8 am to 5 pm. Typically, SIP2 is used to communnicate between the "more open"-system and the ILS, specifically to authenticate the user with a username and password/PIN. Also, you want the ability to turn "more open" access on and off for patrons. An extended patron attribute with possible values of NULL/empty, 0 or 1 should serve well for this. SIP2 does not have a field for saying "this is a moreopen login", so we need a way to identify a SIP2 user as a moreopen user. My plan is to add another attribute to the login element in SIPConfig.xml to achieve this: <login id="koha" password="koha" delimiter="|" error-detect="enabled" institution="kohalibrary" patron-attribute="MEROPPET" /> "MEROPPET" is then the name of an extended patron attribute which can be set to NULL or 0 (patron should not have access to moreopen) or 1 (patron should have access). This should be flexible enough to allow other, similar schemes to use some other patron attribute. -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 38628] New: Item search filters does not work with multiple search fields
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '24

10 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38628 Bug ID: 38628 Summary: Item search filters does not work with multiple search fields Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org When using more than one search field, the datatable filtering does not work. The same resultset is given every time if you are trying to filter. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 33909] New: Improve translation of title tags: Administration
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '24

10 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33909 Bug ID: 33909 Summary: Improve translation of title tags: Administration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 33906 This patch will modify administration templates so that translatable strings in the <title> tag are wrapped in the correct translation function, e.g. [% t('Translate me') %] Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33906 [Bug 33906] [OMNIBUS] Improve translation of title tags -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 38660] New: Add pointers to reports documentation for LIMIT functions
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '24

10 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38660 Bug ID: 38660 Summary: Add pointers to reports documentation for LIMIT functions Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de The Koha manual has some great report documentation, but clarifying that using LIMIT with a batch of results will default results to that many displayed AND send that batch through to batch modification would be a great pointer for librarians interested in unlocking report potential but put off by the idea of having to expand their results past the initial 20 each time. The fix in bug 36534 makes this a bit clearer by indicating the number of results to be acted on, but it would be nice to have that suggested somewhere in the documentation so that a librarian new to report writing can find it, especially since many report writers come to SQL as librarians first, not always with a database background beyond what they pick up on the job for report creation. A logical place for this might be within the SQL Report writing tips section. One place might be in the section for #send-report-output-to-batch-modification-tools. Or earlier in the section, under Runtime parameters as a note/example. Open to further suggestion. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1