Screens not loading.
Hello All, first timer here and have worked extensively everyday on building my family lineage.
There are a few problems with some pages on the wider site that are failing to load.
-The Eurona feed has not loaded since I started working around my family tree in December 2021.
-When beginning to merge. The merge screen does not load at all and I believe this would be because of the maintenance update. Merging was working prior to the maintenance.
Any cheats to get this functioning again. I really love working with the site.
I have tried with all the latest Google Chrome, Microsoft Edge and Mozilla Firefox browsers and none have work.
Really want to merge some all over the place records.
Thanks
Miria
Best Answer
-
FYI
Welcome to the "Community.FamilySearch" Forum.
I am just another 'lowly' User/Patron ...
Just in passing ...
Firstly ...
I would not, be too concerned; nor, worry too much, about the "Eurona" feed ...
Connect on 'FamilySearch'.
Once you are connected you can view and share meaningful moments with family and friends.
We hope you enjoy this new feature.
[ Welcome! Try creating a post to share with family and friends on FamilySearch.
Let us know what you think using the FEEDBACK button. ]
The https://www.familysearch.org/eurona/feed/ is a on-going 'Work-in- Progress'.
That is STILL being "Developed"; and, "Tested" ...
Secondly ...
I have not been having any problems/issues with "Merging"/"Combining".
And, I principally use "Chrome"; but, then, also use "FireFox; and, if needs be, "Edge" ...
ie.
The "Browsers" of,
'Google' "Chrome"; and,
'Mozilla' "FireFox"; and,
'Microsoft' "Edge",
ALL with the "Operating System" of "Windows 10"
And, each with the LATEST version of each.
Now ...
That Said ...
IF, you have not already; THEN, ...
An "Oldie"; but, STILL, often, a "Goodie" ...
Sometimes it works; but, ten, again sometimes it may not ...
Try "Clearing", the "Cookies"; and, the "Cache", of your "Browsers".
[ And, even to the extent of "Clearing" your "Browsing History" ... ]
Another thing that can cause problems/issue is the likes of ADD or POP-UP "Blockers"
As such ...
Here are some "Knowledge Articles", in 'FamilySearch':
Pages won't open on FamilySearch
https://www.familysearch.org/en/help/helpcenter/article/pages-wont-open-on-familysearch
How do I keep pop-up blockers from causing issues?
How do I delete cookies from FamilySearch?
https://www.familysearch.org/en/help/helpcenter/article/how-do-i-delete-cookies-from-familysearch
How do I set my cookie preferences?
https://www.familysearch.org/en/help/helpcenter/article/how-do-i-set-my-cookie-preferences
How do I delete all of the cookies and temporary files stored by my internet browser?
just my thoughts.
Good Luck.
I hope. that this may help/assist, somewhat.
Brett
0
Answers
-
You are not alone in not being able to merge recently Miria. When I try to merge, whether on Chrome or Edge, the page comes up blank. I have cleared cache and have no ad blockers. The JavaScript console (ctrl-shift-j) shows a bunch of errors starting with the following. Note that "https://sdk.split.io/" appears to be an invalid web site.
adrum-latest.js:123
GET https://sdk.split.io/api/mySegments/cis.user....net::ERR_NAME_NOT_RESOLVED
(anonymous) @ adrum-latest.js:123
(anonymous) @ adrum-latest.js:30
(anonymous) @ instrument.js:170
Rr @ index.js:10
ai @ MySegments.js:27
e @ MySegments.js:84
u @ Partial.js:47
(anonymous) @ browser.js:55
(anonymous) @ index.js:257
y @ index.js:256
u @ browser.js:53
start @ browser.js:80
vi @ online.js:72
Ki @ index.js:58
Vi @ utils.js:9
t @ SplitFactory.js:89
ki @ react-dom.production.min.js:3174
Va @ react-dom.production.min.js:4307
xo @ react-dom.production.min.js:6700
vu @ react-dom.production.min.js:6150
hu @ react-dom.production.min.js:6139
ou @ react-dom.production.min.js:5880
(anonymous) @ react-dom.production.min.js:2851
t.unstable_runWithPriority @ scheduler.production.min.js:309
Bl @ react-dom.production.min.js:2816
Xl @ react-dom.production.min.js:2846
Yl @ react-dom.production.min.js:2836
nu @ react-dom.production.min.js:5678
ya @ react-dom.production.min.js:3970
(anonymous) @ FeatureFlagsProvider.js:249
c @ runtime.js:64
(anonymous) @ runtime.js:278
(anonymous) @ runtime.js:116
z @ FeatureFlagsProvider.js:74
o @ FeatureFlagsProvider.js:96
(anonymous) @ adrum-latest.js:30
Show 6 more frames
adrum-latest.js:123
GET https://sdk.split.io/api/mySegments/A_999 net::ERR_NAME_NOT_RESOLVED
(anonymous) @ adrum-latest.js:123
(anonymous) @ adrum-latest.js:30
(anonymous) @ instrument.js:170
Rr @ index.js:10
ai @ MySegments.js:27
e @ MySegments.js:84
u @ Partial.js:47
start @ browser.js:91
vi @ online.js:72
client @ index.js:114
Gi @ utils.js:21
k @ useClient.js:22
F @ FeatureFlagsProvider.js:306
Gi @ react-dom.production.min.js:3667
xo @ react-dom.production.min.js:6635
vu @ react-dom.production.min.js:6150
hu @ react-dom.production.min.js:6139
ou @ react-dom.production.min.js:5880
(anonymous) @ react-dom.production.min.js:2851
t.unstable_runWithPriority @ scheduler.production.min.js:309
Bl @ react-dom.production.min.js:2816
Xl @ react-dom.production.min.js:2846
Yl @ react-dom.production.min.js:2836
nu @ react-dom.production.min.js:5678
ya @ react-dom.production.min.js:3970
(anonymous) @ FeatureFlagsProvider.js:249
c @ runtime.js:64
(anonymous) @ runtime.js:278
(anonymous) @ runtime.js:116
z @ FeatureFlagsProvider.js:74
o @ FeatureFlagsProvider.js:96
(anonymous) @ adrum-latest.js:30
Show 2 more frames
adrum-latest.js:123
GET https://sdk.split.io/api/splitChanges?since=-1 net::ERR_NAME_NOT_RESOLVED
(anonymous) @ adrum-latest.js:123
(anonymous) @ adrum-latest.js:30
(anonymous) @ instrument.js:170
Rr @ index.js:10
Qa @ SplitChanges.js:28
(anonymous) @ SplitChanges.js:79
(anonymous) @ adrum-latest.js:30
adrum-latest.js:123
Uncaught (in promise) TypeError: Failed to fetch
at adrum-latest.js:123:79
at adrum-latest.js:30:486
at instrument.js:170:28
at Rr (index.js:10:18)
at ai (MySegments.js:27:27)
at e (MySegments.js:84:24)
at Object.u [as synchronizeMySegments] (Partial.js:47:12)
at browser.js:55:16
at index.js:257:12
at Array.forEach (<anonymous>)
at y (index.js:256:8)
at u (browser.js:53:5)
at Object.start (browser.js:80:13)
at vi (online.js:72:30)
at Ki (index.js:58:23)
at Vi (utils.js:9:22)
at new t (SplitFactory.js:89:19)
at ki (react-dom.production.min.js:3174:7)
at Va (react-dom.production.min.js:4307:103)
at xo (react-dom.production.min.js:6700:86)
at vu (react-dom.production.min.js:6150:11)
at hu (react-dom.production.min.js:6139:9)
at ou (react-dom.production.min.js:5880:9)
at react-dom.production.min.js:2851:17
at t.unstable_runWithPriority (scheduler.production.min.js:309:12)
at Bl (react-dom.production.min.js:2816:10)
at Xl (react-dom.production.min.js:2846:7)
at Yl (react-dom.production.min.js:2836:3)
at nu (react-dom.production.min.js:5678:92)
at ya (react-dom.production.min.js:3970:5)
at FeatureFlagsProvider.js:249:17
at c (runtime.js:64:17)
at Generator._invoke (runtime.js:278:22)
at Generator.next (runtime.js:116:21)
at z (FeatureFlagsProvider.js:74:20)
at o (FeatureFlagsProvider.js:96:9)
at adrum-latest.js:30:486
0 -
Errors have resolved themselves over the past week I have been working on it. I require a Moderator to close this thread.
Thank You and best of luck
0