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

[Bug 28456] New: Add option to use a WHERE statement in membership_expiry.pl cronjob
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '25

24 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28456 Bug ID: 28456 Summary: Add option to use a WHERE statement in membership_expiry.pl cronjob 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Some libraries have a large amount of accounts and want to be able to limit how many email reminders they send - adding a where statement will allow for flexibility -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 26062] New: Membership Expiry can not be limited by Patron Category
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '25

24 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26062 Bug ID: 26062 Summary: Membership Expiry can not be limited by Patron Category 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Currently, the membership expiry cron runs and can be limited by branchcode, to exclude specific branches. However, it can not limit by patron category. It would be extremely helpful for libraries to be able to utilize a different way of using this cron by allowing the limiting by patron category. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 28841] New: Canceling holds from Waiting Reserves should follow the same rules as for checking in items concerning transfers
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '25

21 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28841 Bug ID: 28841 Summary: Canceling holds from Waiting Reserves should follow the same rules as for checking in items concerning transfers 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: sophie.meynieux(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When a Hold is canceled from Waiting Reserves, it is automatically transfered to homebranch if it is different from holdingbranch, ignoring return policy defined in circulation rules. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 27339] New: Display opac notes and opac messages on check-in
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '25

21 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27339 Bug ID: 27339 Summary: Display opac notes and opac messages on check-in Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: didier.gautheron(a)biblibre.com Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, Circulation note (borrowers.borrowernotes) and item notes (items.itemnotes and items.itemnotes_nonpublic) are displayed during check-in. This patch adds Opac note (borrowers.opacnote) and Opac messages (messages table). Test plan: - Add an Opac note and one or several Opac messages to a patron. - Checkout and check-in an item for this patron. - Check that Opac note and Opac message(s) are not displayed on check-in. - Apply the patch. - Checkout and check-in an item for this patron. - Check that Opac note and Opac message(s) are displayed on check-in. -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 21412] New: Opac upload file access
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '25

20 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21412 Bug ID: 21412 Summary: Opac upload file access Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: scdogan(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 79410 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=79410&action=ed… step1 I want to restrict access to the files I upload in the Koha automation system. What steps can I use? Thank you. 1. 1. Opac Display - Disable ( This collection will be private) 2. https://www.youtube.com/watch?v=mbYgsodcPaU (How to attach a file to a MARC Record in Koha) 3. Cataloging step 4.Copy upload file link ( For Example : http://193.140.223.100/cgi-bin/koha/opac-retrieve-file.pl?id=eca42072bd9eb8… ) 5. Log out Koha 6. Paste link any browser than file is open. I want to system asked username and password -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 29855] New: Add a repeated subfield with a MARC modification template
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '25

20 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29855 Bug ID: 29855 Summary: Add a repeated subfield with a MARC modification template 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: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It seems it is not possible to add a repeated subfield with MARC Modification template with the current options. Ex : it should be possible to create a 099$tBOOK field, then create an other $t (ex: $tCD) in the same 099 field (not in a new 099), to obtain 099$BOOK$tCD -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 20185] New: Some scripts does not pass perl -wc
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '25

18 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20185 Bug ID: 20185 Summary: Some scripts does not pass perl -wc Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: In Discussion Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 16105] New: Cache::Memory is loaded even if memcache is used
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '25

18 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16105 Bug ID: 16105 Summary: Cache::Memory is loaded even if memcache is used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 11998, 16104 Cache::Memory is loaded and Koha::Cache::_initialize_memory is called even if a memcached cache has been correctly initialize, it does not make sense. It should only be initialize if needed. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11998 [Bug 11998] Syspref caching issues https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16104 [Bug 16104] Warnings "used only once: possible typo" should be removed -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 16104] New: Warnings "used only once: possible typo" should be removed
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '25

18 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16104 Bug ID: 16104 Summary: Warnings "used only once: possible typo" should be removed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Since bug 11998, the following warnings are raised: Name "Tie::Hash::FIELDS" used only once: possible typo at /usr/share/perl/5.22/fields.pm line 135. Name "Cache::RemovalStrategy::LRU::FIELDS" used only once: possible typo at /usr/share/perl/5.22/fields.pm line 135. Name "Cache::RemovalStrategy::FIELDS" used only once: possible typo at /usr/share/perl/5.22/fields.pm line 135. It comes from the Koha::Cache 103 if ( can_load( modules => { 'Cache::Memory' => undef } ) ) { -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 21955] New: Cache::Memory should not be used as L2 cache
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '25

18 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21955 Bug ID: 21955 Summary: Cache::Memory should not be used as L2 cache Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: critical Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org If Plack is running with several workers we must not use Cache::Memory as L2 cache. If a value is set from a worker, it will not be available from other workers as the Cache::Memory instance is not shared (of course!) Moreover we now have Koha::Cache::Memory::Lite that does the same job, so we should not expect performance regressions by removing it. -- You are receiving this mail because: You are watching all bug changes.

1 23