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

[Bug 24976] New: Guided report - "Save" button on last step is misleading
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '25

17 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24976 Bug ID: 24976 Summary: Guided report - "Save" button on last step is misleading Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Keywords: Academy Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org "Save" button on last step does not save (!) It should be renamed "Next" instead https://snipboard.io/gXntf8.jpg Next step has a "Save report" button that actually saves. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 37482] New: Add batch patron modification button to patron list
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '25

17 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37482 Bug ID: 37482 Summary: Add batch patron modification button to patron list Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To replicate: 1. Create a patron list. 2. Open the list and see there is no batch patron modification button. It would be nice to be able to do a batch patron modification from a list. It is possible to navigate to Tools and accomplish the same thing, but it is extra steps. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 34860] New: New framework plugin for ISBN/ISSN
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '25

16 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34860 Bug ID: 34860 Summary: New framework plugin for ISBN/ISSN Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Something similar as on bug 34817. But obstacle currently is REST API not supporting ccl search on index. So in its current form it should need a svc script to do the index search. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 25127] New: Fines with an amountoutstanding of 0 can be created due to maxFine but cannot be forgiven
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '25

16 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25127 Bug ID: 25127 Summary: Fines with an amountoutstanding of 0 can be created due to maxFine but cannot be forgiven Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - Set maxFine to 7.50 2 - Manually create some overdues for a patron in the amounts of: 6.99, .1, .1, .1, .1, .1, .01 (create a manual debits then 'UPDATE accountlines SET debit_type_code = "OVERDUE";' 3 - Set fines for an item type to .1 4 - Checkout an item of that type to patron and backdate so it is overdue 5 - Run fines.pl 6 - Check the DB, they have a new fine of "0" 7 - Checkin the item, checking 'forgive fines' option 8 - ISE "Debit amount passed is not positive" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 31968] New: Problems with MARC staging/import
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '25

16 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31968 Bug ID: 31968 Summary: Problems with MARC staging/import Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org I'm having various problems with importing staged MARC records on 22.05.05. One example: I have staged a file and click on "Import this batch to the catalogue". The progress bar jumps to 31% but then it stops and goes no further. In the background there are lots of calls to /cgi-bin/koha/tools/background-job-progress.pl?jobID=<id>, but the last one gives a 500 error. This is when the progress bar stops. The job is actually finished after a while, but the interface never updates. I think these are the relevant errors in the logs: ==> /var/log/koha/koha/intranet-access.log <== ... a.b.c.d - - [25/Oct/2022:10:46:39 +0200] "GET /cgi-bin/koha/tools/background-job-progress.pl?jobID=<id> HTTP/1.1" 200 57 a.b.c.d - - [25/Oct/2022:10:46:40 +0200] "GET /cgi-bin/koha/tools/background-job-progress.pl?jobID=<id> HTTP/1.1" 200 57 a.b.c.d - - [25/Oct/2022:10:46:40 +0200] "GET /cgi-bin/koha/tools/background-job-progress.pl?jobID=<id> HTTP/1.1" 200 57 ==> /var/log/koha/koha/intranet-error.log <== [2022/10/25 10:47:50] [WARN] binmode() on closed filehandle _GEN_70 at /usr/share/koha/lib/C4/Templates.pm line 126. CGI::Compile::ROOT::usr_share_koha_intranet_cgi_2dbin_tools_manage_2dmarc_2dimport_2epl::__ANON__ /usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl (331) [2022/10/25 10:47:50] [WARN] print() on closed filehandle _GEN_70 at /usr/share/koha/lib/C4/Output.pm line 285. CGI::Compile::ROOT::usr_share_koha_intranet_cgi_2dbin_tools_manage_2dmarc_2dimport_2epl::__ANON__ /usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl (331) ==> /var/log/koha/koha/plack-intranet-error.log <== [2022/10/25 10:47:50] [WARN] seek() on closed filehandle _GEN_70 at /usr/share/perl5/CGI/Emulate/PSGI.pm line 34. ==> /var/log/koha/koha/intranet-access.log <== a.b.c.d - - [25/Oct/2022:10:46:41 +0200] "GET /cgi-bin/koha/tools/background-job-progress.pl?jobID=<id> HTTP/1.1" 500 118732 The only related bug I can find is Bug 15032, which mentions "binmode() on closed filehandle" way back in 2015. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

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