Grey and white pulsing image
Comments
-
The following discussion has been merged into this discussion with similar issues.
0 -
The following discussion refers to similar issues and has been combined into this post.
0 -
1
-
Sorry, we believe we have found the problem and are implementing the fix. When this is available I will post again. The fix should allow you to now access your CETs and it's Tree Details.
0 -
The fix should now be live in production. Please let me know you can now access your newly loaded CETs and use the features. Sorry for the inconvenience and the time it took to identify and fix the problem. Looking forward to hear how your experience is going if this fixes the issue.
1 -
I uploaded my GEDCOM two days ago (see this thread) and it took about 2 hours before the "File is Processing" message vanished and give me the tile for my tree. But clicking on that continued to give the pulsing grey screen. I checked yesterday and it was still there.
Today I checked, and I can now access my newly loaded CET.
Thanks for fixing this, Always Strange.
0 -
Mine has opened this morning @Always Strange. Thanks for the fix.
It does report " Some of the data in this GEDCOM file was not uploaded correctly." Have not yet had time to see what those errors may be.
0 -
@Áine Ní Donnghaile thank you for your feedback and for helping us test this new product prior to its final release.
1 -
Áine,
Here's a little background on the "Some of the data in the Gedcom file…" message:
While Gedcom is a standard, the various genealogy software packages often push the limits of the standard at times putting product specific data structures and templates into the file. Also, it is very common for files to have incomplete or bad data (ex. a residence event w/o a place). IT's a pretty wild & wooly standard at times.
The import system is pretty robust and can deal with most things that it encounters (the data parser has been refined for years over in Genealogies). Sometimes it will encounter, either something it doesn't understand, or that our system does not allow (ex. a residence event w/o a place). When this occurs we catalog an import error and present these to the user so that they will know all of the places where the new tree deviates from the Gedcom.1 -
Hi Robert - I'm familiar with how GEDCOM parses. I was just reporting that it was early morning, and I hadn't gotten that far yet.
I have looked now - but I found the process to get from the error message to the profile with the reported issue cumbersome. There's no direct path. One must leave the list of reported issues, search for the profile(s), and view/edit the profile(s). I work on a 3-screen system, so that's not a big issue, but I can see that people working on a single monitor, or, worse, on a small tablet/phone, would find the process very awkward.
0
