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

[Bug 13888] 'Lists' permission should allow/disallow using the lists module in staff
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '25

16 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13888 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 36955] New: Extend data providers in eUsage for different SUSHI credentials in multi branch systems
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '25

15 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36955 Bug ID: 36955 Summary: Extend data providers in eUsage for different SUSHI credentials in multi branch systems Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: michaela.sieber(a)kit.edu CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com In a multi branch system you might have different SUSHI credentials for harvesting COUNTER reports for the different libraries. In our case we have three branches and each branch has separate API-Keys / Customer-IDs and so on ... The data providers should be extended to have a field for the library (dropdown with branches) database table: erm_usage_data_providers -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 13888] 'Lists' permission should allow/disallow using the lists module in staff
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '25

15 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13888 Sara Brown <sbrown(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=40396 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 40359] New: SIP2 Patron Info Fails with "AFInvalid cardnumber" – Item Info Works
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '25

15 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40359 Bug ID: 40359 Summary: SIP2 Patron Info Fails with "AFInvalid cardnumber" – Item Info Works Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: maherahmad1994(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We are experiencing an issue with SIP2 in Koha. When we send a request to retrieve patron information,or even checkout the response returns AFInvalid cardnumber, and the logs show that the system cannot satisfy constraints like cardnumber, userid, and borrowernumber. However, item information requests work correctly, and the SIP2 connection and authentication are confirmed to be successful. The cardnumber we use exists in the Koha borrowers table, and the SIP2 account is configured properly. It seems that the cardnumber value is not being passed or recognized correctly during patron lookup. We need assistance in identifying the cause of this issue and how to resolve it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 13888] 'Lists' permission should allow/disallow using the lists module in staff
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '25

15 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13888 Sara Brown <sbrown(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=40392 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39454] New: Change "self registration" to "self-registration" (space to hyphen)
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '25

15 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39454 Bug ID: 39454 Summary: Change "self registration" to "self-registration" (space to hyphen) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de It was determined in Bug 31270 that "self-registration" should be written with a hyphen and not with a space. We should correct the instances in the manual. Here are the occurrences (if you have a local copy of the manual, you can do `git grep "self regist"` and it will find all the occurrences of the string in all the files) cron_jobs.rst: - To delete expired self registration accounts (accounts that haven't been cron_jobs.rst: - To delete all unverified self registrations in borrower_modifications images.rst: :alt: Error message at the top of the self registration page: "The following fields contain invalid information: This email address already exists in our database. Please correct and resubmit." opac.rst:OPAC self registration opac.rst:generating cardnumbers before providing them to self registered patrons. opacpreferences.rst: on their self registration form. If any of the required fields are opacpreferences.rst:Asks: \_\_\_ patron's email (borrowers.email) as unique on self registering. opacpreferences.rst:Asks: Enable the self registration for the following libraries: \_\_\_ opacpreferences.rst:Asks: \_\_\_ password and login form after a patron has self registered. opacpreferences.rst: OPAC after :ref:`self registration<opac-self-registration-label>`, so the opacpreferences.rst: preference to delete the un-verified self registrations after a -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 14414] Add field for processing fee for invoices
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '25

15 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14414 Martin Renvoize (ashimema) <martin.renvoize(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs(a)lists.koha-commun |martin.renvoize(a)openfifth.c |ity.org |o.uk -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 38612] New: Broken external link to SIP2 documentation
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '25

15 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38612 Bug ID: 38612 Summary: Broken external link to SIP2 documentation Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de In the Other APIs and protocols chapter, under Using SIP2 (https://koha-community.org/manual/latest/en/html/apis_protocols.html#using-…) there is a link to 3M documentation for SIP2. This link is broken. <mediatype> is a three numerical character long value. For a list of the values go to: http://multimedia.3m.com/mws/media/355361O/sip2-protocol.pdf -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 38599] New: Broken internal reference to messaging preferences in Patrons chapter
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '25

15 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38599 Bug ID: 38599 Summary: Broken internal reference to messaging preferences in Patrons chapter Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de In the Patrons chapter, under Notices (https://koha-community.org/manual/latest/en/html/patrons.html#notices) there is an internal reference to the patron's messaging preferences. This reference is not formatted correctly and doesn't lead anywhere. Current The `patron's messaging preferences <#setpatronmessaging>`__ are set There is unfortunately no specific section to setting patron messaging preferences, it is described in Adding a patron. The reference should be removed or a section should be added and the reference properly formatted. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 34745] New: ThingISBN broken: User agent blocked
by bugzilla-daemon＠bugs.koha-community.org 15 Jul '25

15 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34745 Bug ID: 34745 Summary: ThingISBN broken: User agent blocked Change sponsored?: --- Product: Koha Version: master 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Requests to LibraryThing's ThingISBN service are being blocked. Koha tries to access a url like this: https://www.librarything.com/api/thingISBN/0439139600 ...which opens fine in a browser, but triggers the response "WARNING: URL Request Failed 403 Forbidden" when Koha tries it. Koha is currently sending the user agent "libwww-perl/6.52" and if I use Firefox's developer tools to load the page with that set as a custom user agent I get a CloudFlare-generated "access denied" message. I see other CloudFlare customers complaining about this, so it may just be a default. Should we ask LibraryThing to change their configuration? Should we send a less obtrusive user agent with the request? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6