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

[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 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

[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

[Bug 30519] New: Regression: using sys pref CircConfirmItemParts prevents checkin from moremember.pl and circulation.pl
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '24

13 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30519 Bug ID: 30519 Summary: Regression: using sys pref CircConfirmItemParts prevents checkin from moremember.pl and circulation.pl Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With the addition of bug 25261, utilizing the sys pref CircConfirmItemParts and materials specified 952$3, you can no longer use the Check In column on either the morememeber.pl or circulation.pl. To test: --set sys pref to require confirmation --add a materials specified note to an item --check item out to a patron, confirming the note --go to patron record, either moremember or circulation --using the Check In column, attempt to check in the item --notice no confirmation box, and item is not checked in -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 31506] New: Add "backup days" to /etc/koha/koha-common.conf
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '24

13 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31506 Bug ID: 31506 Summary: Add "backup days" to /etc/koha/koha-common.conf Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com koha-run-backups takes the --days argument to say how many days of backup we should keep around. The value of this is set to two in the default /etc/cron.daily/koha-common that is installed by the Debian packages. I routinely increase this value to keep more backup. One thing that can happen now is that I want to create fresh backups for all the sites on a server before doing an upgrade. So I run koha-run-backups manually, but I forget about the --days argument. Result: I loose a lot of backup! It would be nice if the default for --days could be set somewhere like /etc/koha/koha-common.conf. That way we could run koha-run-backups both from cron and manually, without the --days argument, and keep the same amount of backups either way. If --days is given as an argument, it should override the default. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 32641] New: Patron search is not working
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '24

12 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32641 Bug ID: 32641 Summary: Patron search is not working Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: librarian(a)pilani.bits-pilani.ac.in QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 145332 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=145332&action=e… Patron search error by firstname or surname Not getting any search results using Firstname or surname in Koha 22.11.01. System returning 500: Internal server error - Month out of range.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22