July 2022 - Koha-bugs - lists.koha-community.org

[Bug 30935] New: Holds to pull shows wrong first patron
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '22

16 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30935 Bug ID: 30935 Summary: Holds to pull shows wrong first patron 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I've seen a couple of bugs on this and they're all 'Resolved' but I still see the problem. Maybe it's not the exact same thing... So I'm creating this in case. Someone else can test and tell me if I'm crazy or not. When a biblio has more than one hold (record-level), the 'First patron' column on the 'Holds to pull' report is not showing the actual first patron, but the last in the line. I tried it on a bywater sandbox, just in case it was my installation that was the problem, and it does the same thing. To test : 1) Place a record-level hold on a biblio with an available item 2) Check the Holds to pull page (circ/pendingreserves.pl) --> The biblio should appear in the list and the patron should appear in the 'First patron' column 3) Place a second record-level hold on the same biblio 4) Go back to the Holds to pull page --> The biblio is still there, but the patron in the 'First patron' column is the second patron 5) Place a third record-level hold on the same biblio 6) Go back to the Holds to pull page --> The biblio is still there, but the patron in the 'First patron' column is the third patron Other bugs I found that talk about this: Bug 24488 (Closed fixed), Bug 30337 (pushed to master) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 26835] New: Ability to remove Lost Items from Patrons Account without Checking in
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '22

16 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26835 Bug ID: 26835 Summary: Ability to remove Lost Items from Patrons Account without Checking in Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Libraries all have unique ways of handling lost statuses. At the moment, Koha allows libraries to remove a lost item from the patron's account when set to a lost status and also to not remove it. Great! However, we would like to see Koha go one step forward after the library chooses to not remove the lost item from the patron's account, to allow for the item to be removed at a later date. A preference would be to have the Batch Item Modification allow for libraries to change an item's lost status to another lost status, and also remove it from the patron's account. Using the batch item modification will allow for libraries to do this operation in bulk ! Currently, if a library has the option to credit the patron if they do return a lost item, the library has no way of telling Koha (at check-in) don't refund, don't remove the lost status, just remove it from the patron's account. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 23541] New: Duplicate Hold Notifications
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '22

15 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23541 Bug ID: 23541 Summary: Duplicate Hold Notifications Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In 18.11, it was reported that library patrons from several libraries were receiving duplicate hold notifications. This is not performing consistently, and hard to reproduce. Both Firefox and Chrome browsers have performed the same way. It would appear that the hold request has been sent twice and unfortunately, it can't be determined what is causing this. The patrons that have received duplicate hold notifications don't consistently get the duplicate hold notification, it is quite random. This duplicate hold notifications are occurring in Email form and a variety of email providers are doing this. These duplicate hold notifications are happening on holds on the shelf and checked in holds, this is happening sporadically during the day. The libraries that have reported this are not using SIP devices and only one is using a RFID scanner. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 30314] New: Microsoft font makes extra space in OPAC with Chrome, Edge, and Vivaldi browsers
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '22

15 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30314 Bug ID: 30314 Summary: Microsoft font makes extra space in OPAC with Chrome, Edge, and Vivaldi browsers Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Browser compatibility Assignee: oleonard(a)myacpl.org Reporter: frank(a)sydt.com.tw QA Contact: testopia(a)bugs.koha-community.org Created attachment 131850 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131850&action=e… Compare issue between Firefox and other browsers Dear All, We found an issue when using Microsoft font like the attached file in OPAC. When we set the font from Microsoft to Google font. The problem is fixed. The engineer said those browsers who had this issue, within the code, found an extra "user agentstylesheet" from Google. It seems not to influence the system work, but one Koha user reports this to us. So, we also report here and hope it is not a serious problem for all Koha users. Best regards, Frank Chou Shou Yang Digital Technology Co., Ltd. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 28420] New: Allow login via AzureAD OpenID-Connect
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '22

14 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28420 Bug ID: 28420 Summary: Allow login via AzureAD OpenID-Connect Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: mark.jaroski(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Hi, At the World Health Organization our South-East Asian regional office uses Koha for their regional library, with access by all WHO staff in the region and selected staff worldwide. Since local user databases can present a security risk we require that all applications for staff be integrated with our identity provider which at the moment is Microsoft's AzureAD. AzureAD uses OpenID-Connect and is mostly drop-in compatible with Google's implementation, with the exception that in order to construct the URLs both for redirection and for validation you need to know the organization's Azure tenant ID. Because our system integrator is not interested in pursuing this integration I've taken it on myself, and so I've set up a development environment and have started working on the code. My plan is to set up the configuration parameters and to then use them in a very slightly altered copy of the current googleopenidconnect file. I think in the long run it would be better to have a generic OpenID-Connect configuration to allow integrations with other providers like Okta and OneLogin, but we don't need for the moment that so for now I'll just add the AzureAD provider. I'll read up on the rest of the contribution procedure, and I'll be back with a patch/PR in a few days. Best, Mark -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 30344] New: Changing a patron from a category that allows guarantors to one that doesn't should remove that link
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '22

14 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30344 Bug ID: 30344 Summary: Changing a patron from a category that allows guarantors to one that doesn't should remove that link Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a child typo patron is changed to an adult type patron, it hides the patron's guarantors, but does not remove that link. We should be removing that link. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 30351] New: Changing a patron type should warn librarian if a guarantor/guarantee relationship will be severed
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '22

14 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30351 Bug ID: 30351 Summary: Changing a patron type should warn librarian if a guarantor/guarantee relationship will be severed 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Right now, if a librarian changes a child with guarantors to and adult, or an adult with guarantees to a child ( via Bug 30344 ), the relationship is severed automatically. It would be nice if there was a warning that this is going to happen. I'm thinking we could just have a warning show up beside the patron category selector if the new patron category would result in either guarantor relationships or guarantee relationships being severed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20207] New: Anonymous Purchase Suggestions show on OPAC even when OPACViewOthersSuggestions is set to Don't Show
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '22

14 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20207 Bug ID: 20207 Summary: Anonymous Purchase Suggestions show on OPAC even when OPACViewOthersSuggestions is set to Don't Show 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: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When you enable AnonSuggestions and ALLOW patrons that aren't logged in to make purchase suggestions, once a suggestion has successfully been submitted, Anonymous Purchase Suggestions will show on OPAC even when system preference OPACViewOthersSuggestions, is set to Don't Show. The suggestions will show on opac-suggestions.pl. However, if you search for the title you suggested, you will get a message saying "You are not authorized to see pending purchase suggestions." -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 31177] New: Misplaced import in C4::ILSDI::Services
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '22

14 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31177 Bug ID: 31177 Summary: Misplaced import in C4::ILSDI::Services Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Koha::I18N is not added where it should. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 18232] New: Koha::Cache::flush - Simply flush all caches
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '22

14 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18232 Bug ID: 18232 Summary: Koha::Cache::flush - Simply flush all caches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org This is handy when upgrading Koha or fiddling with config. -- You are receiving this mail because: You are watching all bug changes.

1 10