• Topics

  • Blog Entries

    • Darrin Lythgoe
      By Darrin Lythgoe in TNG News 0
      Like TNG, the underlying PHP is constantly changing, and new updates are released every few months. Hosting providers don’t always install the latest version right away, but they almost always get to it eventually.
      When that happens, there are usually a handful of PHP functions that for whatever reason are no longer supported in the newer version. For example, the “session_register” and “session_unregister” functions were removed a while back, and all the “mysql” functions (like mysql_query) were removed with the jump to PHP 7.0.
      I have always tried to keep pace with these changes, removing functions like that from the TNG code before PHP removes them, so if you keep your TNG up to date you shouldn’t experience any problems. If you’re still running an older version of TNG, however, you may suddenly run into trouble if your hosting provider upgrades PHP without notice. It won’t affect every page on your site, but if you happen to execute some of the problem code, you’ll be stopped short. Sometimes you might get a blank page, but most of the time you’ll see an error message like this:
      Fatal error: Call to undefined function session_register() in /public_html/genealogy/globallib.php on line 5
      It’s possible that a message like this would refer to a TNG problem, like if a key file was missing. If you want to know for sure, do a Google search on the the middle part of the error message (“Call to undefined function session_register()”, in this instance). If it’s just a problem with your TNG files, you probably won’t get many results. If the function named is one that PHP has removed though, you should see several hits referring to that fact, and you can know that it’s time to upgrade TNG.
      To get the upgrade at a discount, you can always go back to your previous TNG downloads page. The payment options will be visible in the “TNG Updates” section. If you’ve lost the access info for that page, please feel free to drop me a note.

      View the full article
    • Darrin Lythgoe
      By Darrin Lythgoe in TNG News 0
      Parts of TNG have already been translated into 21 languages (besides English), but there are quite a few languages that are not supported as of yet. If you have thought about translating TNG into a new language, here’s what you’ll need to do.
      First, use an FTP program or the file manager on your site control panel to navigate into the “languages” folder and create a new folder for your new language. You should see folders for all the other languages there, like this:
      Afrikaans Afrikaans-UTF8 Arabic-UTF8 Croatian Croatian-UTF8 The “-UTF8″ at the end of some folders means that the files in that folder are UTF-8 encoded. If your data or your new language uses letters or characters outside of the standard 26-character alphabet used in English, you should name your new folder in similar fashion (e.g., “Hebrew-UTF8″).
      Next, copy the files from the folder of your native language (use the “-UTF8″ version if your new language will also be using UTF-8) and paste them into your new folder. The files should be named admintext.php, alltext.php and text.php.
      Now go in TNG to Admin/Languages and create a new language record for your new language. Select your new language folder in the “Language folder” dropdown box. Put “UTF-8″ in the character set field if your new language will be UTF-8 encoded. Otherwise use “ISO-8859-1″ as the character set. Click the “Help for this area” link for hints on any of the fields or options. Don’t forget to save. Also, if this is the first language record you’ve created under Admin/Languages, you must also create a record for your primary language. If you forget to do that, you won’t be able switch back when you try out your new language later!
      Finally (and this is the biggest step), edit the files you pasted into your new folder and translate the messages. You can do this by editing the files right on your site, or you can download them to your computer and edit them there. Be sure to use a pure text editor (not MS Word or anything that will add formatting). Notepad (Windows) and TextEdit (Mac) are good options.
      When you’re doing the translations, be sure to translate only the messages and not the “keys”. For example, the messages you see will look something like this:
      $text[‘family’] = “Family”; $text[‘birth’] = “Birth”; In these examples, the keys are what you see inside the square brackets. The messages are what you see between the double quotes. In the end, your new translations will look something like this:
      $text[‘family’] = “сям’я”; $text[‘birth’] = “нараджэння”; One other thing to remember is that double quotes within the message need to be “escaped” with a backslash. An escaped message looks something like this:
      $text[‘message’] = “This is an \”escaped\” message”; If you forget to escape the nested quotes, your site may show only blank pages until you fix it.
      When you’re done, save the files and copy them back to your website if necessary. To see your work in action, choose the new language from the language dropdown box on any page of your site. If you weren’t sure of the context while doing the translation, you might want to check to see if any guesses you made were correct, then go back and correct them if necessary.
      And one more thing: If you feel inclined to share, I would love to include your new translations in future versions of TNG so others can benefit. Good luck, and let me know if you have any questions!
       

      View the full article
    • Darrin Lythgoe
      By Darrin Lythgoe in TNG News 0
      Today I’m putting the spotlight on a feature that’s new in TNG 11, the fan chart. First of all, many thanks go to Ben Wagner, a TNG user who contributed most of the code. Great job, Ben!
      To find a fan chart on any TNG 11 site, just search for any individual, then click the Ancestors tab near the top of the page. Finally, click the Fan Chart option on the menu bar just below the tabs.
      I love the fan chart because it gives you a great visual sense of a person’s ancestry while making more efficient use of the space than a standard pedigree chart. In other words, there are no empty holes like you get with a large pedigree chart, even when you’re viewing a large number of generations. It’s great for showing off your tree at family reunions.
      The primary individual (in the sample image here it’s my grandfather Leo Lythgoe) is at the center in the bottom, with each ring around that person representing a new generation (parents, grandparents, etc.). It’s even color coded for the eight largest families. To see more for a particular individual (like birth, marriage and death dates and places), just hold your mouse pointer over any name shown. Doing that will display a small pop-up window containing the information. Of course you can also jump right to the page of any individual listed there by clicking on their name.
      I should also mention that the chart makes good use of the new HTML5 “canvas” element, which lets you draw arcs and show text on an angle. Because of that, you’ll notice that the chart is not an image, it’s just HTML, and that helps keep the bandwidth down.
      As with the other TNG ancestry charts, you can choose a different number of generations by adjusting the number just above the chart on the left. And if you love the fan chart an extra large amount, you can go to Admin/Setup/Chart Settings/Pedigree Chart and set the Initial Display so that the fan chart is the first chart you see whenever you click the Ancestors tab for any person on your site.
      And now that you’re done reading this, click the image above to jump to the actual page and see the fan chart in action.
      So what else would you like to see on this blog? Please comment!

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

    • crashar
    • Merv
    • raisondetre
    • Chris Lloyd
  • Posts

    • raisondetre
      I would like to install the Guestbook on template 14 and was encouraged to see it worked with 12. Did you use the mod from April or the earlier step by step instructions from January? Thanks!
    • alanw
      WantitRight- Thank you for the informative post. I am in the same boat... have had enough trouble getting new iterations of FTM to work correctly that I have not even considered the export of GEDCOM into my TNG site (FTM 2017 final release is behaving ok so far). I was hoping that FTM 2017 would bring a smoother GEDCOM transfer process.  I had been syncing Ancestry.com with FTM 2014, then export to FTM 2012 (as gedcom from 2014 didn't work right)... then exporting out of FTM 2012 via converter into TNG.  And of course, loading the new media as a separate process into TNG. A cumbersome process, but workable. A couple of observations: 1) I have also been experimenting with RootsMagic to see if it might be a more effective vehicle to get data from ancestry.com to TNG... now that RootsMagic syncs with Ancestry.com. I have only taken a brief look, but it appears to me that all links having anything to do with Ancestry.com proprietary sources do not load into RootsMagic as HTML pages... rather a link back to Ancestry.com site appears to be forced. I have not checked this in detail, but that was my initial quick take.    The point here is that perhaps Ancestry.com is enforcing the same limitation on FTM 2017? 2) I read on a review site that FTM 2017 is trying to comply with the most current version of GEDCOM standards. Perhaps that might be part of the problem- if there GEDCOM format does not match up properly with TNG?  It might be worth contacting FTM 2017 support to see what they have to say. Again, thank you for sharing... I'd like to stay in the loop on this topic. If I can't get a smooth transfer of data from Ancestry.com to TNG, then I will discontinue TNG and look for some other way to address the need that it is currently serving. I love the TNG product as it fits the niche need that I use it for. alan  
    • Paul Barrett
      Yes, the upgrade issue did concern me a little but I do like the idea Chris My basic problem is that I keep getting spouse and parent details mixed up when glancing at records.  I think I will first try out the Regroup Person Profile mod, because that adds subtitles to the sections, and they might prevent me from making the mistake.  The upgrade issue will be lessened if I use a mod instead of customising.   Thanks   Paul
    • raisondetre
      OK. I looked into that. First, I had already manually coded the paragraph to the format I wanted (12pt/Georgia), saved it and then looked at 'inspect' as you suggested.  That had merit and helped me dissect the situation. See attached for a section of what comes up . . . but I still don't know how to make the format style "universal" for that particular text block for media. What file is this connected to so I can edit it? I must be missing it in the various style php files. I always can set a 'convention' for myself for consistency but hoped I could manage this more efficiently.  More ideas welcome. Thanks all. MSB
    • jayat1familytree
      What does the "Inspect element tell you? Go to the page and ;ace your cursor over the text , right click and select 'inspect' I think you will probably have to add a new definition for a new class