PGVWiki - User contributions [en]

PhpGedView v4.3

2012-09-16T13:16:46Z

Okbigkid: /* PhpGedView version 4.3 */

PGV v4.3 has not been officially released as a downloadable version, however it is the only version available that has any recent development and then, only a few minor bug fixes. PGV itself remains in a stable, but stagnant condition as there is no base of programmers working on the project.

PGV should continue to work without major problems until there are significant deprecations or changes of the supporting programs, PHP and MySQL.

If you are new to PGV, do not install very old v4.2.4 [released in JAN 2011], but rather download the current SVN version from the SourceForge site and install that code. This is the only code that is currently supported. Additionally, you may wish to investigate [http://webtrees.net webtrees], a MAR 2010 fork of the PGV project which is currently in very active development.

==== From the PGV Help forum: ====
[http://sourceforge.net/projects/phpgedview/forums/forum/185166/topic/4392768 PGV Help Forum SVN download tip]

A copy of the current SVN is created on SourceForge every evening.

Here's the download location:
http://phpgedview.svn.sourceforge.net/viewvc/phpgedview/trunk/phpGedView/?view=tar

This 16 Mb file can be expanded with 7-zip or Winzip to produce a 52 Mb compressed file. This expanded file produces a directory called "phpGedView" containing all of the files comprising the most recently updated version of PGV.

It is this version that is called "4.3.0 SVN". It's actually 4.2.4 with all the latest revised files. You can safely use this version. Any bugs in this version also exist in 4.2.4 (!!)

PhpGedView v4.3

2012-09-16T13:16:11Z

Okbigkid: Created page with "== PhpGedView version 4.3 == PGV v4.3 has not been officially released as a downloadable version, however it is the only version available that has any recent development and ..."

== PhpGedView version 4.3 ==
PGV v4.3 has not been officially released as a downloadable version, however it is the only version available that has any recent development and then, only a few minor bug fixes. PGV itself remains in a stable, but stagnant condition as there is no base of programmers working on the project.

PGV should continue to work without major problems until there are significant deprecations or changes of the supporting programs, PHP and MySQL.

If you are new to PGV, do not install very old v4.2.4 [released in JAN 2011], but rather download the current SVN version from the SourceForge site and install that code. This is the only code that is currently supported. Additionally, you may wish to investigate [http://webtrees.net webtrees], a MAR 2010 fork of the PGV project which is currently in very active development.

==== From the PGV Help forum: ====
[http://sourceforge.net/projects/phpgedview/forums/forum/185166/topic/4392768 PGV Help Forum SVN download tip]

A copy of the current SVN is created on SourceForge every evening.

Here's the download location:
http://phpgedview.svn.sourceforge.net/viewvc/phpgedview/trunk/phpGedView/?view=tar

This 16 Mb file can be expanded with 7-zip or Winzip to produce a 52 Mb compressed file. This expanded file produces a directory called "phpGedView" containing all of the files comprising the most recently updated version of PGV.

It is this version that is called "4.3.0 SVN". It's actually 4.2.4 with all the latest revised files. You can safely use this version. Any bugs in this version also exist in 4.2.4 (!!)

Download v4.2.x

2012-01-29T16:17:32Z

Okbigkid:

While the latest stable release is v[[{{latest version|series=4.2.x}}]], it was released on {{latest version|series=4.2.x|release date=1}}. The current SVN release is a slightly improved version titled v4.3 and should be considered as a stable replacement for v4.2.4. See PGV's Sourceforge help forum for download details.

[[image:gedview.gif|right]]
Older versions are still available ... [[Download_v4.2.1|v4.2.1]] for non-PDO enabled servers, and [[Download_v4.1.x|v4.1.7]] for servers that are only running php4.

==Download Packages==
For convenience PhpGedView {{latest version|series=4.2.x}} has been divided into several packages which allows you to choose what you want to download.

[[Modules]] are plug-ins to PhpGedView which provide additional features or functionality not found in the core files. Some modules may require additional software. See the installation instructions for each module for their requirements.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PhpGedView-basic-{{latest version|series=4.2.x}}.zip PhpGedView (BASIC) {{latest version|series=4.2.x}}]
: This package contains the core files to run PhpGedView. It includes the most commonly requested themes and language files. It does not include place maps or any modules.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PhpGedView-all-{{latest version|series=4.2.x}}.zip PhpGedView (ALL) {{latest version|series=4.2.x}}]
: This package contains the complete set files to run PhpGedView, including all themes and language files, place maps and modules. After installation you can disable the modules you don't need.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Demo-{{latest version|series=4.2.x}}.zip Windows Demo ]
: This package is a self contained demo version of PhpGedView which can be run out of the box on Windows based systems. This package is great if you want to take PGV for a test drive or if you want to burn your own data for distribution on a CD.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Themes-{{latest version|series=4.2.x}}.zip Themes ]
: This package includes other themes maintained with PhpGedView. Other user submitted themes can be found at http://www.pgvthemes.com/

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Places-{{latest version|series=4.2.x}}.zip Places ]
: This package includes place maps for many different countries. Place maps can be enabled in the place hierarchy and on the editing pages.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Languages-{{latest version|series=4.2.x}}.zip Languages ]
: This package includes the other languages that have been submitted to PGV including Arabic, Catalan, Czech, Danish, Greek, Spanish, Estonian, Finnish, Hebrew, Hungarian, Indonesian, Italian, Lithuanian, Dutch, Polish, Portuguese, Romanian, Russian, Serbian, Slovakian, Slovenian, Turkish, Vietnamese, and Chinese.

