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

[Bug 6734] Show location in serials history table
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '22

09 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6734 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA Patch complexity|--- |Trivial patch -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 29801] New: Holds reminder cron not finding notice for all libraries
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29801 Bug ID: 29801 Summary: Holds reminder cron not finding notice for all libraries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: nick(a)bywatersolutions.com Depends on: 28153 When running the holds reminder cron, it will give a "no letter found" error if the only HOLDS_REMINDER email is for all libraries rather than a specific library. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28153 [Bug 28153] Add 'Hold reminder' messaging preference -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 29237] New: When deleting funds from an inactive budget, the results page returns to a different budget
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29237 Bug ID: 29237 Summary: When deleting funds from an inactive budget, the results page returns to a different budget Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: valerie(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In Administration/Budgets, I am in the "inactive budgets" tab, deleting funds under a specific budget. (In this instance, budget period #29.) When I select "delete" for the fund, it opens a new page to verify that I want to delete this budget. After it completes the deletion, it goes to a different budget, an active budget. (In this case, budget period #30). I confirmed that the fund was deleted as expected from the inactive budget, but with the page going to a different budget when complete, a user could easily delete something unintended. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 29559] New: Update creates "unexpected type" entries for standard codes in debit and credit types
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29559 Bug ID: 29559 Summary: Update creates "unexpected type" entries for standard codes in debit and credit types Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com After an update from 18.11 to 20.11.11 we notice that there are a lot of "Unexpected type found during upgrade (Voided)" in the patron accounts. It looks like 19.12.00.027 / Bug 24532 and maybe others are related to this. Following entries have been added: select * from account_credit_types; LOST select * from account_debit_types; Pay W It could be related to voiding entries, but I am not fully understanding the issue yet. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 14907] Item search: Call Numbers in Item search results are ordered alphabetically
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14907 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomascohen(a)gmail.com --- Comment #5 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Owen Leonard from comment #2) > The item search table is rendered server-side, so all sorting happens > server-side. This eliminates some of our standard sorting methods, like > embedding a sortable string in a title tag. > > Renaming the column "cn_sort" has the right effect for the purposes of > sorting: The column name "cn_sort" is passed to the query and the rows are > sorted correctly by call number. > > Unfortunately this breaks the column filter: "cn_sort" is an ambiguous > column name for the purposes of the query because of biblioitems.cn_sort. > I'm not sure if there is a good way to handle this besides adding some > conditional code specific to these columns. > > Suggestions welcome! Hi Owen, does that mean we should expect similar issues for date sorting for server side rendered tables? Or is it something specific to how this table was implemented? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 11750] Overdue report does not limit patron attributes
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11750 --- Comment #6 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Thx for testing, The Minh Luong. I have added your sign-off line to the patch: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=129221 Please have a look at how you can do this yourself using git or the sandboxes and let us know if we can help. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11750] Overdue report does not limit patron attributes
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11750 --- Comment #5 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Created attachment 129222 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=129222&action=e… Bug 11750: (QA follow-up) Remove unconditional warn -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11750] Overdue report does not limit patron attributes
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11750 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #123970|0 |1 is obsolete| | --- Comment #4 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Created attachment 129221 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=129221&action=e… Bug 11750: Hide patron's attributes on overdue list if needed If a patron's attributes is limited to some libraries, we must apply this limit on the overdue list view. Test plan: 1. Create the following patron attributes: A that is not searchable B is searchable and does not have library limitation C is searchable and is limited to another library than yours 2. On the right part of the overdue list view you must see B only Without this patch C is displayed as well. Signed-off-by: The Minh Luong <the-minh.luong(a)inlibro.com> Signed-off-by: Katrin Fischer <katrin.fischer.83(a)web.de> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11750] Overdue report does not limit patron attributes
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11750 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Patch complexity|--- |Small patch Status|Signed Off |Passed QA -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 28812] New: Authority tag editor only copy $a
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28812 Bug ID: 28812 Summary: Authority tag editor only copy $a 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: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 7882 Steps to reproduce: 1- Create a notice with a 700$a and 700$d 2- Click on Tag Editor 3- Only 700$a is copied Expect result: same as 19.11 all other subfields should be copied. There's now one more level in HTML tree and koha-tmpl/intranet-tmpl/prog/js/cataloging.js:openAuth() selects the wrong node. To check: still working in authorities/authorities.pl ==== diff --git a/koha-tmpl/intranet-tmpl/prog/js/cataloging.js b/koha-tmpl/intranet-tmpl/prog/js/cataloging.js index f126c86de2..35cbe499ae 100644 --- a/koha-tmpl/intranet-tmpl/prog/js/cataloging.js +++ b/koha-tmpl/intranet-tmpl/prog/js/cataloging.js @@ -43,8 +43,8 @@ function openAuth(tagsubfieldid,authtype,source) { var elementsubfcode=getSubfieldCode(element.name); var mainmainstring=element.value; var mainstring = new Array(); - var inputs = element.parentNode.parentNode.getElementsByTagName("input"); + var inputs = element.parentNode.parentNode.parentNode.getElementsByTagName("input"); for (var myindex =0; myindex<inputs.length;myindex++){ if (inputs[myindex].name && inputs[myindex].name.match(tagsubfield)){ var subfieldcode=getSubfieldCode(inputs[myindex].name); Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7882 [Bug 7882] Add ability to move and reorder fields and subfields in MARC editor -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27