Changes

Jump to: navigation, search

Gramps 3.0 Wiki Manual - FAQ

18 bytes removed, 23:14, 29 August 2015
no edit summary
{{stub}}
:Use a recent version of GRAMPS! From 2.2.5 onwards there is an automatic backup utility.
:It is extremely important to keep backups of your data, and keep them in a safe place. GRAMPS has a specific portable file format which is small, and human readable, denoted by <code>.gramps</code>. If you have allowed this in the preferences (In <tt>Edit menu->Preferences->General</tt>), GRAMPS will keep a backup of your database on exit. You can copy this backup file from time to time to a save location (eg a usb stick).
: -
:[Note: The .gramps files are compressed. Clicking them will open GRAMPS. To see the XML select them and open them with a decompressing utility (like ark, gunzip), after which you can extract the XML file which is human readable, see [[Generate_XML#How_do_I_uncompress_the_file?|details]].
: -
:'''Do not keep backups in GEDCOM'''. Not all information GRAMPS stores can be written in the GEDCOM. Hence, an export/import operation GRAMPS --> GEDCOM --> GRAMPS, will mean you '''lose''' data. Use the <code>.gramps</code> file format for backups!
: -
:'''Do not keep backups in GRDB format'''. GRDB is a database, which might be computer dependent (read, not working on a different PC). Small damage to a GRDB file can also not be repaired. Use the <code>.gramps</code> file format for backups!
;Does Gramps support Unicode fonts? In particular, does it support non-Roman Unicode fonts?
==Database - GRAMPS file formats==
*;What is the maximum database size (bytes) GRAMPS can handle?:GRAMPS has no hard limits on the size of a database that it can handle. Starting with 2.0.0 release, GRAMPS no longer loads all data into memory, which allows it to work with a much larger database than before. In reality, however, there are practical limits. The main limiting factors are the available memory on the system and the cache size used for BSDDB database access. With common memory sizes these days, GRAMPS should have no problem using databases with [[GRAMPS Performance|tens of thousands of people]]. *;How many people can GRAMPS database handle? :See above. Again, this is dependent on how much memory you have, see [[GRAMPS Performance]]. *;My database is really big. Is there a way around loading all the data into memory?:Starting with 2.0.0 release, GRAMPS no longer loads all data into memory, which allows it to work with a much larger database than before. The fileformat used is <code>.grdb</code> which means gramps database. *;Can I run GRAMPS from a database on a NFS share?:Yes you can. *;Why is the database format not portable?:The biggest issue with GRAMPS portability lies with 'transactions'. WithGRAMPS 2.2, we added support for atomic transactions to protect data.With atomic transactions, multiple changes are committed as a singleunit. Either all the changes make it, or none of the changes make it.You are never left in a situation with a partial set of changes. A sidebenefit of using transactions is that database access (reads and writes)are faster.  :The problem with transactions (at least using BSDDB) is that it does notallow all the data to be stored in a single file. Logging files areneeded to keep track of things. These logging files are kept in a DBEnvironment directory. We need a separate directory for each file,otherwise the log files can interfere with each other.  :In 2.2, we keep the log files under the ~/.gramps/<path> directory,creating a unique directory for each database. The problem is that yourGRDB file needs the log files, which are in a different directory.Copying the GRDB file is only copying a portion of the database.
==Bugs and requests==
*;I found a bug and I want it fixed right now! What do I do?:The best thing you can do is to fix the bug and send the patch to [email protected] :-) :If that is not possible, you should [[How to report bugs|submit a bug report]] :A good bug report would include:
# Version of gramps you were using when you encountered the bug (available through Help → About menu item).
# Language under which gramps was run (available by executing <code> echo $LANG</code> in your terminal).
# Symptoms indicating that this is indeed a bug.
# Any Traceback messages, error messages, warnings, etc, that showed up in your terminal or a in separate traceback window.
 :Most problems can be fixed quickly provided there is enough information. To ensure this, please follow up on your bug reports. :Then we will have a way of contacting you should we need more information. *;GRAMPS should be a .... type of application:It is obvious that GRAMPS absolutely needs to become a (client-server/web-based/PHP/weblog/Javascript/C++/distributed/KDE/Motif/Tcl/Win32/C#/You-name-it) application. When is this going to happen? :The surest way to see it happen is to get it done by yourself. Since GRAMPS is free/open source, nobody prevents you from taking all of the code and continuing its development in whatever direction you see fit. In doing so, you may consider giving your new project another name to avoid confusion with the continuing GRAMPS development. If you would like the GRAMPS project to provide advice, expertise, filters, etc., we will gladly cooperate with your new project, to ensure compatibility or import/export options to your new format of a project. :If, however, you would like the GRAMPS project to adopt your strategy, you would need to convince GRAMPS developers that your strategy is good for GRAMPS and superior to the present development strategy.
==GRAMPS Webhosting ==
*;How can I publish web sites generated by GRAMPS?:Since GRAMPS generates HTML pages, you can upload the pages to your personal web site. If you do not have a personal web site, and still wish to have your pages available on the internet, the GRAMPS project can provide space for you at the http://library.gramps-project.org, see [[GRAMPS:Webhosting|the webhosting article]]. *;How do I submit my pages to the GRAMPS library site (http://library.gramps-project.org)?:If you wish to submit pages to the GRAMPS library site, you will need to contact the GRAMPS project, typically by sending a message to the gramps-users mailing list. You will then be given a username and password that will allow you to upload your files to the site. After you upload the files (in a gzip'ed tar file), the GRAMPS project will install the pages for you on the site. *;After I upload my Family Web Page to library.gramps-project.org, is the password used for write privileges only or read privileges?:In order to prevent abuse of the library.gramsp-project.org site, the password given allows uploads only. If you wish to have a username and password combination to restrict read access to your pages, you will need to contact the GRAMPS project, and we could set this up for you. However, the read and write accounts will be separate accounts. *;Do I view the Family Web Page with a url into my browser? Or through a link on a list of Family Web Pages on the GRAMPS-Project.org site?:The main page on the library.gramps-project.org site will contain an index of the available family sites. However, there will be a unique URL for each site as well.

Navigation menu