==Download Modules==
To install a module just upload it to the "modules" directory in your PhpGedView folder. All of these modules are included in the "PhpGedView (ALL) {{latest version|series=4.2.x}}" package above.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-googlemap-{{latest version|series=4.2.x}}.zip GoogleMap Module ] : This module enables GoogleMap support in the program. It will put a person's events on a map from Google.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-research_assistant-{{latest version|series=4.2.x}}.zip Research Assistant Module ] : This module enables the a research assistant tool in PGV. This tool is designed to help you with your genealogical research. It provides a way to manage and track research tasks as well as the ability to quickly enter data from sources such as census forms.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-Module-lightbox-{{latest version|series=4.2.x}}.zip Lightbox Module ] : This module enables an alternate way to experience media in PhpGedView. It provides an "Album" tab on the individual page, media slideshows, and other media enhancements.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-gallery2-{{latest version|series=4.2.x}}.zip Gallery Module ] : This module enables support and integration with the Gallery project.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-punbb-{{latest version|series=4.2.x}}.zip PunBB Module ] : This module enables support and integration with the PunBB forum project. It will allow you to include message forums in your PGV site.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-phpsysinfo-{{latest version|series=4.2.x}}.zip PhpSysInfo Module ] : This module enables support and integration with the PhpSysInfo project.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-sitemap-{{latest version|series=4.2.x}}.zip Sitemap Module ] : This module enables a site map useful for crawlers and search engines.

==Source Repositories==
You can also obtain the files from one of the following source repositories

===Subversion v4.2+===
You can also get the latest bug fixes from the main trunk of the subversion repository. Code in the [[SVN]] repository can be considered Release Candidate quality.

If you would like to try out the latest features or help to beta test new versions, then you can get the latest development code from the 4.2 branch of the Subversion repository. Code in any branches of the repository should be considered alpha/beta quality and is not recommended for production environments.

The following SVN command will get you the latest code:

export LC_ALL=en_US
svn co https://phpgedview.svn.sourceforge.net/svnroot/phpgedview/trunk/phpGedView phpgedview

You can find out more information and browse the SVN repostory online at this location https://sourceforge.net/svn/?group_id=55456

[[Category:PhpGedView]]

Download v4.2.x

2012-01-29T16:15:32Z

Okbigkid:

While the latest stable release is v[[{{latest version|series=4.2.x}}]], it was released was on {{latest version|series=4.2.x|release date=1}}. The current SVN release is a slightly improved version titled v4.3 and should be considered as a stable replacement for v4.2.4. See PGV's Sourceforge help forum for download details. [[image:gedview.gif|right]]
Older versions are still available ... [[Download_v4.2.1|v4.2.1]] for non-PDO enabled servers, and [[Download_v4.1.x|v4.1.7]] for servers that are only running php4.

==Download Packages==
For convenience PhpGedView {{latest version|series=4.2.x}} has been divided into several packages which allows you to choose what you want to download.

[[Modules]] are plug-ins to PhpGedView which provide additional features or functionality not found in the core files. Some modules may require additional software. See the installation instructions for each module for their requirements.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PhpGedView-basic-{{latest version|series=4.2.x}}.zip PhpGedView (BASIC) {{latest version|series=4.2.x}}]
: This package contains the core files to run PhpGedView. It includes the most commonly requested themes and language files. It does not include place maps or any modules.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PhpGedView-all-{{latest version|series=4.2.x}}.zip PhpGedView (ALL) {{latest version|series=4.2.x}}]
: This package contains the complete set files to run PhpGedView, including all themes and language files, place maps and modules. After installation you can disable the modules you don't need.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Demo-{{latest version|series=4.2.x}}.zip Windows Demo ]
: This package is a self contained demo version of PhpGedView which can be run out of the box on Windows based systems. This package is great if you want to take PGV for a test drive or if you want to burn your own data for distribution on a CD.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Themes-{{latest version|series=4.2.x}}.zip Themes ]
: This package includes other themes maintained with PhpGedView. Other user submitted themes can be found at http://www.pgvthemes.com/

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Places-{{latest version|series=4.2.x}}.zip Places ]
: This package includes place maps for many different countries. Place maps can be enabled in the place hierarchy and on the editing pages.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Languages-{{latest version|series=4.2.x}}.zip Languages ]
: This package includes the other languages that have been submitted to PGV including Arabic, Catalan, Czech, Danish, Greek, Spanish, Estonian, Finnish, Hebrew, Hungarian, Indonesian, Italian, Lithuanian, Dutch, Polish, Portuguese, Romanian, Russian, Serbian, Slovakian, Slovenian, Turkish, Vietnamese, and Chinese.

==Download Modules==
To install a module just upload it to the "modules" directory in your PhpGedView folder. All of these modules are included in the "PhpGedView (ALL) {{latest version|series=4.2.x}}" package above.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-googlemap-{{latest version|series=4.2.x}}.zip GoogleMap Module ] : This module enables GoogleMap support in the program. It will put a person's events on a map from Google.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-research_assistant-{{latest version|series=4.2.x}}.zip Research Assistant Module ] : This module enables the a research assistant tool in PGV. This tool is designed to help you with your genealogical research. It provides a way to manage and track research tasks as well as the ability to quickly enter data from sources such as census forms.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-Module-lightbox-{{latest version|series=4.2.x}}.zip Lightbox Module ] : This module enables an alternate way to experience media in PhpGedView. It provides an "Album" tab on the individual page, media slideshows, and other media enhancements.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-gallery2-{{latest version|series=4.2.x}}.zip Gallery Module ] : This module enables support and integration with the Gallery project.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-punbb-{{latest version|series=4.2.x}}.zip PunBB Module ] : This module enables support and integration with the PunBB forum project. It will allow you to include message forums in your PGV site.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-phpsysinfo-{{latest version|series=4.2.x}}.zip PhpSysInfo Module ] : This module enables support and integration with the PhpSysInfo project.

