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

[Bug 36536] New: Make REST API's validateUserAndPassword update borrowers.lastseen
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36536 Bug ID: 36536 Summary: Make REST API's validateUserAndPassword update borrowers.lastseen 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: magnus(a)libriotech.no CC: tomascohen(a)gmail.com Since ILS-DI (which specifically means the AuthenticatePatron verb) is an option that can be selected for TrackLastPatronActivityTriggers, I would expect the validateUserAndPassword of the REST API to also contribute to updating borrowers.lastseen. Since there is no separate option for activalting it, I thought maybe the REST API is considered so much "core" to Koha that the logins are tracked when "Logging in" is activated as an option for TrackLastPatronActivityTriggers. But it looks like it is not. To reproduce in KTD: TrackLastPatronActivityTriggers = [Select all] RESTBasicAuth = Enable Check the lastseen value of the "koha" user in the database: select borrowernumber, lastseen from borrowers where borrowernumber = 51; The value should be NULL, or some past timestamp. Run this script: https://wiki.koha-community.org/wiki/REST_API:_Checking_username_and_passwo… Check the lastseen value of the "koha" user again. I would expect it to have been updated when the script ran, but it is not. Not sure if validateUserAndPassword should be considered as just another way of "Logging in", or if it should be a separate option for TrackLastPatronActivityTriggers, but the latter would give maximum flexibility. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 36278] New: Relabel "Gone no address"
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36278 Bug ID: 36278 Summary: Relabel "Gone no address" Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Many libraries find the "Gone no address" patron account flag awkwardly phrased/named. Perhaps "Address block", "Wrong address", "Address correction needed", or similar would more clearly indicate to library staff what this flag does. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[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 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

[Bug 22637] New: Add ability to full reindex elasticsearch index from UI
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '25

09 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22637 Bug ID: 22637 Summary: Add ability to full reindex elasticsearch index from UI Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com Target Milestone: --- Button in toolbar on elastic search admin page to initiate full reindex. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 23138] New: Elasticsearch - koha-elasticsearch rebuidl should support -d and other parameters
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '25

09 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23138 Bug ID: 23138 Summary: Elasticsearch - koha-elasticsearch rebuidl should support -d and other parameters Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Target Milestone: --- The helper script should accept all options the script takes directly -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 25453] New: Koha::SearchEngine::ES
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '25

09 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25453 Bug ID: 25453 Summary: Koha::SearchEngine::ES Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: frederic(a)tamil.fr New Koha::SearchEngine for Elasticsearch -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13