After a Treeshare session I am left with the following 6 files that do not exist on Ancestry or RM.
If I delete them they reappear when I use Treeshare again! How do I delete them?
1 Like
@treview_David So I am assuming, you have hit delete on the Ancestry side for all of these and accept all changes ( if it lets you do this) and they crop back up the next time you tree share-- so does it show you anything when you click on SHOW ON ANCESTRY-- if it does then there is something on that page that needs to be deleted or fixed on Ancestry
Neither of the ‘Show on ancestry’ options do anything. The people do not exist on RM or Ancestry anymore. They did exist recently but I cannot delete them on RM or Ancestry because now they don’t exist in either place!!!
Try running the database tools for RM–not sure it will help
Try resetting TreeShare - Settings, Webhints, Ancestry - Reset TreeShare. If that doesn’t work it’s probably best to chat with support - RootsMagic Help and Support Center
2 Likes
I’m not currently active on TreeShare but I recall that drag’n’drop between two databases connected to different Ancestry Trees could result in the copied persons still being linked to their old AMT while the rest of the linked people are linked to their different AMT. Maybe after these RM people were deleted or merged, those links remained. That could give these oddball results.
1 Like
@TomH I have never had 2 RM files connected to 2 different Ancestry database–just 2 RM databases connected to the same Ancestry file-- so could David do a drop and drag and possibly eliminate the problem ( much easier than having to totally download a new copy)..
@treview_David , I have noticed lately that RM is staying connected to Ancestry and my browser is staying connected to Ancestry–so you MIGHT try signing out of Ancestry on the browser and RM – cleaning out the cache on the browser
(maybe even rebooting computer) then sign back in again
Good idea. This issue was resolved with 11.0.3 release but a drag and drop before then, when the bug was active, might possibly be the cause of these results.
@nkess , yes another drag and drop would resolve it if that was the cause. But drag and drop can result in things getting lost, so it would be my last choice. This is an old post that attempted to catalogue what gets lost and what gets preserved with Drag n Drop from back in RM10 days.
I am pretty sure that this is an example of the problems that I have been reporting here and in other posts. Immediately after you add, amend or delete an Ancestry profile from Treeshare you should see Treeshare collecting changes from Ancestry. This is because Treeshare maintains a at least two tables with summary information about the people in your Ancestry tree. At least one table contains the main information about the people and at least one table contains information on the relationships between them. After you amend data in Ancestry, these tables are amened in Treeshare to reflect the changes made.
My general problem is that a small proportion of the data concerned is either not being sent from Ancestry, not being received by Treeshare or not being processed by Treeshare. This has happened repeatedly since the new Ancestry API and the RM software using it were implemented. In your case, Treeshare has not received the messages from Ancestry telling it to update the tables, even though the changes have been effected there.
Running ‘update Treeshare’ as another user has recommended deletes these tables so that next time you run Treeshare it rebuilds them from scratch. It should therefore resolve your problem, but my most recent issue relates exactly to information getting missed when these tables were rebuilt, so although this should work, there is a small chance that it will introduce other errors as described in my other thread.
Hi Folks
Thanks for all your suggestions. I started working through them slowly and discovered that resetting Treeshare appears to have solved the problem… for now at least. I will message again if the problem returns, but for now all is OK. Thanks again
1 Like