Jump to content


Member Since 12 Aug 2017
Offline Last Active Yesterday, 02:26 PM

Posts I've Made

In Topic: Cannot Confirm Webhints

30 April 2018 - 05:32 PM

Essentially that is what I am doing. However, it is not quite as simple as I thought.


If there is a marriage event for the deleted person then TreeShare does not directly add it back it.


Initially I was adding it back it when running a resync on their spouse but I found that TreeShare added a second copy of the marriage event to the spouse.


In the end my solution is to:

go to the spouse in Ancestry

make a change (normally just edit, add a character to the description, save, edit (again), remove the new character, save)

resync the spouse but update the marriage rather than add it because Ancestry has put the event on the spouse but without the source.


I also find that TreeShare affects individuals connected with that deleted and resync'd individual which then involves more clicks to then show them as unchanged.


The good thing is that new hints appear on Ancestry, which of course then need resyncing!


It is a shame that this is so long-winded. I suspect we are back to the problem that TreeShare is a new feature which is slowly evolving to cope with problems imposed by Ancestry.

In Topic: Updates Information

30 April 2018 - 05:19 PM

I note that the website has not yet been updated https://www.rootsmag...uk/patch-notes/

In Topic: Cannot Confirm Webhints

28 April 2018 - 06:12 PM

Thanks, that was so simple.


To confirm all I do is delete a problem individual on Ancestry and then use TreeShare to let RootsMagic upload my copy of that individual back to Ancestry.

In Topic: Treeshare -- button to ignore when prompted to add individuals

07 December 2017 - 02:51 PM

I might be missing something but is that not what TreeShare does now.


If a person is in RM but not in Ancestry then there is an add button. If you do not wish to add that person to Ancestry then just ignore that and do not add them.

Then if their (deceased) parents are in RM but not in Ancestry then TreeShare will have a checkbox to add a new child to that person. Obviously do not check that.


I will grant you that the option to add that child to Ancestry will continue to appear but you could filter them by using groups and only doing a TreeShare on the group which does not have the child.


As an aside (and going in the other direction) if I see someone in Ancestry who has a child (which it knows about because that link is also in Ancestry) but who I have not previously added that child in RM then I first go to that child and add them as a new person to RM before continuing to add their parent. I find that is a better way to create that relationship in RM.

In Topic: Groups: Collateral Lines Select everyone

23 November 2017 - 01:42 PM

Thanks for your help. Actually RM was doing its job since a cousin from the maternal grandparent side was (incorrectly) shown as the spouse of a cousin from the paternal grandparent side.


The problem as caused my me accepting a webhint in Ancestry indirectly from a family tree which had connected the spouse to a person with the right name, in approximately the right location, in the right time period. Once I unlinked the couple them the problem was resolved.


In case anyone is interested this is how I found the wrong link:


I knew that if you went further up the tree then eventually the system would function correctly for a (great) grandparent because the purpose is to select the highlighted person, their ancestors, their spouses and their collateral links. So I copied the complete database and on that copy I found the level for a (great) parent that was the lowest level which selected everyone in the database. I then systematically unlinked each child (i.e. a great uncle/aunt) and each time tried to do a collateral connection until I found the child what was causing the system to fail.


Once that couple were found I simply unlinked then in the real database and everything was fine.