Re: [Gramps-bugs] current Family Tree does not show up in Family Tree manager

[John R. <jr...@ce...>]

On Nov 2, 2012, at 1:34 PM, Mitchell Slep <mi...@mo...> wrote:

> Ok I think I figured what was going on.  I'm totally new to gramps and just created a Family Tree. I wanted it saved in a specific directory (one that has regular backups) but I couldn't figure out how to move a Family Tree. First I tried changing the "Family Tree Database path" setting but that didn't seem to do anything. So then I exported as a Gramps XML (since I had no media) to the desired directory. When I clicked on the .gramps file in Finder, it was opening Gramps but loading the original Family Tree (I had open last used tree checked). So I was never really editing or saving the tree in the new location. The reason the Family Tree Manager was empty was because it only shows what is in the Family Tree Database path, and I hadn't saved any trees to the new location yet.
> 
> I was able to "move" my tree by creating an empty tree in the new location, and importing a grampsdb that I exported from the old one. After that I could archive. Not sure if that's the recommended way of moving a tree but it seems to have worked.
> 
> A lot of this was very confusing. Here are a few suggestions:
> - Add a wiki page for moving trees. I'm still not sure if I did it correctly because it seems there are more settings for where media gets stored.
> - Family Tree manager should show what directory it is currently browsing. It didn't make sense to me why I had a tree open but the manager showed no trees. Ideally I would be able to change the directory from there as well.
> 

Glad you got there. Yes, the method you used is fine, because you said you had no media. If you did have media, you would of course have made a .gpkg and those other settings would have been significant (though the defaults are OK, too). If you mess that part up there's a tool (in Tools) to globally change media paths.

Moving trees is mentioned in passing in the section "Exporting Data". That could be a bit more obvious and clear.

We don't want users to know where their trees are. That's why they're in a hidden folder. More advanced users can use preferences to set the folder that Family Tree Manager looks in, but we'd rather the less proficient ones not be tempted to play around in there.

Regards,
John Ralls