This update of TNG to version 11.0 in the Guild’s Members’ Websites Project has not been without some challenges along the way. The TNG team wants to bring every user up to date on the current progress.
The upgrade took place about a month ago, on April 30th. Our version of TNG is customized to make it work as a multi-instance website. What does that mean? Every member using TNG in the Type 3 category is going to one application and running their own instance of TNG. Which means that when we do an upgrade or a bug fix, every participant gets the upgrade or fix. This is powerful as our user count grows beyond fifty. As well, all of the family tree information is in the one main database, so that we can do some nifty data analysis in the near future.
But, if there is a code problem, then everybody has the same woe at the same time. This happened within a couple of hours of the version 11 upgrade. There was an incompatibility of our custom coding and the new version 11. As a result, every member’s TNG site was looking at the same family tree: Rasco. That took a couple of days to fix and fortunately, or good planning, no data was lost.
Another problem cropped up with the Oldham study later on. This turned out to be settings in the General Settings area and was easily spotted and rectified. The big clue here was that only one surname site reported a problem, which isolated the issue.
More recently, everyone’s media disappeared from the public view. Our MWP sites are supposed to be visible to the public. What went wrong? It turned out to be a customizing issue. One knowledgeable member wanted to activate a privacy modification, available from the TNG community. That worked all too well; all of the TNG sites went ‘private’. We had to root out the mod coding from the main software and block further use of the Mod Manager feature. This will be added in at some point, but with closer control.
As far as we can determine, the MWP Type 3 sites are up and working. Enjoy.
Your TNG team.