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

[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 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

[Bug 36306] New: Make Koha UserName configurable how it is created
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '25

14 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36306 Bug ID: 36306 Summary: Make Koha UserName configurable how it is created Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice to allow libraries to configure how the Koha User Name is created in the system. Libraries have many different ways they use this field, such as patron-picked user name, card number, firstname.lastname, or a totally different value. This would be a nice system preference to allow libraries to identify which works for their library and also would be nice to have it as a patron category choice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 25498] New: Cannot change owner of list
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '25

14 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25498 Bug ID: 25498 Summary: Cannot change owner of list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Once someone owns a list, there is no way to change the owner. This problem often arises when a library staff member uses an individual account to create a public list, and then they leave their job. A superlibrarian (or otherwise privileged user) should be able to change the owner of a list on demand. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 89

[Bug 31947] New: Add 'btn-primary' to the main action button where it's missing
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '25

14 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31947 Bug ID: 31947 Summary: Add 'btn-primary' to the main action button where it's missing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With the staff client refresh, the btn-primary was given a much clearer set of yellow styling.. we should try to add said markup wherever it's missing. This bug servers as a collector. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 32069] New: Make submit button yellow on "create manual invoice"
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '25

14 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32069 Bug ID: 32069 Summary: Make submit button yellow on "create manual invoice" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Blocks: 31947 The other accounting tabs have yellow buttons, but "Create manual invoice" does not. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31947 [Bug 31947] [Omnibus] Add 'btn-primary' to the main action button where it's missing -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 37107] New: Unclear descriptions for DefaultLongOverduePatronCategories and DefaultLongOverdueSkipPatronCategories
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '25

14 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37107 Bug ID: 37107 Summary: Unclear descriptions for DefaultLongOverduePatronCategories and DefaultLongOverdueSkipPatronCategories Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de The descriptions for the DefaultLongOverduePatronCategories and DefaultLongOverdueSkipPatronCategories system preferences refer to 'overdues' - for example: -"Set the default patron categories to receive overdues to" -"Leave this field empty if you want to process overdues for all patron categories" This makes it sound like the system preferences are about whether patrons receive overdue notices ("receive overdues") or are eligible to have items be considered overdue ("process overdues"), but really they control whether items checked out patrons in these categories are set to a lost value by the longoverdue.pl cron. The system preferences' descriptions should be clarified to make this clear. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 32078] New: We should have an easy way for an administrator to update the encryption keys
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '25

14 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32078 Bug ID: 32078 Summary: We should have an easy way for an administrator to update the encryption keys Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz We now use encryption on a number of Koha database fields and utilise a key sorted in koha-conf.xml.. However, we have no easy way to change key should that key be leaked or found to be to simple to crack. We should add a script to allow updating of our encrpyted values from one key to the next... (or alternatively, perhaps we should allow for an array of keys in our config and update the encryption on access whenever we find an prior key is in use?.. I believe this is what we did when we upgraded from SHA to BCrypt for user passwords). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10