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

[Bug 21665] New: Advanced editor - Double clicking on value brings subfield code as well
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '25

19 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21665 Bug ID: 21665 Summary: Advanced editor - Double clicking on value brings subfield code as well Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: carnold(a)dgiinc.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 81165 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=81165&action=ed… Double Clicking field brings subcode When highlighting subfield value, don't bring the subcode as well. See document for details. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 22217] New: error "Connection to the memcached servers '__MEMCACHED_SERVERS__' failed" during install
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '25

19 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22217 Bug ID: 22217 Summary: error "Connection to the memcached servers '__MEMCACHED_SERVERS__' failed" during install Change sponsored?: --- Product: Koha Version: 18.11 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: giuseppe.ciaccio(a)unige.it QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- I'm trying to install Koha on a fresh Debian 9.7 32-bit, following the instructions at https://wiki.koha-community.org/wiki/Koha_on_Debian . I work as root so I have all privileges. One of the installation steps consists of editing file /etc/koha/koha-sites.conf . Inside koha-sites.con, I find the following row: USE_MEMCACHED="yes" 1.1) start memcached in the localhost (this action is not reported in the instructions but is needed): root@myhost:~# service memcached start 1.2) ensure that memcached is indeed active and listening at port 11211 root@myhost:~# ps ax PID TTY STAT TIME COMMAND ... 16908 ? S 0:00 /usr/sbin/apache2 -k start 16909 ? S 0:00 /usr/sbin/apache2 -k start 16910 ? S 0:00 /usr/sbin/apache2 -k start 16920 ? Ssl 0:00 /usr/bin/memcached -m 64 -p 11211 -u memcache -l 127. ... 1.3) proceed with install procedure, get worrying error messages root@myhost:~# koha-create --create-db mylibrary Koha instance is empty, no staff user created. [ ok ] Starting Koha indexing daemon for mylibrary:. root@myhost:~# koha-translate --install it-IT Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the unix socket permissions set properly? Is the host reachable? If you ignore this warning, you will face performance issues Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the unix socket permissions set properly? Is the host reachable? If you ignore this warning, you will face performance issues Use of uninitialized value $pref_name in concatenation (.) or string at /usr/share/koha/misc/translator/LangInstaller.pm line 197. Use of uninitialized value $pref_name in concatenation (.) or string at /usr/share/koha/misc/translator/LangInstaller.pm line 239. 1.4) at this point, try not to use memcached and repeat the koha-translate step, get same error as before root@myhost:~# vi /etc/koha/koha-sites.conf ...set USE_MEMCACHED="no" root@myhost:~# koha-translate --update it-IT Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the unix socket permissions set properly? Is the host reachable? If you ignore this warning, you will face performance issues Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the unix socket permissions set properly? Is the host reachable? If you ignore this warning, you will face performance issues Use of uninitialized value $pref_name in concatenation (.) or string at /usr/share/koha/misc/translator/LangInstaller.pm line 197. Use of uninitialized value $pref_name in concatenation (.) or string at /usr/share/koha/misc/translator/LangInstaller.pm line 239. So it seems that I) the language installer tries to connect to memcached, no matter the value of USE_MEMCACHED II) the language installer fails to connect to memcached even if the daemon is up and listening to the right port. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 16735] New: Replace existing library search groups functionality with the new hierarchical groups system
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '25

19 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16735 Bug ID: 16735 Summary: Replace existing library search groups functionality with the new hierarchical groups system Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We should replace the existing library search groups with the use of the new hierarchical groups system so that old system can be removed completely. General outline: 1) Add the option to each group for it to be a "search" group 2) Port over existing groups by creating a new group for each "categorycode" in the branchrelations table 3) Re-implement the group search using the new system, remove the old system -- You are receiving this mail because: You are watching all bug changes.

1 118

[Bug 29069] New: Accessibility: "Refine your search" link doesn't have sufficient contrast
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '25

19 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29069 Bug ID: 29069 Summary: Accessibility: "Refine your search" link doesn't have sufficient contrast Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The "refine your search" link on the OPAC search results page (opac-search.pl) is hard to read (grey text on a grey background) and doesn't meet accessibility guidelines. WCAG 2.1 1.4.3 Contrast (Minimum) Level AA: "The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: - Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; - Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. - Logotypes: Text that is part of a logo or brand name has no contrast requirement." (https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#contrast-minimum) There are several free websites for checking the contrast ratio, e.g. https://webaim.org/resources/contrastchecker/ You can also use the built-in accessibility functions in Firefox and Chrome, as well as specialist accessibility browser extensions like WAVE (https://wave.webaim.org/) -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 29509] New: GET /patrons* routes permissions excessive
by bugzilla-daemon＠bugs.koha-community.org 18 Sep '25

18 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29509 Bug ID: 29509 Summary: GET /patrons* routes permissions excessive Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com The routes require full borrowers permissions, and that's not the case for Koha, generally. If required permissions were to be lowered, bug 29503 should be pushed first. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 71

[Bug 30031] New: Add lists to table settings
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '25

15 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30031 Bug ID: 30031 Summary: Add lists to table settings 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: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The contents table of List columns in the staff client are not configurable via table settings and should be. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 51

[Bug 21371] New: Ability to add the processing fee to Notices
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '25

15 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21371 Bug ID: 21371 Summary: Ability to add the processing fee to Notices Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org With the addition of Processing Fees that can be assigned to specific item types, it would be great to be able to add this processing fee to a notice (such as the 3rd overdue notice). However, the processing fee lives in the ItemTypes table, which isn't brought into the Notices. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20555] New: usage() function in cleanup_database.pl needs refactoring
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '25

10 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20555 Bug ID: 20555 Summary: usage() function in cleanup_database.pl needs refactoring Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Developer documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org 1) '-m --mail DAYS' is misleading -- this cleans up the message queue, which covers a lot more than mail. 2) usage() should be implemented using pod2usage -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 23756] New: Appendix for workflows
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '25

08 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23756 Bug ID: 23756 Summary: Appendix for workflows Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Wondering if the documentation should include workflow examples for different tasks. I know how different each library can be with their workflows, but workflows seem to be a common topic, and there are multiple ways to approach different tasks. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 28814] New: Messaging preference for renewals
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '25

08 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28814 Bug ID: 28814 Summary: Messaging preference for renewals Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 In bug 18532 we add a messaging preference for the auto_renew notice. It would be good to do the same for the regular renewal notice. Right now, patrons get a renewal notice if the RenewalSendNotice syspref is on and the patron is signed up for CHECKOUT notices, with RENEWAL just following the CHECKOUT preference. That assumption -- that if one wants a CHECKOUT notice one must also want a RENEWAL notice -- is both spurious and largely undocumented. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5