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

[Bug 17643] New: The bug 3333 breaks intranet search results in column Location
by bugzilla-daemon＠bugs.koha-community.org 12 May '25

12 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17643 Bug ID: 17643 Summary: The bug 3333 breaks intranet search results in column Location Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: christophe.croullebois(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The Bug 3333 corrects in Opac by setting notforloan=1. But it has a side effect on intranet search result page due to the use of authorized value on 'notforloan'. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 15516] Allow to place a hold on first available item from a group of titles
by bugzilla-daemon＠bugs.koha-community.org 12 May '25

12 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516 Magnus Enger <magnus(a)libriotech.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |magnus(a)libriotech.no --- Comment #476 from Magnus Enger <magnus(a)libriotech.no> --- Lots of history here... Can I ask what the status is? Is anyone planning to continue working on this? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39873] New: Patron club holds - separate permission for ability to place club holds
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39873 Bug ID: 39873 Summary: Patron club holds - separate permission for ability to place club holds Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com >From bug 25787 - Club holds can't be placed without modify_holds_priority permission: > The ability to place club holds should really be its own separate user > permission nested under the reserveforothers (or possibly clubs?) permission > group. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 30723] New: Allow for notices to have custom header/footer includes
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30723 Bug ID: 30723 Summary: Allow for notices to have custom header/footer includes 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries like to add the same custom header/footer to many notices/slips. It would be handy if there was a way to set a custom header/footer and then call on it in each notice/slip where you'd like to have them. That way you would not have to add the same header/footer content to each notice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 39527] New: Cannot create a new notice when running Koha as a Mojolicious application
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39527 Bug ID: 39527 Summary: Cannot create a new notice when running Koha as a Mojolicious application Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When running Koha as a mojolicious application, trying to create a new notice results in a CSRF error, because two different 'op' parameters are sent (one in the URL, one in the POST body) -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 27730] New: Innocent changes to framework silently delete bibliographic data
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27730 Bug ID: 27730 Summary: Innocent changes to framework silently delete bibliographic data Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major Priority: P3 Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: ian.bays(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you copy and change a framework and either delete a subfield in the new framework or mark the subfield tab as "ignore", then any bib data with data in that subfield, when saved in the new framework will be silently destroyed with no option to undo. Test Plan to confirm behaviour: 1. Create bib record in default framework with minimal data, but add tag 365 (as it has a number of subfields all visible) and populate subfields a through h with "fa" through "fh". Save the record and with sql check the contents of the metadata. (I found this SQL gives enough information substituting the correct bib number of the saved record: select tagfield, tagsubfield, frameworkcode, tab, hidden, (select ExtractValue(metadata, '//datafield[@tag="365"]/subfield[@code>="a"]') from biblio_metadata where biblionumber = 37002 and (select frameworkcode from biblio where biblionumber = 37002) = marc_subfield_structure.frameworkcode) tv from marc_subfield_structure where frameworkcode in ('', 'TEST') and tagfield = '365'; ) 2. Copy the default framework to a TEST framework and set (say 365$b to tab ignore and delete 365$d). (I used export the default framework to a csv, create new TEST framework and import from the saved default csv) 3. Edit the bib record and change framework to TEST framework (settings > change framework) and save the record. 4. Run the SQL again and observe the data from subfields b and d have both disappeared from the metadata. If you were to rerun these tests you may need to reload memcache to ensure the newly changed frameworks are picked up. I understand it has been broadly known by some long-term Koha users that deleting a subfield from the framework has this effect, but both these situations potentially cause bib data to be silently and permanently delated from the database. Many users will be unaware and may not discover the problem for some time. Potential solutions might include: a) For subfields not in the framework or with tab "ignore" allow the data to be saved as is on saving for edit; b) When selecting "change framework" detect if data would be lost and alert the user with an option to back out of the change without losing data; c) Do not allow deletion of a subfield from a framework and do not allow the "ignore" option for the tab. If a field is to be ignored but hidden there are plenty of visibility options in the framework. NB: The current delivered default framework has 13 subfields set to the "ignore" tab. I cannot see what purpose these serve as no data can survive within them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 36867] ILS-DI AuthorizedIPs should deny explicitly except those listed
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36867 --- Comment #34 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Wainui Witika-Park from comment #33) > Sorry I spoke too soon! Just needed to update the allowed IPs > > Sorry my bad!!!!!! No worries! I'm glad it's working for you! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39862] New: Make cookie auth take more precedence than other methods
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39862 Bug ID: 39862 Summary: Make cookie auth take more precedence than other methods Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API 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 It seems to me that, in most cases, cookie auth will be regularly used when contacting Koha from its UI. It might not be critical, but we should probably save some CPU cycles by checking CGISESSID first. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 36867] ILS-DI AuthorizedIPs should deny explicitly except those listed
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36867 --- Comment #33 from Wainui Witika-Park <wainuiwitikapark(a)catalyst.net.nz> --- (In reply to David Cook from comment #32) > (In reply to Wainui Witika-Park from comment #31) > > I believe this is causing a login error in the opac > > Could you be more specific? What's the error say and in which version? Sorry I spoke too soon! Just needed to update the allowed IPs Sorry my bad!!!!!! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 36867] ILS-DI AuthorizedIPs should deny explicitly except those listed
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36867 --- Comment #32 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Wainui Witika-Park from comment #31) > I believe this is causing a login error in the opac Could you be more specific? What's the error say and in which version? -- You are receiving this mail because: You are watching all bug changes.

1 0