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

[Bug 17515] New: Advanced Editor - Rancor - Z39 sources not sorted properly
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '23

31 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17515 Bug ID: 17515 Summary: Advanced Editor - Rancor - Z39 sources not sorted properly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This appears to be a bug, the list of servers is retrieved from the database in order, however, it is stored in an unordered object, so the lists are posted to the page in a random order. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 23997] New: sample_z3950_servers.sql is failing on MySQL 8
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '23

31 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23997 Bug ID: 23997 Summary: sample_z3950_servers.sql is failing on MySQL 8 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Blocks: 23996 koha_1 | DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'rank, syntax, encoding,recordtype) VALUES koha_1 | ('lx2.loc.gov',210,'LCDB','','','LIBRA' at line 2 at /usr/share/perl5/DBIx/RunSQL.pm line 273. https://dev.mysql.com/doc/refman/8.0/en/keywords.html => RANK (R); added in 8.0.2 (reserved) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23996 [Bug 23996] MySQL 8 support -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 17649] New: Create only one message per borrower and overdue level
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '23

30 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17649 Bug ID: 17649 Summary: Create only one message per borrower and overdue level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Following a discussion on french list koha-infos, it appears that, among other ones, 2 things are expected from the overdue_notices.pl script (but not currently achieved) : 1) It should be possible to send only one message grouping all branches overdue items with same delay level => by now there are as much messages sent as overdue items branches with same level ( a patron that have overdue with same level in library A and B will received 2 messages claiming the same items.) This patch try to solve this problem ( provided to use only a default notice model in Notices and Slips). It introduces a new option (a|all_in_one) that has to be followed by a branchcode from which will be set the sender address of the message. 2) each branch should be able to send claims including only its very overdue items => by now messages also include, if they exist, all overdues with same delay level from other branches, even if library option is used. Patch from bug 17470 aims to solve this problem. Test plan (almost entirely and shamefully copied from bug 17470 !) 0/ Have (or create) at least two branches B1 and B2. Have (or create) a default notice for all branches in Notices and Slips Module 1/ Make sure you're logged in with an account belonging to B1, or switch to branch B1 2/ checkout item I1 (belonging to B1) to patron P (preferably while specifying a due date < today) 3/ switch to branch B2 4/ checkout item I2 (belonging to B2) to patron P (preferably while specifying a due date < today) 5/ make sure you have defined "Overdue notice/status triggers" for that patron category, ie with Delay=1 so that "Overdue Notice" is selected and "Email" is checked. 6/ from cli run 'perl ./misc/cronjobs/overdue_notices.pl' (optionally specifying also '-library B1 -library B2') example (say that B2CODE is the branchcode of B2 branch ): ./overdue_notices.pl -t -a B2CODE 7/ Two new entries will be generated in message_queue DB table, coming from different branches that have the SAME list of overdue items 8/ either see the 'content' field in these entries, or run 'perl ./cronjobs/process_message_queue.pl' to receive the actual emails (provided the email is properly setup). Apply patch redo step 6/ You will see that only one message had been created. Its content shows both B1 and B2 overdue items and the sender address matches B2 address as well. Olivier Crouzet -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 17754] New: MARCXML encoding problems
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '23

29 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17754 Bug ID: 17754 Summary: MARCXML encoding problems Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org Uploading authorities in MARCXML in 16.11 and master kills Umlauts while they work ok in the same file in mrc format. I have not checked biblios yet. Upload mrc: Universität Berlin (Freie Universität) Upload xml: Universitt̃ Berlin (Freie Universitt̃) -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 29480] New: Add email address as a method for generating the userid when self registering in OPAC
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '23

29 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29480 Bug ID: 29480 Summary: Add email address as a method for generating the userid when self registering in OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org - Add a system preference for selecting a method for generating the userid when self registering - Fall back to the default method (firstname.surname[uniqueness identifier when needed]) -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 28363] New: Always use semicolon when preference CSVDelimiter is missing
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '23

29 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28363 Bug ID: 28363 Summary: Always use semicolon when preference CSVDelimiter is missing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Some places use comma as value when preference CSVDelimiter is missing or empty. >From installer/data/mysql/mandatory/sysprefs.sql whe see that defaut install value is semicolon. This patch sets semicolon when preference CSVDelimiter is missing. "We are perl, we love semicolon ;)" Test plan : 1) With SQL, set system preference 'CSVdelimiter' to empty string. 2) Create CSV export in impacted pages 3) Check columns are separated by semicolon character -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 27812] New: Remove the ability to transmit a patron's plain text password over email
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '23

29 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27812 Bug ID: 27812 Summary: Remove the ability to transmit a patron's plain text password over email 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 We should not give libraries the ability to compromise patron accounts, it is considered a huge security issue and nobody in network security would ever recommend allowing passwords to be transmitted in clear text over email. It should simply not be possible to send a patron's password in plain text via email. As such, we should remove this ability from Koha. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 63

[Bug 21135] New: Upon log in, user is redirected to account page instead of the page where they logged in from
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '23

28 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21135 Bug ID: 21135 Summary: Upon log in, user is redirected to account page instead of the page where they logged in from 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When a user clicks on a link "log in to ..." they are redirected to their account page instead of staying on the page they were on to do whatever they needed to log in to do. To reproduce : 1- In Administration > System preferences, enable TagsEnabled 2- Make sure TagsInputOnDetail is set to Allow 3- Go to OPAC, and do a search 4- Click on title to go to the details page 5- Click on the "Log in to add tags" link 6- Enter your login credentials in the popup window Result : user is redirected to "My account" Desired result : user is now logged in but stays on the record detail page Second case : 1- In OPAC, click on Lists > View All 2- Click on "Log in to create new lists" 3- Enter your login credentials Result : user is redirected to "My account" Desired result : user is now logged in but stays on the lists page -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 25972] New: SIP2 server doesn't have a TLS/SSL-enabled listener
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '23

28 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25972 Bug ID: 25972 Summary: SIP2 server doesn't have a TLS/SSL-enabled listener Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com I'm not super familiar with SIP2, but I don't see why we couldn't have a TLS/SSL-enabled listener for the SIP2 server. Most people use stunnel to secure their SIP2 server, but why not build in TLS/SSL support directly? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 19464] New: emailLibrarianWhenHoldIsPlaced email enhancement
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '23

24 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19464 Bug ID: 19464 Summary: emailLibrarianWhenHoldIsPlaced email enhancement Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: karen(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com A school library that I'm working with would like the email sent by the preference emailLibrarianWhenHoldIsPlaced to go the library where the hold is placed rather than the admin email address. Sending an email directly to the branch email address would be a really nice option for multibranch systems that want to use this system preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3