Source Linker just "blew up" .... anyone else having this problem?
Yes, across all browsers, so it is not "my computer". I emailed a similar screenshot to nasupport@
Thank you for posting yours.
That looks interesting. Certainly explains a lot. For 3 days now I have not been able to even attempt to add a source. Search results appear, but when I click something I get an error. It happened yet again today. I am being patient as I assume it will ultimately be fixed.
So would we call this a source linker clinker? Doesn't matter what type of source it is either. So they are having source server issues.
The error in the code is probably displayed there somewhere. It kind of reminds me of the old stack overflow errors. Breadcrumbs were there if you knew what to look for.
Gail, this "issue" just began a few minutes ago here for me in Washington State. I had reported an issue with source servers for Germany a few days ago and it got resolved.
Yes. It isn't happening on all sources I try to link but but I am seeing it too.
Yes it does remind me of a "stack overflow"😎 thingy.
RobertLeighPritchett You still have been getting farther than I have. I cannot click a link in a search results without getting an error. I have been ONLY adding sources from external locations: Ancestry, various newspaper collections, Fold 3 and Find a Grave. Those will create sources in FamilySearch, but anything housed in FS won't work for me. 3 days now.
Just being facetious, but it is kind of ironic that FamilySearch support for North America would be "na" or "Not Applicable" on forms elsewhere.
This might lead to an unnecessary rabbit hole, but just throwing it out there
Findagrave source is working!
Marriage Source is working!
Thank you to whomever resolved this issue.
That problem happens to me occasionally and, every time, clearing my cache solves the problem. It happened just a few minutes ago, and I saved before and after screenshots to illustrate.
Áine Ní Donnghaile
Which computer platform are you using? (the attachments are either loading or not showing)
I'm running Windows 10, fully updated, and that example is from Firefox 101.0, 64-bit. I clear the cache, refresh the page, and source linker displays correctly, EVERY time.
The images finally appeared. Nice work with the labeling!
With this thread, the issue was happening to lots of folks around the world on different platforms all at the same time earlier and within an hour, the coders had resolved it after we had "proved" to that that it was in all browsers on all platforms. The original canned response from the FamilySearch support team was "clear your cache", but at that time the "cache fix" was not the solution.
Elsewhere on this forum I mentioned I have lived on both sides of the fence as a "client" and also as a tech support person for insurance software years ago, so I understand the pain. When software gets too bulky, code snippets that fix one part of a program may alter another part, causing unintended consequences and coding whack-a-mole ensues, until the mirky water clears up in the programming pool.
The other issue FamilySearch deals with are the constant attacks by those satan's minions who desire to shut it down. I salute the coding warriors who protect FamilySearch from such attacks. And a little divine intervention never hurts either. Prayer, faith and works go together in keeping FamilySearch vibrant, productive and efficient.
The labeling is a feature of IrFanView, a free photo editor.
For me - the clear cache has worked EVERY time, across weeks-months of encountering the issue.