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

[Bug 24868] New: When CircControl or ReservesControlBranch are enforced based on item location limits are enforced per library
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '25

19 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24868 Bug ID: 24868 Summary: When CircControl or ReservesControlBranch are enforced based on item location limits are enforced per library Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Here's the situation: - Library has Branch A and Branch B - Library has ReservesControlBranch set to enforce based on item home library - Library has circ rule for all branches / all patrons / itype DVD that has max of 1 hold allowed - Patron is allowed to place 1 hold on a DVD from Branch A AND 1 hold on a DVD from Branch B This same logic applies to other parts of the circ and fine rules that are enforcing counts - holds per day, current checkouts allowed, total current checkouts allowed, maximum holds allowed, etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[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 35669] New: Update check in message for a specific authorized value in the LOST authorized values
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '25

19 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35669 Bug ID: 35669 Summary: Update check in message for a specific authorized value in the LOST authorized values Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. Set an item to a Lost status of "Lost". When you check in that item you will get a message that says "Item was lost, now found." 2. Set an item to a Lost status of "Missing". When you check in that item you will get the same message that says "Item was lost, now found." Some libraries would like this message to reflect the correct authorised value that was previously set. So if they have a lost value of "In repair", the check in message would say "Item was In repair, now found." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 42

[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 37214] New: We should migrate to Koha::Patron->queue_notice wherever possible
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '25

19 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37214 Bug ID: 37214 Summary: We should migrate to Koha::Patron->queue_notice wherever possible Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The 'queue_notice' method introduced to Koha::Patron in bug 15986 introduces a wrapper around GetPreparedLetter and EnqueueLetter that will appropriately pick the message transport type and for the patron based on their own preference and personal data provided. We should try to use this method consistently throughout Koha rather than manually setting these in different area's of the codebase. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 37050] New: Add select2 to SQL report multi select
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '25

19 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37050 Bug ID: 37050 Summary: Add select2 to SQL report multi select Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: blawlor(a)clamsnet.org QA Contact: testopia(a)bugs.koha-community.org Bug 36545 adds select2 to improve the user experience when making multiple selections in item search. Bug 35746 adds the ability to reports to make multiple selections for SQL parameters. It would be nice for consistency and ux for the report multiselect to use select2. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 62

[Bug 37230] New: Add ability to define arbitrary statuses for items in Z3950
by bugzilla-daemon＠bugs.koha-community.org 18 Sep '25

18 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37230 Bug ID: 37230 Summary: Add ability to define arbitrary statuses for items in Z3950 Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Bug 36996 adds the ability to define a not-available status for items in Z3950 based on several criteria It would be nice to extend the use of YAML here to allow for defining several different statuses for different criteria -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 36996] New: Add a system preference to determine Z3950 availability
by bugzilla-daemon＠bugs.koha-community.org 18 Sep '25

18 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36996 Bug ID: 36996 Summary: Add a system preference to determine Z3950 availability Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some libraries would like to use additional item fields for determining if an item is available when showing z3950 results. This bug is to add a new system preference to determine availability (yes|no) via a YAML system preference - similar to OPacHiddenItems -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29