Family Tree access
While working in a distant part of one's Family Tree, ability to access a closer position in the Tree has been changed, i.e., I'm viewing 10th cousin & I want to return to myself or my parents' Tree position. When you click on Family Tree in the main title bar, you are taken to the Tree of the 10th cousin instead of your immediate Tree. This has changed; please consider reverting to its original configuration. Please & thank you.
I agree that this is an annoying and undesirable change, but there are a couple of workarounds: use the "home" button (which looks like a house) at the top right of the tree/chart page (and then re-adjust the zoom, because it annoyingly resets Every Single Eff..ervescent Time), or click Recents and then the tree-stublet icon to the right of your name.0
1940 census... None of the 1940 census records allows for a Date Change or Name modification. This has been occurring for many months. please help! thank you. Toria0
A van Helsdingen ✭✭✭✭✭
Not all indexed records can be edited. Some records were originally indexed by other organizations and do not belong to FamilySearch (I believe the 1940 census was indexed as a joint venture between Ancestry and FamilySearch). Sometimes the record custodian (in this case the US National Archives (NARA)) may not want it. Sometimes it is technically difficult or impossible.0
the "home" button (which looks like a house) at the top right of the tree/chart page
The home button is present only in the Portrait and Landscape tree views. Fan Chart and Descendancy tree views do not have it.0
@dontiknowyou, the fan chart does have the home button. I don't use it (because of the zoom reset), but it's definitely there. The only view it's missing from is descendancy.
@ToriaMoran Smith, I just looked at a bunch of random 1940 U.S. census entries, and they were all editable. You can change the name, the event date (dunno why you'd want to, it's always 1940), and the event place.
Have you tried it in a different browser? If it works there, then some housekeeping (clearing your cache and cookies) should get it working again in the original browser.0