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

[Bug 28061] New: Cash Register Stats table (cash_register_stats.pl) should include a timestamp
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28061 Bug ID: 28061 Summary: Cash Register Stats table (cash_register_stats.pl) should include a timestamp Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be handy if on the cash register stats page the table column 'Transaction date' would include not just a date but also a timestamp. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 26436] New: Quick add patron will not copy over details from cities and towns pull down into patron details
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26436 Bug ID: 26436 Summary: Quick add patron will not copy over details from cities and towns pull down into patron details Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: drigney(a)equinoxinitiative.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using the quick add patron option in koha 19.11 : If a library has cities and towns pre-populated in a drop down list and has added this field into the quick add patron form this information will not copy into the full patron form after saving. This was fixed in bug 18569 for 17.11 but is not working in 19.11. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 21821] New: We should bundle and up to date RangeMessage.xml for Business::ISBN
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21821 Bug ID: 21821 Summary: We should bundle and up to date RangeMessage.xml for Business::ISBN 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Business::ISBN::Data isn't especially maintained and suggests using an up to date RangeMessage.xml file from https://www.isbn-international.org/range_file_generation. We should bundle a more up to date RangeMessage file with koha and set the appropriate environment in both plack and apache to point to the bundled version. This would help with new ISBN's that are not yet in the shipped Business::ISBN::Data package. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 31162] New: Add a clear cataloguing module home page
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31162 Bug ID: 31162 Summary: Add a clear cataloguing module home page 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The cataloguing module doesn't really have a 'home page' like circulation does. We have a number of tools under the cataloguing banner, we could have a clear jump-in point on the module home page. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 178

[Bug 30614] New: check-url-quick gives false error 404
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30614 Bug ID: 30614 Summary: check-url-quick gives false error 404 Change sponsored?: --- Product: Koha Version: 20.05 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: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, Many 404 errors come out after running the check-quick-url script while the urls are correct when checked manually. Apparently this is because the script uses HTTP HEAD instead of HTTP GET. HTTP HEAD returns only the headers of the urls and the header can return an error but the url is accessible when you do a GET. Is there a reason for this? My fellow analyst was pointing to line 104 of https://github.com/Koha-Community/Koha/blob/master/misc/cronjobs/check-url-… Thank you Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 21214] New: cleanup_database.pl --mail should let admin choose which letter codes to keep
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21214 Bug ID: 21214 Summary: cleanup_database.pl --mail should let admin choose which letter codes to keep Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: charles.farmer(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz We are often asked if an email was sent to a patron, and despite not having 100% confirmation that the message reached the person, it feels bad when fines are attached to it and no information's left in the database for our librarians. A new patch would let certain messages stay in the database, despite their age, based on their letter_code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 50

[Bug 28657] New: Expand branches.branchip to allow for multiple space separated ip ranges
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28657 Bug ID: 28657 Summary: Expand branches.branchip to allow for multiple space separated ip ranges Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: michael.hafen(a)washk12.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com change branches.branchip to a mediumtext, and remove '*' from existing branchip settings. Change C4/Auth.pm from a regexp to using in_iprange() to check client address against branchip. (in_iprange() doesn't work with '*' in branchip.) Change in_iprange() to default to false (which is what the POD says it should do). Also, have it trim '*' in case someone adds some back later. Change note in admin/branches.tt under branchip field to reflect changes to branchip handling. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 55

[Bug 25603] New: Add 001 and 003 to biblio table
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '26

27 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25603 Bug ID: 25603 Summary: Add 001 and 003 to biblio table 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org Koha itself does not care too much about these fields, but sometimes they are used when importing/syncing in records from external sources, and then it can be work intensive to match on WHERE ExtractValue( metadata,\'//controlfield[@tag="001"]\' ). This would be much easier if the 001 and 003 fields from the record had their own database columns we could match on. Similar to: Bug 11529 - Add subtitle, medium and part fields to biblio table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 19339] New: Enhance streaming cataloging to include Vimeo
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '26

27 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19339 Bug ID: 19339 Summary: Enhance streaming cataloging to include Vimeo 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: leire(a)scanbit.net QA Contact: testopia(a)bugs.koha-community.org It will work like Youtube videos but with links of Vimeo. -- You are receiving this mail because: You are watching all bug changes.

1 41

[Bug 24438] New: index can fail on timeout
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24438 Bug ID: 24438 Summary: index can fail on timeout Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com We have seen occasional timeouts when indexing elasticsearch, these cause the indexing to stop and fail. We should handle the response as the code indicates: 102 sub update_index { 103 my ($self, $biblionums, $records) = @_; 104 105 my $conf = $self->get_elasticsearch_params(); 106 my $elasticsearch = $self->get_elasticsearch(); 107 my $documents = $self->marc_records_to_documents($records); 108 my @body; 109 110 for (my $i=0; $i < scalar @$biblionums; $i++) { 111 my $id = $biblionums->[$i]; 112 my $document = $documents->[$i]; 113 push @body, { 114 index => { 115 _id => $id 116 } 117 }; 118 push @body, $document; 119 } 120 if (@body) { 121 my $response = $elasticsearch->bulk( 122 index => $conf->{index_name}, 123 type => 'data', # is just hard coded in Indexer.pm? 124 body => \@body 125 ); 126 } 127 # TODO: handle response 128 return 1; 129 } -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14