August 2020 - Koha-bugs - lists.koha-community.org

[Bug 24940] New: Serials statistics wizard: order vendor list alphabetically
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24940 Bug ID: 24940 Summary: Serials statistics wizard: order vendor list alphabetically Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Currently the vendor pull down in the serials statistics wizard appears to be ordered by vendor id instead of sorting alphabetically by vendor name. This is quite confusing for a longer list. To test: - Add at least 2 vendors: - First: Zzzz - Second: Aaaa - Add subscriptions for each of the vendors - Check the pull down in the serials statistics wizard - Verify it lists them as Zzzz, Aaaa -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 26312] New: Add some error handling during Elasticsearch indexing
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26312 Bug ID: 26312 Summary: Add some error handling during Elasticsearch indexing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Currently Elasticsearch dies if we get an error rather than a response from the ES Client. Generally we can see something like [6056] Committing 5000 records... [Timeout] ** [http://XXX.XXX.XXX.XXX:9200]-[599] Could not write to socket: 'Connection timed out', called from sub Search::Elasticsearch::Role::Client::Direct::__ANON__ at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Indexer.pm line 123. With vars: {' Rather than killing the whole indexing process, we should catch the error, fail the commit, and keep indexing records. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 55

[Bug 24000] New: working title
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '21

25 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24000 Bug ID: 24000 Summary: working title 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 16335] New: Refactor OpacHiddenItems
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '21

23 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16335 Bug ID: 16335 Summary: Refactor OpacHiddenItems 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: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org See 14385 and 10589 as well. The problem is this functionality would be better written using the newer Koha::RecordProcessor filtering functionality. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 21754] New: If an item is marked as lost, any outstanding transfers upon it should be automatically cancelled
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '21

23 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21754 Bug ID: 21754 Summary: If an item is marked as lost, any outstanding transfers upon it should be automatically cancelled 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: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When an item is marked as lost automatically cancel any outstanding transfers on it (this is an alternative to bug 21732 - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21732- which checks if a syspref is enabled before cancelling outstanding transfers on the lost item). Also set the items holding branch to the transfers source ('from') branch. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 23129] New: Items holdingbranch should be set to the originating library when generating a transfer
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '21

23 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23129 Bug ID: 23129 Summary: Items holdingbranch should be set to the originating library when generating a transfer 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- In C4::Items::ModItemTransfer we call ModItem to update the holdingbranch of the item. Currently we set this to the transfer destination. By definition we are generating a transfer because the item has not yet arrived. We should set the holdingbranch to the current location of the item -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 23503] New: Personal name authority search: search results aren't sorted in alphabetical order after page 51
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '21

23 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23503 Bug ID: 23503 Summary: Personal name authority search: search results aren't sorted in alphabetical order after page 51 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: marie-luce.laflamme(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org After performing an authority search by "Personal name", we have noticed that search results aren't sorted in alphabetical order after page 51. 1) Go to Authority search (click on "More" and select "Authorities" on the top left corner) 2) Select "Personal Name" in the Default Menu. Leave the search box empty and submit. 3) Assess the first 50 pages of results (all results are sorted alphabetically) 4) Access page 51 and notice the different pattern of results ( results aren’t sorted in alphabetical order). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 25950] New: REMOTE_ADDR set to undef if client IP matches a koha_trusted_proxies value
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '21

23 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25950 Bug ID: 25950 Summary: REMOTE_ADDR set to undef if client IP matches a koha_trusted_proxies value 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If you have a koha_trusted_proxies value of 192.168.1.0/24 and your client IP is 192.168.1.100, it'll set REMOTE_ADDR to undef. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 21111] New: Add --exclude-indexes option to koha-run-backups
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21111 Bug ID: 21111 Summary: Add --exclude-indexes option to koha-run-backups Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz koha-dump implements the --exclude-indexes option, and koha-run-backups should inherit it so it is of more use. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 22248] New: Error when incrementing Mana comment
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22248 Bug ID: 22248 Summary: Error when incrementing Mana comment Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 17047 Target Milestone: --- When I select an existing Mana comment on a subscription the process completes successfully but in the console this error is returned: Can't return outside a subroutine at /home/vagrant/kohaclone/svc/mana/increment line 48. It looks like that script should return JSON. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17047 [Bug 17047] Mana Knowledge Base : share data -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11