September 2024 - Koha-bugs - lists.koha-community.org

[Bug 32957] New: Add option to CMS pages to make page private
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '26

13 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32957 Bug ID: 32957 Summary: Add option to CMS pages to make page private 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Currently CMS pages (Bug 15326) will be public or private, depending on the OpacPublic system preference. It would be cool to set specific pages as private so a login is forced. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 37421] New: Apply Protected Status to a Patron Category
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '26

13 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37421 Bug ID: 37421 Summary: Apply Protected Status to a Patron Category Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice if the option of the protected status for patrons to be optional by patron category. So when a library creates a new patron within this patron category, then the protected status is automatically applied. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 33013] New: Add age, interface and operator as additional report stats
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '26

13 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33013 Bug ID: 33013 Summary: Add age, interface and operator as additional report stats Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Reports Assignee: stalkernoid(a)gmail.com Reporter: stalkernoid(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 36492] New: memcached: Unclear where the pid file of memcached should be
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '26

12 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36492 Bug ID: 36492 Summary: memcached: Unclear where the pid file of memcached should be Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Sometimes at container restart the memcached process does not come up for some reason. (Running Debian11.) In the logs I found: Could not open the pid file /var/run/memcached/memcached.pid.tmp for writing: No such file or directory The *funny* thing is that the init.d script refers to /var/run/memcached.pid but the /etc/memcached.conf file contains: -P /var/run/memcached/memcached.pid In my case this folder does not exist in /var/run. Seems like a Debian problem, but directly affects daily Koha operation. Solving it temporarily by a sed on memcached.conf. Maybe this workaround may also help others. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 30209] New: Upgrade DBD::SQLite2 package to DBD::SQLite3
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '26

12 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30209 Bug ID: 30209 Summary: Upgrade DBD::SQLite2 package to DBD::SQLite3 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com the DBD::SQLite2 package has been removed in debian-testing, therefor we should upgrade to DBD::SQLite3 package only one script uses DBD::SQLite2 (misc/cronjobs/create_koc_db.pl), see BZ-4269 'create_koc_db.pl' can use both sqlite2 and sqlite3, so we can upgrade this package without a problem -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 36787] New: staticfines.pl missing use Koha::DateUtils::output_pref
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '26

10 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36787 Bug ID: 36787 Summary: staticfines.pl missing use Koha::DateUtils::output_pref Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz misc/cronjobs/staticfines.pl is calling output_pref() but it is missing from module import : use Koha::DateUtils qw( dt_from_string ); -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 37629] New: Link to news are broken
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '26

10 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37629 Bug ID: 37629 Summary: Link to news are broken Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When browsing news in the opac (opac-main.pl), links in the titles of news are broken. The id pasted in the link is the id from the additional_contents_localizations instead of the id from additional_contents. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 37684] New: Direct link to expired news are broken
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '26

10 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37684 Bug ID: 37684 Summary: Direct link to expired news are broken Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When using a direct link to a news (koha.url/cgi-bin/koha/opac-main.pl?news_id=XXX), the link is broken if the news is expired. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 28817] New: It should be possible to configure the reply_address for various notices
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '26

09 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28817 Bug ID: 28817 Summary: It should be possible to configure the reply_address for various notices 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently except for messages originating from the patron we do not set a reply_address when enqueuing letters, git grep reply_address If no reply address is specified when we are sending the messages we use the patron's library's address: 1325 sub _send_message_by_email { ... 1363 if ($patron) { 1364 $library = $patron->library; 1365 $branch_email = $library->from_email_address; 1366 $branch_replyto = $library->branchreplyto; 1367 $branch_returnpath = $library->branchreturnpath; 1368 } ... 1393 reply_to => $message->{'reply_address'} || $branch_replyto, This means that when an overdue is sent by the issuing library, replies go to the patron's branch -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 24499] New: sys pref EnhancedMessagingPreferences if set to Don't Allow does not even show within Patron Categories
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '26

09 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24499 Bug ID: 24499 Summary: sys pref EnhancedMessagingPreferences if set to Don't Allow does not even show within Patron Categories Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The system preference EnhancedMessagingPreferences, which allows or doesn't allow for staff to see patron's messaging preferences. If Don't Allow, staff cannot see a specific patron's message preferences. If set to Don't Allow, this also hides the overall Messaging Preferences for Patron Categories in Admin, It would be extremely helpful for the Messaging Preferences to still be seen in the Admin - Patron Categories and a place to view what patrons are defaulting to be set up. Understanding that general staff can't see a specific patron's messaging preferences, but admin can see what patron categories are set up for. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36