Comment mettre à jour PhpGedView d'une version 4.0.2 ou 4.1.x vers une version supérieure

Cet article vous explique comment effectuer une mise à jour d'une version PhpGedView v4.0.x ou 4.1.y vers une version PhpGedView v4.1.x.

Mise à jour de 4.1 vers 4.1.x

Mettre à jour PhpGedView d'une version 4.1 vers une version 4.1.4 ou toute autre version 4.1.x n'est pas difficile, mais cette opération ne consiste pas uniquement à remplacer les fichiers présents sur le serveur par de nouveaux fichiers.

Voici les différentes étapes à suivre pour réaliser cette migration:

1. Pour effectuer une mise à jour d'une version 4.1 vers une version 4.1.4 ou toute autre version 4.1.x, remplacez les fichiers présents sur votre serveur par les fichiers de la nouvelle version, en écrasant les fichiers présents sur votre serveur.
2. N'oubliez pas de supprimer également tous les fichiers qui sont présents dans le répertoire PhpGedView/index/cache, car ces fichiers sont faits pour fonctionner avec votre version actuelle de PhpGedView, pas avec une nouvelle version. Pour supprimer les fichiers présents dans le répertoire PhpGedView/index/cache, il vous suffit de vous rendre sur la page "Mon Portail --> Administration --> Nettoyer le répertoire «index»", puis de cocher la case "cache" qui apparaît sur la page "Nettoyer le répertoire «index»". Vous pouvez également détruire manuellement ces fichiers dans votre répertoire "index" en utilisant votre logiciel FTP.

Ces instructions concernent les sites pour lesquels aucune modification de la base de données n'a été faite en ligne ou pour les sites dont les modifications ont été réalisées en ligne mais dont leur base de données et leurs fichiers GEDCOM sont synchronisés. Si vous n'avez pas synchronisé votre base de données et vos fichiers GEDCOM, exportez une copie de votre base de données.

1. Réalisez une sauvegarde (backup) de votre base de données SQL. Vous pouvez avoir besoin de faire appel à l'aide de votre hébergeur web pour réaliser cette opération.
2. Make a backup copy of your index folder, media folder, and the "config.php" file.
3. If you have made changes to the language files (which should have been concentrated in the "languages/extra.xx.php" files), make a backup copy of these as well.
4. Make a backup copy of any changes or additions to the themes.
5. If you have the room on your server, rename your existing installation and temporarily leave it in place. This will serve as an additional backup.
6. Download a copy of the latest PhpGedView version (4.1.2 is the current release) and unpack it on your local PC.
7. Copy all of the following original files/folders from the backups to your local PC, replacing those in the new download:

• file "config.php"
• directory "media"
• directory "index" - NOTE: you may have moved this folder from its PhpGedView master folder into server file space that's not accessible from the Internet for security purposes. If so, simply delete the new index folder that came with the latest version of PhpGedView.
• changes to the themes. Do NOT copy the entire backup of the "themes" directory, since new versions of PhpGedView may contain essential updates to the standard themes.
• file "languages/extra.xx.php" - If you have created any language variations, add these files. Do NOT copy the entire backup of the "languages" directory.
• If you do not plan on using all of the included modules, you may wish to delete any subdirectories for modules you do not wish to use. If you don't intend to use any of the modules, you can delete the entire "modules" directory prior to transferring your directory to your server.

These preparatory steps have left you with a complete copy (except the database) of your PhpGedView installation on your local PC. Follow these steps to install that copy on your server:

1. Copy the entire contents of the new local PC PhpGedView directory to your server's PGV operating directory. If necessary, create that directory first.
2. Be sure to set full read/write/modify permission (0777) on the "index" folder and all its contents.
3. If you intend to use PGV to upload media files or to create thumbnails from media files that have been uploaded outside PGV, you must set full read/write/modify (0777) permission on the "media" folder, its contents, and all its sub-folders and their contents. Please see the article on the Media_Firewall for instructions on how to relocate the Media folder to be outside the web-addressable space.
4. If you need to reconfigure the entire PGV site or change any of the database connection information, you must set full read/write/modify (0777) permission on the file "config.php". After your configuration changes have been stored, you can set this file to read-only.
5. Some of the internal structures have changed, so you must delete the Upcoming Events cache file. This file's name ends with "_upcoming.php" and is housed in your "index" folder.
6. Via your web browser, navigate to your PhpGedView installation (localhost or internet domain or IP number) and log in as Administrator.
7. Immediately re-import your GEDCOM (a fresh upload isn't necessary unless you modified the GEDCOM offline or did not use the sync function).

• Let PGV make whatever corrections it deems necessary.
• Be sure to let PGV erase existing database contents. PGV will only erase and repopulate the tables relevant to the GEDCOM.
• PGV might change the structure of certain other tables, including Users, Favorites, News, and Blocks to suit the requirements of the new version, but the contents will remain intact.

Upgrading 4.0 to 4.1.x

Use the following steps to upgrade to v4.1. These steps assume that you are familiar with PhpGedView and have successfully installed it before.

1. Upload the new 4.1 files to your server replacing the old files with the new files. Do not replace the config.php file or the index directory.
2. In order to create the data required for the new version, you will have to re-import your GEDCOM.
3. You can now use your upgraded site.
4. If you are using a customized theme you will need to update your theme with new stylesheets and variables. An excellent tool that can help you to merge themes is the WinMerge project http://winmerge.sourceforge.net/

Note to SQLite users: Unfortunately SQLite does not support the ALTER TABLE
SQL command.  This means that we must first drop the tables and recrate
them.  It is highly reccomended that you run the backup before upgrading.

Version 4.x no longer includes support for index files. If you do not have PHP 5 with built-in SQLite support or a database account then you should not upgrade to PhpGedView 4.x. Maintenance releases will continue for the 3.3.x version until PHP 4 is no longer supported.