{"id":37,"date":"2004-04-15T17:48:00","date_gmt":"2004-04-15T22:48:00","guid":{"rendered":"http:\/\/www.familytidings.com\/blog\/?p=37"},"modified":"2004-04-15T17:48:00","modified_gmt":"2004-04-15T22:48:00","slug":"phpgedview","status":"publish","type":"post","link":"https:\/\/www.familytidings.com\/blog\/?p=37","title":{"rendered":"phpGedView"},"content":{"rendered":"<p>After reading more about phpGedView and sifting through their online forums, it became clear that the authors expect phpGedView to be the web-based viewer of genealogical data and that <a href=\"http:\/\/gdbi.sourceforge.net\">GDBI<\/a> will be used for editing this data.  So I canned GRAMPS and pulled down <code>gdbi-7-pgv.jar<\/code>, the <a href=\"http:\/\/sourceforge.net\/projects\/gdbi\/\">GDBI JAR file<\/a> for phpGedView.  A JAR is a Java Archive file, so of course <a href=\"http:\/\/java.sun.com\">Java<\/a> is required to run it:  <code>java -jar gdbi-7-pgv.jar<\/code>.<\/p>\n<p>I won&#8217;t repeat what&#8217;s already in the documentation, but these fields required by GDBI could use some explaining:  The URL is the location of your phpGedView website with <code>\/gdbi.php<\/code> appended to it.  So it should look something like <code>http:\/\/www.example.com\/phpGedView\/gdbi.php<\/code>.  The GEDCOM is the name of the GEDCOM you uploaded to your site, e.g., <code>my-family.ged<\/code>.  Leave the <i>Read-only<\/i> and <i>Blank Editor<\/i> boxes unchecked.<\/p>\n<p>Make whatever changes you want, then just exit the program.  To update the site, sign in to phpGedView.  At the top-right of the page where is says <i>logged in as (<code>username<\/code>)<\/i>, click on <i>Admin<\/i>.  Choose the third item on the right side of the table <i>Accept \/ Reject Changes<\/i>.<\/p>\n<p>At the bottom, under <i>Import Gedcom<\/i>, select <i><code>my-family.ged<\/code> \u00e2\u20ac\u201c Import Gedcom<\/i>.  At the bottom of the next screen, select <i>Continue Adding<\/i>.  On the next screen (<i>Import GEDCOM<\/i>), below <i>Do you want to empty the dataset?<\/i>, select the <i>Yes<\/i> button.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>After reading more about phpGedView and sifting through their online forums, it became clear that the authors expect phpGedView to be the web-based viewer of genealogical data and that GDBI will be used for editing this data. So I canned GRAMPS and pulled down gdbi-7-pgv.jar, the GDBI JAR file for phpGedView. A JAR is a [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-37","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.familytidings.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/37","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.familytidings.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.familytidings.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.familytidings.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.familytidings.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=37"}],"version-history":[{"count":0,"href":"https:\/\/www.familytidings.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/37\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.familytidings.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=37"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.familytidings.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=37"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.familytidings.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=37"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}