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

[Bug 9121] C4::Serial SQL possible collision on subscription.subscriptionid and subscriptionhistory.subscriptionid
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '25

28 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9121 Nick Clemens (kidclamp) <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=37569 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 9121] C4::Serial SQL possible collision on subscription.subscriptionid and subscriptionhistory.subscriptionid
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '25

28 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9121 Nick Clemens (kidclamp) <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=27964 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 27964] New: Link to subscription in serial collections view is broken - the field subscriptionid is undefined in the subscription object.
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '25

28 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27964 Bug ID: 27964 Summary: Link to subscription in serial collections view is broken - the field subscriptionid is undefined in the subscription object. Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org The functions C4::Serials::GetSubscription and C4::Serials::GetSubscriptionsFromBiblionumber return subscriptions where subscriptionid is undefined when the subscription have no subscription history. The database queries use wildcards to include fields from a left joined table. subscriptionhistory.subscriptionid will be NULL, which might be the value choosen as the field subscriptionid. How the field is chosen may depend on the version of DBI as this problem was discovered after an upgrade to Ubuntu Focal Fossa from Bionic Beaver. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 39477] New: Highlighting the item search field that is being deleted doesn't work
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '25

27 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39477 Bug ID: 39477 Summary: Highlighting the item search field that is being deleted doesn't work Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org Steps to reproduce: 1. Administration - Item search fields 2. New field - fill out any values for the required fields and submit 3. Click the delete button for the new field Expected result: koha-tmpl/intranet-tmpl/prog/js/item_search_fields.js#L13 thinks it will add the class "highlighted-row" to the table row, and that doing so will show that row with a yellow background while the alert asks if you are sure Actual result: since CSRF protection added a form around the button, the row is three parent()s up, not two, but even after adding the third parent(), the page doesn't reflect the added class until after the confirm() alert is dismissed, which is too late. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 26867] New: Holds to Pull should use cn_sort
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '25

27 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26867 Bug ID: 26867 Summary: Holds to Pull should use cn_sort Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: - create three bibs, each with one item. those items should have these call numbers: -- JC43 .G6 1890 -- JC330 .F74 2000 -- JC480 .R63 2006 - place an item level hold on each item - go to Holds To Pull, sort by call number - notice items are order incorrectly, going 330, 43, 480 - use a report to pull the cn_sort values for your 3 items, confirm that ordering by cn_sort in your report correctly orders them 43, 330, 480 We should use cn_sort here to get them in the correct order. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 33516] New: Accessibility: WCAG 1.4.1 - Content reflow
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '25

27 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33516 Bug ID: 33516 Summary: Accessibility: WCAG 1.4.1 - Content reflow Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org 1.4.10 Reflow: Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: (Level AA) • Vertical scrolling content at a width equivalent to 320 CSS pixels; • Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require two-dimensional layout for usage or meaning. These 2 requirements are to be met simultaneously and are not independent of each other. A user should be able to increase the size of text to 200% even when the information is displayed on a narrow mobile phone screen. Alternatively, a user should be able to magnify the screen to 400% and increase the text size a further 200% Users with visual impairments often enlarge web content to make it easier to see. When content is enlarged to 400% zoom or viewed on a screen with a width of 320 CSS pixels, content should be presented to a user with no loss of information or functionality, and without requiring scrolling in two dimensions. The value of 320 CSS pixels was chosen as a reasonable minimum size that authors could achieve and also replicates the smaller screen sizes of common mobile devices. The width of 320 CSS pixels exactly corresponds to a desktop browser window set to a width of 1280px and zoomed in to 400%. FAIL: When the browser window is set to a width of 320px on the homepage, the horizontal scroll bar is displayed. FAIL: When the browser window is set to a width of 320px on the ‘Details for: Biblio title’ page, the horizontal scroll bar is displayed. Other pages may also be failing on this criteria.. To reach AA standard, we are required to rework these pages and how they reflow for such zoom levels/screen sizes. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 39472] New: WCAG 2.1: 2.5.3 - Label in Name (Level A)
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '25

27 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39472 Bug ID: 39472 Summary: WCAG 2.1: 2.5.3 - Label in Name (Level A) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Accessibility Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, oleonard(a)myacpl.org https://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html Issue • The ‘Sign in’ button has been given the aria-label ‘Log into your account’ • Although this is a clear label, it does not match the visible label • This may prevent speech-input users from being able to interact effectively with this button as the label they can see and that they will speak, does not match the programmatic label required to activate the control Solution • Ensure that the accessible name matches or contains the text that is presented visually • Where possible, the accessible name should be assigned through native elements and semantics. That helps ensure an exact match between the visible label and name • Note: aria-label and arialabelled-by overrides any other information associated with the element so make sure it matches the visible text https://webaim.org/articles/label-name/ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 39474] New: Stock rotation - clicking OK on transfer modal leaves item in Transit pending status
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '25

27 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39474 Bug ID: 39474 Summary: Stock rotation - clicking OK on transfer modal leaves item in Transit pending status Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: heather(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When an item belonging to a rota is checked in to advance it to the next stage of the rota, clicking the OK button of the modal leaves the item in "Transit pending" status with no messaging to clarify, rather than initiating the transfer and putting the item "In Transit". Users currently need to click the Print Slip button of the modal to move the item to In Transit status. Some libraries may not print slips for their stock rotation workflow, so this workflow could be confusing for them and result in unnecessary clicks to dismiss the print modal. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 39401] New: Item date accessioned should prevent future dates
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '25

27 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39401 Bug ID: 39401 Summary: Item date accessioned should prevent future dates Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The date accessioned flatpickr on additem.pl should not allow dates in the future. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 39470] New: Circulation debt confirmations should be independently configurable
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '25

27 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39470 Bug ID: 39470 Summary: Circulation debt confirmations should be independently configurable Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The AllFinesNeedOverride syspref originally only popped up a circ confirmation when a specific patron had fines under the noissuecharge limit. The syspref now also pops up confirmations when a patron's guarantees or guarantor (and guarantor's guarantees) have charges. We deliberately do NOT use the NoIssuesChargeGuarantorsWithGuarantees syspref as we do not want to limit a child's ability to check out based on the debts of other family members. While the confirmation doesn't restrict checkouts, an untrained circ worker might still take it as a reason to not check out to the child when it pops up. Currently there's no way to enable/disable the guarantor/guarantee debt confirmations without also disabling the confirmation about fines under the noissuecharge limit. It would make sense to change AllFinesNeedOverride to a checkbox list where the "debt", "debt_guarantees", and "debt_guranators" confirmations could be enabled/disabled independently. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0