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

[Bug 37079] New: Searching a column in the Item Search table requires the authorized value code
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '24

17 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37079 Bug ID: 37079 Summary: Searching a column in the Item Search table requires the authorized value code Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Go to Item Search and do a search. 2. Under the ItemType column attempt to do a search such as "Books". It shows "No data available in the table" even though "Books" is an available item type. 3. Attempt to do the same search using "BK", which is the item type code for "Books". This will filter the column for just "Books". This is also affecting the shelving location. Previously both those columns had a dropdown for selecting the search filter. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 35628] New: Add additional statuses to catalog concerns
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '24

17 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35628 Bug ID: 35628 Summary: Add additional statuses to catalog concerns Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The catalog concerns system currently only supports 'open' and 'resolved' states. We should allow for a more fine-grained approach to these ticket workflows.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 126

[Bug 26471] New: Datatables js error on missing pdfmake.min.js.map
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '24

17 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26471 Bug ID: 26471 Summary: Datatables js error on missing pdfmake.min.js.map Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Seeing this error in the Firefox console on a page with a datatables table (e.g. admin/z3950servers.pl) Fout bij brontoewijzing: Error: request failed with status 404 Bron-URL: https://dev.rijkskoha.nl:28443/intranet-tmpl/lib/datatables/datatables.min_… Brontoewijzings-URL: pdfmake.min.js.map Compare with an older mention of this error from bug 15400: > I'm getting a different error that I'm not sure how to fix > > Source map error: Error: request failed with status 404 > Resource URL: > http://localhost:8081/intranet-tmpl/lib/datatables/datatables.min_19.1200060. > js > Source Map URL: pdfmake.min.js.map I am kind of lost in datatables land. It is a nightmare component imo. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 33426] New: Add client storage of user-selected DataTables configuration to suggestion.tt
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '24

17 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33426 Bug ID: 33426 Summary: Add client storage of user-selected DataTables configuration to suggestion.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: emily.lamancusa(a)montgomerycountymd.gov Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Depends on: 22276 Bug 22276 added a method to columns_settings.inc to support the use of the DataTables "saveState" option. Making use of that function in suggestion.tt would enable the suggestion table to remember individual users' local changes to the table configuration. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22276 [Bug 22276] Add client storage of user-selected DataTables configuration -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 31181] New: Merge function does not include local copy images
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31181 Bug ID: 31181 Summary: Merge function does not include local copy images Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It seems that merge-from item local cover images are not merged to the merge-to entry. Is thie intentional or is it a bug? If intentinal there should be a warning to the user before the merge is performed, so that they may save the current images and re-locad them once the merging is complete. Are the images left in limbo, or are they deleted from the db once the merge is complete? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 26820] New: "Important" flag enforced only at subfield level
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26820 Bug ID: 26820 Summary: "Important" flag enforced only at subfield level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: - edit your framework so the 001 is set to Important at the tag level but not at the subfield level - create a new record in that framework, note that the 001 is not marked Important - edit framework, set it to Important on the @ subfield in the 001 - reload new record, see the 001 is now marked Important We're not doing anything with Important at the tag level, so let's not ask for it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 34924] New: Add ability to send 'final auto renewal notice'
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34924 Bug ID: 34924 Summary: Add ability to send 'final auto renewal notice' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com See bugs 19014 and 31427 - users can end up receiving an auto renewal failure immediately after a success. 31427 updates to send this notice at the end of a circ period, but then the user doesn't know the book won't renew until it is nearly due We should have a way to mark that an issue has reached the end of the allowed renewals and warn the user that the item won't be renewed when it becomes due. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 50

[Bug 35017] New: If creating items when ordering, an alert should appear if the item type is not filled out
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35017 Bug ID: 35017 Summary: If creating items when ordering, an alert should appear if the item type is not filled out 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Step to reproduce 1. Create a basket 2. Choose to create items upon ordering 3. Use either a new file or a staged file 4. When adding records to the basket, the required fields seem to only be fund and price. Fill out the required fields. 5. Close the basket 6. Go to receive from that vendor, - add invoice number, then see a 500 error instead of being able to receive anything from that vendor. When a basket is created in Acquisitions with the "create items on ordering", but the item type is not filled in, a 500 error will appear when attempting to receive. Although the item type is not required, thus allowing a user to go through the whole process only to receive a 500 error when receiving. This error will appear regardless of what the user is receiving if an order within that vendor has an order without an item type. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 36902] New: Blank year fields should not be indexed.
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36902 Bug ID: 36902 Summary: Blank year fields should not be indexed. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se The comment says 'Only accept years containing digits and "u"' but proceeds to also accept fields with blanks: # Only accept years containing digits and "u" push @{$default_options->{value_callbacks}}, sub { my ($value) = @_; # Replace "u" with "0" for sorting return map { s/[u\s]/0/gr } ( $value =~ /[0-9u\s]{4}/g ); }; If the field contains blanks it is either because it is invalid or because the year is missing, so the field should not be indexed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 36483] New: Calling $object->to_api directly should be avoided
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36483 Bug ID: 36483 Summary: Calling $object->to_api directly should be avoided Change sponsored?: --- Product: Koha Version: master 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 CC: tomascohen(a)gmail.com Highlighted on bug 36482, calling $object->to_api directly on our API controllers makes several parameters ineffective. Notably, x-koha-embed. We should call instead: ```perl $c->objects->to_api( $object ) ``` A follow-up bug replacing all existing calls should've been filled but we somehow missed it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30