PhpGedView

PhpGedView and SunTzu Worm Attack

by

Last week, a notice was publishLast week, a notice was published on PhpGedView’s main site, about a security issue that PhpGedView using genealogists should be aware of:

There is currently a worm targeting PhpGedView websites. It is highly reccommended that everyone update to the latest versions of PhpGedView 3.3.7 or 4.0 beta 3 and apply the patch files located here:
https://sourceforge.net/tracker/index.php….

ed on PhpGedView’s main site, about a security issue that PhpGedView users should be aware of:

PhpGedView 3.3.7

by

A new version of the “stable” branch of PhpGedView, version 3.3.7, has been released today. PhpGedView is an online genealogy application, and this version encompasses changes that went into version 3.3.6 (which wasn’t formally released) as well as corrects some errors created by 3.3.6.

PhpGedView parses GEDCOM 5.5 genealogy files and displays them on the internet in formats and charts that you are familiar with. It also allows relatives to edit their genealogy online and collaborate together on their research.

It can be downloaded here – SourceForge.net

Updates:

Read more

PhpGedView 4.0 beta 2

by

PhpGedView 4.0 beta 2 is now available. This is part of a major revision of the PhpGedView, an online genealogy application.

PhpGedView parses GEDCOM 5.5 genealogy files and displays them on the internet in formats and charts that you are familiar with. It also allows relatives to edit their genealogy online and collaborate together on their research.

It can be downloaded here.

As of yet, the official release notes are not complete – when they are published, we’ll add them in, so that you know what changes have been made.

There is information contained in this SourceForge.net forum posting by Stephen A.:

This release solves many of the issues plaguing the Beta-1 release, including pretty smooth handling of media.

HOWEVER, please remember that this release, like the previous Beta-1, is as advertised – BETA software, intended to be pushed around, beat-up and mangled by testers to discover what are most certainly still existing bugs to be squashed prior to a production release. Use it in production at your own risk.

You can read the full changelog below:

Read more