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

[Bug 37931] New: Wrong OPAC facet item types label
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '25

04 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37931 Bug ID: 37931 Summary: Wrong OPAC facet item types label Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org Bug 36750 patch "Bug 36750: Fix some labels" missed OPAC item type label changes. https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=166289 -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 39030] New: Search results in the index, when in Arabic, are based on the letters that make up the searched word in the index. Therefore, the results display the entire index, unlike in French or English, where the results are accurate and based on complete words.
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '25

04 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39030 Bug ID: 39030 Summary: Search results in the index, when in Arabic, are based on the letters that make up the searched word in the index. Therefore, the results display the entire index, unlike in French or English, where the results are accurate and based on complete words. Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: riadilan(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com Created attachment 177515 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=177515&action=e… pictur Search results in the index when in Arabic are based on the letters that make up the searched word in the index. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 39033] New: BlockExpiredPatronOpacActions set to block renewals gives 500 error if OverduesBlockRenewing set to "Allow"
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '25

04 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39033 Bug ID: 39033 Summary: BlockExpiredPatronOpacActions set to block renewals gives 500 error if OverduesBlockRenewing set to "Allow" Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: heather(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a library has the system preference OverduesBlockRenewing set to "Allow" renewals of overdue items AND the system preference BlockExpiredPatronOpacActions set to block "Renewing an item," clicking the renew link from the Overdues tab of the expired patron's OPAC account generates a 500 error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 39009] New: Creating new patron "Preferred Name" is not working
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '25

04 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39009 Bug ID: 39009 Summary: Creating new patron "Preferred Name" is not working Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: julie(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In 24.11.01 creating a new patron the "Preferred Name" field is not used in the new patron account. Instead the "First Name" is used. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 19605] New: ILL backends should be pluggable through regular Koha plugins
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '25

04 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19605 Bug ID: 19605 Summary: ILL backends should be pluggable through regular Koha plugins 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Right now, the ILL module requires a configuration entry for a path in which to look for the backend implementations. This should be implemented in a more simple way for end-users. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 77

[Bug 35464] New: When importing records diff view implies imported records will overwrite even ignored
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '25

04 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35464 Bug ID: 35464 Summary: When importing records diff view implies imported records will overwrite even ignored Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - Export some records form Koha 2 - Strip all the subject fields 3 - Stage for import - Set matching rule on 999 or isbn, whatever works - Set action when matching record found to ignore 4 - View the batch and see the matches 5 - Click the diff view 6 - It shows the imported record with subject stripped 7 - It shows the subject fields in the existing record crossed out 8 - This makes it look like the import will remove fields 9 - Import the batch 10 - Confirm the records are still complete, subject not removed -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 22925] New: AuthenticatePatron should fail if patron has lost card
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '25

04 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22925 Bug ID: 22925 Summary: AuthenticatePatron should fail if patron has lost card Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- If Patron is declared as lost card it might be better not to allow an authentication, so that no renewal of holds can be made. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 23011] New: AuthenticatePatron could alert if password is not safe
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '25

04 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23011 Bug ID: 23011 Summary: AuthenticatePatron could alert if password is not safe Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- I work on a portal solution called Bokeh and we need to get the information from the webService that the patron's password is not safe and should be renewed. Reply from the webservice could look like this : <?xml version="1.0" encoding="UTF-8"?> <AuthenticatePatron> <patronId>4</patronId> <error>PatronPasswordNotSecure</error> <securePasswordPattern>^(?=.*[A-Za-z])(?=.*\d).{6,}$</securePasswordPattern> <securePasswordLabel>Password must be at least 6 character long and include a letter and a digit</securePasswordLabel> </AuthenticatePatron> That would allow the borrower to authenticate but provide the portal software with information about the rules to define a new password. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 12469] Add more information to the ILS-DI results
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '25

04 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12469 Arthur Suzuki <arthur.suzuki(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |RESOLVED Resolution|--- |WONTFIX --- Comment #16 from Arthur Suzuki <arthur.suzuki(a)biblibre.com> --- As sonia said, the callnumber was already added. Also, the return date is available through the rest-api. This ticket is not really needed anymore. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 18994] New: Show the branch name where checkin occurred on a title' s Checkout History display
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '25

04 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18994 Bug ID: 18994 Summary: Show the branch name where checkin occurred on a title's Checkout History display Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: techservspec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The Checkout History tab (issue.pl) currently shows the branch name and time stamp for a checkout, but only the time stamp for when it was returned. There are occasions in multi-branch systems when it is helpful to also know where the checkin occurred. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12