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

[Bug 39883] New: NEW_SUGGESTION email notices end up in the patrons notice tab (members/notices.pl) when they should not
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39883 Bug ID: 39883 Summary: NEW_SUGGESTION email notices end up in the patrons notice tab (members/notices.pl) when they should not Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Turn on EmailPurchaseSuggestions and add an email address to EmailAddressForSuggestions. 2. Create a new suggestion and set the " Created by:" field to a patron with an email address 3. Check the message queue ( select * from message_queue where letter_code = "NEW_SUGGESTION" ) 4. There is a NEW_SUGGESTION queued, the to_address should be the email you entered in EmailAddressForSuggestions. 5. The borrowernumber is the borrower who made the suggestion. This shouldn't end up in the notice tab for the borrower since these notices are for staff. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 39824] New: Add a direct link to default framework in MARC bibliographic frameworks page
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39824 Bug ID: 39824 Summary: Add a direct link to default framework in MARC bibliographic frameworks page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In Administration > MARC bibliographic frameworks, add a direct link to default framework can be very useful. Currently one needs to move to the actions button, click to open it, and click on "MARC Structure". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 38997] New: Remove reference to "members" in SendAlerts
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38997 Bug ID: 38997 Summary: Remove reference to "members" in SendAlerts Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Developer documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org In SendAlerts documentation, it says "- notify patrons when their account is created (members)" but that documentation is out of date. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 40126] New: Typo in "# of % selected"?
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40126 Bug ID: 40126 Summary: Typo in "# of % selected"? Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: anneli.osterman(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Is there a typo in "# of % selected"? I found this while translating string https://translate.koha-community.org/translate/koha/25-05/messages-js/fi/?c… Should it be "# of %s selected"? This is used in koha-tmpl/intranet-tmpl/prog/js/categories.js:127 and koha-tmpl/intranet-tmpl/prog/js/ill-list-table.js:653 -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 36453] New: BlockExpiredPatronOpacActions should allow multiple actions options
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36453 Bug ID: 36453 Summary: BlockExpiredPatronOpacActions should allow multiple actions options 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: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 34597 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34597 [Bug 34597] Expired patrons can still place ILL requests through OPAC -- You are receiving this mail because: You are watching all bug changes.

1 79

[Bug 32604] New: Patron categories upper age limit not respected when creating a patron
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32604 Bug ID: 32604 Summary: Patron categories upper age limit not respected when creating a patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Koha treats patron categories upper age limit inconsistently. E.g. if child patron category's upper age limit is 18, one is still able to add child patron who is 18 years old. However, when cronjob update_patrons_category.pl is run, patrons over and exactly aged 18 are considered overaged and their categorycode is updated. We should either fix patron creation or cronjob to avoid confusion. To test: 1. Add upper age limit as 18 for child patron category. 2. Create a child patron whose age is 18. 3. Save. => Patron is saved successfully. 4. Run cronjob update_patrons_category.pl with verbose option. perl update_patrons_category.pl --too_old --from CHILD --to ADULT -v => Note that patron is reported as updated (or would have updated) as an adult patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 29921] New: Allow to index in Elasticsearch all records modified since a given date
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '25

09 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29921 Bug ID: 29921 Summary: Allow to index in Elasticsearch all records modified since a given date Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 17921] New: Shelf Browser does not take OpacSuppression or OpacHiddenItems into consideration
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '25

09 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17921 Bug ID: 17921 Summary: Shelf Browser does not take OpacSuppression or OpacHiddenItems into consideration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Items that shouldn't be displayed in the OPAC are displayed in the shelf browser The links work as expected (redirect to opac-blocked or 404) but we should not display them in the first place -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 39933] New: acqui/basket.tt does not deal with col visibility correctly
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '25

09 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39933 Bug ID: 39933 Summary: acqui/basket.tt does not deal with col visibility correctly Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org See the FIXME: > > [% IF !(Koha.Preference('EDIFACT') && ediaccount) %] > > // FIXME This cannot work correctly without > > bKohaColumnsUseNames > > table_settings['columns'].splice(18, 1); > > [% END %] > -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 28195] New: When on-shelf holds are not allowed, it's impossible to force item-level holds in OPAC
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '25

09 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28195 Bug ID: 28195 Summary: When on-shelf holds are not allowed, it's impossible to force item-level holds in OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This is the setting: a library doesn't allow on-shelf holds. But we want OPAC users to be able to place holds on checked out serial issues. Serials are catalogued as one record for the title with each issue being an item on this record. The circulation rule for serials says - holds allowed: 5 - holds per record: 5 - on-shelf holds: if all unavailable (aka, no on-shelf holds allowed) - OPAC item level hold: force (aka, OPAC users must choose a specific item to reserve) item-level_itypes syspref is set to specific item So for example, we have this record (there is no serial subscription attached to this record, just regular items) National Geographic - June 2020: available - July 2020: available - August 2020: checked out - September 2020: checked out - October 2020: available - November 2020: checked out - December 2020: available Ideally, in this context, an OPAC user should be able to place a hold on the august, september and/or november issues. I also tried changing on-shelf holds to "if any unavailable", but it doesn't allow my OPAC user to place a hold either. To test: 1) Make sure item-level_itypes is set to specific item. 2) Create a circulation rule for serials (Patron/Continuing resources for example) with - holds allowed = 5 - holds per record = 5 - on-shelf holds allowed = if all unavailable - opac item level hold = force 3) Create a record and add several serial-type items (Continuing resources for example) 4) Check out some (but not all) items to patrons 5) In the OPAC, log in with a patron of the right category (Patron for example) 6) Try to place a hold on a checked out serial item -> it says "There are no items that can be placed on hold." Is this a bug or am I misunderstanding something? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2