Jump to content
TNG Community
  • Topics

  • Blog Entries

    • Darrin Lythgoe
      0 comments
      With the impending release of TNG 14, I thought I’d take a minute to go over some of the things to watch out for while you’re upgrading your site. All of these apply no matter which version you’re installing.
      Make sure you choose the right upgrade. Before you begin, go to your TNG Admin menu and look at the top of the screen. It should say there what your current version is. Anything that starts with “13” (like 13.0.1 or 13.1.2) counts as “13.x”. You will see links for several different upgrades on the v14 downloads page. Be sure to get the one most appropriate for your currently installed version. If you install the wrong upgrade, you will likely notice errors when you’re done. Install the upgrade, not the full version. When you get to the v14 downloads page, the first links near the top will be for brand new TNG users. What you want is a little further down in the Updates section. Look for the upgrade most appropriate for your currently installed version, then look next to the download link for the name of the file that will include the upgrade instructions. Note: A new version of the full version “readme.html” file will also be included with your upgrade, but you can ignore that since you’re upgrading. If you accidentally open that file, it should warn you that you’re about to install the full version. If you see that, go back! Installing the full version on top of an existing install will cause you to lose your data and your customizations. Don’t forget the backup. At the top of the instructions, you’re advised to back up your key files (mainly the configuration files, like config.php, pedconfig.php, etc., but also any others that you may have customized) and your database tables. If you do make a mistake at some point, having a backup can save you a lot of headaches. Once the upgrade is finished and everything is running smoothly, back up your tables again. Remember to view the upgrade readme from your browser, not your home computer. One of the first steps is to upload the files to your site. After that, you need to load the instructions again from your site. In other words, if your site is www.mysite.com and you’re upgrading from 13.0.1, open your web browser and go to http://www.mysite.com/readme13x-14x.html from there. If you continue with the local copy you opened immediately after downloading, some of the later steps won’t work. Update your template. For most people, this should be simple. If you’ve never tinkered with the HTML or PHP in your template files, just upload the entire “templates” folder from the upgrade and that’s it. If you have made any customizations (not the Template Settings or the mytngstyle.css style sheets) and you want to keep those, then you’ll probably want to merge your changes into the latest files instead of just uploading those new files. Some of the new features may not work unless you’re using the latest template files. Watch for the twist. Large upgrades usually include a step to update your database table structures, but a lot of people miss it and then wonder why things are broken. This time the database update step directs you to visit the TNG Admin menu on your site, where you’ll be given the next steps. If you skip those, you’ll be reminded again each time you visit the admin area. Don’t forget to click the final link to delete the upgrade files when you’re done (the upgrade page will still show until that happens). Clear your browser cache. Once you’re done, go into your browser settings or preferences and clear the cache (or “temporary Internet files”). Until you do that, your browser might decide to hang on to some of the old pages, and that could present a conflict. Some features might not work. The instructions for clearing the cache vary from one browser to another, so do a Google search on this if you’re not sure how to do it.
      View the full article
    • Darrin Lythgoe
      0 comments
      TNG 14 is almost here! This major upgrade includes more than 100 enhancements, fixes and new features. Here’s a quick summary of the most significant changes:
      Import: The inner workings of the GEDCOM import have been improved to make the process much more robust. Unresponsiveness issues have been addressed, and “resume” operations should be seamless. Also, support has been added for some GEDCOM 7.0 features. Media included with a zipped GEDCOM file can now be extracted at the time of import. Admin Home Redesign: The look and feel of the Admin home page has been modernized. Menu items are larger, and excess text has been removed. The redundant left-side menu has been removed, and rotating banner images display at the top. The number of mods installed is also now visible on the Admin home page. Connections: The Relationship tab has been supplemented by an advanced relationship/connection search, powered by the Connections mod (by Michal Jarocinski). This will allow you to quickly find more connections between two individuals, including those that include one or more marriages/pairings along the way. Style Upgrades: The size and font of most form fields has been increased to 14px. Rounded corners and extra padding have been added to most tables, and a drop shadow has been added on some tables. These and other elements combine for a softer, more modern look and feel for all pages, both public and admin. Media: Several here too, including: 1) Image tags may now point to places, families, sources, repos and citations (in addition to people). The tree selection defaults to either the tree assigned to the image or the one used for already existing media links. 2) Image tags can also be just a label (any text or name), which can optionally point to any URL. 3) DOC and DOCX files can now be viewed inline instead of being automatically downloaded (based on Michel Kirsch’s “Office Viewer” mod). Search: The submit button on the Advanced Search page is now fixed so you never have to scroll to find it. Most search fields have also been widened, and the “Other events” list starts off as collapsed, but the form remembers ones you have used before and sorts those at the top. Descendant Tables: Jim Graham’s Table of Descendants mod has been incorporated. Visitors will see a “Tables” option on the Descendants tab. Click through to see a tabular list of all descendants for a particular individual. Choose any row to instantly list all individuals from that generation. Charts: Zoom and drag functions have been added to several more charts. Also, birth and death years are now displayed on the fan chart. Report Generator: The report builder interface has been redesigned to be more modern, easier to use, and more functional on mobile. The Custom SQL box has also been enlarged. Backups: Backups can now be created as SQL files (the old method will still be supported). They can also be downloaded with a download icon. Backups may also include DROP and CREATE table directives. A restore operation may be made to drop all existing records or not. Additional Genders: Other gender choices can now be entered on the Admin/People pages. Alternate Birth Events: A list of acceptable “alternate birth event types” can now be maintained in the settings, and users may choose the alternate birth event for each individual from the Edit Person page. Mod Manager: Many improvements, including 1) The source code has been restructured to improve the Mod Manager internal structure. New diagnostic error prefix is included on messages in Mod List. 2) Michel Kirsch’s “Analyze only install mods” mod has been incorporated. 3) A fixed-position header now applies to all screens and includes the table column header line. PHP Compatibility: Pro-active changes will make sure TNG remains compatible with the latest versions of PHP and MySQL. You will be able to get the upgrade at a discount by going back to your previous downloads page after the release is officially announced. 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 13 or the v13 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 in the next few days to those who are eligible.

      View the full article
    • Darrin Lythgoe
      0 comments
      With TNG 13 being released today (Sep. 21, 2020), I thought I’d take a minute to go over some of the things to watch out for while you’re upgrading your site. All of these apply no matter which version you’re installing.
      Install the upgrade, not the full version. When you get to the v13 downloads page, the first link near the top will be for brand new TNG users. What you want is a little further down in the Updates section. Also take note that a new version of the full version readme.html file will be included with your upgrade, but the installation instructions for the upgrade will be in a different file. The name of that file will be listed next to the download link. For example, if you’re coming from version 12, the file will be called readme12x-13x.html or readme123-13x.html. If you accidentally open readme.html, it should warn you that you’re about to install the full version. If you see that, go back! Installing the full version on top of an existing install will cause you to lose your data and your customizations. Make sure you choose the right upgrade. Before you begin, go to your TNG Admin menu and look at the top of the screen. It should say there what your current version is. Anything that starts with “12” (like 12.0.1 or 12.1.1) counts as “12.x”. You will see links for several different upgrades on the v13 downloads page. Be sure to get the one most appropriate for your currently installed version. If you have v11 but you install the upgrade for users with 12.x, you will likely notice errors when you’re done. Don’t forget the backup. At the top of the instructions, you’re advised to back up your key files (mainly the configuration files, like config.php, pedconfig.php, etc., but also any others that you may have customized). If you do make a mistake at some point, having a backup can save you a lot of headaches. Once the upgrade is finished and everything is running smoothly, back up your tables again. Remember to view the upgrade readme from your browser, not your home computer. One of the first steps is to upload the files to your site. After that, you need to load the instructions again from your site. In other words, if your site is www.mysite.com and you’re upgrading from 12.0.1, open your web browser and go to http://www.mysite.com/readme12x-13x.html from there. If you continue with the local copy you opened immediately after downloading, some of the later steps won’t work. Don’t skip any steps. A lot of people think they just have to upload the files, but there’s a little more to it than that. The step most people still skip is the one relating to database structure changes (if you see a bunch of database query errors after installing the upgrade, this is probably what you did). There’s usually just a simple link you have to click. Doing that will open another page that runs through a list of database updates. Depending on the version you had previously, some of the items may say “Failed or done previously”. Don’t be alarmed if you see some of those. Update your template. For most people, this should be simple. If you’ve never tinkered with the HTML or PHP in your template files, just upload the entire “templates” folder from the upgrade and that’s it. If you have made any customizations (not the Template Settings or the mytngstyle.css style sheets) and you want to keep those , then you’ll probably want to merge your changes in with the latest files. Some of the new features may not work unless you’re using the latest template files. Clear your browser cache. Once you’re done, go into your browser settings or preferences and clear the cache (or “temporary Internet files”). Until you do that, your browser might decide to hang on to some of the old pages, and that could present a conflict. Some features might not work. The instructions for clearing the cache vary from one browser to another, so do a Google search on this if you’re not sure how to do it. If you still have issues and you think you may have botched the instructions, feel free to ask for help from me or the user list (tngusers2). If you think you might have found a program bug, please contact me directly (darrin@lythgoes.net).
      Despite the possible pitfalls described here, the upgrade process should be fairly easy. If you’re still sure you won’t be able to do the upgrade yourself, there are other options though. Simply Hosting no longer does upgrades, but I can do it for an extra $15, and others could be hired as well. I might be swamped at first if too many people request this, so please be patient.

      View the full article
  • Posts

    • Ken Roy
      Thanks Roger, You did a better job of explaining it than I did.  I was hoping to get Darrin to include the Enable Allow Private Media mod in TNG but life keeps interfering.   I will try again to get Darrin to include it in TNG 14.1 but unless we also get Chris Moss' Private Media Mod also included as part of TNG we will not be any closer to TNG controlling the privileges without mods. Part of Chris Moss Private Media Mod was included in TNG v13 but using the Allow Private privilege.  I suspect because the request was not made clear to Darrin that Chris' Allow Private Media privilege was also required to control who has access to the Private Media such that users in Branch 1 might have access but not users in Branch 2.   for what I wanted to do and Chris had done, Michel Kirsch's Secret medias and Steven Davis Media Access Mod does not provide the required granular control that the Private Media Mod  did in TNG v12
    • theKiwi
      My understanding of what Ken said was that Darrin added this to the TNG 14 upgrade. And looking at the "upgrade_db13x-14x.php" file, I see at line 68 alterTable( "ALTER TABLE $users_table ADD allow_private_notes TINYINT(4) NOT NULL after allow_private" ); which added the column to the table. But there is no facility in a pure TNG14 Admin screen to set or not set that value. The https://tng.lythgoes.net/wiki/index.php/Enable_Allow_Private_Media that Ken referenced presumably adds that check box to the Admin screen. Roger
    • GOGGS
      That link is embedded in tons of levels of style groups (the final one being "home-menus"). In your browser, from the menu select More Tools, then Developer Tools and drill down in the top section until the link is highlighted. In the lower section in the Styles tab, you can see what controls the placement relative to the DIV blocks on the page and how the DIV blocks are arranged. To move just that link via style manipulation might be complicated, without re-arranging a big chunk of the whole template/page layout. You might consider just editing the page directly; delete the link and re-insert it in another DIV block in your template where you'd like it to sit (or leave the current one and add another in a new place. <li> <a href="login.php">Log In</a> </li> GOGGS
    • tngrlkrz
      Sorry to belabor this fine point.  OK, I confirmed phpMyAdmin shows it's there, but, it is not in the admin:users  rights checkbox display like your earlier post shows, at least not or all of us.  So perhaps the mod you mentioned did that for you? Ron
    • Ken Roy
      If you look at the database structure in phpMyAdmin, it shows a new field Allow Private Media    
×
×
  • Create New...