Bug: Document Type and other options no longer appearing on search page
The Search interface usually includes more options below "Add a Family Member" such as Document Type, Image Group, Location, and Affiliate ID. None of those appear currently.
Example
https://www.familysearch.org/search/record/results?count=100&q.anyPlace=Pulaski%2C%20Virginia%2C%20United%20States&q.surname=davis
Answers
-
The issue seems to be intermittent. I was just experimenting - sometimes I get a record type and the ability to filter to the Principal. Other times, I don't. All this within a few minutes.
Windows 10, tested on both Chrome and Firefox. All fully updated.
1 -
Áine, Thank you for testing this. I'm still not seeing those search options on Firefox and Chromium on Linux.
1 -
For me - a Search from Record Search seems to populate with type while a search for a record from within the Tree does not always.
If it doesn't clear @Anne986 be sure to flag your post so that a Mod will see it and escalate if needed.1 -
Áine, Thank you for continuing to test this. I am noticing, too, that starting from Record Search,
and selecting "More Options" does display Location, Type, etc. However the results page does not include those options in the right-hand search results.By flagging my post, do you mean, clicking on the flag icon of the first post of this thread? When I do that the icon changes to "Report."
1 -
Yes, if you Flag your own post, using the Flag button, that will call the post to a moderator's attention and allow him/her to escalate the report to the appropriate engineering team.
0 -
Áine, Thank you for suggesting flagging and explaining how. I have flagged it.
1 -
Mine is quite flakey. I just entered Search / Records and got a decent set of choices - including selection by record Type, Principal and "Film" number (is that one new?) (Windows 10, Firefox)
When I submitted that query and looked at the list of results, the righthand side of the screen, that supposedly allows further selection, doesn't have the selection by record Location, record Type, Principal and "Film" number. Indeed, it actually lost data that was entered on the first screen - only the name got through. There is no way, therefore, to then select (say) only-Principals, or tune the record Location, other than by going back to the very first screen. And, of course, if you do that, everything has gone…
So - if you don't get it right the first time, it's like being told to do it again from the start and get it right this time.
1 -
I started noticing some issues late yesterday, but a refresh or browser switch fixed it then. Today it seems to be worse, and especially bad if searching for a record from a profile in the tree.
DGS or Film is not a new field. It's a great filter that I use often.
1 -
I confirm what @Anne986 describes and in my case it's solid and consistent. All searches return zero. Methinks it's maybe a hasty untested patch on a friday that won't get fixed until monday.
A possible workaround is to always start from : https://www.familysearch.org/search/
After the results are obtained, any attempt to use the right hand side column to change the parameters yields no results. To change the parameters, you have to go back to the URL above and enter everything again from there.
2 -
-
And also functioning in Chrome.
0 -
I stand corrected ! It did get fixed before Monday.
0 -
Yes - mine seems OK on a swift test of what I previously complained about.
As an aside, my impression is that the fact that it appears to be fixed doesn't necessarily mean that there was manual intervention. My impression is that things can just get better by themselves - perhaps a software roll-out doesn't reach all servers in perfect synchronicity??? Or some such??? I don't know - I never had to contend with those issues when I got called out at 2 a.m.
1 -
Agreed, Adrian. You'll notice I only said better today, not fixed. Sometimes it's a simple matter of some element, whether mechanical, digital, or electronic, malfunctioning for a short time.
0 -
@Ashlee C. It has been working well. Thank you to all those who reported and fixed the issue!
0