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

[Bug 27963] New: touch_all_items.pl script is not working at all
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '21

24 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27963 Bug ID: 27963 Summary: touch_all_items.pl script is not working at all 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: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org Depends on: 18501 The touch_all_items.pl script doesn't work at all currently, e.g. it is not modifying any of the items. Based on a quick look at the history this seems to have started after "Bug 18501: (QA follow-up) Fix regressions highlighted by unit tests" (7e2514ac) commit. The itemcallnumber column would need to be marked as dirty using ->make_column_dirty('itemcallnumber') for this to work. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18501 [Bug 18501] Automatic refunds need protection from failure -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 27251] New: Rewrite the QOTD editor using the Koha REST API
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '21

23 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27251 Bug ID: 27251 Summary: Rewrite the QOTD editor using the Koha REST API Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: System Administration Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The quote of the day editor has some bugs and is not like the other screens. We should rewrite it to fit better the libraries and SMTP servers administration pages (for instance). -- You are receiving this mail because: You are watching all bug changes.

1 53

[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 26517] New: Avoid deleting patrons with permission
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26517 Bug ID: 26517 Summary: Avoid deleting patrons with permission 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: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The patron deletion script misc/cronjobs/delete_patrons.pl uses C4::Member::GetBorrowersToExpunge() to get patrons that may be deleted. This method filters patrons from a staff category. I propose to also filter patrons having permission, so a staff member. Some small libraries do not define a "staff" category and give permissions to regular patrons. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 28001] New: delete_patrons.pl requires category but does not mention this in POD
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28001 Bug ID: 28001 Summary: delete_patrons.pl requires category but does not mention this in POD Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz You cannot run the script without category, the SQL fails - we should either fix this or note that category is mandatory in the script root@kohadevbox:koha(master)$ perl misc/cronjobs/delete_patrons.pl --expired_before =1910-01-01 C4::Members::GetBorrowersToExpunge(): DBI Exception: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ') GROUP BY borrowers.borrowernumber ) xxx WHERE currentissue IS NULL' at line 12 [for Statement " SELECT * FROM ( SELECT borrowers.borrowernumber, MAX(old_issues.timestamp) AS latestissue, MAX(issues.timestamp) AS currentissue FROM borrowers JOIN categories USING (categorycode) LEFT JOIN ( SELECT guarantor_id FROM borrower_relationships WHERE guarantor_id IS NOT NULL AND guarantor_id <> 0 ) as tmp ON borrowers.borrowernumber=tmp.guarantor_id LEFT JOIN old_issues USING (borrowernumber) LEFT JOIN issues USING (borrowernumber) WHERE category_type <> 'S' AND ( borrowers.flags IS NULL OR borrowers.flags = 0 ) AND tmp.guarantor_id IS NULL AND dateexpiry < ? AND categorycode IN () GROUP BY borrowers.borrowernumber -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17