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

[Bug 29691] New: Use template plugins to display opac news on homepage
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '24

19 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29691 Bug ID: 29691 Summary: Use template plugins to display opac news on homepage 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently the news for display are fetched in the script, if we move this to the template, bug 28955 will allow displaying branch news by default on home page -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 33809] New: Accessibility: OPAC results page needs more descriptive links
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '24

19 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33809 Bug ID: 33809 Summary: Accessibility: OPAC results page needs more descriptive links 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: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org A report by the Shaw trust for the British Museum's installation of Koha has identified some links in the OPAC results that are not descriptive enough for screen reader users. Extract below: "The text of a link should describe the destination of the link and the link’s purpose. Providing a descriptive link text will allow users to easily determine the function of the link and make educated decisions to click the link or not. If it is not possible to identify the purpose of the link from the link text itself, then this information should be provided in context. Screen reader users have the ability to display and navigate by lists of elements, or jump from element to element. Navigating this way is much quicker than listening to a whole page, however the context provided by paragraphs and other narrative is lost and non-descriptive links become harder to understand. For downloadable links, we recommend that the file type and size of the file is also included in the link text to allow the user to make a decision whether or not to download the file." This bug addresses the links identified in the report as needing clearer descriptions. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 22340] New: Elasticsearch - sorting fields should have a fallback mechanism
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '24

19 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22340 Bug ID: 22340 Summary: Elasticsearch - sorting fields should have a fallback mechanism 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 Target Milestone: --- As an example 264 and 260 should be sortable for publisher Some records will have one, some will have both, it should eb configurable which to use and that we should not leave the sort field empty if one field is missing -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 28653] New: Sorting loans by due date doesn't work after renewing
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '24

19 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28653 Bug ID: 28653 Summary: Sorting loans by due date doesn't work after renewing 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: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On patrons check out or details page, after renewing loans they don't sort correctly when clicking on "Date due" tab. Page has to be reloaded so that sorting works. To test: 1. Add 3 loans for patron. 2. Change date dues so you they are e.g. 07/01, 07/02, 07/04 3. Make sure you have renewal period set e.g. 5 days and check your RenewalPeriodBase syspref (I use current date there) 4. Renew loan with date due on 07/01, it should now be 07/07 3. Sort loans by date due => Note that order from top to bottom is 07/04->07/02->07/07 or 07/07->07/02->07/04, not 07/02->07/04->07/07 as one would assumme. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 24589] New: Add plugin hook addbiblio_check_record
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '24

19 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24589 Bug ID: 24589 Summary: Add plugin hook addbiblio_check_record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Adds a new plugin hook, addbiblio_check_record, to addbiblio.pl. When saving a record, the hook is called with the MARC record as a parameter. If the hook returns anything, the return values are shown to the user, and saving the record is prevented. This can be used to create plugins that eg. check or modify the record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 17975] New: TT syntax for notices - Prove that HOLD_SLIP is compatible
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '24

16 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17975 Bug ID: 17975 Summary: TT syntax for notices - Prove that HOLD_SLIP is compatible Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 28729] New: Return-path Header not correctly set in emails
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '24

16 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28729 Bug ID: 28729 Summary: Return-path Header not correctly set in emails Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: System Administration 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 We have been testing the email setup in Koha comparing our 18.11 installations with a 20.11 one. In those tests we see an issue with the Return-Path header. The Return-Path header should be using (if set) the * ReturnpathDefault system preference * Return-Path from library configuration But in 20.11 we see that it's set using * KohaAdminEmailAddress * branch email This is quite an issue. Wer are using specific and different email addresses for each of those settings: * KohaAdminEmailAddress / branch email * ReturnPathDefault / return-path for library * ReplytoDefault / reply to for library Something between versions has changed to cause the change in the Return-Path header. Maybe another side effect of the SMTP library change? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 81

[Bug 29835] New: 2FA - ask for the password when 2FA is disabled
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '24

16 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29835 Bug ID: 29835 Summary: 2FA - ask for the password when 2FA is disabled Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org The user should confirm by 2FA deactivation by entering their password. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 21858] New: RFC: Notices and slips documentation
by bugzilla-daemon＠bugs.koha-community.org 15 Feb '24

15 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21858 Bug ID: 21858 Summary: RFC: Notices and slips documentation Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Developer documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Koha doesn't currently have a single point of truth for documentation of notices and slips, which has lead to a proliferation of markup syntaxes, especially in regard to repeating detail, e.g. DUEDGST/PREDUEDGST: <<items.content>> ODUE* <<items.content>> or <item> </item> CHECKOUT/CHECKIN/RENEWAL ---- Detail here ---- These have been documented in https://wiki.koha-community.org/wiki/Customising_Notices_and_Slips#Notice_M… , but this has gotten out of date as new notices get added in each version of Koha. Work to be done: Add Koha/Notices.pod which will document the following for each notice in the Letter table: * Letter Code * Source file where the notice is populated * Logic that triggers the notice * Detail syntax (if any) * Available data (tables and substitutions) * Message transport restrictions The output from this pod should be used as the basis for the Koha user documentation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 17967] New: TT syntax for notices - Prove that ODUE is compatible
by bugzilla-daemon＠bugs.koha-community.org 15 Feb '24

15 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17967 Bug ID: 17967 Summary: TT syntax for notices - Prove that ODUE is compatible Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 18