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

[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 31 Dec '25

31 Dec '25

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 31 Dec '25

31 Dec '25

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

[Bug 34274] New: In batch patron modification adding a new attribute clears all existing values and applies authorised values to all attributes
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '25

31 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34274 Bug ID: 34274 Summary: In batch patron modification adding a new attribute clears all existing values and applies authorised values to all attributes 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To test: 1 - Define 2 new patron attributes types, both marked repeatable: Repeatable Duplicatable - linked to authorised value 'YES_NO' 2 - Perform a batch patron modification 3 - Select attribute type 'Repeatable' and enter 'Repetition' 4 - Click - +New to add a second attribute 5 - Set the type to 'Duplicatable' 6 - WRONG - values are cleared and Repeatable is now a YES_NO dropdown -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31616] New: koha_worker isn't using RabbitMQ on startup if it's a local server.
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '25

31 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31616 Bug ID: 31616 Summary: koha_worker isn't using RabbitMQ on startup if it's a local server. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org If RabbitMQ is on the same host that koha then koha_worker is started too early and it is unable to connect to RabbitMQ so it fallback to polling. Example with koha-testing-docker rabbitmqctl list_channels Listing channels ... root@kohadevbox:kohadevbox$ No channels. $ restart_all Restarting Apache httpd web server: apache2. Restarting Koha ILS: koha-commonStopping Plack daemon for kohadev:. Stopping Z39.50/SRU daemon for kohadev:. Stopping Koha worker daemon for kohadev (default):. Stopping Koha worker daemon for kohadev (long_tasks):. Stopping Koha indexing daemon for kohadev:. Starting Plack daemon for kohadev:. Starting Z39.50/SRU daemon for kohadev:. Starting Koha worker daemon for kohadev (default):. Starting Koha worker daemon for kohadev (long_tasks):. Starting Koha indexing daemon for kohadev:. . root@kohadevbox:kohadevbox$ rabbitmqctl list_channels Listing channels ... pid user consumer_count messages_unacknowledged <rabbit(a)kohadevbox.1663923239.864.0> guest 1 0 <rabbit(a)kohadevbox.1663923239.883.0> guest 1 0 root@kohadevbox:kohadevbox$ or double check with ss -ntp port 61613 connections. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 19897] New: Make status 'on hold' more specific
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '25

30 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19897 Bug ID: 19897 Summary: Make status 'on hold' more specific 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In some cases 'on hold' can mean the item is waiting (item detail page in OPAC), in other cases it just means that someone has placed a hold (no renewal possible because...). It would be nice if we could be more clear about this. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 35036] New: Incorrect chopping to punctuation in 245$b
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '25

30 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35036 Bug ID: 35036 Summary: Incorrect chopping to punctuation in 245$b Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Add a 245$b to a record that ends with punctuation. ie. 'E.B.' 2. Go the record detail page on both the staff interface and OPAC. 3. The last period does not display. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18