Jump to content
TNG Community
  • 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)

    • tngrlkrz
    • Bill Herndon
  • Posts

    • Bill Herndon
      Sorry Merv, but this is just not the case.  Using only information that I could glean from my own genealogy database, along with some rudimentary information about the members of my living immediate family, I have managed to talk my way past the 1st tier operators at a number of financial institutions that I do, ...well *did*, do business with.  (Those accounts have since been moved elsewhere.) Identity proofing is a tricky subject, and the majority of high-profile data breaches, are traced back to two simple techniques:  1) The exploitation of legitimate credentials left exposed by a third party or 2) Failures by online or telephone support personnel to insist on physical credentials or a second factor of authentication prior to conducting business.  It's a sad state of affairs, but many 'reputable institutions' only employ 3 or 4 easily ascertainable facts in order to establish someone's identity to their satisfaction.  You're not wrong that the law is probably on your side if someone spoofs the institution where your brokerage account resides, but is the hassle re-establishing control over your account worth it?  JMHO...but I'd rather act cautiously and make sure there's nothing on the living for an attacker to find in my TNG database.  But, of course, one's mileage may vary... k/r Bill Herndon Lindell-Herndon Genealogy
    • Bill Herndon
      Mats, There's no magic here, unfortunately.  Reunion, the software that supports my primary database, has options for scrubbing the data about living individuals based on criteria that I set--in my case a custom "living" flag with GEDCOM tag "_LVNG".   So on export, an empty entry in the GEDCOM is substituted for any living individual.  You can see many of these in Lindell-Herndon Genealogy...about 1/5 of my entire database of 5000+. And, with all due respect to Ken and Merv, I do not consider scrubbing an issue of whether or not TNG's algorithms are good enough to figure it out for me, nor an issue of identity theft and spoofing.  Rather, this is a courtesy I extend to the family members who have done so much to make my database what it is... out of an abundance of caution.  As a cybersecurity professional, I monitor exactly how often my host system is attacked, and I can tell you that it's not dozens, or hundreds...but thousands of times per day.  And although I know most of what there is to know about securing a Linux system, even I am not as skilled as the people who are trying to crack my host system and site.  That is simply the nature of the beast, hence...I take extra precautions, and I don't feel that my site, as Merv put it, is boring because it only has dead people in it. k/r Bill Herndon Lindell-Herndon Genealogy  
    • Newfloridian
      My online website is https:// I have localhost versions of the website on my PC using (variously) Wampserver, MoWeSII and USBWebserver. As far as I am aware, none of these would run directly as https:// and I wasn't sure whether there was a way to get any of them to recognise https:// The solution was to add a couple of lines to the beginning of the .htaccess file in the root of each of the localhost setups as follows: RewriteEngine On
      RewriteCond %{HTTPS} off
      RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} At the very end of the same file I have: #RewriteCond %{HTTP_HOST} ^thenameofmywebsite$ [OR]
      #RewriteCond %{HTTP_HOST} ^www.thenameof my website$ This has the effect of each of the localhost programs treating my website as if it was still http:// Alan            
    • Ken Roy
      There is a TNG Wiki article on TNG and SSL but I don't think it covers setting up a local server as https.  I think it is more oriented to using a hosting service. As to robots.txt, Google might be one of the few who honors its directions.   You might take a look at the other articles in the Security category on the TNG Wiki
    • manofmull
      Bill I can't answer the first part as my site is online and is https. For the second part, I don't use a robots.txt file. My site requires login and that I believe is good enough i.e. the crawlers can't get past the basic pages, home and login.
×