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

[Bug 38987] New: Cannot link authorities with other authorities
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38987 Bug ID: 38987 Summary: Cannot link authorities with other authorities Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: a.roussos(a)dataly.gr QA Contact: testopia(a)bugs.koha-community.org Starting with Koha 24.11.01, we can no longer link authorities with other authorities (linking a bibliographic record with an authority still works fine). This affects both MARC21 and UNIMARC instances, and is valid on the main branch, too. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 38515] New: Generate next serial deletes the notes from the expected serial and ignores preference PreserveSerialNotes in the new serial
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38515 Bug ID: 38515 Summary: Generate next serial deletes the notes from the expected serial and ignores preference PreserveSerialNotes in the new serial Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: adolfo.rodriguez(a)xercode.es QA Contact: testopia(a)bugs.koha-community.org If a serial with the status Expected has notes and you click the "Generate next" button, the serial status will change to Late and the notes will be gone. If the system preference PreserveSerialNotes is activated, it won't have any effect, as the new serial won't keep the notes from the previous serial. This is cause by the call to the function ModSerialStatus at serials-collection.pl inside operation cud-gennext, that passes "" where the notes should go. This means that field will be deleted in the current serial with status 1 (Expected) and won't be copied to the new serial. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 38900] New: translation script explodes without meaningful error when "incorrect" structure is found
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38900 Bug ID: 38900 Summary: translation script explodes without meaningful error when "incorrect" structure is found Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com Found when working on bug 38714, the translation script can break with en error that does directly point to the problematic string [13:00:23] Error: Command failed: misc/translator/xgettext.pl --charset=UTF-8 -F -o /tmp/koha-2rwDEm/Koha-opac-bootstrap.pot -f /tmp/koha-2rwDEm/files Can't use an undefined value as a HASH reference at misc/translator/xgettext.pl line 131. at ChildProcess.exithandler (node:child_process:422:12) at ChildProcess.emit (node:events:517:28) at ChildProcess.emit (node:domain:552:15) at maybeClose (node:internal/child_process:1098:16) at ChildProcess._handle.onexit (node:internal/child_process:303:5) at Process.callbackTrampoline (node:internal/async_hooks:128:17) [13:00:23] 'po:update' errored after 992 ms -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 38773] New: SMTP server is not showing on the library detail page
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38773 Bug ID: 38773 Summary: SMTP server is not showing on the library detail page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When an SMTP server is selected for a library, it is well displayed in the form to modify the library and in the list of all libraries (in column SMTP server) but when viewing a library detail (without editing) the line "SMTP server" is empty. To reproduce : 1- Create an SMTP server in Koha (it doesn't need to be valid) a- Go to Administration > Additional parameters > SMTP servers b- Click on "New STP server" c- Fill all mandatory fields (it doesn't need to be valid information) d- Click on "Submit" 2- Add the created SMTP server to a library a- Go to Administration > Basic parameters > Libraries b- Choose a library and click on Edit (in column "Actions") c- On the line "SMTP server" select the server created d- Click on "Submit" 3- Check the display a- Go to Administration > Basic parameters > Libraries b- Check that the name of the SMTP server you just selected is displayed in the column SMTP server c- Click on the name of the library you modified d- Check that the line "SMTP server" is empty e- Click on "Edit library" f- Check that the name of the SMTP server you just selected is still selected -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 38988] New: If JobsNotificationMethod is not STOMP the about page shows as if there was a problem
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38988 Bug ID: 38988 Summary: If JobsNotificationMethod is not STOMP the about page shows as if there was a problem Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I'm not sure how bug 35655 ended up doing this, but it is not ok: * If polling is selected, the `text-bg-warning` is picked, and in the STOMP case it is `text-bg-info`. Both are ok so should be displayed the same. * In the `System information` section, you end up with the message about not being able to connect to the message broker. Which is a feature if you chose `polling` so no error at all. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 39000] New: "Encoding errors" block on detail page hurt the eyes
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39000 Bug ID: 39000 Summary: "Encoding errors" block on detail page hurt the eyes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 35402 https://snipboard.io/wUmV50.jpg Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 [Bug 35402] Update the OPAC and staff interface to Bootstrap 5 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 35826] New: Optimize building of holds queue based on transport cost matrix
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35826 Bug ID: 35826 Summary: Optimize building of holds queue based on transport cost matrix Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are several problems when building the holds queue which makes it hard for the libraries to predict the outcome for how items are allocated based on their configured policy. 1. The allocation of items should be done by optimizing on transport cost. Currently a greedy algorithm is applied when building the holds queue which doesn't always produce optimal results. 2. The allocation of items should not fall back to some default allocation if an allocation by using the transport cost matrix fails. If no allocation can be found that satisfies the configured constraints it is a violation of the configured policies o proceed and make an allocation. 3. Although items at the local library have transport cost 0, assigning local items should not be given absolute precedence. It is simply false that assigning local items "is obviously the least costly" as the comment says. (That we hard code the cost to 0 for local items is also an arbitrary restriction in Koha, there is no technical reason as to why we shouldn't allow the libraries to set a cost for allocating local items.) I am currently working on a solution based on the Hungarian Algorithm. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 75

[Bug 17437] New: Advanced cataloging editor - editing the 001 field overwrites data
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17437 Bug ID: 17437 Summary: Advanced cataloging editor - editing the 001 field overwrites data Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In the Advanced Cataloging Editor, when you add any data to the beginning of the 001 tag it types over the data already entered in the field. For example, adding the 'ocn' prefix to OCLC numbers in the advanced editor overwrites the first 3 digits of the OCLC number, causing you to reenter the data. In the basic editor you can enter data in the 001 without it overwriting an current data in the field. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 23674] New: Allowing editable notes when posting Payments/Writeoffs
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23674 Bug ID: 23674 Summary: Allowing editable notes when posting Payments/Writeoffs Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice if a librarian forgot to add a note to a payment/write-off/manual invoice transaction, or if a note was added at time of transaction, that this note is editable. Currently, this is not something that can be edited, therefore, a librarian would have to remove the entire transaction to edit the note. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 109

[Bug 31481] New: Pass message_id to SMS drivers
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31481 Bug ID: 31481 Summary: Pass message_id to SMS drivers 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: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Most of the SMS Gateways support REST API and it is common that the operator sends their report back to the service. Now it is impossible to catch reports if sms was succesfully sent or it failed since we can't pass the message_id to our report url when sending the message to the gateway. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20