January 2023 - Koha-bugs - lists.koha-community.org

[Bug 32503] New: waitingreserves: UK format dates not sorting correctly
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '23

10 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32503 Bug ID: 32503 Summary: waitingreserves: UK format dates not sorting correctly 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Dates in the waiting reserves page are not sorting correctly when UK dates are used. When you view the waiting reserves page with a large number of resereves, and you sort them by 'Waiting since' or 'Date hold placed', if the system uses UK date format (DD/MM/YYYY) the sorting doesn't working correctly - for example, you might see: 02/02/2017 03/03/2017 08/02/2017 10/01/2017 16/12/2016 instead of the correct order, which would be: 16/12/2016 10/01/2017 02/02/2017 08/02/2017 03/03/2017 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 20228] New: Circulation alerts don't take AutoEmailPrimaryAddress system preference into account
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '23

10 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20228 Bug ID: 20228 Summary: Circulation alerts don't take AutoEmailPrimaryAddress system preference into account Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: sophie.meynieux(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In C4::Message->enqueue(), to_address is email or if not defined emailpro or if not defined B_email, irrespective of the value of AutoEmailPrimaryAddress system preference -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 32404] New: Two-factor authentication for staff client doesn't work for all staff accounts
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '23

09 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32404 Bug ID: 32404 Summary: Two-factor authentication for staff client doesn't work for all staff accounts 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org With the new feature, Two-factor authentication for staff client - TOTP, staff permissions seem to be needed to activate this: my ( $template, $loggedinuser, $cookie ) = get_template_and_user( { template_name => 'members/two_factor_auth.tt', query => $cgi, type => 'intranet', flagsrequired => { editcatalogue => '*' }, } ); which means that only staff with top-level catalogue permissions can activate their two-factor authentication. However, I believe this should be allowed by all staff accounts which would change this feature to allow staff to have just the "Staff access, allows viewing of catalogue in staff interface (catalogue) " permission. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 30953] New: Add sharing a list to staff client
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '23

09 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30953 Bug ID: 30953 Summary: Add sharing a list to staff client Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Bug 9032 added this OPAC feature. And I was quite sure that there was an intranet report too for it. But cant find it. So here it is.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 32527] New: can`t use <<user>> variable in SLIPS
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '23

08 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32527 Bug ID: 32527 Summary: can`t use <<user>> variable in SLIPS Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: paliotti(a)mdp.edu.ar QA Contact: testopia(a)bugs.koha-community.org Hi: Making customized ISSUESLIP and ISSUEQSLIP, the library circulation staff ask me if it´s possible add the staff user to the slips. Thinking that <<user>> variable works fine in cataloguing frameworks, by example, I added it but did'nt work. Neither [% user %], [% loggedinusername %], [% loggedin_user_name %] and others. If <<today>> works, why <<user>> don't ? it's not a global var? Thks in advance Pablo -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 32687] New: About lists version of sql client, not server
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '23

08 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32687 Bug ID: 32687 Summary: About lists version of sql client, not server Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CLIENT root@master:/usr/share/koha# mysql -V mysql Ver 15.1 Distrib 10.5.18-MariaDB, for debian-linux-gnu (x86_64) using EditLine wrapper SERVER root@mastersql:/app# mysql -V mysql Ver 15.1 Distrib 10.5.17-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2 About lists 10.5.18. The server is still on 17.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 31563] New: Numbers on claims tab not showing in translated templates
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '23

08 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31563 Bug ID: 31563 Summary: Numbers on claims tab not showing in translated templates 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When looking at the patron account details or checkouts tab in the staff interface, the tab Claims is missing the numbers in translated templates. Verified on master for German and Greek. I had filed bug 26561 about this a while ago, but the issue reappered and I don't see how to fix it in the po files. Also we have a second language where it's broken now. I wonder if it's the problem with 0 in templates showing here again. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 22490] New: Some strings in javascript files are untranslatable
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '23

08 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22490 Bug ID: 22490 Summary: Some strings in javascript files are untranslatable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Target Milestone: --- You can find them easily with these commands: git grep "_(" koha-tmpl/intranet-tmpl/prog/js git grep "_(" koha-tmpl/opac-tmpl/bootstrap/js They should be fixed, see https://wiki.koha-community.org/wiki/Coding_Guidelines#JS5:_Enabling_transl… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 32353] New: items.item_group_id should be undefined in tests by default
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '23

08 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32353 Bug ID: 32353 Summary: items.item_group_id should be undefined in tests by default Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Test Suite Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 24857 TestBuilder should set it to NULL and don't generate the item group. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24857 [Bug 24857] Add ability to group items for records -- You are receiving this mail because: You are watching all bug changes.

1 41

[Bug 24094] New: Authority punctuation mismatch prevents linking to correct records
by bugzilla-daemon＠bugs.koha-community.org 07 Mar '23

07 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24094 Bug ID: 24094 Summary: Authority punctuation mismatch prevents linking to correct records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In a bibliographic record, the comma preceding the relationship designator, i.e., the comma before $e, is prescribed--it has to be there for the record to conform to RDA and MARC21. Authority records view this as a different name/etc, so it does not match. Every, single, correctly cataloged RDA/MARC21 record is going to have a $e preceded by a comma in every authority controlled X00 and X10 field. Authorities need to disregard/strip trailing commas. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25