May 2024 - 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 34287] New: Patron's should not be able to ask for checkoutability for different patrons
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '24

15 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34287 Bug ID: 34287 Summary: Patron's should not be able to ask for checkoutability for different patrons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com CC: tomascohen(a)gmail.com Bug 30979 implemented an endpoint for checking availability for checking out an item, and the description explains it is for checking out themselves... but it allows asking for any patron's checkoutability. I open this bug to discuss that behvior. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 36722] New: REST API won't work if json-schema.org is down
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '24

15 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36722 Bug ID: 36722 Summary: REST API won't work if json-schema.org is down Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au CC: tomascohen(a)gmail.com This is arguably the same issue as bug 23653 except that it's a different website this time. Also, Koha won't crash if json-schema.org is down, but the API will return a 404 for all endpoints. Like bug 23653, I think that we should use a local copy of the specification. At the moment, the way to do that is to download http://json-schema.org/draft-04/schema#, save it into our source tree, and then run the following: my $schema = JSON::Validator::Schema::OpenAPIv2->new; $schema->specification($saved_schema_spec); In theory, that's it. I'll look at providing a patch shortly... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 35181] New: Can no longer edit sample records with advanced cataloguing editor
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35181 Bug ID: 35181 Summary: Can no longer edit sample records with advanced cataloguing editor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I wonder if this is a side effect on the recent work on 'invalid metadata'. * Activate * Make sure you open any record with the advanced editor * Try to open: Perl best practices / Damian Conway. * You get stuck in loading * Javascript error shows "Invalid-metadata" on top of the MARC record, causing a syntax error -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 35443] New: Persistent encoding error message in Advanced Editor
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35443 Bug ID: 35443 Summary: Persistent encoding error message in Advanced Editor Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 159376 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=159376&action=e… Record with encoding errors? Related to bugs 34014 and 351814 Recreating this bug requires having a record with some kind of encoding error. Usual errors included bad characters or record separator characters such as blank spaces. My understanding of the bug fixes above are that the fix should automatically strip out the errors. The encoding error notification should only appear one time. 1. Find record with errors (example record attached that has a persistent error message). 2. Open record in the advanced editor. 3. See the encoding error notification. Click on it to make it go away. 4. Edit the record in some way. 5. Save the record and close the advanced editor. 6. Reopen the record in the Advanced editor and see the encoding warning box again. No encoding error message appears when opening the record in the Basic Editor. Also if we tell the user to check the logs, there should be a convenient way to access them - which perhaps is a separate issue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5