Jump to content
TNG Community
  • Topics

  • Blog Entries

    • Darrin Lythgoe
      By Darrin Lythgoe in TNG News 0
      TNG 12 is almost here! This major upgrade includes dozens of enhancements, fixes and new features. Here’s a summary of the most significant changes:
      DNA: Jeff Robison’s DNA mod has been incorporated, providing several significant enhancements to the previous method of tracking DNA tests. Mod Manager: Rick Bisbee, Ken Roy and others have added significant improvements to this utility that allows users to easily install or remove code modifications and add-ons. Translations: TNG has now been translated into Chinese, as well as 20 other languages. Google Translate tools have also been added to the online help pages and the installation guide to allow users to view those resources in their own language. New Designs: Three new templates have been added, and improvements have been made to several others. The template settings have also been moved to a more robust location, within the database. Media Enhancements: Many improvements have been made in the way TNG handles photos and other media. These include importing media linked to citations, creating thumbnails from some PDFs, being able to show thumbnails in a single horizontal row if desired, and showing captions on top of image previews. Libraries Upgraded: Third party libraries for jQuery, jQueryUI and PHP Mailer have been upgraded to the latest versions. The C3 and D3 charting libraries have also been added. New Visualizations: A First Names page (like the existing Surnames page) provides a different way to look at your data, and the new C3/D3 charting libraries allow for pie chart representations on those pages and on the Statistics page. Security: The reCaptcha mod has been incorporated, giving TNG site owners a way to fight spam from bots. A few other security updates will prevent authorized access in previously vulnerable areas. User Access: Registered site users can now be assigned to multiple trees. Admins and editors will still see only one tree at a time, but they can easily switch from one tree to another without logging in multiple times. New Tools: A “Refresh Living” utility will re-mark people as living or deceased, depending on dates entered or time elapsed from birth, while a “Make Private” tool will mark people as private if they have been deceased less than the configured number of years. Compatibility: Pro-active changes will make sure TNG remains compatible with the latest versions of PHP and MySQL. You can get the upgrade at a discount (starting at $15.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 purchased TNG 11 or the v11 upgrade at any time in the six months prior to the upgrade release date, you’ll be eligible to get the upgrade for free. Information on that will be sent out to those affected.
      If you purchased TNG through a third party (like the Guild of One-Name Studies), please contact them for information on upgrading your site.
      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
    • 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
  • Who's Online (See full list)

    • Jan Bastiaanssen
    • MichaelM
    • Chris Lloyd
    • Packrat
    • Horsman_ONS
  • Posts

    • MichaelM
      Thank you, Jürgen You are right, this a good workaround and will be my first approach. On the other hand, there is a database behind TNG, where media attributes like description, note, path, thumbpath, datetaken,  etc..
      are maintained separately in the media table. So i think it should be possible to "Order By" one of these. Michael      
    • JPB
      Michael, for example, write in the description: A date or a sequence number: Name of the person etc. Thus it is sorted first by number, then by name. All pictures of a person are in a chronological order. So that's solved on my site. Jürgen
    • Katryne
      Hi Scott ! Did you have to provide your bank details to Google for this free account ?
    • Scott_Pryer
      I had the same issue with geocoding error message of "over-quota". I finally determined that google changed their policies this summer.  I signed up for another free account and geocoding works again. Scott www.waynepryergenealogy.com  
    • Scott_Pryer
      I am somewhat new but have created a branch for similar purpose. So I thought I would give my thoughts. To confirm your need: 1. all users to be able to make suggestions for the entire tree.   2. certain users to be able to make changes to specific portions of the tree. (for a specific ancestor and their descendants) You might have to provide two users.  One user for the all trees (suggestion only) and a separate user that provides 'editor' rights to a specific branch. For example: user: bsmith    password:1234   (set for suggestions for the entire tree) user bsmith-editor   password: abcd  (set for editor rights and roles for a specific branch)
×