Searches not working for me
Answers
-
I've been trying to acess SEARCH RECORDS for 2 weeks...Nothing comes up.
Blank screen to left . Entry boxes show the names I'm looking up.
0 -
When I've searched for the past few days, the results flicker or flash up one name, and then back down synchronized with the scrolling arrow appearing and disappearing. Haven't had that before with the many years I've been here. Am I doing something (new) wrong??
0 -
The page with the results come up, but no actual results appear.
0 -
Do you mean you have a blank screen where the search results should be? Then take a look at this thread and see if any of the suggestions help. https://community.familysearch.org/en/discussion/145559/blank-screen#latest
1 -
Yes, but it's isn't images I'm not seeing, it's the list of search results that don't appear. I've tried both the firefox and chrome browsers. They were working fine until a couple of hours ago.
0 -
That's the same some others are seeing. Try the troubleshooting suggestions in that thread - starting with clearing your FS cache/cookies.
0 -
Still having the results in searches "jump" up one line, then back down one line. Very hard to read. Results are there, but jumping.
Thanks.
0 -
Right now, for every search I try to make, I get the "Something Went Wrong" page back. Is anyone else getting this?
0 -
Me, for the past couple of hours. No doubt they will fix it , hopefully soon!
0 -
I've seen it a few times, but a refresh/reload clears it.
0 -
This morning when I want to search record on the surname "Scheepers" I can not find any results. I am working on the family tree of the Scheepers Surname for the last 2 years in South Africa. If I search other surnames there are results. What happened????
0 -
I am getting "no results found" when searching this morning, even when I search for records already attached to a person.
For example Herbert Forster G234-38K. The 1891, 1901 and 1911 UK census records are attached to him. I can access for example the 1911 census record using the URL: https://www.familysearch.org/tree/sources/viewedit/QCTS-4G7?context
But searching for Herbert Forster using the "Residence" field, dates 1891 to 1911, gives no results.
Cache cleared, cookies (I had 94) deleted. Using a Windows 10 PC, Firefox browser (up to date).
Update: Searching for the name Forster in England with no other search field filled, almost every single result of a total of 2,213 is from Surrey, with 2 or 3 from Hampshire, Staffordshire and Middlesex, nothing from Lancashire?
Something seems to be amiss today.
0 -
Hi.
Herbert Forster G234-38K https://www.familysearch.org/tree/person/details/G234-38K has two UK census records attached in his exact name, 1901 https://familysearch.org/ark:/61903/1:1:X9KV-6YR and 1911 https://familysearch.org/ark:/61903/1:1:XWTM-H9P in Lancashire.
Please bear in mind he has 9 siblings all born in Lancashire, and his father has 7 siblings all born in Lancashire, all of whose multiple residence, BMD etc. records should appear in a search for the name Forster in Lancashire.
Searching the exact surname Forster in England with no other fields populated https://www.familysearch.org/search/record/results?count=20&q.recordCountry=England&q.surname=forster&q.surname.exact=on gives no results in Lancashire. There are 1,329 Surrey Parish Register records, 167 Rutland Parish records and 3 Middlesex Parish Records, and apparently no Birth, Marriage or Death index records. This cannot be correct.
Using the Residence Filter, it says there are 2 records in Lancashire, but when you click the Lancashire Filter they are actually in Rutland.
I have been having this problem for about two weeks now.
Clearly there is a major problem with the search function in this instance.
Help would be very much appreciated.
It is a little disappointing that there is no clear way to report problems like this, but I understand Familysearch have finite resources.
Regards,
Martin Coogan.
P.S. Similar problems (no BMD, mainly Surrey Parish Register records) with the surnames Foster, Fortnam and Fotheringham, but not with Finch or Fort? Weird.
0 -
At least part of the issue you are encountering may have been caused by the placename standardization algorithm. Searching by place has been rendered nearly impossible due to the algorithm
0 -
Weird: it's like the search algorithm has decided to be blind to the name "Forster". Searching for "Herbert Forster" or "Louisa Forster", marked exact, yields a grand total of four results each, all in Surrey -- but if I put in "Mary Standish" instead (still marked exact), I get the expected thousands of results, and if I filter that to the 1911 census, then there's the result with Louisa (and Herbert, though he's not in the search results page's summary).
I wonder if whatever gremlin was infecting the Hungary Civil Registration film back in February (https://community.familysearch.org/en/discussion/139244/search-records-cant-find-a-particular-index-entry#latest) has now decided to move to Lancashire instead? Whatever is going on, it seems to be a particularly infuriating game of whack-a-mole: one is fixed, three others show up. (The February one works for me now, but people keep reporting other similar situations where the entry is in the index -- they've found it by other means -- but Search refuses to cough it up.)
1 -
Thanks for responding Áine.
Hopefully someone at Familysearch will see the post and be able to identify what exactly has gone wrong here.
I agree about the placename standardization. If the records were actually 100% accurate, and standardized themselves to start with, it would be fine.
0 -
Thanks Julia.
Weird is indeed the word.
It's encouraging that a similar international gremlin was identified and fixed. I have hope!
0 -
@MartinCoogan Thank you for reporting the fact that record search is not showing records we know are there. This is a problem we are seeing recently and have reported to the folks who are looking into it to try to discover what is going on. I will add your search quandary to the report.
1 -
@N Tychonievich
Thank you, I will wait to hear further.
0 -
Mod note - several discussion about no search results have been merged here so that when a solution is found, we can update everyone at once.
0