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

[Bug 31761] New: Toolbar clarity and consistency
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '26

03 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31761 Bug ID: 31761 Summary: Toolbar clarity and consistency Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Our toolbars are widely inconsistent across the staff client and with bug 30952 they became much less obvious as a 'call to action' to the end user. See https://github.com/jajm/koha-staff-interface-redesign/issues/26 for some discussion around this. I think we can still improve here.. Consistency wise and also overall contrast/clarity improvements. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 23752] New: Search all z39.50 / SRU targets and resource discovery layer / open link resolver from any ILL backend
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '26

02 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23752 Bug ID: 23752 Summary: Search all z39.50 / SRU targets and resource discovery layer / open link resolver from any ILL backend Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: niamh.walker-headon(a)it-tallaght.ie There needs to be additional options on the manage request screen irrespective on the ‘interface’ selected Koha/Koha, FreeForm or BL. This ‘Search’ button should be the first button on the row, and preferably pre-populate the search with the request metadata. This should then open a new tab or pop up window that presents the results to the staff member. This should be the 1. The locally appropriate resource discover layer and 2. The z39.50 targets set up on the system which already pop-up in the cataloguing module. Ideally the resource discovery layer and/or the open link resolver should searchable from within the manage request screen irrespective of interface so that subscription resources and open access materials can be located efficiently. When a patron submits an ILL via the opac, library staff in 'manage request' can't search for a provider from within the ILL functionality and have to go to other sources directly such as the resource discovery layer, and all the individual suppliers catalogues to identify a source. This an inefficient workflow and a significant increase in work load. Staff time wasted on ensuring item is the one required on inter-library loan as there is insufficient information on the current Koha to Koha screen, and no option at all to search from the freeform or bl backends, therefore the search must be repeated elsewhere. Th results presented should be be expanded to include edition and year, but preferably be configurable as it is for the z39.50 search in cataloguing it is currently difficult to identify the title that best matches the request. Please at least enable z39.50 searching for all targets set up on the system within ILL and not just for other koha sites. The addition of local availability from those targets would also be of value to our staff. Without more details returned on a search, library staff must go to the individual library catalogue to get more information on the title before placing the request. The current system results in Staff time wasted, user frustration, and ILL requests submitted for material already available to the user. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 23465] New: Add item form in acq is missing Select2 style selects
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '26

02 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23465 Bug ID: 23465 Summary: Add item form in acq is missing Select2 style selects Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When adding items in acq the form doesn't offer the same features that the item form in cataloguing does. One of those is the select2 style pull downs that allow for easy searching and limiting in a long list of values. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 24483] New: When batch deleting patrons, report who was not deleted and why
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '26

02 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24483 Bug ID: 24483 Summary: When batch deleting patrons, report who was not deleted and why Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using the batch patron deletion tool, patrons are not deleted if: - They have current checkouts - They have a non-zero balance - They are the guarantor to another patron - They are of a patron category of type staff But Koha never specifically tells the user which borrowers out of their defined pool for deletion are not deleted or why. To test: - Create a patron list - Add to that list one patron for each of these conditions: -- one patron with an item checked out -- one patron with a non-zero balance -- one patron who is a guarantor -- one patron in a staff category -- one patron not meeting any of the conditions above - Go to batch patron deletion, attempt to delete all patrons on your list - Koha tells you 1 patron will be deleted Ideally, Koha would give a list of which patrons will not be deleted and why. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 23333] New: Course Reserves: Instuctor search box positioning
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '26

02 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23333 Bug ID: 23333 Summary: Course Reserves: Instuctor search box positioning Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: claire_gravely(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 91567 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=91567&action=ed… Screenshot When creating a new course in the course reserves module the "Instructor search" box is oddly positioned. Perhaps it could be moved more in line with 'Instructors'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 23125] New: Tabs in patron account adjust to window size but text does not
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '26

02 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23125 Bug ID: 23125 Summary: Tabs in patron account adjust to window size but text does not Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- In the patron account in the OPAC the size of the tabs will shrink when resizing the window to a smaller width. This happens independent from the text inside, the text will break onto mulitple lines if it can, but that doesn't work for every language. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 33674] New: Landscape cover images are resized ignoring if image/book cover width > height
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '26

