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

[Bug 8088] Png-images of covers lost transparency
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '25

08 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8088 Hammat wele <hammat.wele(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8088] Png-images of covers lost transparency
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '25

08 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8088 --- Comment #11 from Hammat wele <hammat.wele(a)inlibro.com> --- Created attachment 176278 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=176278&action=e… Bug 8088: (follow-up) keep image transparency when importing a batch of cover images Images of covers must preserve transparency of png-images when uploading a batches of images in a ZIP file Plan test : Make sure you have a valid Zip file that contains the images to upload and a valid datalink.txt or idlink.txt file 1. Apply the patch. 2. In 'Cataloging > Upload local cover image', set 'LocalCoverImages' to 'show' and OPACLocalCoverImages to 'show'. 3. Click on « Drop files here » and select the ZIP file to upload then click «Process images» 6. For each notice check the transparency of images --->Notice the background is transparent -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38849] New: Unable to add multiple tags using MARC modification template
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '25

08 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38849 Bug ID: 38849 Summary: Unable to add multiple tags using MARC modification template Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To Replicate on 24.05.05 1. Create a MARC modification template such as: Add new 500 $a value: This is a note 2. Find a bibliographic record which already contains text in 500$a or add it if it does not. 3. Apply the MARC modification template from the bibliographic page. See that the note is not added. Repeat these steps but find a bibliographic record in which the 500$a does not have any text. See that a note is added.* Repeat these steps for the record in which the note was added. See that a second note is not added. I tried other tags, such as adding a 655$a and was only able to add it one time and not a second time. In theory, the record should be able to have multiple 655$a. I was able to add multiple 500$a notes and 655$a tags using the basic editor as normal. I tested this on 23.05 and I could apply the same MARC modification template multiple times and add the note every time. *I was not able to replicate this consistently. On one site I was able to add the note and on another site the note was not added. The MARC modification templates and bibliographic frameworks were identical.The Frameworks had the 500$a enabled to show in the staff interface and editor. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 38464] New: Move funds between active budgets
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '25

08 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38464 Bug ID: 38464 Summary: Move funds between active budgets Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: holly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries would like the ability to move a single fund from one active budget to another. Current functionality only allows for all unspent funds to be transferred from a closed budget to a new budget. Ideally moving a fund from one budget to another would retain the history of orders from that fund. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 38843] New: Ability to add note to patron charges without making payment
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '25

08 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38843 Bug ID: 38843 Summary: Ability to add note to patron charges without making payment Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries would find it helpful to be able to add notes to patrons' unpaid fines/fees without making a payment or writing off the charge. For instance, college/university libraries who send charge details to a centralized bursar's office could use this to indicate when the charge has been sent. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 38848] New: Add a "processing" status for notices between "Pending" and "Sent/Failed"
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '25

08 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38848 Bug ID: 38848 Summary: Add a "processing" status for notices between "Pending" and "Sent/Failed" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CHECKOUT, CHECKIN and HOLD digest notices have the potential for confusion when circ transactions happen while process_message_queue is running. We've seen instances in which large batch checkins via RFID happen during process_message_queue such that the notice received by the patron contains fewer titles than the notice shows in the database. We could prevent this if the cron were to gather the notices to act on, first set them all the "Processing" and then proceed with the rest of its work. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 29422] New: Add additional match types to dataTables api wrapper
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '25

08 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29422 Bug ID: 29422 Summary: Add additional match types to dataTables api wrapper 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart+koha(a)gmail.com, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 29302, 29408 The `criteria` key in the dataTables wrapper allows the developer to pick the type of comparison that is used in searches. However, it is currently limited to `contains`, `starts_with`, `ends_with` and `exact`. I propose to add some additional comparisons for numeric and date comparisons. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29302 [Bug 29302] The dataTables Koha RESTful API wrapper should allow picking match type at the column level https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29408 [Bug 29408] The datatables api wrapper is ambiguously named -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 36270] New: Remove special handling for <<borrower-attribute:CODE>>
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '25

08 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36270 Bug ID: 36270 Summary: Remove special handling for <<borrower-attribute:CODE>> Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Borrower attributes should be simple enough to fetch using TT syntax now and the special casing here for the old template syntax is a blocker for it's removal. As this functionality is not documented anywhere and there's not any cases of it in use in the default shipped notices I think we should just remove it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 30751] New: Print autorenewal notice to console when running in verbose.
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '25

08 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30751 Bug ID: 30751 Summary: Print autorenewal notice to console when running in verbose. Change sponsored?: --- Product: Koha Version: unspecified 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 It would be really helpful to be able to preview how the notices look for autorenewals. It's fairly simple to add this to the script when running in verbose mode. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 36617] New: The old googleopenidconnect service should redirect to page that initiated login
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '25

07 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36617 Bug ID: 36617 Summary: The old googleopenidconnect service should redirect to page that initiated login Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: vanoudt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Splitting bug 34164 up, with this bug referring to the old googleopenidconnect service. At the moment, a successful googleopenidconnect login is sent to opac-user.pl/opac-main.pl or mainpage.pl instead of the page that initiated the login process. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7