Profile page not completing load of children and siblings
When a profile is displayed on the website, the load starts by showing grey pulsating placeholders for each of the profile's children and siblings. Then each placeholder is replaced with the relevant profile details. As of a few hours ago, the load is frequently not completed; the placeholders remain visible but the children and siblings are also displayed as they should be. The placeholders remain there until I switch to another profile tab, browser tab, window and back again, or open and close a pop-up dialog. I can reproduce this when I open the profile from a descendancy tree view or from the burials list from a Cemeteries Search. This occurs with Chrome and Firefox browsers and Windows 10. I have cleared the FS cookies; that made no difference.
This screenshot comes from opening the profile of Frances Franklin (LDRK-XW8) from her descendancy tree view:
This can be somewhat erratic. For example, Frances's husband is Charles Kinsley. Charles happens to have a duplicate parental relationship with his father and an apparent duplicate mother Leah. If I open his profile from Frances's dependency view, their children have persistent placeholders, but only Charles's relationship with the duplicate Leah has a persistent placeholder:
Answers
-
I need some help. Hopefully someone knows what to do.
From a person's Sources tab, click on ADD SOURCE then choose Add New Source, the pop up is too big. I can't see the date portion at the top nor anything below Vital Tags.
I use the latest chrome. My zoom is 100%. Everything is normal sized except the pop up. I tried the same steps in Firefox and the pop up is normal there.
I even cleared cache and cookies just in case, but it didn't help.
0 -
I think I I solved it myself. AI suggested I disable browser extensions one by one, I did that and found the culprit. That extension has never been an issue in the year or more that I've used it, but this morning it caused the website to not function correctly. I'll have to look for an alternative, but at least FS is working again.
Carry on,
Michael0 -
This discussion was created from comments split from: Add new source pop up was only the tip of the iceberg.0
-
@Michael J. Allen I reposted part of this discussion due to technical error…
Michael J. Allen✭✭3:14PMedited 3:18PM131.191.82.20My previous post was closed so I had to make a new one. I thought I had solved my own issue, but it turns out there's more to the story.I just discovered that other extensions make familysearch wonky. I will attach a screenshot to show the behavior.With all extensions disabled everything is fine. If I turn on Goldie May by itself or if I turn on Malwarebytes by itself I get what you see in the picture. All of my extensions played well with familysearch until this morning.0 -
My screenshot didn't carry over so I'll add it again.
0 -
Screenshot posted by Michael.
0 -
I've also noticed this issue today. When I left the profile and returned, the full list displayed.
And, I've also experienced the same problem in my following list. There, it does not clear. I reported that issue a few weeks ago.
2 -
Me, too. It didn't take too long for the page to fully load, but certainly needs engineers to take a look if the problem persists. It's not that the children are not displaying (apparently in the OP's example,too) but the impression being given there are 4-5 "missing" children:
1 -
@JulianBrown38 I was also able to replicate your issue and will forward this up the chain to see if we can get the issue resolved.
3 -
It appears to be that the number of "missing" children corresponds with the number of actual children in the family. So, just now, I noticed ten greyed-out items, which corresponded with the ten children listed below. Took rather longer for them to disappear on this occasion.
1 -
As an aside, the issue on my Following list has gotten worse - more changes are indicated only with the pulsing gray lines.
0 -
Okay, I was wrong about what caused what. This morning with a fresh head I now think extensions don't have anything to do with this.
This is what I am seeing.
When I refresh any person's details age, I see the issue in the image. When I look at a different tab and then back on that person's page the problem fixes itself as I watch. Refresh the page and the problem is back. Look at any other page and come back and I can see the problem go away.Its the same for opening a person's details page for the first time. I will see this issue with any person, everytime.
(turning on and off extensions required me to look at a different tab and then come back to the page to see results. I mistook turning them on or off as the cause, when really it was the act of looking elsewhere and then back again)
Sorry about the confusion.
0 -
There's another thread on this topic
0 -
Hmmmm. That's interesting. Pretty sure that is not intended. I'll make sure this is reported. Thanks for being our eyes! Sam 🙂
2 -
I've also noticed this bug the past couple days. The number of greyed-out pulsing children is equal to the actual number of children in the list.
0 -
I was having the same problem for the last day as well. It now seems to have been fixed.
0 -
@YColeman It seems that normal service has been resumed.
Thanks, eveyone.
0 -
Good things are working well again. I'm just wondering though about this. Whenever this type of thing occurs, I've always assumed it was not a bug or anything to do with the program but rather an internet connectivity issue or a server working on crashing.
As I've understood the process from various descriptions years ago, it takes dozens if not hundreds of requests to various servers and databases to construct the profile page each time it loads. For example, I don't think the initial load of the profile page contains anything more than pointers to the children and as the page is constructed a query has to go out for each child to retrieve the information than eventually displays. If that connection is having a problem or times out altogether, the child information is not going to appear.
With the massive winter storms in the eastern US last week and all the power outages, I'm not surprised some internet issues appeared.
2
