Looks like tech problems today. I am unable to put any new info on my ancestors' sites. Says Save failed.
Welcome to the "Community.FamilySearch" Forum. ]
I am just another 'lowly' User/Patron ...
Just in passing ...
'Yes' you are CORRECT ...
That Said ...
For ME is is Saturday, 12 February 2022 ( at 9am ); as, MY 'Time' Zone is UTC +11 Hours ...
[ ie. NOT, Friday, 11 February 2022 ... ]
There CURRENTLY seems to be a MAJOR Problem/Issue in the "System" (ie. "Family Tree", of 'FamilySearch').
I have been UNABLE to do a NUMBER of things (ie. Add "Sources"; and, "Create" individuals/persons; etc).
The "System" (ie. "Family Tree", of 'FamilySearch') is playing up considerably ...
Such may be a "Server" problem/issue; or, some other SIGNIFICANT cause ...
Just my thoughts.
@Nancy Thornton_3 You're not alone. Noticed same thing. Can't add, amend, attach, link. Only look. At first I thought it was just me 'cause I'm working remotely through a tethered phone, but thanks to you I now know It's more widespread. Looks like somebody left the lock on. Oh well, I suppose there's something else I could be doing. Maybe cat wrestling.
Related 'Comments' and 'Posts' ... SO FAR ...
[ 1 ]
'Category' = Family Tree
HOME > FAMILYSEARCH HELP > FAMILY TREE
Cannot standardize place name: "! Save failed. This data already exists."
[ 2 ]
There may be MORE ...
I hope this isn't a Friday problem so we have to wait until Monday before somebody can fix it. Otherwise I'll have to find something else to do for a whole weekend.
@LDS Search Test
This, is TOO much, of a Major SIGNIFICANT, Problem/Issue, that MUST be dealt with ... IMMEDIATELY ...
PLEASE; Please; please ...
How about ...
IMMEDIATELY, "Adding" a "Banner", to 'FamilySearch', regarding this Major SIGNIFICANT, Problem/Issue ...
That, would definitely SAVE, a lot of UNNECESSARY, Telephone Calls/Chats to 'FamilySearch' "Support"; &, posts, in this Forum.
The MAJOR Problem/Issue, in the "System" (ie. "Family Tree", of 'FamilySearch') ...
I getting addressed/fixed ...
SOME things, are NOW working, again ...
NOT All ...
Some things, are still, NOT working properly ... yet ...
It's working now
@LDS Search Test
Are these troubles also extending to the Search Records area? I sure hope what I'm (not) seeing isn't someone's idea of a 'new' or 'better' user experience. The way the hit list is being presented today is useless - only the name of the record shows up, no details.
This WAS, a MAJOR Problem/Issue, in the "System" (ie. "Family Tree", of 'FamilySearch') - "Outage".
I was UNABLE to do a NUMBER of things (ie. Add "Sources"; and, "Create" individuals/persons; etc).
This was NOT specific, to the "Search" ( Records ) ... this related to EVERYTHING ...
The ( WHOLE ) "System" (ie. "Family Tree", of 'FamilySearch') WAS playing up considerably ...
Such may have been a "Server" problem/issue; or, some other SIGNIFICANT cause ...
ps: I DO NOT want, to even go there, with regard to the NEW, "Search" ( Records ); and, the "Results" page/screen ... UGH ...
So there IS a NEW "Search Record" look for the Results??I now have to open each and every record to see the other associated names. Seeing the other names at a glance is the only way you can tell when you're looking at a correct record. This new design is a HUGE waste of time. If there's not a way around it, this will be enough to make me abandon FamilySearch where I've been filling out an enormous Source-proven tree and have already invested months of time. Extremely disapointing!
I also ran into a few problems during the day Saving but was lucky enough to be doing other things during the majority of it, apparently.
I agree that the new search results screen is ineffective and inefficient.
I have had on-going connection problems for weeks, perhaps even months. Every log-in has to be done twice (not an exaggeration). The first time gives an oops. I am getting tired of oops as it comes up on almost every search as well. Repeating usually works but that's not a solution. Site link ALWAYS fails when clicking a suggestion, resource or any other item in email received from familysearch.org
Trying to clear cookies as suggested leads to 502 error.
And in order to make the site completely user unfriendly, there is no "Tech Support" button that I can find.
"Contact Us" leads to the chat / discussion groups, not to Tech Help.
These technical issues added to the poorly designed new search screens have changed familysearch to family search frustration, but I can't seem to find a way to let the 'powers that be' know. If I click a thumbs down icon, there's no way to give specific feed back.
So having vented my frustration, is there any one out there with suggestions for how to overcome these problems?
Welcome to the "Community.FamilySearch" Forum.
And, NOT in reference to ANY real "Technical Support" ...
WHAT is the AGE of your Computer?
[ ie. Is you Computer, an OLDER Model? ]
WHAT "Operating System" are you using?
WHAT "Browser(s)" do you use?
ARE both, the "Operating System"; and, the "Browser(s)", that you use, "Up-to-Date" with the LATEST (or, al least, the PREVIOUS) "Versions" of each.
▬ your Computer, is an OLD Model; and/or,
▬ you are NOT using, a "Browser(s)", that is (are) "Supported", by 'FamilySearch; and/or,
▬ your "Operating System"; &, "Browser(s)", are, NOT "Up-to-Date"
.... [ ie. WITH, the LATEST (or, al least, the PREVIOUS) "Versions" of each ];
THEN, you WILL experience Problem/Issues, with 'FamilySearch'.
As an aside ...
That is even if, one "Clears", the "Cookies"; and, the "Cache", of one's "Browser".
'Food for thought'.
NOT really that "Technical", just the way it is ...
I know, that this certainly may not help/assist; but, I hope, that this may provide you with, some additional, insight; and, perspective; and, another avenue to pursue.
Feb. 17, 2022 -I'm not able to view notifications, etc, for weeks now. I'm a regular user, non-Church member. I'm using macOS High Sierra 10.13.6 and Safari 13.1.2 (13609.3.5.1.5), also having same issue with Mozilla Firefox 91.6.0 ESR (64-bit). Any ideas?
I enjoy the site overall and like the steady improvements and innovation. I appreciate all the efforts everyone puts in to improve the web site, as well as to help others study their family history.
I am using a macOS Big Sur 11.6.3, and Safari 15.3. As of today, the old search features with the additional info have been restored. I still get a message on "most" of the 1900 census lines as "record removed" or something like that. I never had any problems with discoveries or messages as far as I know, and I don't use notifications, wouldn't know where that is on the site.
@Daniel-V - From what you've said, I believe the issues you're having are due to your current operating system. Here is an article for you - Which internet browsers are compatible?
I hope this information helps.
re: "Oops, something went wrong. Please refresh the page." error message
Thanks. I had a custom hosts file, so I put the original hosts file back in place ... upon doing this everything is back to normal.
Do you know of an official supported operating system list or minimum system hardware requirements list for FamilySearch.org?
@Daniel-V - The only thing I've seen, besides a great deal of speculation, is this from the above article:
The website supports the current Windows and Mac operating system (OS) versions and one version back.
Thank you for letting me know the situation. It might be helpful if the organization formalized a "minimum system requirements" web page, even if they only put that one sentence in it?
Another suggestion, any way that message alerts from https://community.familysearch.org could be configured to show up when one logs into https://www.familysearch.org ?
@Daniel-V and @PiperTWilson Just to add a lower line to the minumum on MacOS at least.
The system works on El Capitan 10.11.6 (15G22010), with Chrome 85.0.4183.83 (Official Build) (64-bit)
Anyone having problems with certain genealogy sites with El Capitan will need to include to workaround for the outdated DST Root CA X3 certificate which involves getting the ISRG Root X1 if you haven't already, and then using the keychain to use this certificate instead of the outdated one.