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

[Bug 42852] New: SIP2 self-check check-in does not resolve mis-routed transfers
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42852 Bug ID: 42852 Summary: SIP2 self-check check-in does not resolve mis-routed transfers Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Blocks: 42851 Target Milestone: --- Split off from bug 42851. When an item that is in transit (datesent set) is checked in via the SIP2 self-check interface at a branch that is NOT the transfer's tobranch, AddReturn returns a WrongTransfer message but does not close the row. C4/SIP/ILS/Transaction/Checkin.pm:158-161 only sets destination_loc and an alert; it never cancels/redirects the stale transfer. The original in-transit row is orphaned and shows forever on the "Transfers to receive" report. (The staff page circ/returns.pl:554-578 does handle this; SIP does not.) Proposed approach: - Complete the original transfer, recording the actual branch it ended up at (update tobranch / comment so the error is recorded, not lost). - Open a new transfer from the check-in branch to the original tobranch. - Re-link anything pointing at the old transfer (e.g. holds) to the new one so a subsequent check-in at the correct branch triggers correctly. Test plan: 1. Transfer an item from A to B (in transit). 2. Check it in at branch C via a SIP2 self-check device. 3. Before: branchtransfers row A->B stays open forever. 4. After: original transfer recorded as resolved at C, new transfer C->B created and in transit, holds re-linked. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42851 [Bug 42851] [OMNIBUS] Items left stuck in transit when checked in outside the staff returns page -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 35784] New: Wrong POD for updateWrongTransfer
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35784 Bug ID: 35784 Summary: Wrong POD for updateWrongTransfer 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org =head2 updateWrongTransfer $items = updateWrongTransfer($itemNumber,$borrowernumber,$waitingAtLibrary,$FromLibrary); This function validate the line of brachtransfer but with the wrong destination (mistake from a librarian ...), and create a new line in branchtransfer from the actual library to the original library of reservation =cut Check this with parameters in code: sub updateWrongTransfer { my ( $itemNumber,$waitingAtLibrary,$FromLibrary ) = @_; NOTE: $FromLibrary is NOT USED at all. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 34976] New: Encryption keys should not be shared between modules
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34976 Bug ID: 34976 Summary: Encryption keys should not be shared between modules 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org At this time we are using the encryption key in koha-conf to encrypt stuff for 2FA, EDI and Acquisition already. The key was introduced for 2FA. I think that it would be better to differentiate and use separate keys for various processes in Koha. For instance, the key for 2FA should be used exclusively for that purpose. We could consider if that is needed also for EDI and Acq since these are related modules. They could use one or two new keys. When adding a new call to Encryption, we should think about it. Perhaps this would be forced a bit more by passing a parameter to K::E indicating which key to use? Opening the discussion :) What do you think? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 42197] New: Item search results : display in the filters only values from the results
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42197 Bug ID: 42197 Summary: Item search results : display in the filters only values from the results Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: laurence.rault(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In item search results, dropdown are displayed at the top of the colums to be able to filter the results. However, all the existing values (authorised values, itemtypes, branches) are displayed here, with sometimes very long lists (of locations for example). It would be better if only values existing in the results were proposed in the dropdown. Add also a value "Empty", to be able to display only the results with empty or null values for the column. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 38779] New: Record sources not working on packages install
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38779 Bug ID: 38779 Summary: Record sources not working on packages install Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Interestingly, we miss `record_sources.js` in Makefile.PL Seen this on a packages install: [2024/12/23 10:26:39] [WARN] File not found : js/vue/dist/admin/record_sources.js at /usr/share/koha/lib/Koha/Template/Plugin/Asset.pm line 84. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 32609] New: Remove compiled files from src
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32609 Bug ID: 32609 Summary: Remove compiled files from src Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We need to improve our yarn build commands to generate css and js compiled files. Then remove them from our codebase, and generate them when needed: - when generating the debian packages - when ktd is starting up - when patches are applied on the sandbox -- You are receiving this mail because: You are watching all bug changes.

1 104

[Bug 42781] New: Declare 'name' before using it in patron-format.js
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42781 Bug ID: 42781 Summary: Declare 'name' before using it in patron-format.js Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com The JS in patron-format.js uses a variable called "name" without declaring it first. Looks like "var name" was removed in this patch: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=188806 (thanks to Joubu for spotting that.) We should restore it. Dicussion: https://chat.koha-community.org/koha-community/pl/56eb7shuifbu8q7s1sarwkjawa -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 42741] New: Plural strings don't apply in list content column
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42741 Bug ID: 42741 Summary: Plural strings don't apply in list content column Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N 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: caroline.cyr-la-rose(a)inlibro.com, f.demians(a)tamil.fr, jonathan.druart(a)gmail.com, julian.maurice(a)biblibre.com I'm not sure if this is a translation problem or simply a code problem... I noticed my plural strings in the lists content display weren't applying. But it seems there is a problem in English as well. To recreate: 1. Go to Lists 2. Create three lists called: - Test 0 items - Test 1 item - Test 2 items 3. Add one item in the "Test 1 item" list and add two items in the "Test 2 items" list 4. Go to lists and view the list of lists --> In the Contents column, "Test 0 items" has "0 items" (items plural -- OK?) --> "Test 1 item" has "1 items" (items plural -- NOT OK) --> "Test 2 items" has "2 items" (items plural -- OK) Optionally test translations 5. In the terminal, run gulp po:update --lang fr-CA ./misc/translator/translate install fr-CA (or other language code that uses plurals) 6. Enable the language in the StaffInterfaceLanguages syspref 7. Check the fr-CA-message.po file (or other language code), the strings should be different for single or plural #: koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/results.tt:777 #: koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/results.tt:795 #: koha-tmpl/intranet-tmpl/prog/en/modules/virtualshelves/tables/shelves_results.tt:18 #, perl-brace-format msgid "{count} item" msgid_plural "{count} items" msgstr[0] "{count} exemplaire" msgstr[1] "{count} exemplaires" I don't get why in English it's always items. In French Canada, it seems to be always exemplaire (singular). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 42395] New: Missing translations on load_patron_holds_table
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42395 Bug ID: 42395 Summary: Missing translations on load_patron_holds_table Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com The load_patron_holds_table() datatable is missing some translation tags. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 41829] New: Tag editor button has wrong id on copied MARC field when value builder plugin is used
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41829 Bug ID: 41829 Summary: Tag editor button has wrong id on copied MARC field when value builder plugin is used Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Noticed this when testing bug 39522. When one copies MARC field, Tag editor button on fields containing value builder plugin have same id as original MARC field. To reproduce: 1. Find MARC framework which has value builder plugin attached to one of its fields. 2. Navigate to Cataloging -> New record. 3. Navigate to MARC field with plugin attached to it. 4. Inspect fields Tag editor button with browsers developer tools. -> Check the id of Tag editor button. 5. Copy the field and check id of copied Tag editor button. -> Notice that it has the same id as in original field. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14