Existing person are removed from FamilySearch - please restore!
Christen Pedersen Gaarde / LBS7-XWJ
Family Search write:
Person Not Found
This person does not exist, has been removed, or is restricted in FamilySearch.
But this person does exist! Please correct error!
It is not removed. I searched by the ID and went directly to the person page. Christen Pedersen Gaarde (1831–1917) • Person • Family Tree • FamilySearch1
There is an infrequent, erratic glitch in the new Details page. See: https://community.familysearch.org/en/discussion/140526/error-when-click-on-a-persons-name#latest
It is annoying but resolves itself rather quickly.0
Julia Szent-Györgyi ✭✭✭✭✭
As Gail says, he's still there.
Most FamilySearch webpages are built of what I call "layers": there's a base layer that's just the navigational framework (the header and footer), which loads first; then there's a layer that depends on the type of page but is some version of "nothing to see here, move along", which loads next, but is normally quickly overridden by the actual content requested, once the system has checked that the user has permission to view that content. It's done this way so that connectivity glitches and other errors do not inadvertently reveal content to unauthorized users. If you see the error page, it means something has gone wrong with loading the content. Sometimes (pretty rarely, in my experience), the error is actually what the error page says, but more often, FS's server exceeded a time limit in offering the next batch of data, and your browser gave up on the page. Refreshing or reloading the page sometimes fixes it, unless your browser has also "helpfully" saved the incompletely-loaded page and keeps offering that instead of actually reloading (because browsers know better than us, donchaknow). If the latter has occurred, you may need to manually clear your FS-related cache (although just closing and restarting your browser can accomplish this, too, depending on your settings).1