01 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33674 Bug ID: 33674 Summary: Landscape cover images are resized ignoring if image/book cover width > height Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: steve(a)softwaremage.co.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The code fragments below (/Koha/CoverImage.pm) need to determine if the width is greater than the height before resizing and creating the thumbnails and 'fullsize' image version. Otherwise wide books are always resized as if they were tall books. As a result the thumbnails and fullsize images of wide books are always scaled smaller than their 'portrait' counterparts. Needless to say these hardcoded values should be part of system preferences. They were set before the days of 4K monitors. I think that might be an open item. sub new { my ( $class, $params ) = @_; my $src_image = delete $params->{src_image}; if ( $src_image ) { ; # GD autodetects three basic image formats: PNG, JPEG, XPM; we will convert all to PNG which is lossless... # Check the pixel size of the image we are about to import... my $thumbnail = $class->_scale_image( $src_image, 140, 200 ) ; # MAX pixel dims are 140 X 200 for thumbnail... my $fullsize = $class->_scale_image( $src_image, 600, 800 ) ; # MAX pixel dims are 600 X 800 for full-size image... $params->{mimetype} = 'image/png'; $params->{imagefile} = $fullsize->png(); $params->{thumbnail} = $thumbnail->png(); } return $class->SUPER::new($params); } sub _scale_image { my ( $self, $image, $maxwidth, $maxheight ) = @_; my ( $width, $height ) = $image->getBounds(); if ( $width > $maxwidth || $height > $maxheight ) { my $percent_reduce; # Percent we will reduce the image dimensions by... if ( $width > $maxwidth ) { $percent_reduce = sprintf( "%.5f", ( $maxwidth / $width ) ) ; # If the width is oversize, scale based on width overage... } else { $percent_reduce = sprintf( "%.5f", ( $maxheight / $height ) ) ; # otherwise scale based on height overage. } my $width_reduce = sprintf( "%.0f", ( $width * $percent_reduce ) ); my $height_reduce = sprintf( "%.0f", ( $height * $percent_reduce ) ); my $newimage = GD::Image->new( $width_reduce, $height_reduce, 1 ) ; #'1' creates true color image... $newimage->copyResampled( $image, 0, 0, 0, 0, $width_reduce, $height_reduce, $width, $height ); return $newimage; } else { return $image; } } -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 33633] New: Check if email exists
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '26

01 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33633 Bug ID: 33633 Summary: Check if email exists 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Is there any kind of mechanism available for Koha to use to test the existence of an email address before actually trying to send an email? It seems like there should be some way to ask email servers if the address at least exists, if not asking the status of the account, so it can make an informed decision on sending notices. Right now, Koha just sends to the address without knowing anything. If it doesn't exist, or is full, or blocked, then it is up to staff to figure it out and pass that information along to the patron. If there is some way to figure this out before sending, then we would be able have Koha do something else, like send to a secondary email address, text, phone, restrict the account, etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 28231] New: MARC modification template "1st" vs "Every" bug?
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '25

31 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28231 Bug ID: 28231 Summary: MARC modification template "1st" vs "Every" bug? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 120184 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=120184&action=e… MARC authority record with two 151$x Hi all, I think this is a bug, if someone could confirm, I would appreciate it! In MARC modification templates, we have the option of choosing to modify the first or every field specified. But when trying to delete only the first occurrence of a subfield, it deletes every subfield anyway. To test: 1) Create an authority record with two 151$x, one containing [BLANK] and the other containing real information (I've attached my authority record if you want to simply import it) 2) Go to Tools > MARC modification templates 3) Create a new template 4) Add the following action Delete 1st field(s) 151 x if field 151 x matches [BLANK] 5) Go to Tools > Batch record modification 6) Fill in the form Record type: Authorities Enter a list of record numbers: enter the authid of your authority record Modify record using the following template: Template created previously 7) Click Continue 8) Click "Show MARC" Both 151$x are deleted, rather than just the first one -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 29331] New: Batch edit items.itemlost
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '25

31 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29331 Bug ID: 29331 Summary: Batch edit items.itemlost Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: In Discussion Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: katrin.fischer(a)bsz-bw.de, nick(a)bywatersolutions.com, oleonard(a)myacpl.org >From IRC "I think Bug 28445 broke the ability to batch update lost status" So I fixed it, but actually it was not possible before 28445. Do we want it? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10