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

[Bug 25710] New: On ElasticSearch only system zebraqueue table is never purged
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '22

15 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25710 Bug ID: 25710 Summary: On ElasticSearch only system zebraqueue table is never purged Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 21820, 16248 Even if there's no zebra server zebraqueue table is populated (with done == 0). misc/cronjobs/cleanup_database.pl is only deleting zebraqueue table with done == 1 But without a zebra indexer daemon nothing is setting zebraqueue.done to 1. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16248 [Bug 16248] ModZebra doesn't update zebraqueue if ES is enabled https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21820 [Bug 21820] Zebraqueue should not be added to -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19642] New: If autoMemberNum is enabled, we should just ignore cardnumber entry in BorrowerMandatoryField
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '22

10 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19642 Bug ID: 19642 Summary: If autoMemberNum is enabled, we should just ignore cardnumber entry in BorrowerMandatoryField 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 19225 proposes a warning for users that the config is wrong. I propose instead, we should just ignore that field if automembernum is enabled (since it autocalculates and becomes mandatory -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 27009] New: Use 301 to redirect from tracklinks.pl
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '22

10 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27009 Bug ID: 27009 Summary: Use 301 to redirect from tracklinks.pl 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org In opac/tracklinks.pl we use a simple redirect to send the user on to the actual URL, after tracking: print $cgi->redirect($uri); This sends a "302 Moved Temporarily" to the browser as a default. One of our clients had some SEO work done on their websites, and one of the recommendations was to use "301 Moved Permanently" instead. This makes some sense, the URLs we redirect to do not change very often, I guess. According to https://metacpan.org/pod/CGI#Generating-a-redirection-header, the solution is to change the call to redirect() thusly: print $q->redirect( -uri => $uri, -status => '301 Moved Permanently' ); Patch coming. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 26650] New: Add Koha::Object->reset_messages
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '22

09 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26650 Bug ID: 26650 Summary: Add Koha::Object->reset_messages 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org This method was originally introduced as part of bug 26555. But it was not clear if it was required, or even if some more complex mechanism for marking 'seen' messages is required. I'm leaving this specific patch here for discussing it once someone finds a real need for it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 26651] New: Add Koha::Object->reset_messages
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '22

09 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26651 Bug ID: 26651 Summary: Add Koha::Object->reset_messages 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org This method was originally introduced as part of bug 26555. But it was not clear if it was required, or even if some more complex mechanism for marking 'seen' messages is required. I'm leaving this specific patch here for discussing it once someone finds a real need for it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 20336] New: Add a generic way for Koha::Object(s) to call logaction as required
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '22

09 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20336 Bug ID: 20336 Summary: Add a generic way for Koha::Object(s) to call logaction as required 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: tomascohen(a)gmail.com 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 2

[Bug 23091] New: Restore Forgiven Overdue Fines When Lost Item Returned
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '22

09 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23091 Bug ID: 23091 Summary: Restore Forgiven Overdue Fines When Lost Item Returned Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Bug 22877 is closing a loophole that several libraries have been happily using to achieve their desired fine behavior. These libraries want this behavior: - item accrues overdue fine up to maximum - when item is lost, overdue fine is forgiven and lost fee is applied - when item is returned, lost fee is forgiven and overdue fine is restored So, while many libraries will see bug 22877 as a fix, for some libraries it will be a very big disruption. My understanding of bug 22877 is that we're changing the fine calculation at checkin to not do anything with fines if the item is lost. Maybe we need to instead say don't add fines if the item is lost and the there is an existing fine for that issue where amountoutstanding!=0? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 225

[Bug 28247] New: Add a MARC preview column to to Authority search results table
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '22

09 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28247 Bug ID: 28247 Summary: Add a MARC preview column to to Authority search results table Change sponsored?: --- Product: Koha Version: master 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: timothy_alexis.vass(a)ub.lu.se QA Contact: testopia(a)bugs.koha-community.org We added this and want to make it available for others too. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 23347] New: Columns settings for items in OPAC should be according to the framework
by bugzilla-daemon＠bugs.koha-community.org 07 Mar '22

07 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23347 Bug ID: 23347 Summary: Columns settings for items in OPAC should be according to the framework Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Hi, It would be nice to be able to choose which fields of the item would be displayed in the OPAC in the items table, in connection with columns settings holdingst. Regards Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 29432] New: Item type deletion should test frameworks
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '22

04 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29432 Bug ID: 29432 Summary: Item type deletion should test frameworks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Actually the test to allow deleting an item type is : sub can_be_deleted { my ($self) = @_; my $nb_items = Koha::Items->search( { itype => $self->itemtype } )->count; my $nb_biblioitems = Koha::Biblioitems->search( { itemtype => $self->itemtype } )->count; return $nb_items + $nb_biblioitems == 0 ? 1 : 0; } But using item types on biblioitems.itemtype is not mandatory (for items.itype I do not know), so we should test if this DB column is configured in frameworks to use item types. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3