;[https://sourceforge.net/project/downloading.php?group_id=55456&filename=PGV-Module-sitemap-{{latest version|series=4.2.x}}.zip Sitemap Module ] : This module enables a site map useful for crawlers and search engines.

==Source Repositories==
You can also obtain the files from one of the following source repositories

===Subversion v4.2+===
You can also get the latest bug fixes from the main trunk of the subversion repository. Code in the [[SVN]] repository can be considered Release Candidate quality.

If you would like to try out the latest features or help to beta test new versions, then you can get the latest development code from the 4.2 branch of the Subversion repository. Code in any branches of the repository should be considered alpha/beta quality and is not recommended for production environments.

The following SVN command will get you the latest code:

export LC_ALL=en_US
svn co https://phpgedview.svn.sourceforge.net/svnroot/phpgedview/trunk/phpGedView phpgedview

You can find out more information and browse the SVN repostory online at this location https://sourceforge.net/svn/?group_id=55456

[[Category:PhpGedView]]

Main Page

2012-01-29T16:10:47Z

Okbigkid: /* News and Updates */ added SVN download notation as 4.2.4 is long-in-the-tooth

__NOTOC__
<table width="95%" valign="top" cellspacing="4" cellpadding="6" >
<tr bgcolor="#ADB7C9">
<td colspan="2" align="right">
__NOTOC__
<h1>Welcome to PGVWiki</h1>A community documentation and support resource for [[What is PhpGedView|PhpGedView]]</td>
</tr>
<tr valign="top">
<td width="50%" bgcolor="#E0E6E0" valign="top">
== News and Updates ==
[[image:ReadingIcon.gif|right|75px]]

* '''[[PhpGedView v4.3]] SVN Download Only - [[January|Jan]], [[2012]'''
* [[PhpGedView v4.2.4]] Released - [[13 January|13 Jan]], [[2011]]
* [[PhpGedView v4.2.3]] Released - [[26 December|26 Dec]], [[2009]]
* [[PhpGedView v4.2.2]] Released - [[1 August|4 Aug]], [[2009]]
* [[PhpGedView v4.2.1]] Released - [[4 April|4 Apr]], [[2009]]
* [[PhpGedView v4.2.0]] Released - [[31 January|31 Jan]], [[2009]]
* [[PhpGedView v4.1.7]] Released - [[31 January|31 Jan]], [[2009]]
* [[PhpGedView v4.1.6]] Released - [[16 November|16 Nov]], [[2008]]
* [[PhpGedView v4.1.5]] Released - [[27 April|27 Apr]], [[2008]]
* [[PhpGedView v4.1.4]] Released - [[4 April|4 Apr]], [[2008]]
* [[PhpGedView v4.1.3]] Released - [[16 November|16 Nov]], [[2007]]
* [[PGVWiki:Contributing to PGVWiki|To Do Lists now in place]] - [[9 November|9 Nov]], [[2007]]
* [[:Category:Contents|PGVWiki Index]] added to sidebar - [[9 November|9 Nov]], [[2007]]
* New Look (Just in case you missed it) - [[9 November|9 Nov]], [[2007]]

For further news and updates, see the following pages:
* PhpGedView [[News]] feeds
* [[PGVWiki:Bulletin Board|Community Bulletin Board]]
* [[:Category:Dates|Date specific events]]
</td>
<td valign="top" bgcolor="#D5E7E9">

==Why PhpGedView?==
PhpGedView (PGV) is a revolutionary genealogy program which allows you to view and edit your genealogy using a web interface. As a flexible, collaborative web server program, hosted online, PhpGedView has full editing capabilities, full privacy functions, can import standard GEDCOM text files from most genealogy programs, and it supports multimedia like photos and document images. PhpGedView also simplifies the process of allowing others to add to your family tree by presenting all of these functions via a standard web server and browser interface. By using PhpGedView, your latest genealogy information is always on your website and available for others to see.

PhpGedView can run locally on your computer using a webserver, but it is not like typical desktop programs. It requires access to an http server, a database and php. Easy to use and install versions of these functions can be installed with several programs designed for local use - like XAMMP, MAMP and LAMMP - depending on your operating system. However, PhpGedView's primary mission is to foster good, collaborative genealogical practices via a web environment, allowing you to share your family history and expand your tree with the help of others.

[http://phpgedview.net/about.php To learn more about PhpGedView and how it can help you with your genealogy, please read more on the ABOUT page.]

The links to '''[[What is PhpGedView|PhpGedView]] documentation''' are always available on menu to the left of the page. Key documents are:-
* The [[Users Guide]]
* The [[Administrators Guide]]
[[image:gedview.gif|right]]
* The [[Installation Guide]]
* The [[Upgrading|Upgrade Guide]]
* Our [[How To]]'s
* [[Feature Requests]]
* [[FAQ]]
* The [[Developer resources]]
</td>
</tr>
<tr>
<td valign="top" rowspan="2" bgcolor="#D5E7E9">

==Introduction==
Welcome to PGVWiki, the [[What is PhpGedView|PhpGedView]] documentation and support site that [[PGVWiki:Community Portal|anyone can edit]]. This is a community of people who are interested in recording their family histories and getting the most out the software that we use, [[What is PhpGedView|PhpGedView]].

PGVWiki reached '''{{NUMBEROFARTICLES}} articles''' on [[{{CURRENTMONTHNAME}} {{CURRENTDAY}}]], [[{{CURRENTYEAR}}]] thanks to increasingly active contributions from the community.

The basis of this site is on '''text''' and links take you to different pages where you can easily add '''text''', whilst those more adventurous members can add graphics and tables. The design of the site is such that if mistakes are made things can be rolled back to previous versions so please get involved. If you are not sure of what to do, read some of the [[Help:Contents|help documentation]] for the site or contact one of the other users who might help you:- In summary

::*if you can improve it or have something to add, do it
::*edit without fear
::*have your say

If you are not confident and would like to '''experiment in a risk free environment''' try out our [[PGVWiki:Sandbox|sandbox]].
</td>
<td align="top" valign="top" bgcolor="#D5DCE1">

==Genealogy==
[[image:Genstsign1.gif|right|100px]]
These '''general genealogy help''' links will lead you to an area for information that may assist you in your pursuit of your family's history.
*[[Genealogy:Contents#Introduction to|Introduction to]]
*[[Genealogy:Contents#Articles|Articles]]
*[[Genealogy:Contents#Resources and Links|Resources and Links]]
</td>
</tr>
<tr>
<td valign="top" bgcolor="#D3D7D9">

==PGVWiki Community==
[[image:100px-Help-browser.svg.png|right|75px]]
Visit our [[PGVWiki:Community_Portal|Community Pages]] for information on how PGVWiki is organised and what you can do to help.
</td>
</tr>
</table>


[[da:Forside]]
[[de:Hauptseite]]
[[fr:Accueil]]

Create a new GEDCOM

2010-10-04T03:34:35Z

Okbigkid:

You can start a new genealogical database from scratch.
 
From "Manage GEDCOMS and edit Privacy" select "Create a new GEDCOM" 
[[image:Gedcom_Menu.jpg|center]]

 This presents the GEDCOM configuration screen. At this time we suggest you leave most settings at their defaults. You can return later and adjust them when you are sure of your requirements - see the [[Configuration File|Configure Gedcom Parameters]] article for details. For now, only two items should be entered 
[[image:Create_Gedcom_screen.jpg|center]]
;Name the new GEDCOM
:In the field "Path and name of GEDCOM on server" enter a name for the new GEDCOM. By convention, gedcom files should end with the extension .ged, although this is not required. This name will appear in the URLs for records on your site, so a short name with no spaces or diacritics is recommended. For example "smith.ged" or "myfamily" '''NOTE: Be sure to assign a name for the file as failing to do so may disable many program features.'''
;Create a display title for your new GEDCOM
:In the next field "GEDCOM title" enter the name of the file you want to use for display purposes. '''NOTE: Be sure to assign a title for the file as failing to do so may disable many program features.'''

Click ''Save configuration'' to create the Gedcom. The Gedcom is created and automatically "Imported", and you are ready to go. In the centre of this page you have three menu options to take you to new locations.
{| cellspacing="3" width="30%" valign="top" align="center"
|style="border: 1px solid #99CC99; color: #000; background-color: #EAFFEF; padding: 0 1em 1em 1em" |
<center>
[[Pedigree Chart|Click here to go to Pedigree tree]] 
[[Welcome Page|Welcome Page]] 
[[Manage GEDCOMs and edit privacy|Manage GEDCOMs and edit privacy]]
</center>
|}

That's it. Now you can go to the Pedigree chart to see this newly created individual in this newly created GEDCOM. This person is named "Given Name Surname" - simply click the name of this person to visit their INDI page and then start editing. After that, you can begin adding new relatives (branches) of this person by selecting the "Close Relatives" tab and clicking ''Add a new father'', ''Add a new wife'' etcetera.
<ul>
'''''Note:''''' 
Additions and changes to the GEDCOM are not finalized until the administrator (you) accepts the updates in the Administration section. While this allows hasty edits to be undone and provides control over those contributors who do overly enthusiastic additions, it can be a bit confusing as certain fields will only display validated additions. Administrators setting up PGV for the first time and creating a GEDCOM from scratch might be worried because their base person seems to be inconsistent in showing some of the information as it is added. Validating the updated information will correct the displayed information.
 
Once you add your first person, click on the '''Admin''' hyperlink at the top center of the screen. Select '''Accept / Reject Changes''' option in the '''Data and GEDCOM administration''' section. Accept all the changes as appropriate and return to the individual which was displaying unexpected data.
 
This is a good first exercise for becoming comfortable with Administrative controls as well as adding individuals. The '''Accept / Reject Changes''' option will only appear in the administration page when there are updates that have not yet been accepted or rejected.
</ul>


[[Category:Administrators Guide]]
[[Category:phpGedView]]



[[fr:Créer un nouveau GEDCOM vide]]

Installation Guide v4.2.x

2010-09-30T17:38:37Z

Okbigkid: /* Online PhpGedView Configuration */

{{Phpgedview}}

This guide is for first-time installations. If you are upgrading an existing installation, see the article on [[Upgrading]].

The latest release on the v4.2.x series is version [[{{latest version|series=4.2.x}}]]. The release was made on {{latest version|series=4.2.x|release date=1}}.

We provide here a list of the [[#Requirements|requirements]] needed to install PhpGedView. We do not provide full details on how to install these since there are many dedicated websites providing such details and we would not do it justice in this guide. We assume you will have these [[#Requirements|requirements]] satisfied by your [[w:ISP|Internet Service Provider (ISP)]] or your chosen [[Web_hosting|web hosting]] solution. If you are unsure, contact them to check if they do.

==Quick Install==

* Contact your [[w:ISP|ISP]] or [[Web_hosting|web host]] to ensure they are able to supply the [[#Requirements|requirements]] to run PhpGedView.
* Download and unzip <tt>[http://downloads.sourceforge.net/phpgedview/PhpGedView-all-{{latest version|series=4.2.x}}.zip PhpGedView-all-{{latest version|series=4.2.x}}.zip]</tt> into a directory named <tt>phpgedview</tt> on your computer.
* Upload the <tt>phpgedview</tt> directory and all its contents to your web space using a method allowed by your ISP or [[Web_hosting|web host]].
* On the webserver, change the permissions of the following files and directories to be writable by the web server:
config.php
index/*
media/
media/thumbs/
* Point your browser to the directory where you uploaded your PhpGedView files (for example, http://www.yourserver.com/phpgedview/). You should now see a PhpGedView configuration screen. NOTE: make sure to have cookies enabled.
[[Image:Fig_3.jpg|centre|frame|Configuration Screen]]
* Enter the information required using the '?' help icons next to each label for guidance. You will need the MySQL database name, username and password provided by your ISP or web [[Web_hosting|web host]]. Click "Save".
* Enter the details of the PhpGedView administrator and click "Create User". 'NOTE: Password must be ≥ 6 characters.
[[Image:Fig_4.jpg|centre|frame|Create Admin User]]
* If you have not yet received any errors you will see a message like:
[[Image:Fig_5.jpg|centre|frame|Configuration Complete]]
* On the web server, change the permissions of the <tt>config.php</tt> file to be non-writable by the web server.
* You now have a clean PhpGedView installation ready for [[Add a GEDCOM|adding a GEDCOM]].

==Requirements==
Your [[w:ISP|ISP]] may provide you with the following services. If they do not, you will need to to find a suitable [[Web_hosting|web hosting]] solution.

; Web server
: A web server such as [http://httpd.apache.org/ apache] is required to serve the web pages over the internet.

; PHP v5.2+
: Your web server needs to be running [http://www.php.net PHP] version 5.2 or greater to generate dynamic HTML pages and use all of PhpGedView 4.2.x functions. A minimum 30 second script maximum execution is needed in your php.ini.
['''VERY IMPORTANT''' - You also need to install/enable PDO/mysql. This is a standard part of PHP, and allows PHP to connect to databases. This is a new requirement, effective from this version onwards. This improves performance, fixes the sqlite compatibility issues, and will allow a wider range of databases to be used.]

; Database
: You will need at least 1 database and a username and password to access it.
: PhpGedView primarily supports MySQL, but has also been tested and shown to work with Postgresql, SQLite, and SQL-Server. The versions required for each of these databases is outlined below:
: MySQL 4.1+
: PostgreSQL 8.0+
: SQLite available through PDO-SQLite which is included in PHP 5
: MS SQL-Server 2003+

; Web space
: At least 20MB of web space on the web server. You will need more than this if you intend to store [[w:multimedia|multimedia]] linked to individuals.

; GD Graphics Library (optional)
: You may wish to install the [[w:GD Graphics Library|GD Graphics Library]] which can then be used by PhpGedView for image manipulation such as creating thumnails. This can be important in saving bandwidth if large images (photos and scanned documents) are used in the genealogy.

; Freetype Library (optional)
: If [[w:Freetype|Freetype]] is installed, you will have access to the "Circle Diagram" in the Charts menu. You will also get better watermarking from the [[Media Firewall]].

; Calendar (optional)
: This is required for Jewish dates/calendars wish to be used.

; zlib (optional)
: If the web server being used by your ISP or [[Web_hosting|web host]] is the apache web server, it can be configured to send data over the internet in a compressed form using the [[w:zlib|zlib library]] - this will save bandwidth. To enable this compression, your ISP or [[Web_hosting|web host]] needs to add the following lines to the <tt>php.ini</tt> file:
php_flag zlib.output_compression On
php_value zlib.output_compression_level 5

Alternatively, your ISP or [[Web_hosting|web host]] may allow you to make these changes yourself. Simply create a file called <tt>.htaccess</tt> (including the leading dot) in your PhpGedView directory on the web server and add the above two lines to it.

==Installation==
You must be familiar with methods to transfer files to another computer.

The method used may depend on the [[w:OS|OS]] and the settings of your web space provider as well as your own computer abilities. It is not possible to address every combination, thus we will address the most generic way to do so - the use of a graphical [[w:File Transfer Protocol|File Transfer Protocol (FTP)]] client. An example of a [[w:Free_software|free]], [[w:Open_source|open source]] [[w:FTP_client|FTP client]] is [[w:FileZilla|FileZilla]] - feel free to explore other [[w:Comparison_of_FTP_clients|alternative clients]].

We aim not detail how to use an FTP client as this is best addressed by the documentation of the client you choose to use. We will however, detail the tasks that need to be undertaken with the FTP client. Another alternative, if your web space provider allows it, is to use an [[w:SSH_clients|SSH client]]. However, we assume that if you know about SSH, you will likely already know what to do, so we will not discuss it here.

===Obtaining PhpGedView===
There are [[Download_v4.2.x|several packages available for PhpGedView v4.2.x]], and you should decide which is most appropriate for your needs.

Once you have downloaded the appropriate file to your own computer, you will need to [[w:ZIP (file format)|unzip]] the file into a directory of it's own e.g. <tt>phpgedview</tt>

===Uploading PhpGedView to Your Web Space===
Next, you should use your FTP client to transfer the <tt>phpgedview</tt> directory and all it's contents to your web space. The contents of this directory is quite large (~37MB) so this could take some time depending on your internet connection speed. However, you probably won't need all those files. With careful pruning, the upload can be reduced to around 9MB. You can also use your host's control panel, such as [[w:cPanel|cPanel]], to upload the compressed zip or tarball archive and then extract it once it is on the server.

The <tt>phpgedview</tt> directory in your web space, will now be referred to as the "PhpGedView install directory".

===Setting File Permissions===
{{main|Setting File Permissions}}
In order for PhpGedView to function correctly, the web server hosting your PhpGedView installation needs to have the permission to save and modify files in a limited number of directories within your PhpGedView install directory. Your FTP client should be capable of allowing you to modify these permissions (called attributes in some clients). Briefly, you should make the following directories and files in your PhpGedView install directory writable by everyone:

index/* # comment: '*' means all files and folders in that directory
media/
media/thumbs/

Essentially, this will allow PhpGedView to save multimedia files on the server.

====More Secure Permissions====
If your web server is hosted on a [[w:Unix-like|Unix-like]] OS and you know enough about what permissions are and how to set them, you should set permissions rigidly for a more secure installation.
# Determine what "user group" the web server runs process as. e.g. Apache2 on Debian runs as "www-data" by default.
# Change the "ownership" of all directories and files under the PhpGedView install directory to be owned by you.
# Change the "group membership" of all directories and files under the PhpGedView install directory to be that of the web server.
# Ensure all directories and files under the PhpGedView install directory '''cannot''' be written by the group members.
# Set specified directories and files to be group writable.

If you have SSH access to your [[w:Unix-like|Unix-like]] web server, the following commands should take care of this. It assumes the web server is running with group membership of "www-data", and your username is YOUR_USERNAME):
chown -R YOUR_USERNAME ./phpgedview/
chgrp -R www-data ./phpgedview/
chmod -R g-w ./phpgedview/
chmod g+w ./phpgedview/index/
chmod g+w ./phpgedview/media/
chmod g+w ./phpgedview/media/thumbs/

===Online PhpGedView Configuration===
There exists a tool in PhpGedView that allows you to make changes to the PhpGedView configuration, this needs to be performed to complete the installation.

In order to do this, the web server must have permissions to write to the <tt>config.php</tt> file in the PhpGedView install directory to be able to save the changes.

WARNING: you should set <tt>config.php</tt> permissions back to not writable by the web server immediately after performing the configuration! Failing to do so will leave your PhpGedView installation at risk!

'''NOTE: you need cookies enabled to run the install script.''' This is not checked for. Without cookies enabled the install script fails in ways that point to other issues like not having the config.php file write-able or not having proper access to the database.

* Using the FTP client, set the permissions of <tt>config.php</tt> in the PhpGedView install directory to be writable by everyone. Alternatively, if you are using an SSH client you could issue the following command:
chmod g+w ./phpgedview/config.php

* Point your web browser to the PhpGedView install directory (for example, http://www.yourserver.com/phpgedview/). You should now see a PhpGedView configuration screen.
[[Image:Fig_3.jpg|centre|frame|Configuration Screen]]

* Enter all relevant information into the form, clicking the help ('?') icons for guidance. You will need the MySQL database name, username and password provided by your ISP or [[Web_hosting|web host]]. Click "Save".

* Extra Configuration tips for those with ISPs who do not host PHPGedview ( this advice relates to an ISP which uses the online control panel program called "cpanel" and the phpmyadmin and mysqldatabases utilities);
host name is "localhost",
database name is "accountname_name of database",
use mysqldatabases utility to create a database and then a user that can access the database. Again usernames may have been automatically prefixed with the ISP account name - use the mysqldatabases utility to see.

* Enter the details of the PhpGedView administrator and click "Create User". 'NOTE: Password must be ≥ 6 characters.
[[Image:Fig_4.jpg|centre|frame|Create Admin User]]

* If you have not yet received any errors you will see a message like:
[[Image:Fig_5.jpg|centre|frame|Configuration Complete]]

* Using your FTP client, change the permissions of the <tt>config.php</tt> file to be non-writable. If you are using an SSH client, make the <tt>config.php</tt> file non-writable by the group:
chmod g-w ./phpgedview/config.php

* You now have a clean PhpGedView installation ready for [[Add_a_GEDCOM|adding a GEDCOM]].

==Upgrading From a Previous Version==

Go to this page for [[Upgrading]]. It is usually a reasonably straightforward process, but can vary widely depending on your [[w:OS|OS]], your [[w:ISP|ISP]] etc.

=Post-Install Tasks and Configuration=

==License==
{{License}}

[[Category:PhpGedView]]
[[Category:Installation Guide]]

Limit access to related people

2010-05-30T15:32:06Z

Okbigkid:

{{glossary | description = Known as relational privacy, it limits a user's access to only people to which he or she is related. The [[Max relationship privacy path length|Max privacy length]] defines the radius of relations. This setting affects both access and editing privileges, since the user cannot edit information he or she canot see. ''Used in:'' [[Add a new user#Data fields|Add a New User]]}} [[Category:PGV Configuration Fields]]

Privacy File

2010-05-30T15:29:32Z

Okbigkid: /* Max. Relationship Path Length */

PhpGedView has a wide range of privacy settings. Most of them are configured in the "Privacy file", some in [[Configuration - Access and Privacy|Access and Privacy]] settings in the Gedcom configuration, and some in the Gedcom data using the [[Setting a Restriction|Restriction]] tag. The Gedcom Privacy configuration screen is divided into sections.

Many settings (like e.g. ''Show Sources'') have the same '''''Show to?''''' selection of options in a drop down menu:
* Show to public
* Show only to authenticated users
* Show only to admin users
* Hide even from admin users

Please remember to press the '''Save configuration''' button after your changes.
==General Privacy Settings==
You can have different Privacy settings for each GEDCOM on your PhpGedView web site. Check under the page title whether you are editing the correct GEDCOM.

You can override these general settings by using the other sections (''Privacy Settings by ID, User Privacy Settings, Global Privacy Settings'' and ''Facts Privacy Settings by ID'') on this configuration page.

===Show Dead People===
Set the privacy access level for all dead people. Default is ''Show to public''.

===Show Living Names===
Should the names of living people be shown to the public? Default is ''Show only to authenticated users''.

This sets $SHOW_LIVING_NAMES in xxx.GED_priv.php.

===Show Sources===
Set the privacy access level for all Sources. If the user does not have access to Sources, the Source list will be removed from the Lists menu and the Sources tab will not be shown on the Individual Details page. Default is ''Show to public'', recommended value is ''Show only to authenticated users''.

===Enable Clippings Cart===
The clippings cart allows users to add people to a temporary file that they can download in GEDCOM format for subsequent import into their genealogy software. Default is ''Show to public'', recommended value is ''Show only to authenticated users''.

===Show Research Assistant===

What type of user can view the Research Assistant module if it is installed? Default is ''Show only to authenticated users''.

This sets $SHOW_RESEARCH_ASSISTANT in xxx.GED_priv.php.

===Show Multi-Site Search===
Multi-site search allows users to search across multiple PhpGedView websites which you have setup in the Manage Sites administration area or remotely linked to. This option controls whether the Multi-site Search feature is available to everyone or only to authenticated users. Default is ''Show only to admin users''.

===Limit Privacy By Age of Event===
The Limit Privacy by age of event setting will hide the details of people based on how old they were at specific events regardless of whether they are dead or alive.

Use this setting along with the Age at which to assume a person is dead setting. For example, if you made the Age setting 100 and set this option to Yes, all persons, alive or dead, born less than 100 years ago would be set to private. People who were married less than 85 years ago and people who died less than 75 years ago would also be marked as private. Please note that using this option will slow down your performance somewhat.

This sets $PRIVACY_BY_YEAR in xxx.GED_priv.php.

===Use GEDCOM (RESN) Privacy Restriction===
The GEDCOM 5.5.1 specification includes the option of using RESN tags to set Privacy options for people and facts in the GEDCOM file. Enabling this option will tell the program to look for level 1 RESN tags in GEDCOM records. It means that it will honor restrictions for all data for '''Individual''' and '''Family''' if such restrictions are found in the Gedcom file. See [[Setting a Restriction|details on setting a Restriction]].

Level 2 and higher RESN tags are always applied and will not be affected by this setting. This means that restrictions on '''Facts''', '''Events''' for people and families are always honored by PGV.

Note that this might slow down some of the functions of PhpGedView such as the Individual list.

===Use Relationship Privacy===
'''No''' means that authenticated users can see the details of all living people. '''Yes''' means that users can only see the private information of living people they are related to.

This sets $USE_RELATIONSHIP_PRIVACY in xxx.GED_priv.php.

===Max. Relationship Path Length===
If Use relationship privacy is enabled, logged in users will only be able to see or edit individuals within up to this maximum number of relationship steps. Each user account has its own relationship privacy access level setting, which can not be set in excess of this master setting.

This sets $MAX_RELATION_PATH_LENGTH in xxx.GED_priv.php.

===Check Marriage Relations===
Check relationships that are related by marriage.

This sets $CHECK_MARRIAGE_RELATIONS in xxx.GED_priv.p

===Age at which to Assume a Person is Dead===
If this person has any events other than Death, Burial, or Cremation more recent than this number of years, he is considered to be "alive". Children's birth dates are considered to be such events for this purpose.

==Privacy Settings by ID==

These settings allow administrators to override default privacy settings for a particular object:
* An Individual
* A Family
* A Source
* A Multimedia Object
The override can either increase or decrease access to his object, compared to default setting in the [[#General Privacy Settings|General section]].

Suppose for example you have a child who died in infancy. Normally because the child is dead, its details would be shown to public users. However, you and everyone else in your family are still private. You don't want to remove the death record for the child but you want to hide the details and make them private. If this child had the ID of I100 you should enter the following privacy settings:
ID: I100
Show to: Show only to authenticated users

This works the other way as well. If you wanted to make public the details of someone (ID 101) who you know to be dead but don't have a death date for, you could add the following:
ID: I101
Show to: Show to public

You can add as many such restrictions as you want.

This sets $person_privacy in xxx.GED_priv.php.

==User Privacy Settings==
These settings allow administrators to override default privacy settings for a particular object:
* An Individual
* A Family
* A Source
* A Multimedia Object
- not for everyone but only for a particular '''User'''. This setting can be used to both decrease and increase access to the object, it could for example be used to allow the user to see an otherwise restricted object.

You can use any "Show to?" option, but they don't have their usual meanings: ''Show to public'' and ''Show only to authenticated users'' permit the user to see the object, while ''Show only to admin users'' and ''Hide even from admin users'' restrict the access to the object for this user.

Suppose you don't want the user "John" to be able to see any details of an individual with ID I100 in the GEDCOM, you could configure it like this:
Username: John
ID: I100
Show?: "Show only to admin users"
and details for the specified individual would be hidden for the user "John" only.

To show the details of I101 (which usually would be hidden because I101 is still alive) to user "John" set:
Username: John
ID: I101
Show?: "Show only to authenticated users"

This sets $user_privacy in xxx.GED_priv.php.

==Global Fact Privacy Settings==

This feature is meant to hide certain facts, identified by GEDCOM tags, for all individuals alive or dead. By default the SSN tag is hidden to public users. This is to prevent people from stealing social security numbers and committing identity theft of dead persons. This is probably mostly relevant for the USA.

The following fields should be selected:

;Name of fact
:A list displays the Gedcom Tags and corresponding names: select the one that should be hidden.

;Choice
:The Choice element specifies the fact itself or related details. If you select "Show fact details" to limit the restriction to details only, or "Show fact" to restrict fact '''and''' its details
;Show to ?
:Allows you to select the restriction level (see the list of levels at the beginnig of the article)

===Rules and limits===
;All tags can be restricted
:This means that not only Facts and Events, but all possible tags - the "Name of fact" combo box lists all tags available for restriction. For example you can restrict ''Repository (REPO)'' tag, which is used in Sources, hiding all repository references or ''Media Object (OBJ)'' tag, hiding all media references, or ''File Name (FILE)'' tag, hiding the file names in all Media Objects, etc.

;Only Display is affected
:You can hide only the display of the Tag on the object main screen (for example you can prevent displaying "Occupation" on the person's screen). All other occurences of this tag will still be visible, in particular in the "Raw Gedcom" view (Note: this may be abug - see [[#Known Problems/Bugs|Known Problems/Bugs]]). If you want to restrict a tag from some group of users, you need to restrict the view of the Raw Gedcom Record from the same group.

: Events such as Marriage, which have their own display, are not affected. Restricting the Marriage tag only hides the fact of marriage from the Individual display, not the Family created by this Marriage. The example given in the Help will in fact not hide all marriages.

;Only level 1 facts will be effected
:This means that only the Tags applicable to [[Gedcom data structure#Top level records in Gedcom|Top Level Records]] can be restricted this way. For example, if you restrict the ''Address (ADDR)'' fact, addresses in Individual record will be restricted, while addresses in ''Residence (RESI)'' fact will not. To hide person's and family addresses you need to set restrictions on both ADDR and RESI tags. Check the appropriate [[:Category:Gedcom Structures|Gedcom structure]] to see what will be restricted.

;Hiding the event also hides its details
: If you use "Show fact" in the ''Choice'' field for a restriction, you will restrict displaying the fact and its details. If you use "Show fact details" you will allow the display of the fact but not its details

;Hiding fact details does not hide it from editing
:Limiting the "Show fact details" to Administrators only does not hide the details from Editors if they open the editing screen.

In general, if you use this feature to restrict some details, it is recommended that you thoroughly test the results to make sure that the consequences of the settings match your intent.

This sets $global_facts in xxx.GED_priv.php.

==Facts Privacy Settings by ID==
This is an extension of the previous type, [[#Global Fact Privacy Settings|Global Fact Privacy Settings]]. While the former restricts all occurences of a specific Fact, here you can restrict the visibility of this Fact (or Tag) in a selected (by ID) object: '''Individual, Family''' or '''Source'''.

The first element is the ID of the person (family or source), the second element is the fact (fact type). The Choice element specifies the fact itself or related details. The Show to? element determines at what access level the fact is shown.

You could, for example, hide the Marriage record for a specific Individual, or a Media Object for a specific Source, or even a File name in a specific Multimedia Object.

This sets $person_facts in xxx.GED_priv.php.

{{known problems|Version 4.1|* ''Global Fact privacy Settings'' and ''Fact Privacy Settings by ID'' remove the Tags from display, but '''not from Raw Gedcom view'''. If [[Allow Users To See Raw Gedcom Records|viewing the Raw Gedcom]] is enabled, the Tag, even if restricted in this setting, may still be visible. This problem has been fixed in version '''4.1.4''' - the tags are removed both from display and from raw Gedcom}}


[[Category:Administrators Guide]]
[[Category:phpGedView]]



[[fr: Fichier de définition des paramètres de confidentialité]]

Add a new user

2010-05-30T15:25:42Z

Okbigkid: /* Data fields */

There are two distinct ways of adding a user. When the [[Configuration#Allow visitors to request account registration|Request new user account ]] option is active on the login screen, the user can register himself or herself. Alternatively, the administrator can create a user. The Administrator and the User form share some fields, and the Administrator can then approve (or reject) the new user. If enabled, user can update some fields in his or her account.

==Data fields==
[[image:4_add_new_user_1.jpg|frame|right|Administrator's "Add / Update User" screen, part 1]]
[[image:4_add_new_user_2.jpg|frame|right|Administrator's "Add / Update User" screen, part 2]]

[[image:My_Account.jpg|frame|right|Users "My Account" screen]]

;Username / Desired user name
:User name. The username is case sensitive. That means that John is not the same as john or JOHN. You should only use characters from the alphabets that PhpGedView supports. You may use uppercase and lower case letters with or without diacritical marks, numbers, dash (-), and underscore (_). Do not use punctuation marks or spaces. Avoid conflict with existing user names: both user and admin will be informed of a conflict, and given an opportunity to re-enter data.
;Firstname
:User's first name. Will be overwirtten by data users from Gedcom reord if ''Synchronize User Settings'' option is checked
;Lastname
:User's last name. Will be overwritten by data users from Gedcom reord if ''Synchronize User Settings'' option is checked
;Password / Desired password
: Type in a password here. Like user name, password is case sensitive. Password should be minium 6 characters long, the longer the better. You may use uppercase and lower case letters with or without diacritical marks, numbers, dash (-), and underscore (_). Do not use punctuation marks or spaces. Use a combination of upper and lower case, numbers, and other characters.
;Confirm Password
: Retype the password here. If the password and its confirmation are not identical, you will get a suitable error message. You will have to re-type both the original password and its confirmation.
;Change Language
:Select user's preferred / default language on multi-lingual sustems.
;GEDCOM INDI Record ID
: User's ID in the family tree. Upon login the user will be recognized as a member of the tree.
;Pedigree chart root person
: A Root person for default Pedigree chart. This Root Person does not need to be the user himself; it can be anybody. The user will probably want to start the Pedigree chart with himself. You control that, as well as the default Root person on other charts, here. If the user has Edit rights to his own account information, he can change this setting himself.
;Synchronize User Settings with GEDCOM Data
:Will use Gedcom data for person's name (it may change the name in the User screen) and will add / update Email address in the person's record.
;User can administer
:Designate this user as PGV Administrator
;Access level
:Available levels are:
::*Access (User)
::*Edit (Editor)
::*Accept (Acceptor)
::*Administer Gedcom (Gedcom Administrator)
:See [[Administrators Guide]] for description of access level privileges. If the installation has more than one Gedcom, you can select different level for each Gedcom
;Automatically accept changes made by this user
:Bypasses the default reviewing process. Use with caution, the admin and the user will not have the opportunity to review the changes. The user must also have accept privileges on the Gedcom in order for this setting to take effect.

;Limit access to related people
:Known as relational privacy, it attempts to limit user's access to only people to which he or she is related. The Max privacy length defines the radius of relations. This setting affects both access and editing privileges, since the user cannot edit information he or she canot access.
;Max relationship privacy path length
: Defines the radius of relatons accessible when relational provacy is activated (see above). You will be unable to set the length here to a higher level than the maximum length already defined in the GEDCOM privacy configurations.
;Email address
:User's email address. It is important to enter it here correctly, as it will allow user to recover a lost password. If Synchronization is selected (see above), it will be added (replaced) in user's Gedcom record.
;User verified himself
:It is marked automatically when the user confirms his or hers email address
;User approved by Admin
:User has been approved by admin.
:'''Warning:''' Both checkboxes, ''User verified himself'' and ''User approved by Admin'' '''must be checked''' for the account to be active. When the Administrator approves a self-registered user, he should check the ''User verified himself'' box as well.
;Change language
:In multi-lingual systems select the default (preferred) language for this user.
;My Theme
:Select the default theme for this user
;Preferred contact method
PhpGedView has several different contact methods. The administrator determines which method will be used to contact the user. Depending on site configuration, some of the listed methods may not be available.

{{Contact methods}}
;Visible to other users when online
:When this box is checked, the user, when online, will be visible to others, and will also be able to see others who are configured to be visible. When this box is unchecked, user online will be completely invisible to others, and also will not be able to see other online.
;Allow this user to edit his account information
:Checked by default, allows user to change his or her user account information. If checked, the user can make changes him/herself, editing his/her data (like Email address) and preferences, without bothering the Administrator.
;Default Tab to show on Individual information page
:This setting allows to specify which tab is opened automatically when this user accesses the Individual Information page. If allowed to edit their account, the user can change this setting later.
;Admin comments on user
:Any comments the Admin has on this user. Not visible to the user
;Admin warning at date
:Set a warning for Admin to check this account at a specific date.

==Adding a user by Admin==
Administrator can create a user using the form above. He should then inform the user of his / her username and password. The administrator must manually send an email to the user to let the user know that his account is active.

==Self registration==
[[Image:Request New User1.jpg|frame|right|Users "Request new user account" screen]]
If the [[Configuration#Allow visitors to request account registration|Request new user account]] option in the PGV configuration is enabled, the user can request a registration, and will be presented with a registration form. Together with the form, a privacy notice will be displayed, by default:

'''''Notice:''''' 
''By completing and submitting this form, you agree:''
* ''to protect the privacy of living people listed on our site;''
* ''and in the text box below, to explain to whom you are related, or to provide us with information on someone who should be listed on our site.''

The user is expected to fill in (in the Comments filed) the reason for requesting registration, if the site is restricted to family members (presumably the family connection). After submitting the form, the Administrator is informed (by email) and the user is sent email with code to verify his/her email address. The Administrator can then accept (or reject) the regisration. If he accepts, the account is still not active unless user verifies himself or the Admin checks the ''User verified himself'' checkbox. The administrator then must manually send an email to the user to let the user know that his account is active.

==User account update==
The user, if allowed (see ''Allow this user to edit his account information'' above), can edit some of his data on-line. This is a preferred method of user maitenance, as he/she can change the password, email address and other user data (see the ''My Account'' screen image above)

{{known_problems|Version 4.0|* The name collision is not properly detected for self-registered user, if the difference is only in letter case (e.g. Smith vs. smith). The process continues normally, but the account is not usable.}}


[[Category:Administrators Guide]]
[[Category:PhpGedView]]


[[fr:Ajouter un nouvel utilisateur]]