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

[Bug 28546] New: Framework default value special var for year in Manual
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28546 Bug ID: 28546 Summary: Framework default value special var for year in Manual Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org There is a mistake (or change) in framework default value special vars. In manual : There are several values that you can use here that will be replaced automatically when a new record is created: <<MM>> - the current month, 2 digits <<DD>> - the current day of month, 2 digits <<YEAR>> - the current year, 4 digits <<USER>> - the username of the currently logged in user For example: a default of "<<MM>>/<<DD>>/<<YEAR>>" (without quotes) will print the current date in the form of "01/21/2021" See https://gitlab.com/koha-community/koha-manual/-/blob/master/source/administ… But in Koha code in cataloguing/addbiblio.pl : $value =~ s/<<YYYY>>/$year/g; $value =~ s/<<YY>>/$shortyear/g; -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 28501] New: Document how to use the search configuration page
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28501 Bug ID: 28501 Summary: Document how to use the search configuration page Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Keywords: Manual Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org In the manual there is currently no information on how to use the search configuration page for Elasticsearch. I am especially thinking of: - How to add a field/subfield to an existing index - How to create a new index to use for search -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 21250] New: Auto-self-checkout not fully compatible with two-branch library setup
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21250 Bug ID: 21250 Summary: Auto-self-checkout not fully compatible with two-branch library setup Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: oliver.behnke(a)aei.mpg.de QA Contact: testopia(a)bugs.koha-community.org We use a two-branch library setup, both with auto-self-checkout enabled, so patrons log in with their cardnumber via the pre-defined staff user account (see below). The problem is that since the internal self-checkout user also has to be assigned to exactly one branch, that branch will be used as "current location" when a patron checks out a book. So, it's the self-service account's branch that's used instead of the patron's/borrower's branch. >From looking at the code it seems that C4::Circulation->AddIssue() is using "C4::Context->userenv->{branch}" where "$borrower->{'branch'}" should probably be used instead, since the current user's branch isn't relevant (even wrong) in the auto-self-checkout context. FYI, we use the following config (if relevant at all): - Koha 18.05.01-2 - AutoSelfCheckAllowed: Allow (AutoSelfCheckID/AutoSelfCheckPass) - CircControl: the library the item is from - HomeOrHoldingBranch: the library the item is from Thank you. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 25165] New: Explain all the cataloging plugins
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25165 Bug ID: 25165 Summary: Explain all the cataloging plugins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org The only one that I could find in the manual is the cn_browser plugin, the upload plugin and a vague mention of unimarc 1XX plugins. https://koha-community.org/manual/19.11/en/html/administration.html#edit-ex… (towards the end of the section) As of writing this (19.12.00.071) this is the list of plugins: - barcode - barcode_manual - callnumber-KU - callnumber - cn_browser - dateaccessioned - macles - marc21_field_005 - marc21_field_006 - marc21_field_007 - marc21_field_008 - marc21_field_008_authorities - marc21_field_008_classifications - marc21_field_245h - marc21_leader - marc21_leader_authorities - marc21_linking_section - marc21_orgcode - normarc_field_007 - normarc_field_008 - normarc_leader - stocknumber - stocknumberAV - stocknumberam123 - unimarc_field_010 - unimarc_field_100 - unimarc_field_100_authorities - unimarc_field_105 - unimarc_field_106 - unimarc_field_110 - unimarc_field_115a - unimarc_field_115b - unimarc_field_116 - unimarc_field_117 - unimarc_field_120 - unimarc_field_121a - unimarc_field_121b - unimarc_field_122 - unimarc_field_123a - unimarc_field_123d - unimarc_field_123e - unimarc_field_123f - unimarc_field_123g - unimarc_field_123i - unimarc_field_123j - unimarc_field_124 - unimarc_field_124a - unimarc_field_124b - unimarc_field_124c - unimarc_field_124d - unimarc_field_124e - unimarc_field_124f - unimarc_field_124g - unimarc_field_125 - unimarc_field_125a - unimarc_field_125b - unimarc_field_126 - unimarc_field_126a - unimarc_field_126b - unimarc_field_127 - unimarc_field_128a - unimarc_field_128b - unimarc_field_128c - unimarc_field_130 - unimarc_field_135a - unimarc_field_141 - unimarc_field_210c - unimarc_field_210c_bis - unimarc_field_225a - unimarc_field_225a_bis - unimarc_field_4XX - unimarc_field_686a - unimarc_field_700-4 - unimarc_leader - upload -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 28626] New: Scrolling through the docs doesn't highlight the section heading on the left
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28626 Bug ID: 28626 Summary: Scrolling through the docs doesn't highlight the section heading on the left Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org As you scroll through the documentation, it would be good if the bold highlighting on the navigation links tracked with the page location. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 18365] New: Appendix D. Notice & Slips Guides is out of date
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18365 Bug ID: 18365 Summary: Appendix D. Notice & Slips Guides is out of date Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: nengard(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I've just brought https://wiki.koha-community.org/wiki/Customising_Notices_and_Slips#Notice_S… up to date with master. The 'Can be branch specific' column is no longer needed; as far as I know, any notice may be branch specific at this point. The only gap on the wiki are the letter codes for notices generated via SendAlerts -- If someone can help me out there, that would be great. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 39173] New: maxRecordsForFacets doesn't seem to apply to Elasticsearch, only to Zebra, the docs should clarify that
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39173 Bug ID: 39173 Summary: maxRecordsForFacets doesn't seem to apply to Elasticsearch, only to Zebra, the docs should clarify that Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: schodkowy.omegi-0r(a)icloud.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de As in title, the "maxRecordsForFacets" pref has a scary warning about performance. But the setting seems to be wholly ignored by Elasticsearch (and it makes sense, you can test by setting the value to some ridiculously low number while showing facets and then see the counts are much higher, if searching for "*"). So the pref should mention it's only for Zebra. And then ALSO, as #2 thing, displayFacetCount, it has this mention: 1. "The relevance of these numbers highly depends on the value of the maxRecordsForFacets preference." 2. "Showing these numbers can potentially affect the performance of your searching, so test your system with different values for this preference to see what works best." Fix: 1. Only with Zebra. Clarify that with ES, the full proper real number of facet count will be displayed. 2. Only with Zebra. Explicitly clarify that on ES there's no performance hit to showing facet counts. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 26909] New: Add circulation_rules values to FAQ
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26909 Bug ID: 26909 Summary: Add circulation_rules values to FAQ Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The manual's FAQ includes a section that explains various coded values from the database: https://koha-community.org/manual/latest/en/html/faq.html#codes-stored-in-t… We should add the numeric codes from circulation_rules to this section. For example, the holdallowed rule is stored with these codes: 0: no holds 1: home library 2: any library 3: hold group -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 27018] New: Update library transfer limit info in manual
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27018 Bug ID: 27018 Summary: Update library transfer limit info in manual Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The manual entry on library transfer limits needs updating. https://koha-community.org/manual/latest/en/html/administration.html?highli… It needs to reflect the updated corrected wording from bug 24747. It needs to include the fact that limits can be set by item type. If bug 26633 gets in, that will need to be included, too. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 18962] New: Including valid system requirements in Koha manual
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18962 Bug ID: 18962 Summary: Including valid system requirements in Koha manual Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mik(a)adminkuhn.ch QA Contact: testopia(a)bugs.koha-community.org According to https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Introduction Ubuntu 14.04 is no longer supported - but the information given on the page https://koha-community.org/download-koha/ still says that Koha is "Actively supported for packages: Debian 7 (Wheezy), Debian 8 (Jessie), Ubuntu 14.04 (Trusty Tahr)". It would probably be a good idea to have correct and complete information about the system requirements of Koha at the very beginning of the manual for every Koha version as it is good practice for almost every other software. * the manual of every Koha version * the release notes of every Koha version (or a link to the respective manual) * https://koha-community.org/download-koha/ (or a link to the respective manual) The systems requirements can be changing with every new version, of course, thus it is not enough to say in the manual: "Full system recommendations can be found on the official Koha wiki along with the developer documentation: http://wiki.koha-community.org". I suggest the manual of every Koha version should include a section with the exact requirements for the respective Koha version, e. g. * supported Linux distributions * supported version of Apache HTTP Server * supported version of MySQL * supported version of Perl This would probably also be helpful for all the guys that are trying to install Koha on unsupported Linux distributions like CentOS, Redhat etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4