February 2025 - Koha-bugs - lists.koha-community.org

[Bug 22435] New: account_offset types should be codes not descriptions
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '25

04 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22435 Bug ID: 22435 Summary: account_offset types should be codes not descriptions 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 Target Milestone: --- Currently, account_offset.types are all descriptive strings.. they should really be 'codes' to distinguish them from user-facing data and discourage developers from adding more untranslatable strings at the database level. I also don't think the current strings make a great deal of sense as they're often not describing an 'offset' action but the account action itself which is already better defined within the accountline.accounttype fields. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 282

[Bug 31095] New: Koha::Patron::Debarment should be updated to follow current Koha:: style
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '25

04 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31095 Bug ID: 31095 Summary: Koha::Patron::Debarment should be updated to follow current Koha:: style 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 The Koha::Patron::Debarment module is written in the C4 style when it should really be a Koha::Object based class now. We should update it to the modern practices to enable simple addition of API's and more standard use codebase wide. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 151

[Bug 35043] New: Handling of \t in PO files is confusing
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '25

04 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35043 Bug ID: 35043 Summary: Handling of \t in PO files is confusing Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We have our own "quote_po" sub that is stating that Locale::PO::quote is buggy because it does not deal with quoting new lines correctly. However it seems that it is fixed now. Ideally we could use Locale::PO::quote everywhere, but it does not escape tab characters: $string =~ s/\\(?!t)/\\\\/g; # \t is a tab This means the following: msgid "Tabulation (\\t)" msgstr "Tabulation (\\t)" become: -msgid "Tabulation (\t)" -msgstr "Tabulation (\t)" And we are seeing the following on Weblate: https://snipboard.io/BjQmDC.jpg Note that Locale::PO has not been updated since 2014... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 31197] New: Enabling Authority checks for all library staff but restrict the ability to edit Authority files to system admin
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '25

04 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31197 Bug ID: 31197 Summary: Enabling Authority checks for all library staff but restrict the ability to edit Authority files to system admin Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: susan.merner(a)nhs.net QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The ability to check whether an Authority such as a subject heading is in the authority file should be available to all staff BUT the option to edit authority files should be restricted to selected staff with system admin permissions. The Authority files affected would be Subject Headings (650), Series (490) and Corporate Authors. We want to ensure staff keep to the authorised lists and do not introduce or amend entries within Authorities. Is there a way to give cataloguers permission to have the "Link authorities automatically" button, but not edit, create or delete the authorities? If we could have a 'check authorities' button with no additional permissions, it would be really helpful! Or a way to flag unauthorised headings upon saving. We all need to be able to check if the subject headings (650 field) being pulled through by z39.50 are included in the authority file on Koha. At present, this is not possible, and there is no way to check z39.50 against the authority file. This raises an issue with cataloguers adding in unauthorised headings -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 36361] New: Show warning about pending ILL requests when a patron is deleted
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '25

03 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36361 Bug ID: 36361 Summary: Show warning about pending ILL requests when a patron is deleted Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: clemens.tubach(a)kit.edu, gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com, michaela.sieber(a)kit.edu, pedro.amorim(a)ptfs-europe.com When a patron is deleted and they have pending/undelivered ILL requests, we should at least show a warning, like we do with suggestions/holds. This is even more important until bug 32630 is fixed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 28141] New: Accessibility: OPAC Advanced Search fields aren't labelled
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '25

03 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28141 Bug ID: 28141 Summary: Accessibility: OPAC Advanced Search fields aren't labelled 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: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The OPAC advanced search page has unlabelled search fields making them inaccessible to users of screen readers. This is a complicated page to get right and I'm not entirely sure how best to fix this. Here are some of the issues with the page currently: Example issue 1: When using NVDA to access the search form fields out of context, it is hard to tell which index (keyword, author, title etc.) you are searching. This is an issue when searching multiple fields at once. "Enter search terms; edit; has auto complete" It would be better if the search form field was linked to the index combo box. We could use aria-labelledby but there may be better ways to do this. Example Issue 2: The label for "search-field_0" is blank. Example Issue 3: The search terms are linked by 'and' but this isn't entirely clear out of context using a screen reader: " ;combo box; collapsed; Subject" "and;combo box; collapsed; Title" "and;combo box; collapsed; Publisher Location" "Location and availability:; combo box; collapsed; All Libraries" "Sort by:; combo box; collapsed; Relevance" "Language; combo box; collapsed; No Limit" Example Issue 4: The remove field buttons aren't programmatically linked to the field they are removing -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 36471] New: Accessibility: OPAC search results header obscures content when zooming in
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '25

03 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36471 Bug ID: 36471 Summary: Accessibility: OPAC search results header obscures content when zooming in Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Blocks: 33516 Moved from comment on bug 33516: (In reply to Georgia Newman from comment #1) > We have recently reviewed our accessibility statement and we have noticed > this issue on the search results page of our OPAC. Users should be able to > enlarge/zoom up to 400% without loss of function. However, when display is > set to 1280x wide, looking at the search results page, we find that a user > can’t enlarge above 200% before the search results header obscures > everything on the page, so the search results aren’t visible. This fails > WCAG 2.1 criterium 1.4.10. We have noted this as an issue in our > accessibility statement and would like to see this improved in order to > comply with WCAG standards. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33516 [Bug 33516] Accessibility: WCAG 1.4.1 - Content reflow -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 36285] New: Staff UI form fieldset styling needs update
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '25

03 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36285 Bug ID: 36285 Summary: Staff UI form fieldset styling needs update Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 19772] New: Wrong success message if PATRON_NOTE is not defined
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '25

03 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19772 Bug ID: 19772 Summary: Wrong success message if PATRON_NOTE is not defined Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: aleisha(a)catalyst.net.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 14224 There is no PATRON_NOTE notice template created for new installation. If the pref (AllowCheckoutNotes) is set to on, a patron can let a note from the OPAC and the message "Your note about $TITLE / has been saved and sent to the library." is display to the screen. But actually the Koha logs mention "No circulation PATRON_NOTE letter transported by email at /home/vagrant/kohaclone/C4/Letters.pm line 697." and no notice is generated Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14224 [Bug 14224] patron notes about item shown at check in -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 15500] Add FRBRized view to OPAC & staff interface results
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '25

28 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15500 Carl <ctodd(a)hcc.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ctodd(a)hcc.edu -- You are receiving this mail because: You are watching all bug changes.

1 0