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

[Bug 16623] New: Limit patron discharge management by library
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '22

04 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16623 Bug ID: 16623 Summary: Limit patron discharge management by library 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Like Bug 10904 and patron modification requests, discharge requests should probably be limited by library. In fact I think it would make sense to use the same system preference, IndependentBranchesPatronModifications, for both. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 18403] New: Hide patron information if not part of the logged in user library group
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '22

03 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18403 Bug ID: 18403 Summary: Hide patron information if not part of the logged in user library group Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: new feature Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com Add the ability to hide patron record information from any other library (outside the group). -- You are receiving this mail because: You are watching all bug changes.

1 163

[Bug 29115] New: Placing a club hold is not showing warnings when unable to place a hold
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '22

02 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29115 Bug ID: 29115 Summary: Placing a club hold is not showing warnings when unable to place a hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)iki.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The code that is supposed to show warnings if someone in a club cannot reserve the item when placing a club hold is broken and not showing the warnings. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 29970] New: 500 Error when a record cannot be displayed
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '22

02 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29970 Bug ID: 29970 Summary: 500 Error when a record cannot be displayed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When a record cannot be decoded Koha shows a 500 error to the user. The code throws a Koha::Exceptions::Metadata::Invalid which is recorded in the plack-error We should catch the exception and provide a better message to the user. Often, these records will load in the editor, we should provide a link to the user so they can attempt to fix the record Alternately, we should attempt to assume the record is encoded in a different format (marc8) and attempt to convert uft-8 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 24993] New: koha-sip --restart is too fast, doesn't always start sip
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '22

02 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24993 Bug ID: 24993 Summary: koha-sip --restart is too fast, doesn't always start sip Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Sometimes doing koha-sip --restart inst happens too fast and start sip doesn't start it. A pause in there to let SIP catch up would probably fix it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 29976] New: (Bug 21729 followup) fix holds unit tests
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '22

02 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29976 Bug ID: 29976 Summary: (Bug 21729 followup) fix holds unit tests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests 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 Bug 21729 added to holds table the column patron_expiration_date. Currently test suite is failing : https://jenkins.koha-community.org/view/master/job/Koha_Master_D10/516/test… We must fix where TestBuilder is creating with source Reserve and data expirationdate : t/db_dependent/Holds/WaitingReserves.t t/db_dependent/Reserves/CancelExpiredReserves.t -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 29255] New: Built-in offline circulation broken with SQL error
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '22

01 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29255 Bug ID: 29255 Summary: Built-in offline circulation broken with SQL error Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Testing the built-in offline circulation system in a browser which still supports applicationCache, I ran into this error: DBD::mysql::st execute failed: Column 'branchcode' in field list is ambiguous at /kohadevbox/koha/offline_circ/download.pl line 84 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 29424] New: Replace the table on 'HTML customisations' administration with a visual alternative.
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '22

01 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29424 Bug ID: 29424 Summary: Replace the table on 'HTML customisations' administration with a visual alternative. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org There are a fixed set of 'Blocks' available for HTML Customisations.. I propose that instead of a table, we have a more visual representation of where these blocks will appear once content is added to them. Something more akin to the image we have in the Manual that is used to display where the blocks reside: https://koha-community.org/manual/21.05/en/html/tools.html?highlight=custom… But with the "Green blocks" being clickable to enter the editing process. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 29988] New: Log hold modification due to checkout of waiting hold to another patron
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '22

31 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29988 Bug ID: 29988 Summary: Log hold modification due to checkout of waiting hold to another patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: - turn on the holds log - make sure you have force_checkout permission - place a hold on item for Patron A - check item in, confirm item shows as Waiting for Patron A - try to check item out to Patron B, get a popup about Patron A's hold - choose "Revert waiting status" and "Yes, check out" - confirm item is checked out to Patron B - confirm hold no longer shows as waiting for Patron A - check action logs for your hold, confirm there is no entry for the reversion of waiting status -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 14783] Allow patrons to change pickup location for non-waiting holds
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '22

31 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14783 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA --- Comment #25 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi Björn, there is a small conflict when I try to apply these patches that I had hoped I had fixed, but there is also this: FAIL t/db_dependent/Hold.t FAIL valid "my" variable $dt masks earlier declaration in same scope "my" variable $dt masks earlier declaration in same scope Could you please have a look? Also we have some guidelines of how the patch subject line should be formatted (always starting with Bug xxxx: optionally followed by (QA follow-up) or (Follow-up). Let me know if I can help with fixing those: Processing additional checks * Commit title does not contain 'follow-up' correctly spelt - 19baf3584b * Commit title does not contain '(QA follow-up)' correctly spelt - 19baf3584b * Commit title does not contain 'follow-up' correctly spelt - 65676a3ba0 * Commit title does not contain '(QA follow-up)' correctly spelt - 65676a3ba0 -- You are receiving this mail because: You are watching all bug changes.

1 0