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

[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 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

[Bug 36909] New: Eliminate duplicate ID in cookie consent markup
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36909 Bug ID: 36909 Summary: Eliminate duplicate ID in cookie consent markup Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: ASSIGNED Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 27378 The HTML validator complains about duplicate IDs in the cookie consent markup: One div#consentButtons in the header, one in the footer. These can be updated to be classes instead. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27378 [Bug 27378] Enable compliance with EU Cookie Legislation via cookie consent -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 37002] New: Correct several HTML markup errors
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37002 Bug ID: 37002 Summary: Correct several HTML markup errors Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Blocks: 33195 There are several HTML markup errors reported by the W3C validator when looking at the source of the bibliographic detail page in the staff interface. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33195 [Bug 33195] Reindent the bibliographic details page -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 36966] New: Fix links for local cover images for items on staff detail page
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36966 Bug ID: 36966 Summary: Fix links for local cover images for items on staff detail page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The links for local cover images aren't built correctly on the detail page of the staff interface While it doesn't cause a problem on current "main", any development that sets the "item" variable in the template at a higher level will generate fatal errors. Owen has bumped into this in his Bootstrap 5 work. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 36672] New: Circulation rules are performing too many lookups
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36672 Bug ID: 36672 Summary: Circulation rules are performing too many lookups Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration 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 See bug 36668 - it tackles the size of the circulation page but doesn't significantly increase load time. Profiling it seems we spend about 50% of the loading time on Koha::Template::Plugin::CirculationRules::Search Looking at the template, for every section after the main rules block we loop over categories or itemtypes, and lookup the value for each rule name. In systems with large numbers of categories and item types this becomes very slow. In the rules section, we have already built a hash of rules by category and itemtype - we should continue to use this throughout the page. Additionally, we don't need to use all category/item types, we can use the 'used_categories' array from bug 36447 to only attempt categories that we know have rules -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 36785] New: opac-tags: Resolve warning about unrecognized biblionumber
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36785 Bug ID: 36785 Summary: opac-tags: Resolve warning about unrecognized biblionumber Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org The warning actually contains a typo: [2024/05/04 18:07:29] [WARN] get_approval_rows received unreconized argument key 'biblionumber'. at /usr/share/koha/opac/opac-tags.pl line 336. Where does it come from? Apparently by adding a biblionumber to the URL parameters. opac-tags does silently seem to ignore it. Note that you can see the tags on a specific biblionumber on opac-detail. Small fix coming. -- You are receiving this mail because: You are watching all bug changes.

1 17