• Topics

  • Blog Entries

    • Darrin Lythgoe
      By Darrin Lythgoe in TNG News 0
      A lot of people have asked me lately how they’d go about moving their TNG site to a new site without losing any data. In a nutshell, here’s what you’d have to do:
      1. Back up your TNG data, either with TNG (under Admin/Utilities) or with phpMyAdmin (on your site control panel or “cPanel”; recommended for larger sites). The TNG backup creates a series of .bak files in the “backups” folder on your site. If you use phpMyAdmin, you should end up with a large .sql file on your computer.
      2. Download all the TNG files and folders from your old site. If you used TNG to do the backup, the backup files will be included here.
      3. Upload all the same files to your new site.
      4. Use the “Express” option on the readme.html page on your new site to install TNG again. You might need to create a new MySQL database, and the installation will ask you for the connection info. After creating the TNG tables, you can skip the rest of the installation.
      5. Now restore your data on the new site. If you backed up with TNG, restore the data from Admin/Utilities. If from phpMyAdmin, go there on your new site and import the .sql file you created earlier.
      That’s it. Now you should be up and running on the new site with all the same data, including user accounts.

      View the full article
    • Darrin Lythgoe
      By Darrin Lythgoe in TNG News 0
      If you’ve seen the TNG Facebook page , you may have also seen Jim Benedict posting a lot of helpful “how to” articles on various TNG-related topics. You can see them all on his site at http://tng.one-name.net/, but I’d like to spotlight some of them here as well. Today I’m going to highlight all of the ones relating to “Trees” (as defined in TNG) and the importing and exporting of GEDCOM files:
      How to import a GEDCOM
      Getting all your family data into TNG, including an explanation of the Import screen options.
      Exporting a GEDCOM to TNG
      A few words on the process of preparing your data for import, along with some useful tools.
      Adding and deleting Trees
      A “Tree” in TNG is a container for your GEDCOM data. Here Jim talks about creating and editing these containers.
      Trees and GEDCOM downloads
      How to allow or prevent users from downloading GEDCOM files from the trees on your site.
      How importing a GEDCOM is different from uploading
      Examining the different parts of the import process.

      View the full article
    • Darrin Lythgoe
      By Darrin Lythgoe in TNG News 0
      TNG 11 is almost here! The currently estimated release date is about March 16 or 17, 2016. This major upgrade includes nearly a hundred fixes, enhancements and new features. Here’s a summary of the most significant changes:
      DNA: Aid your research by keeping track of DNA tests taken by the people in your tree. Enter the specifics once and link them to those affected. Fan Charts: A fan-oriented chart of ancestors can now be displayed for each person in your tree. Data Validation: Several preconfigured validation reports will help you spot potential errors in your data. New Design: Another new template has been added. Family Chart: This view shows a person’s spouse, children and parents all together on one page in graphical fashion. Mobile-Friendly: More improvements here will make your site even more usable on mobile devices. Administration: Enhancements to the Admin menu show quick totals for all data categories, plus an “Important Tasks” area to remind administrators of items that need attention. Heat Maps: Color codes on the Places, Surnames and Search Results pages now show the global distribution of surnames and places. Search: A Google search page now allows you to search across your entire site using Google’s indexes. Timeline: The Simile Timeline layout has been redesigned to be more readable, with separate bands for family and general events. Compatibility: Pro-active changes will make sure TNG remains compatible with the latest versions of PHP. You’ll be able to get the upgrade at a discount ($14.99) by going back to your previous downloads page. If you’ve lost the URL or access info, send me a message at darrin@lythgoes.net and I’ll send it to you again. If you only purchased TNG or the v10 upgrade recently (in the past 6 months), you’ll be eligible to get the upgrade for free.
      Also take note that Simply Hosting does not install upgrades. A helpful 15-minute video will be available to walk you through the process, but there will also be an option to pay an extra $15 to have the upgrade installed for you. If you’re doing the upgrade yourself, take a minute to review the post here from the v10 release on helpful tips for a successful upgrade.

      View the full article
  • Who's Online (See full list)

    • FrankB
    • ojay
    • Hiraeth
  • Posts

    • Merv
      Hi, How did you do this? Have you set up a test user without admin rights??
    • manofmull
      Merv Re photo/doc mod = duh me (of course). All my mebers have email addresses (required), so maybe the auto-fill works for admin only. I tried in non-admin mode but box required manual insertion of address for submitting or suggesting. It's no big deal, but I seem to remember a mod which auto-filled the email box of submitters.  
    • Jan Suhr
      Thanks Roy, that will work for the Y-DNA but not for mtDNA where all the children get the mtDNA from her mother. So a filter for mtDNA should also have the sons of a mother in addition to the maternal line.

      Diedrich Hesmar with his GEDCOM-tools has such a filter to create a new GEDCOM with only the mtDNA persons. http://ofb.hesmer.name/gedserpro_e.html   Jan
    • Ken Roy
      Jan, Take a look at Erik Hoppe's Maternal and Paternal Lines mod.  You can see examples of both using my Dad's web page
    • Jan Suhr
      Is there any way in current version to filter out Y-DNA or mtDNA descendants in the tree views. If not it would be a great option when viewing a descendants tree to sort of clean up the tree from the persons that do not share a certain DNA-type.   Thanks   Jan