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

[Bug 22160] New: OMNIBUS: Transfers enhancements
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '25

27 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22160 Bug ID: 22160 Summary: OMNIBUS: Transfers enhancements 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 88

[Bug 33137] New: Make sure columns on transactions and 'pay fines' tab are matching up
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '25

24 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33137 Bug ID: 33137 Summary: Make sure columns on transactions and 'pay fines' tab are matching up Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The information visible on the transactions and 'pay fines' tabs is drifting apart with different columns visible on each. It would be nice to make them consistent again. -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 30088] New: Forgotten password
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '25

23 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30088 Bug ID: 30088 Summary: Forgotten password 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Two thoughts: Is there a reason patrons have to be presented with two fields, one for login or one for e-mail address? The prompt says to enter one or the other. Since there is the possibility for more than one account to have the same e-mail address, should we only ask for the username? The second thought is, should Koha e-mail the account user if a request has been made to reset the password? This seems to be common practice these days. -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 30070] New: There are performance issues with edifactmsgs when you have a large number of messages
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '25

23 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30070 Bug ID: 30070 Summary: There are performance issues with edifactmsgs when you have a large number of messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client 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 The edifact messages table can grow to a very large size over time, and the page to display them has issues with this growth as it always loads all messages. We should switch this to an ajax driven datatable. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 136

[Bug 29858] New: Item.pm "Use of uninitialized value" warn when $field var is NULL
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '25

20 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29858 Bug ID: 29858 Summary: Item.pm "Use of uninitialized value" warn when $field var is NULL Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: OPAC Assignee: stalkernoid(a)gmail.com Reporter: stalkernoid(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 31800] New: REST API: POST endpoint for Biblios
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '25

20 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31800 Bug ID: 31800 Summary: REST API: POST endpoint for Biblios Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com CC: tomascohen(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 22013] New: Command line staging: Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202.
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '25

19 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22013 Bug ID: 22013 Summary: Command line staging: Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: simon.hohl(a)dainst.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Created attachment 83307 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=83307&action=ed… MARC File containing geographical authority data When using stage_file.pl to import authority data (see attachment), I get the warning: Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in regexp compilation at /usr/share/perl5/MARC/Record.pm line 206. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 207. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. That's 28 warnings for 31 records, but I am unable to decide which cause the warning and which do not. Anybody able to find out why a pattern? Cheers -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 26780] New: have a parameter to export authorized-values labels instead of codes.
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '25

17 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26780 Bug ID: 26780 Summary: have a parameter to export authorized-values labels instead of codes. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz When exporting biblios to another software it would be nice to be able to export authorized values labels instead of their codes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 26794] New: Item transfer modal may close automatically after a delay
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '25

17 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26794 Bug ID: 26794 Summary: Item transfer modal may close automatically after a delay 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: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi Koha, We got complains from users that the new item transfer modal is not convenient when using barcode scanner and mouse/keyboard is unavailable. I've made a small javascript to add in intranetuserjs that closes this modal after a delay (here, 3 secs). Some colleagues of mine told me I shall open a BZ to document this, there it is : <pre> /* Close item transfer modal after 3sec */ $('#item-transfer-modal').on('shown.bs.modal', function (e) { window.setTimeout(function () {$('#item-transfer-modal').modal('hide')}, 3000) }); </pre> Best, Arthur from BibLibre's Koha Support -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 27872] New: Expand {QUERY_KW} function from OPACNoResultsFound to not-empty search results page
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '25

17 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27872 Bug ID: 27872 Summary: Expand {QUERY_KW} function from OPACNoResultsFound to not-empty search results page 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If a patron finds a record but it is unavailable, they can use OPACSearchForTitleIn to look for that same record elsewhere. If a patron finds nothing at all, they can use OPACNoResultsFound to repeat their search in another catalog. But if a patron performs a search that returns *something* but not the thing they want, then they don't have a path to another catalog. We should allow that. -- You are receiving this mail because: You are watching all bug changes.

1 3