FamilySearch. Update/Release of Sun22/Mon23 March 2020. Problem/Issue. Search Records. Partner Acces
LegacyUser
✭✭✭✭
Brett said: FamilySearch
Update/Release of Sunday 22 / Monday 23 March 2020
Problem/Issue
Search Records
Partner Access
MyHeritage.com
Attempt: Result = HTML Error
Using (latest versions of) 'Google' "Chrome" with "Windows 10"
Using (latest versions of) 'Mozilla' "FireFox" with "Windows 10"
Submitted for your information; attention; and, consideration.
Brett
.
Update/Release of Sunday 22 / Monday 23 March 2020
Problem/Issue
Search Records
Partner Access
MyHeritage.com
Attempt: Result = HTML Error
Using (latest versions of) 'Google' "Chrome" with "Windows 10"
Using (latest versions of) 'Mozilla' "FireFox" with "Windows 10"
Submitted for your information; attention; and, consideration.
Brett
.
Tagged:
0
Comments
-
Brett said: FamilySearch
FYI
I just 'jagged it'.
I now know what caused this to happen.
Old pre.2012 individuals/persons.
Originally, a number of the "Children" in this Family, DID NOT have "Last Names" recorded in the "System", only "First Names", in the "Vitals" Section.
Whereas, they did have (both, "First Names"; and,) "Last Names" recorded in the "Other Information" Section; as, "Alternate Names".
I had been correcting that; and, progressively "Adding" the "Last Name" in the "Vitals" Section.
I got a little carried away and ahead of myself with this one Child; where, I had not "Added" the "Last Name" in the "Vitals" Section; but, tried to "Search Records" using "MyHeritage".
And ...
vwä-ˈlä ( voilà ) ...
Resulting in the above ...
Brett
.0
This discussion has been closed.