Summary: | Wrong interface in action logs for some staff actions | ||
---|---|---|---|
Product: | Koha | Reporter: | Nick Clemens (kidclamp) <nick> |
Component: | Architecture, internals, and plumbing | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED WORKSFORME | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | dcook, jonathan.druart, pedro.amorim |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31908 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33879 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34478 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Nick Clemens (kidclamp)
2022-02-15 13:21:04 UTC
No idea how this is possible! Theory: - Related to bug 31042 - problem arises from api (or other?) calls where setenv is not explicitly set - plack worker retains most recent env that was set until something else overwrites it - when one of these scripts requests userenv, it gets the stale one from plack Checking production sites, I am not seeing this issue since August, so maybe something in 21.11.05 -> 21.11.10 fixed this Still valid in master To recreate: 1 - Sign in to staff client 2 - Checkout an item to a patron 3 - Stay on that page 4 - Hit the patrons API with a post request: http://localhost:8081/api/v1/patrons { "surname": "kidclamp", "library_id": "CPL", "category_id": "S" } 5 - Check the box next to the checkout and 'Renew selected' 6 - Check the action logs - interface=api I remember bumping into this in the past too although I can't remember exactly how... I'm pretty sure in my memories somewhere I know what causes this and how to fix it. Which is super helpful right now I know... (In reply to David Cook from comment #5) > I remember bumping into this in the past too although I can't remember > exactly how... > > I'm pretty sure in my memories somewhere I know what causes this and how to > fix it. > > Which is super helpful right now I know... Ah, it looks like it was bug 32140. I cannot recreate this, and haven't seen it in recent spot checks in production, so closing this one |