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

[Bug 17650] New: Create the option to save the cover with the uploaded files.
by bugzilla-daemon＠bugs.koha-community.org 16 Aug '24

16 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17650 Bug ID: 17650 Summary: Create the option to save the cover with the uploaded files. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: rsantellan(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Create the option to save the uploaded cover files with the rest of the files. Removing them from saving on the DB and save them on the koha uploads directory. Giving the implementation of creating cache miniatures for using them. There must be an option to enable this feature or not for backward compability. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 25983] New: Accessibility: 2.4.7 Focus Visibility
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '24

15 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25983 Bug ID: 25983 Summary: Accessibility: 2.4.7 Focus Visibility 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The purpose of this success criterion is to help a person know which element has the keyboard focus. It must be possible for a person to know which element among multiple elements has the keyboard focus. If there is only one keyboard actionable control on the screen, the success criterion would be met because the visual design presents only one keyboard actionable item. Where the success criterion says “mode of operation”, this is to account for platforms which may not always show a focus indicator. In most cases, there is only one mode of operation so this success criterion applies. https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 32659] New: Bootstrap identification
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '24

15 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32659 Bug ID: 32659 Summary: Bootstrap identification Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org It would be helpful to show bootstrap versions in the About page. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 28000] New: Locking expired patrons via cronjob should have a switch to remove holds/article requests
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '24

15 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28000 Bug ID: 28000 Summary: Locking expired patrons via cronjob should have a switch to remove holds/article requests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com Bug 21549 introduces 'LockExpiredDelay' - I think there should be a second pref 'RemoveRequestsWhenLocking' to allow the library to decide whether hold/article requests are removed when locking -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 31908] New: Context accessed but not always set on mainpage.pl
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '24

15 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31908 Bug ID: 31908 Summary: Context accessed but not always set on mainpage.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org To recreate: 1 - Sign in to staff interface as a user without 'catalogue' permission 2 - Get a message that you don't have access 3 - From that page, sign in as an authorised user 4 - Error: Can't use an undefined value as a HASH reference at /kohadevbox/koha/mainpage.pl line 88 I have also seen this error in production when using SSO and signing out of the staff client -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 32208] New: Adjustable title
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '24

15 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32208 Bug ID: 32208 Summary: Adjustable title 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org More info follows -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 31579] New: Improve reserve/request.pl to avoid mistakes with pick up locations
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31579 Bug ID: 31579 Summary: Improve reserve/request.pl to avoid mistakes with pick up locations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the place hold page reserve/request.pl, there are two sections. One is the "Hold details" section which allow for record hold. The other is "Place a hold on a specific item" which speaks for itself. The pick-up location by default is the signed-in user (the employee). But it is different from the "Allowed pick-up location" for the item which defaults to the homebranch. The wording should be "Pick-up location", btw, the "Allowed" states there's a list, not that the user should select it. A common tread is that the user comes in, select the pick up location in the record section, select an item *and doesn't modify the last column*, which overrule the pickup location in the notice. We propose a patch where a modification of the first drop down in the record modifies all the items dropdown to the same value by default. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 29700] New: Koha performs a second cashup in error when changing registers immediately after cashup
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29700 Bug ID: 29700 Summary: Koha performs a second cashup in error when changing registers immediately after cashup Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com To recreate: - perform a cashup for library A, register A - after cashup, koha takes you do /cgi-bin/koha/pos/register.pl?op=cashup - from that url, click to Set Library - Change yourself to library B and register B - koha takes you back to /cgi-bin/koha/pos/register.pl?op=cashup, this time for your new register, and performs a second cashup -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 28406] New: Point of sale don't register a sale when total amount is 0
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28406 Bug ID: 28406 Summary: Point of sale don't register a sale when total amount is 0 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Is that a valid use case? Likely. - For free stuff where it's useful to track the "sales" like for stock management or just to know the sold quantity as a stat. - Some real use: http://irc.koha-community.org/koha/2021-05-19#i_2353796 ==Test plan== 1. Try to sell with debit type item with price 0.00 2. Submit 3. page refreshes but no sign of a transaction 4. Register details show nothing either -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 28164] New: Sorting on POS register details transactions table is not working right
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28164 Bug ID: 28164 Summary: Sorting on POS register details transactions table is not working right Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com Sorting on the transactions table on the point of sales register details page doesn't appear to work correctly. - Make some transactions in the points of sale page - Go to the register details page - Try to sort on the different columns - Only the price column will (partially?) sort - There is also sorting on the Actions columun -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6