Bug 17760 - patron search not working in firefox
Summary: patron search not working in firefox
Status: CLOSED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: 16.05
Hardware: All All
: P5 - low minor (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-12 11:57 UTC by Heinrich Hartl
Modified: 2017-12-07 22:16 UTC (History)
2 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 Heinrich Hartl 2016-12-12 11:57:21 UTC
After upgrading my test version from 3.22.2 to 16.5.5.1 I observed problems when searching patrons. These problems were not visible when using MS-IE11.
However normally I am using Firefox(50.0.2) and the following problems are observed:
Giving the patrons full cardnumber (barcode) : ok, everything is fine.
Giving a substring of username or cardnumber : no success (even the small pop-up "loading" doesn't show.
Choosing the start letter of the username: no success.
Comment 1 Heinrich Hartl 2016-12-13 13:32:19 UTC
Problem continues to exist after upgrading to koha stable (16.11.0).
Comment 2 Heinrich Hartl 2016-12-13 14:00:40 UTC
Problem doesn't exist when tested from another laptop (windows 10, also Firefox 50.0.2). This suggests the problem is a problem with the laptop and not with koha.
I will try to give more details as soon as available.
Comment 3 Heinrich Hartl 2016-12-13 14:33:37 UTC
clearing the cache (Firefox options Advanced: Cached Web Content"clear now" has solved the problem.
Comment 4 Heinrich Hartl 2016-12-13 17:04:22 UTC
Apparently wrong content was cached by Firefox. This resulted in apparent function failure. Conditions for caching such wrong content are unknown. I can not reproduce the incorrect behaviour. Just in case some one else runs into a similar problem: clearing the cache may solve your problem.