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

[Bug 37018] SQL injection using q under api/
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37018 Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|Pushed to stable |RESOLVED -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37247] On subscriptions operation allowed without authentication
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37247 Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|Pushed to stable |RESOLVED -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 37146] plugin_launcher.pl allows running of any Perl file on file system
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37146 Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to stable |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38066] New: New authority finder footer blocks page content
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38066 Bug ID: 38066 Summary: New authority finder footer blocks page content Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 35857 Bug 35857 gave the authority lookup popup window a floating footer with the choose, clear form, and close window buttons, but it didn't give the window contents enough space to display it without blocking content. Steps to reproduce: 1. Cataloging - New record 2. Tab 6 - in 650 subfield a type the letter a and click the postcard with a pencil Tag editor icon to the right of the input 3. In the popup window, scroll to the bottom Expected result: The paging controls at the bottom of the first page of results, and the "Back to top" arrow are completely visible Actual result: Half the "Back to top" arrow and maybe 20% of the paging controls are visible Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35857 [Bug 35857] Update display of Clear and Cancel links in the authority search pop-up window -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 38273] New: Koha::Object->discard_changes should return the Koha::Object for chaining, not the Schema Object
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38273 Bug ID: 38273 Summary: Koha::Object->discard_changes should return the Koha::Object for chaining, not the Schema Object Change sponsored?: --- Product: Koha Version: Main 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 Depends on: 17594 The dbic discard_changes method returns the current schema object ready for chaining.. for some reason we didn't wrap it to return the current Koha object when we do the same and as such we have to always call it in a distinct statement and we lose chainability. my $patron = Koha::Patron->new()->store()->discard_changes; This returns a Koah::Schema::Result::Borrower object.. it should return the fully updated from the database Koha::Patron object. Instead, one has to do my $patron = Koha::Patron->new()->store(); $patron->discard_changes; This is confusing and inconsistent with the parent library. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17594 [Bug 17594] Make Koha::Object->discard_changes available -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 18397] New: Sent notices for...: Display email address ( including which field it's taken from)
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18397 Bug ID: 18397 Summary: Sent notices for...: Display email address (including which field it's taken from) 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: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org Display in Home > Patrons > Sent notices for... the email address and the field where it is taken from. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 37491] New: Remove duplicate asset import from KBART template
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37491 Bug ID: 37491 Summary: Remove duplicate asset import from KBART template Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 Lauren Denny <lauren_denny(a)sil.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lauren_denny(a)sil.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 1652] Reordering of a repeated subfield
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1652 Phil Ringnalda <phil(a)chetcolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME CC| |phil(a)chetcolibrary.org Status|NEW |RESOLVED -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 31923] New: 'Ignore' tab description is misleading
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31923 Bug ID: 31923 Summary: 'Ignore' tab description is misleading Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When you are modifying a MARC bibliographic framework, you can choose in which tab a particular subfield appears, or 'ignore' it. The description under this choice is 'Ignore means that the subfield does not display in the record editor' Which is true, but it doesn't mention that the subfield is completely removed from the record. This can cause data loss. If you're not aware of this, the 'Ignore' description is a bit misleading. I always instruct system administrators to use the 'Editor' checkbox if they do not want to see a particular subfield in the editor, and use only 'Ignore' if they really want to flush that subfield completely. I think the description could be improved to add that values will be deleted from the subfield as well. Maybe 'Ignore means that the subfield does not display in the record editor and that it's value, if any, is deleted from the record' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24