I have tried twice - now on my third time after the update to Tree Share - its slow and had frozen twice and need to reboot with Task Manager. Third time worked but listed everyone in my tree as having a change - Are you kidding me
Go to Settings, WebHints and click on “Reset TreeShare” and see if that helps. Clearing out the old .DT8 files and using the new .DT11 files should help. It will run slow when it first creates the new files needed for the new Ancestry API.
Nope did not work - It was slow but when completed it looks like mostly everyone in my tree is identified as having a change. Before the update I may have had people where there were differences between RM and Ancestry e.g. sources but before the update I had them “X” out so I will not see them again in Tree Share- Does this mean I need to go through each person and re-”X” them out again? I do see individuals that are saying there is a change, but I can see that both RM and Ancestry agree in Tree Share.
It’s a new API, it shouldn’t have marked everyone as changed. I’m not seeing that in my trees. You will need to go through them individually or click on Options, Clear everyone from “changed” list.
That’s what I figured - Thanks
Is there any downside using - under the Options button in Tree Share the “Clear everyone for changed list” button vs going through each one individually? I know if I had any outstanding changes I had not reviewed before the update would be cleared but I’m okay with that. Anything else I’m not thinking about?
Thanks
No, that would be only issue clearing everyone. Those that you truly needed to update would no longer be on the list.
@rzamor1 Awesome! Thank you for your Help!
So Renee, you know I reported several issues related to TreeShare not working in certain cases on the Mac in basically every version up through 11.0.4. My concern is the statement “Clearing out the old .DT8 files and using the new .DT11 files”, as it may force me to move my database back to a Windows PC, build the new DT11 files, and move everything back to the Mac. That is the only way I can create a “fresh” .DT8 file on even a high end Mac with a gigabit fiber connection. That same rebuild take a few minutes on a WIndows PC. It can be reproduced easily by simply renaming the .DT8 file, witnessing the failure, deleting the failed .DT8 file, and rename the orginal file back. Once that’s done all is well.
My question is has the dev team used the file I gave you to use ON A MAC, and successfully rebuilt a .DT11 file? Little files aren’t sufficient for testing, some testing ON A MAC, using a file of at least 25K people is necessary.
Keith, I did test the Ancestry Stone Costner Mac.rmtree upload on the mac and it did finish, but not all the people were included. It wasn’t tested on last two builds before this final one for release, so there is a chance even that improved. I still have it on my list to finish testing.
1 Like
Thanks @rzamor1. I finished my Ancestry sync with 11.0.4, backed everything up, installed 11.1 and went back to TreeShare without deleting the DT8 file. It took about 25 minutes to build the DT11 file (see the screen shots I posted on Facebook). So far so good, but it would be nice have source maintenance work correctly by replacing the sources on Ancestry with what’s on RM. If you remove or merged sources that are additive on Ancestry. This has always been the case, and some folks are claiming this as a “new” issue, but it’s worked that way as long as I’ve used TreeShare and it’d be nice to have it fixed.
I can’t believe TreeShare STILL refreshes back to the top of the list after each “Accept changes”. Even if the changes make the person match so it disappears from the list, RM should bookmark the person above or below so the list stays at the same place.
Yea, there are a number of UI issues that don’t follow normal UI standards. Someday I need to document them all. As far as TreeShare it still displays the last person in the “changed” list even though you accepted changes and the list is empty.
That’s not my issue, mine is that, if I accept changes for a name in the middle of my LONG list of changed people, the list goes back to the top, and I have to scroll down and find where I was working.