Bug 34147 - Patron Search Displays "Processing" when Category Has Library Limitations that Exclude the Logged In Branch Name
Summary: Patron Search Displays "Processing" when Category Has Library Limitations tha...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: 22.05
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-28 16:00 UTC by John Yorio
Modified: 2023-07-14 17:59 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Yorio 2023-06-28 16:00:16 UTC
I'll start by saying that I don't know if this relates to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24132 or not.

To replicate, you'll need more than one library in Administration | Libraries.

Setup a patron category with a Library Limitation, so that one library is excluded (by not selecting it).

Create a patron with a common surname in your borrowers table and assign to that category.

While the logged in branch is set to one of the libraries that are not excluded for that category you created above, search for patrons with the surname of your test patron.

You should get results as expected.

Change the logged in branch name to the excluded library. Conduct the same search. A processing message appears and just spins.

I'm not sure whether the desired result should be to exclude the patron in question from the search results or whether it should display but with some restriction on the Patron Category.
Comment 1 Jonathan Druart 2023-07-05 10:50:20 UTC
Still valid in master? I don't recreate.

If you do can you provide what you have in the console and eventually the Koha log if you got a 500?
Comment 2 Jonathan Druart 2023-07-05 10:51:32 UTC
Is this a duplicate of bug 34145?