Upgrading from GRAMPS 2.2.x to 3.0.x - Revision history

Daleathan at 02:34, 28 October 2011

2011-10-28T02:34:03Z

Dm1407: language

2009-06-08T00:09:09Z

language

Dm1407: be a bit more reasuring

2009-02-20T05:03:57Z

be a bit more reasuring

Dm1407: remove wip message.

2009-02-20T04:54:24Z

remove wip message.

Robocoder: cat

2008-08-08T17:37:18Z

cat

Robocoder: New page: :''This is a work in progress.'' '''Upgrading from GRAMPS 2.2.x to 3.0.x''' can be a pain-free process. The first step is to backup your database using GRAMPS' Export function. (Your ve...

2008-08-08T17:35:46Z

New page: :''This is a work in progress.'' '''Upgrading from GRAMPS 2.2.x to 3.0.x''' can be a pain-free process. The first step is to backup your database using GRAMPS' Export function. (Your ve...

New page

:''This is a work in progress.''

'''Upgrading from GRAMPS 2.2.x to 3.0.x''' can be a pain-free process. The first step is to backup your database using GRAMPS' Export function. (Your version of GRAMPS may already automatically save copies of the .grdb and GRAMPS XML files.) The second step is to upgrade the application (discussed elsewhere). For the final step, this How-To article discusses some of the finer details in migrating your database.

==Oops==

The internal database format has changed between GRAMPS 2.2.x and 3.0.x. When you first start GRAMPS 3.0.x, your existing family tree(s) won't appear in the "Family Trees" window. '''Don't panic.''' You have not lost any data. Yet. ;)

If you didn't manually backup your database, look in <tt>~/.gramps/env</tt> to see where your automatic backups are stored.

find ~/.gramps/env -name '*.grdb'

A path like <tt>/home/jdoe/.gramps/env/home/jdoe/subpath/data.grdb</tt> would suggest we look in the folder, <tt>/home/jdoe/subpath</tt> where we'll hopefully find files, <tt>data.backup.gramps</tt> (your family tree in GRAMPS XML format) and <tt>data.grdb</tt>.

Now would be a good time to make a copy of these files ... just in case.

If you don't have any backup files, you should revert the application back to GRAMPS 2.2.x and then make a backup.

==Database Migration==

# Launch GRAMPS 3.0.x.
# In the (Manage) "Family Trees" window, select "New" to create a new family tree database.
# Enter an appropriate name for your family tree. You can safely use the same name because your new family tree is stored in a different directory, <tt>~/.gramps/grampsdb</tt>.
# Next, Import from your backup file, e.g., <tt>data.backup.gramps</tt>.
# Go to Media and check for broken links to be fixed. Broken links occur if you used Relative Paths.
# If you imported from a .grdb file, you will have to select an Individual before some functions work correctly (e.g., Pedigree).

Corrections appreciated. Enjoy!

← Older revision		Revision as of 00:09, 8 June 2009
Line 1:		Line 1:
		+	{{languages}}
	'''Upgrading from GRAMPS 2.2.x to 3.0.x''' can be a pain-free process.		'''Upgrading from GRAMPS 2.2.x to 3.0.x''' can be a pain-free process.

← Older revision		Revision as of 04:54, 20 February 2009
Line 1:		Line 1:
−	~~:''This is a work in progress.''~~
−
	'''Upgrading from GRAMPS 2.2.x to 3.0.x''' can be a pain-free process. The first step is to backup your database using GRAMPS' Export function. (Your version of GRAMPS may already automatically save copies of the .grdb and GRAMPS XML files.) The second step is to upgrade the application (discussed elsewhere). For the final step, this How-To article discusses some of the finer details in migrating your database.		'''Upgrading from GRAMPS 2.2.x to 3.0.x''' can be a pain-free process. The first step is to backup your database using GRAMPS' Export function. (Your version of GRAMPS may already automatically save copies of the .grdb and GRAMPS XML files.) The second step is to upgrade the application (discussed elsewhere). For the final step, this How-To article discusses some of the finer details in migrating your database.

← Older revision		Revision as of 17:37, 8 August 2008
Line 27:		Line 27:

	Corrections appreciated. Enjoy!		Corrections appreciated. Enjoy!
		+
		+	[[Category:How do I...]]

@@ Line 28: / Line 28: @@
 # Go to Media and check for broken links to be fixed.  Broken links occur if you used Relative Paths.
 # If you imported from a .grdb file, you will have to select an Individual before some functions work correctly (e.g., Pedigree).
 [[Category:How do I...]]

@@ Line 1: / Line 1: @@
-'''Upgrading from GRAMPS 2.2.x to 3.0.x''' can be a pain-free process.  The first step is to backup your database using GRAMPS' Export function.  (Your version of GRAMPS may already automatically save copies of the .grdb and GRAMPS XML files.)  The second step is to upgrade the application (discussed elsewhere).  For the final step, this How-To article discusses some of the finer details in migrating your database.
+'''Upgrading from GRAMPS 2.2.x to 3.0.x''' can be a pain-free process.
-==Oops==
+# The first step is to backup your GRAMPS 2.2.x database using GRAMPS Export function.  (Your version of GRAMPS may already automatically save copies of the .grdb and GRAMPS XML files.)
-The internal database format has changed between GRAMPS 2.2.x and 3.0.x.  When you first start GRAMPS 3.0.x, your existing family tree(s) won't appear in the "Family Trees" window.  '''Don't panic.'''  You have not lost any data.  Yet. ;)
+==New GRAMPS 3.x database format==
-If you didn't manually backup your database, look in <tt>~/.gramps/env</tt> to see where your automatic backups are stored.
+GRAMPS 3.x uses a newer database format than GRAMPS 2.2.x.  When you first start GRAMPS 3.0.x, your existing family tree(s) won't appear in the "Family Trees" window.  '''Don't panic.'''  Your GRAMPS 2.2.x family database is safe and you have not lost any data.
   find ~/.gramps/env -name '*.grdb'
-A path like <tt>/home/jdoe/.gramps/env/home/jdoe/subpath/<i>data</i>.grdb</tt> would suggest we look in the folder, <tt>/home/jdoe/subpath</tt> where we'll hopefully find files, <tt><i>data</i>.backup.gramps</tt> (your family tree in GRAMPS XML format) and <tt><i>data</i>.grdb</tt>.
+A path like <tt>/home/jdoe/.gramps/env/home/jdoe/subpath/<i>data</i>.grdb</tt> would suggest we look in the folder, <tt>/home/jdoe/subpath</tt> where we'll hopefully find files, <tt><i>data</i>.backup.gramps</tt> (your family tree in GRAMPS XML format) and <tt><i>data</i>.grdb</tt> (your family tree in GRAMPS .grdb format) .
-Now would be a good time to make a copy of these files ... just in case.
+Now would be a good time to make a backup copy of these files ... just in case.
 If you don't have any backup files, you should revert the application back to GRAMPS 2.2.x and then make a backup.
@@ Line 23: / Line 27: @@
 # Go to Media and check for broken links to be fixed.  Broken links occur if you used Relative Paths.
 # If you imported from a .grdb file, you will have to select an Individual before some functions work correctly (e.g., Pedigree).
 [[Category:How do I...]]