https://wiki.phpgedview.net/en/api.php?action=feedcontributions&user=MarekZ&feedformat=atomPGVWiki - User contributions [en]2024-03-29T08:02:55ZUser contributionsMediaWiki 1.34.2https://wiki.phpgedview.net/en/index.php?title=Backup_your_data&diff=11640Backup your data2009-07-24T12:29:11Z<p>MarekZ: Backup your data moved to Backup and Archive: Add Archive as part of the title to better reflect content</p>
<hr />
<div>#REDIRECT [[Backup and Archive]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Backup_and_Archive&diff=11639Backup and Archive2009-07-24T12:29:10Z<p>MarekZ: Backup your data moved to Backup and Archive: Add Archive as part of the title to better reflect content</p>
<hr />
<div>The data you collected are likely the result of hundreds (or thousands) of hours of work, your own or other contributors. Unlike transient documents, the expectation is that the fruits of this work will serve the next generations of researchers and interested viewers. One could look at the collected data as an archive, which could be visited perhaps 20, 50 or 100 years from now.<br />
<br />
It is imperative that that data is preserved against all kinds of disasters. Disasters can be as simple as a disk crash, which will occur with certainty, given time; the web provider can go out of business; the database will become obsolete (this is a certainty as well, with much shorter time span than the disk crash). Possibly the biggest danger is fading data formats. Who can read today documents written in a very popular in 1985 text editor PC-Write? It is difficult (or more precisely impossible) to predict the future of standards like Gedcom, and one needs to be vigilant and always look into the future. <b>Gedcom</b> appears to be stable for many years, is wildly popular, and is reasonably verbose, all of which add chances that (unlike PC-Write format) it will be decipherable in 20 years. One should also consider handing the work to one's sucessor. What data will he/she need if tomorrow I am unable or unwilling to continue?<br />
<br />
To begin with, general backup rules apply here: back up everything, automatically, with copies off-site. One could start with Wikipedia articles on [http://en.wikipedia.org/wiki/Backup Backup] and [http://en.wikipedia.org/wiki/Archive Archive]. In many cases your website provider does (more or less diligently) backups, and you may not have a control over it. Such procedures will, if properly applied, allow you to restore the current, live system, but not to prepare a migration unknown future. <br />
<br />
==Backing up and archiving==<br />
What are the data you need to backup and / or archive?<br />
<br />
<ol><br />
<li> The most valuable (or the most irreplaceable) are the results of genealogical research. They are candidates to both backup and archiving. They are stored in three (or possibly more) places: <br />
<ul><br />
<li><b>Gedcom</b> - textual genealogical data are stored in Gedcom file, or temporarily in a database but transferable to the Gedcom format file.</li><br />
<li><b>Media</b> - digital images of photos and documents, and all other records in one of many multimedia formats are stored as separate files on disk, in a hierarchy of directories.</li><br />
<li><b>Originals</b> (paper or other 'old' medium) of the material - records, photos, documents, etc., stored in a physical repository or in many of them. </li><br />
</ul><br />
<li>Difficult (but not impossible) to replace are the data on <b>users</b> of the system, their preferences and details, configuration and options, etc. Those need to be backed up, but a archiving is also a welcome option, as the future researcher may be interested in the users as well</li><br />
<li>Easiest to restore (but still may need some work) are the data used by various external plug-ins and modules. GoogleMap module may be an example here, where you might have added a lot of geo-data with your preferred method of identifying places. Back it up; archiving is probably not very important.</li><br />
</ol><br />
PhpGedView has several tools for exporting and backing the data. <br />
<br />
<br />
((Work in progress)</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Features_v4.1.x&diff=11595Features v4.1.x2009-06-21T20:37:03Z<p>MarekZ: Removed old "NEW" indicators</p>
<hr />
<div>==Charts and Lists==<br />
* PDF Reports - The reports menu allows you to generate nice PDF reports of your data for printing. XML report templates allow for simple creation of new reports.<br />
* Fan Chart - Get a unique view of an individual's ancestry using the Fan Chart.<br />
* Ancestry Chart - View the ancestry of a person including aunts and uncles and their spouses.<br />
* Zoom Chart Boxes - On charts you can allow visitors to zoom in on the boxes and get more information and bigger fonts.<br />
* Anniversary Calendar- Lists all of the events that happened on a given date. Filter the events to show only living people or only recent events.<br />
* Relationship Chart- Provides a visual reference of how two individuals link together.<br />
* Timeline Chart- You can now chart up to 6 people on a single timeline. From the timeline chart you can see how people's lives overlapped, find out how old they were at different times and chart the course of their life through time.<br />
* Multiple Generation Pedigree Chart - View as many generations as you want and quickly navigate up and down the pedigree tree. Click on any person or family to get their details.<br />
* General Keyword and Soundex Searches - Search the entire GEDCOM file for keywords or based on Soundex values of individuals last and first names.<br />
* Descendancy Chart Navigation - View descendency charts and move up and down the chart or easily switch branches with simple mouse clicks.<br />
* Place hierachy - Browse through all of the places in your GEDCOM file and quickly see who lived where. For example, start with browsing in the United States, then choose a state such as Arizona, then choose a county. At any time click on the view results link to see who lived in those areas.<br />
* Individual, Family, and Source Lists - View lists of the sources, families, and individuals broken down by surname<br />
* Photos and Multimedia - View photos and other multimedia items in the Multimedia list or attached to records in the Gedcom file.<br />
<br />
==Visitor Options==<br />
* RSS Feed - PhpGedview comes with an RSS feed generator for your users who like to view the latest updates read news through RSS feeds.<br />
* GEDCOM Clippings Cart - The clippings cart gives visitors to your site the ability to take Family Tree Clippings from your family tree, download them as a GEDCOM file and import them into their favorite family history program.<br />
* Print Preview Mode- Print your pedigree charts and any other page in PhpGedView without all the headers and footers--just the information that you want.<br />
* Multiple Language Support- PhpGedView has the best international support for alternate languages, dates, times, and sorting. PhpGedView is currently packaged with many languages including Chinese, Czech, Danish, Dutch, English, Finnish, French, German, Hebrew, Hungarian, Italian, Norwegian, Polish, Portuguese, Russian, Spanish, Spanish [Latin American], Swedish, and Turkish language files. Users can also change the language they are viewing when they visit your site.<br />
* Online Help - There is online contextual help for every page that your visitors can use to help them navigate the site and operate the many different functions in PGV.<br />
* Dynamic Menus - Dynamic drop-down menus make navigating the site quick and easy.<br />
<br />
==User Options==<br />
<br />
* MyGedView Portal - When users login to your site they will now have the option of using their MyGedView Portal. This portal allows them to keep a list of their favorite people, track messages, see a list of upcoming events, view today's events, and get a random picture. They can also see who else is logged on.<br />
* Customize the MyGedView Portal - Users can customize the location of blocks on their MyGedView portals. They can choose which blocks they want to see and where they should be located on the page.<br />
* View Private Data - When users login they will be given greater access to the private data based on the privacy settings chosen by the administrator. If you use relationship privacy they will only be able to see the data of living people they are related to within a certain distance.<br />
* Favorites - Users can keep bookmarks of their favorite people.<br />
<br />
==GEDCOM 5.5 Support==<br />
<br />
* Support for multiple spouses and families- no matter how complex your families may be, PhpGedView will correctly link them together.<br />
* Support for native GEDCOM multimedia objects - Add multimedia files to the scrapbooks in the programs on your home computer and upload them with your gedcom to instantly add photos, videos, or sound to your GEDCOM.<br />
* Excellent support for Notes and Sources - Click on a source and get the links to all the individuals and families that cite that source.<br />
<br />
==Site Administrator Options==<br />
<br />
* User Migration Tool - Easily migrate users and settings from index mode to MySQL mode or vice-versa.<br />
* Online Configuration - You don't have to edit any PHP or HTML files to configure PhpGedView. Simply upload the files and your gedcom and the configuration script automatically starts.<br />
* Multiple Gedcom Support - You can add as many gedcom to the site as you want. Each gedcom has its own configuration settings so that they can each have their own theme, language, and privacy settings.<br />
* Multiple Calendar Formats- PhpGedView allows administrators to show dates in alternate calendar formats such as Hebrew, Jewish, Hijri, and Arabic.<br />
* Access, Edit, Accept, and Admin user levels- Administrators may define users can set the editing level that users have when they login. With Access level they will only be able to view data. With Editing level, they will be able to edit data online. Accept users will be able to review and accept or under changes made by other users. Admin users will be able to upload Gedcom files and manage configuration and privacy settings for the gedcoms they can administer.<br />
* Privacy based on relationship - As an administrator you have the option of specifying if you want to use relationship privacy. With relationship privacy authenticated users can only see the details of individuals they are within a certain relationship radius to. See the Privacy Documentation for more information about using the unique privacy options of PhpGedView.<br />
* Privacy Setting Editor - Admins can easily customize the privacy settings for their Gedcom online. With these settings you can hide certain facts or privatize certain individuals in your Gedcom and specify the access level that is needed in order to view the data.<br />
* Choose a unique look with the provided themes - You can use the provided themes to give your site the look and feel you like.<br />
* Customizable Themes - Whether you know a little or lot of HTML you can customize the look and feel of the site by modifying one of the provided themes. The themes are made up of HTML template files and CSS style sheets.<br />
<br />
==Online Editing==<br />
<br />
* Merge Records - The merge records option can help you to see the differences between records in your gedcom file and choose how you would like to merge them.<br />
* Online Editing - Administrators can give users edit privileges to add, edit, and delete through online html forms.<br />
* Accept or Undo changes - Administrators are alerted when changes have been made online to the gedcom and they can choose to accept or undo those changes.<br />
* Change Diff View - Users with edit privileges can choose to view an online diff of the changes that have been made.<br />
* Add new people - You can add new people to the Gedcom as children or spouses.<br />
* Edit Names - You can edit the names of people in your gedcom file.<br />
* Add Parents, Children, and Spouses - You can extend your tree online by adding parents children and spouses online.<br />
* Replace your old genealogy program - PhpGedview allows you to replace your old genealogy application and do everything online.<br />
* Collaborate with Family - PhpGedview helps family members work together by allowing them to see all of the latest information and edit it online.<br />
* Remote GDBI Client - PhpGedView has teamed up with the GDBI project to provide a remote Java client that can be used to edit your genealogy data remotely.<br />
<br />
== Version Specific Features ==<br />
<br />
This section details features that have been introduced in the 4.1.x series since the 4.1.1 release. These should be reasonably small in number since most 4.1.x releases are simply bug fix releases.<br />
<br />
[[Category:PhpGedView]]<br />
[[Category:Version Features|4.1.x]]<br />
<br />
[[fr:Caractéristiques v4.1.x]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Features_v4.2.x&diff=11594Features v4.2.x2009-06-21T20:34:59Z<p>MarekZ: </p>
<hr />
<div>* Improvements to the external database structure, and a redesign of the internal data structures, for performance, flexibility and ease of maintenance.<br />
* More options for statistics and charting.<br />
* Improved multimedia handling.<br />
* Support for three new languages: Slovenian, Romanian and Indonesian.<br />
* Improved soundex searching for non-English languages.<br />
<br />
==See also==<br />
[[Features v4.1.x]]<br />
[[Category:PhpGedView]]<br />
[[Category:Version Features|4.2.x]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Administrators_Guide&diff=11593Administrators Guide2009-06-21T19:30:10Z<p>MarekZ: Corrected Upgrading link</p>
<hr />
<div><!-- #REDIRECT [[Administrators Guide v4.1.x]] !--><br />
(This page under development)<br />
<br />
==Intended audience==<br />
The PGV Administrator manages users who can have different roles (or privileges): <br />
<br />
*'''Site Administrator''' who can do and see anything on the site and can create new users.<br />
*'''Gedcom Administrator''' who can administer Gedcom configuration and privacy and accept changes.<br />
*'''Acceptor''' who has edit privileges, and who can also accept or undo changes made by others.<br />
------<br />
*'''Editor''' who can edit anything he or she can see. The changes he or she made need to be accepted by a user with higher access privileges. <br />
*'''User''' (authenticated user) has access to the MyGedView portal and can view all public data and those private data that are allowed by privacy settings. <br />
*'''Public visitor''' is a visitor that has not authenticated by entering a username and password. Default privacy settings do not give the public visitor an access to the data of living people. Public visitor cannot edit data. <br />
<br />
The division between topics covered in [[Administrators Guide]] and '''[[Users Guide]]''' runs more or less in the middle of this list: information in this guide is geared for the Site and Gedcom Administrators and also Acceptors, while the [[Users Guide]] covers topics for Ediors and Users, (and also Visitors), with some Acceptor topics as well. Sections below outline responsibilities of the Administrators.<br />
<br />
==PhpGedView==<br />
*Install, update and manage PGV<br />
:*[[Features v{{latest stable series}}|Features]]<br />
:*[[Download v{{latest stable series}}|Download]]<br />
::*[[Download v{{latest stable series}}]]<br />
:*[[Installation Guide v{{latest stable series}}|Install]]<br />
:*[[Upgrading]] (General instructions, all versions)<br />
::*[[Upgrading from 3.x to 4.x]]<br />
::*[[Upgrading from 4.0.x to 4.1.x]]<br />
::*[[Upgrading from 4.1.x to 4.2.x]]<br />
:* [[Perform maintenance|Perform periodic maintenance]] (logs, updates, backups, etc.)<br />
::* [[Database import/export/conversion utility]]<br />
*[[Configuration|Configure PGV]]<br />
<br />
:* [[Configuration of PhpGedView|A Guide to configuration functionality]]<br />
:* [[:Category:PGV Configuration Fields|A Glossary of configuration fields]]<br />
<br />
==Family Trees==<br />
*Import and maintain Gedcoms<br />
:*[[Starting a New Tree|Import or create the first Gedcom]]<br />
:*[[Manage GEDCOMs and edit privacy|Add and manage Gedcoms]]<br />
:*[[Configuration File|Configure Gedcom parameters]]<br />
:*[[Privacy File|Configure privacy]]<br />
*Verify and approve changes made by editors, manage media, places and other objects<br />
:*[[Accept / Reject Changes|Accept or reject changes]]<br />
:*[[Manage Media|Manage media]]<br />
:*[[Place Hierarchy List|Manage places]]<br />
:*[[Place Maps|Add and maintain place maps (optional)]]<br />
*Add and mange unlinked and duplicate objects<br />
:*[[Add an unlinked person]]<br />
:*[[Add an unlinked source]]<br />
:*[[Merge Records|Merge records]]<br />
*[[Research Assistant module|Maintain Research Assistant]]<br />
*Setup and manage multiple sites and site links (optional)<br />
:*[[How Remote Linking Works]]<br />
:*[[Remote Link Individuals Across Websites And Databases]]<br />
<br />
==Users==<br />
*[[User Administration|Add and manage users]]<br />
<br />
==User experience==<br />
*[[Welcome Page|Welcome page]]<br />
:*[[Blocks|Select and configure Welcome Page components (blocks)]]<br />
*Customize <br />
:*[[Themes|Themes]] <br />
:*[[Modify your theme|Customizing themes]]<br />
:*[[Modules|Add-on modules]]<br />
:*[[Integrate with CMS|Integration with Content Management Systems (optional)]]<br />
:*Modify the menu system (optional). There are two articles on this topic, the second approach required more extensive coding changes<br />
::*[[Build a New Menu|Build a custom menu]]<br />
::*[[Modify the toplinks menu]]<br />
*Write News, Policy rules etc.<br />
*[[Write and manage FAQ's]]<br />
:*[[Help - FAQ List|Sample FAQ entries]]<br />
:*[[Writing FAQ's in multiple languages]]<br />
*Manage languages<br />
:*[[Languages]]<br />
:*[[Configure supported Languages]]<br />
:*[[Translator tools|Translator tools]]<br />
:*[[Create New Language|Add a new language]]<br />
*[[Google Map module|Configure and update Google maps]]<br />
<br />
==See also==<br />
*Administrators menu in [[Administrators Guide v4.1.x]]<br />
*[[Admin Menu]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Create_New_Language&diff=11506Create New Language2009-03-28T12:54:00Z<p>MarekZ: </p>
<hr />
<div>{{stub}}<br />
<br />
Begin by editing file "includes/lang_settings_std.php". Copy one of the other<br />
language settings, and make the changes appropriate for the new language. I<br />
suggest you use Vietnamese as a guide, but empty the alphabet settings (they<br />
can be changed later). The order in which the various languages appear in this<br />
file doesn't matter. Although this file contains a lot of special characters,<br />
you MUST treat it as a plain ASCII text file. Do NOT attempt to get your text<br />
editor to display the non-ASCII characters in their correct form. The file<br />
is actually in UTF8 code without the self-identifying Byte Order Mark.<br />
<br />
The language name should be "sundanese", and the language shortcut should be<br />
"su". This is what you also enter in the file names in place of "vi", "en",<br />
or whatever other language you selected as a starting point.<br />
<br />
<br />
You also need to tell PhpGedView what name to display in English menus when<br />
it sees a reference to "sundanese". This is basically a definition of the language<br />
variable $pgv_lang["lang_name_sundanese"]. You will find the list of language<br />
names in file "languages/configure_help.en.php" between lines 539 and 562. <br />
The order of the entries is not important. In fact, you could even add your<br />
new language name anywhere else in the file. However, we ask that you not do<br />
this, since that would make maintenance of the language list more difficult.<br />
<br />
<br />
Once you have made these changes, PhpGedView will have "Sundanese" in the list<br />
of languages.<br />
<br />
Begin by editing the settings for that language. You need to enter the correct<br />
name in Sundanese, and you need to enter the alphabet in the correct sorting<br />
order, both upper and lower case. If you're using the Latin alphabet with diacritics<br />
(normally diacritics are guides to pronunciation), you also need to decide whether<br />
you want to use dictionary rules for sorting. Don't forget to mark the language<br />
as "active", and to select the correct flag (it should be "Indonesia.gif").<br />
<br />
<br />
When the Sundanese language is marked as "active", you can find it in the language<br />
selection menus. Initially, all text will be in English since you haven't made<br />
any translations. It's OK to have missing or empty language files.<br />
<br />
<br />
You can use the Translator tools to get PhpGedView to create a basic file that<br />
you can then edit (translate) on-line. To make this work, the "languages" directory<br />
MUST have full read/write/modify permissions for the world. This is the 0777<br />
permission set. Alternatively, you can make a copy of the English files and<br />
re-name them with "su" in place of "en" in the file name. You can then edit<br />
(translate) these files off-line using your favourite text editor.<br />
<br />
The method you use depends on your personal preference. I find it easier to<br />
edit off-line when I'm making a lot of changes.<br />
<br />
You MUST remember that the language files are in the UTF8 character set without<br />
that Byte Order Mark. This is important when you're editing the files off-line.<br />
<br />
Sources:<br />
<br />
By: [https://sourceforge.net/forum/message.php?msg_id=4968215 Gerry Kroll] (canajun2eh) - 2008-05-16 20:08<br />
<br />
<br />
[[Category:Administrators Guide]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=File:ChangeFamily.png&diff=11018File:ChangeFamily.png2008-06-21T20:34:28Z<p>MarekZ: Change family</p>
<hr />
<div>Change family</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Editing_People&diff=11016Editing People2008-06-21T19:31:29Z<p>MarekZ: /* Merging records */</p>
<hr />
<div>You always add a person as a relative of another, who is aleady in the database. (The Administrator can aslo add unlinked persons). There are several forms for adding people, trying to help you in the task by filling some fields (for example if you are adding a child, last name is aleady selected), but allowing you to change any information – you can also leave out any information that is not known. <br />
<br />
The most basic information about a person is Name, Gender, and basic facts of life: Birth, Death (and possibly Marriage). <br />
<br />
==Names==<br />
''Last Name'' is a relatively recent historical invention. Depending on the country, few hundred years ago people were known by their names (''John'') with possible addition of their professions ''Smith'' or a place where they lived (''Anaximenes of Miletus''). Later those nicknames were converted into the family names, which in some countries can be very complex. PGV gives you the tools to enter the names using the following fields:<br />
<br />
;Name<br />
:This is a display field, which will show the name as you enter data in other fields. By convention, the family name is enclosed in slashes „/” - this is how Gedcom recognizes the last name. You should try to make this name look like the usual way of writing the person's name, for example ''John D /Smith/'', ''Gustav /von Aschenbach/'', ''Arthur /Brown/ Jr'', ''Dr. Anna /Clark/'' etc. <br />
; Prefix<br />
: Name prefix, for example ''Mr, Dr, Sir, Don'' etc. <br />
;Given Names <br />
:One or more given names separated by spaces. If only initial is known, enter it here as well. You can indicate the preferred name with an asterisk after the name, e.g. ''John Arhur*''; in display the preferred name will be underlined. <br />
; Surname Prefix<br />
:Prefix that comes before the surname, like in German or Dutch ''Von, van, van der'' etc. Some common prefixes are already spelled out for you , just click on the name: ''al, da, de, den, dem, der, di, du, el, la, van, von''. The prefix will be displayed together with the surname like in ''Gustav /von Aschenbach/''. <br />
;Surname<br />
: Surname or most commonly used surname (if there are several), or surname acquired at birth, if applicable. <br />
;Suffix <br />
: Part that come after surname; typical suffixes are also spelled out for your convenience, ''Jr, Sr, I, II, III, IV, MD, PhD'', but you can add your own.<br />
; Nickname<br />
: Many people are commonly known by their nickname rather than first name; a nickname is usually acquired later in life, and is not part of formal name. <br />
;Married Name <br />
: Like ''Name'' it is an display field showing a complete Married Name <br />
;Married Surname <br />
:Typically after marriage wife's or husband's names change. You can enter here the name of a person as known after marriage. In searching for (or listing) people, the person can now be located both by her/his Surname and Married Name, which makes it easier to find him/her (and also causes double listing). <br />
<br />
If you use non-Latin alphabets such as Hebrew, Greek, Cyrillic or Arabic, and the administrator enabled additional tags, you will also see fields like '''Romanized''', '''Phonetic''', '''Hebraic''' etc., allowing you to store different versions of the name in several alphabets.<br />
<br />
===Multiple names===<br />
It is possible to add additional names to the person record. The preferred name should be listed first, and it is useful to add a note explaining the circumstances of changing the name. It is also possible to enter multiple Married Names (see Married Name above) <br />
===Editing / Deleting Names===<br />
The ''Options for individual'' menu allows one to edit any aspect of individual name. It is also possible to delete a name. When you delete the name, you do not delete the individual, he still exists with all the family link – his/her name will be listed as unknown.<br />
<br />
==Gender==<br />
Select the person's gender or leave as ''unknown''. Gender will be filled for you if you add a wife, husband etc, but you must remember to select the gender of a child. There is also a shortcut in adding a child, little icons [♂][♀] allow you to immediately add a boy or a girl. Gender can be later edited using the ''Options for individual'' menu item.<br />
<br />
==Birth – Marriage – Death==<br />
When adding a person, you have an option to immediately add his or her Birth date and place, Death date and place and , if you are adding wife or husband, Marriage place place and date. Make sure that you follow the rules for entering [[Dates]] and [[Place data]]. You can also add the Birth, Death and Marriage events later. <br />
<br />
==Quick Update form==<br />
The Quick Update form in the ''Options for individual'' menu allows you to quickly add, edit or delete multiple events and facts about a person. It is useful if you need to make a large number of changes. Please note, that the current version does not add nor edit the Residence fact, only an untimed Address record.<br />
<br />
==Merging records==<br />
{{main|Merge Records}}<br />
Sometimes the same person appears twice in the database. This can happen if you used two Gedcom files, when a person was added twice in his/her two different roles in the family, etc. PGV has a tool to merge both records into one, allowing you to select the facts and events that are relevant from either of the records. The tool requires Admin privileges and is available in the Admnistrator menu.<br />
<br />
==See also==<br />
*[[Editing Families|Editing families]]<br />
*[[Adding an individual|Adding an individual]]<br />
*[[Deleting an individual]]<br />
<br />
<br />
<br />
[[category:Users Guide]]<br />
<br />
[[fr: Ajouter une personne]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Editing_Families&diff=11015Editing Families2008-06-21T19:30:44Z<p>MarekZ: /* Merging records */ added link to main merge article</p>
<hr />
<div>A family is created automatically once you add a husband or wife to an existing person. A family has its own display page: you can get there from the ''Close Relatives'' tab on person's page, which shows all families the person is involved in. <br />
<br />
A person has at least two biological parents. If one of them is unknown, you can leave him/her as ''unknown'' person. You can also delete this person, and leave the family with a single parent only. <br />
<br />
==Adding children==<br />
You can add a child to a family on the individual page (the ''Close Relatives'' or families tab) or on the Family page. When adding a child to a family you can specify the role of the child, or Pedigree. The following roles are defined in the standard:<br />
*Birth<br />
*Adopted<br />
*Foster<br />
*Sealing<br />
*unknown<br />
<br />
Birth is the default selection. The child can belong to more than one family, and have different role in each. The Sealing is used chiefly in the Church of Jesus Christ of Latter-day Saints (LDS). The more complicated cases (e.g. child was not adopted but raised by another member of the family etc.) can be handled by selecting one of the options and adding a detailed explanation in the note. <br />
<br />
After adding an adopted child to a family, you can also add the details of the Adoption event to the child record, indicating, among others, which of the parents (or both) adopted the child. <br />
==Family events==<br />
You can add facts/events to the family as well as to the individual. There is a default set of ''family'' events, which, as almost everything in user interface, is configurable by the administrator. The family Events, Multimedia etc. are visible on the family page and on the pages of each of the spouses.<br />
<br />
==Merging records==<br />
{{main|Merge Records}}<br />
Sometimes the same family appears twice in the database. This can happen if you merged two Gedcom files, when two researchers work on the Gedcom at the same time, one adding a father and another a mother, creating two separate families instead of one, etc. PGV has a tool to merge both records into one, allowing you to select the facts and events that are relevant from either of the family records. The tool requires Admini privileges and is available in the Admnistrator menu.<br />
<br />
==See also==<br />
*[[Editing People|Editing people]]<br />
*[[Adding an individual to a single parent|Adding an individual to a single parent]]<br />
<br />
<br />
<br />
[[Category:Users Guide]]<br />
[[Category:PhpGedView]]<br />
<br />
[[fr:Ajouter des familles]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Search&diff=10938Search2008-04-28T20:30:42Z<p>MarekZ: </p>
<hr />
<div>PhpGedView has an extensive search facility, which can be found in the main Search menu with ''General search'', ''Soundex search'' and ''Search and replace'' items. In addition to the Search Menu and a quick search box on the top of the page, many data entry forms access search screens to locate a specific person, family, source, etc. The search results also depend on language, and the use of non-English languages in the Gedcom data poses its own challenges. <br />
<br />
==General search==<br />
General Search will search the selected records for any search term or phrase you enter. <br />
<br />
===Search options===<br />
;Enter Search terms<br />
: Enter your search criteria here. You can search not only for names, places, dates, but for any word or phrase likely to be found in the record. You can even search for the Gedcom tags (for example to find all records where number of children is recorded as an event, enter NCHI in this field). The search is case in-sensitive, you can enter search terms in upper, lower or mixed case. The wildcards are assumed before and after the search term, i.e. the search is not limited to whole words. For example search for ''Pete'' will return records of ''<u>Pete</u> Smith'', ''Will <u>Pete</u>rson'' and ''Dmitri Shostakovich'' born in St. <u>Pete</u>rsburg. See Dates below for special consideration of date searches.<br />
<br />
;Search for<br />
:This option really means ''Search In'' and the options are: <br />
:*Individual records<br />
:*Family records and <br />
:*Sources<br />
<br />
:You cannot search in the ''Repositories'' nor in ''Media Objects'' using this form, but you can find Media using a filter (only for tiles and file names) in the Media List. <br />
<br />
:The default is ''Individual'' - by default you search for a phrase in the Individual records. All names and individual events are to be found there. If you are looking for an event specific to couples (like the marriage event and its details), you should check the Family box. Some events, for example '''Residence''', '''Census''' etc. can occur both in family and indvidual records. If you don't check both boxes, you are likely to miss some results. When you check ''Sources'' you will (also if others are checked) search in the Source records. <br />
<br />
;Exclude Filter<br />
:The following "non-genealogical" tags and their content are excluded by default: File Name ([[FILE]]), File Format ([[FORM]]), Type ([[TYPE]]), Change Record ([[CHAN]]) and User [[_PGVU]], Submitter ([[SUBM]]) and Reference ([[REFN]]). You can remove this exclusion (for example if you are looking for Marriages, which Type is marked as Religous) by checking the "off" option.<br />
<br />
:In addition to these optionally excluded tags, the User ID ([[_UID]]) and Restriction ([[RESN]]) are always excluded, except for the administrator. <br />
<br />
;Associates<br />
:The "Associates" option makes PGV show all individuals or families to which the "hit" person has an "Association" relationship, as indicated by the existence of ASSO tags in that person's database record. For example, if person "A" is godparent to person "B" and this was indicated through an ASSO tag in person "A"'s database record, whenever person "A" is listed in the search results, person "B" will be listed too. (Needs verification - [[User:MarekZ|MarekZ]] 23:57, 25 April 2008 (EST))<br />
<br />
;Databases to search in<br />
:You can select, in which Gedcom to perfom the search - useful if the installation has more than one Family Tree.<br />
<br />
===Dates===<br />
The dates are recorded in Gedcom as DD MMM YYYY, for example ''15 JAN 1845'', and the search termas should be used the same way. You can enter ''year'', or ''month year'', or ''day month year'' (1845 or JAN 1845 or 15 JAN 1845) to locate people with events that occured on those dates. You '''must''' write the date in this order and use the english abbreviation for the month name. (See [[Dates| the article on Dates]] for more details on date formats). <br />
<br />
As an alternative to using the Search facility, you can use the '''Anniversary Calendar''' to obtain the same results. The calendar has the advantage of working in your language (in multi-lingual pages) and gives you a visual confirmation of your searches. You can additionally limit your searches in year ranges: you can search all events older than selected year, or filter for events that occured in the past 100 years. <br />
<br />
Dates that are approximate will generally be found, if the approximation is a modifier of the date: about ([[ABT]]), estimated ([[EST]]), calculated ([[CAL]]) or interpreted ([[INT]]). Only the limits of approximate dates ([[BET]] ... [[AND]]) and the of date periods ([[FROM]] ... [[TO]]) will be located using either method. For eaxmple if the event occured ''between March 1801 and September 1801'' searching for ''March 1801'' will find the event, searching for ''April 1801'' will not.<br />
<br />
===Regular expressions===<br />
<br />
You can use regular expressions in your search if you are familiar with them. For example, if you wanted to find all of the people who have dates in the 20th century, you could enter the search 19[0-9][0-9] and you would get all of the people with dates from 1900-1999. (Needs verification - [[User:MarekZ|MarekZ]] 06:00, 26 April 2008 (EST)<br />
<br />
==Soundex search==<br />
[http://en.wikipedia.org/wiki/Soundex Soundex] is a method of coding words according to their pronunciation. This allows you to search the database for names and places when you don't know precisely how they are written. PhpGedView supports two different Soundex algorithms that produce vastly different results.<br />
<br />
;Basic<br />
:This method was patented in 1918 by Russell<br />
<br />
;Daitch-Mokotoff<br />
:This method, developed in 1985 by genealogist Gary Mokotoff and later improved by genealogist Randy Daitch is more complex than the Basic method and produces much more accurate results, especially if used for names of people and places. <br />
<br />
Because the Basic method retains the first letter of the name as part of the resultant code, it is not very helpful when you are unsure of that first letter. The Basic algorithm is not well suited to names that were originally in languages other than English, and even with English names the results are very surprising. For example, a Basic Soundex search for Smith will return not only Smith, Smid, Smit, Schmidt, Smyth, Smithe, Smithee, Schmitt, all of which are clearly variations of Smith, but also Smead, Sneed, Smoote, Sammett, Shand, and Snoddy.<br />
<br />
A Soundex search using this method produces much more accurate results. It is also the preferred method in searching for any name with diacriticals (see Non-English searches below)<br />
<br />
==Search and replace==<br />
This option is available to Administrators. <br />
<br />
<u>Before you start</u>, make sure that the option [[Automatically accept changes made by this user]] is '''unchecked''' for you as the user. Search and Replace does not have its own review mechanism and relies on the built-in PhpGedView review system. <br />
<br />
You can use this feature to correct misspelling or other inaccurate information, and change almost any data in Gedcom, including tags. <br />
<br />
;Enter Search terms<br />
:All three types of records (Individual, Family and Sources) are searched for the string you type in this field.<br />
<br />
;Replace with<br />
:All instances of the search term that are found are replaced by the replacement term you typed here. If you leave this field blank, the instances of the search term will be deleted. <br />
<br />
;Search for<br />
: Here you can limit the scope of the search. By default, you can search everything (Entire record), in which case other options are disabled. If you uncheck this option, you can limit the search to:<br />
:*'''Individual Names ''' - search only in individual names fields. This means First and Last name is affected as well as the name prefixes and suffixes, but Married name is not.<br />
:*'''Place''' - search in place names only.<br />
:*'''Whole words''' - the search string you entered must be a whole word (and not part of another word).<br />
<br />
<u>Note:</u>. If only one instance of the search result is found, the replacement operation is not executed, and you are brought to the record where the term was found. You can do the replacement manually. <br />
<br />
After you click the "Search" button (this is the scary part) all the replacement are completed, and you are presented with the lists of the three record types: Individuals, Families and Sources, in which the search term was replaced. At this point you can review the changes (see "Before you start" at the top of this section). Click the '''Accept / Reject Changes''' option at the bottom of the page, which will bring you a reviewer's screen, listing all the changes. You can view the difference in each case and approve the changes one-by-one. If you are satisfied you can approve them all, if not, you can undo all changes with one click and start again. If you skip some approvals, they will wait for your action in the 'suspended' state until you return to the ''Accept / Reject Changes'' screen.<br />
<br />
==Quick Search==<br />
There is a search box for a quick search on each page - you enter the search term and press the arrow icon to perform a search. It uses the same search meachnism as General Search, with all three Search In items checked (Individual, Family and Sources) and with all databases selected. <br />
<br />
==Non-English searches==<br />
<br />
If your database has mostly '''English''' names, the General seach works well enough. For '''non-English''' families, there are language and culture based issues.Some examples are:<br />
; Letters with diacriticals <br />
: The General search is exact, i.e. it will not return a result if you substitute Muller or Mueller for Müller, or Lodz for Łódź. Spelling of names change when the people emigrate, especially in the USA, where the diacriticals are very often ignored. The dataase may have variants of the name with and without diacritical signs. <br />
; Declension<br />
: In many languges names undergo declension depending on gender, (e.g. the daughter of Kowalski is Kowalska: looking for Kowalski misses all his daughters, looking for Kowalska may find his wife only if the Married name is added, but will miss her sons). <br />
All such issues cause incomplete search results. Currently the best remedy is to use the Soundex Search with Daitch-Mokotoff type, as described above.<br />
<br />
{{known problems|Version 4.1.4|The General search fails for characters with diacriticals and mixed-case searches. See the [https://sourceforge.net/tracker/index.php?func&#61;detail&aid&#61;1852202&group_id&#61;55456&atid&#61;477079 tracker ticket related to this issue]. When looking for strings with diacriticals, always use the Soundex (Daitch-Mokotoff) search. }}<br />
<!-- replaced the equals sign with &#61; in the URL to make it work --!></div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Dates&diff=10902Dates2008-04-25T17:20:57Z<p>MarekZ: /* See Also */</p>
<hr />
<div>Dates are very important in genealogy, and most editing screens have place for entering date. There are two types of dates that can be entered:<br />
* Date / Time of an event <br />
* Date period for extended period of time. <br />
Date / Time is a single point in time continuum, date period is defined by the beginning and end dates.<br />
<br />
If entered correctly, dates are understood by the program, and are used in calculating and displaying data on the time scale. [[PGV]] (and GEDCOM standard) are very flexible in how dates can be entered, and account for most cases found in genealogy. If absolutely necessary, date can also be entered as a free form text, but with a loss of functionality. <br />
<br />
== Date / Time ==<br />
<br />
# One enters the ''date / time events'' as DD MMM YYYY: day (as number), month (as abbreviation in English) and year (as number), e.g. '''12 Jan 1907'''. If you are using non-English version, the month will be translated in display, but not in data entry; use English month abbreviation. <br />
# If some part of the date is not known, you can skip it, e.g. '''Jan 1907''' or '''1907'''<br />
# If you are unsure of the information, you can use the approximation: ''[[ABT]]'' (about), e.g. '''[[ABT]] Jan 1907''', or the limits between which the event occurred: ''[[BET]]'' .. ''AND'' (between - and) e.g. '''[[BET]] 1 Jan 1907 AND 20 Mar 1907'''. One-sided limit of approximation allows you to use [[BEF]] (before) and [[AFT]] (after), if the event is known to occur before or after some date. <br />
# Less frequently used, but allowed are the details on the approximate date: ''[[EST]]'' (estimated), ''[[CAL]]'' (calculated for example from another date and period) and ''[[INT]]'' (interpreted). In case of [[INT]], you should add the base of the interpretation in the date field. Alternatively you can use ''[[ABT]]'' and enter the details in the note field. Examples: '''[[EST]] 1907''', '''[[CAL]] 1907''', '''[[INT]] 1907 (two years before marriage)'''.<br />
<br />
PGV displays a calendar as an aid in entering dates. There is a field for time as well; the format is hh:mm (24-hour or 'military' clock). <br />
<br />
== Date period ==<br />
<br />
{{main|DATE_PERIOD}}<br />
<br />
For events that occurred over a period of time you should use a [[DATE_PERIOD]] construct using ''[[FROM]] .. [[TO]]''. For example '''[[FROM]] 1907 [[TO]] 1911''' or '''[[FROM]] 15 Jan 1907 [[TO]] Dec 1911'''. If one end of the period is unknown, you can use only ''[[FROM]]'' or only ''[[TO]]''. The rules for approximate dates listed above also apply here.<br />
<br />
== See Also ==<br />
<br />
; GEDCOM Terms<br />
: [[DATE_APPROXIMATED]]:<br />
:: [[ABT]], [[EST]], [[CAL]]<br />
: [[DATE_PERIOD]]:<br />
:: [[FROM]], [[TO]]<br />
: [[DATE_RANGE]]:<br />
:: [[BET]], [[AFT]], [[BEF]]<br />
: [[INT]]<br />
<br />
[[category:PhpGedView]]<br />
[[Category:Users Guide]]<br />
<br />
[[fr: Dates]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=FAQ:Creating_relationships&diff=10874FAQ:Creating relationships2008-04-23T17:03:35Z<p>MarekZ: </p>
<hr />
<div>==I have been having problems adding an existing person as a Father to another existing person.== <br />
<br />
For instance, If I have both father and mother in the database already and I want to add a new son, how can I do this without editing the gedcom files?<br />
<br />
The problem is that some of my users cannot quite understand what it takes to edit gedcom records.<br />
<br />
Also, '''how do I add an existing person as a second wife to an existing male?'''<br />
<br />
Also, '''how do I add an existing person to a father if I do know that the existing wife is not the mother and I do not know who the mother is?'''<br />
<br />
Thank you for the help. This has been a great program.<br />
<br />
=== General Answer ===<br />
<br />
Editing GEDCOM is not a good idea unless you ''really'' understand the format. It’s been suggested the option be removed, but folks who know how to do it don’t want to lose the capability.<br />
<br />
There are alternatives: '''at least''' nine ways to add or change links to relatives.<br />
*Seven are on the “Close Relatives” tab of an Individual Information page.<br />
*Four of them are on the “Quick Update” pop-up.<br />
*Two of them are in the “Edit Family” menu in the “Options for family” box on a Family Information page.<br />
<br />
'''See also:''' [[Adding an individual]]<br />
<br />
=== Detailed Examples ===<br />
<br />
==== Add existing person as a spouse ====<br />
<br />
Do not use a person's Quick Update pop-up for this. “Add a new spouse” means create a new individual ''and'' make that person the spouse. (Also note that “spouse/wife/husband” in the context of GEDCOM doesn’t require an actual legal marriage.)<br />
<br />
#Select the “Close Relatives” tab on the person’s Individual Information page<br />
#Select “Add a (spouse) using an existing person”<br />
#Enter the ID of the person in the “Wife” (“Husband”) box '''''OR'''''<br />
##Click the little person icon next to the box<br />
##Enter some or all of the spouse’s name<br />
##Click “Filter”<br />
##Click on the spouse’s name to dismiss the search list and enter the ID<br />
#If you know they were married, check that box.<br />
#If you know any of the other facts, fill them in. (See [[where?]] for tips on the place and date entry features.)<br />
#Click “Set link.” Another window will appear, hopefully without an error message.<br />
#You don’t have to use the “Close Window” link, but if you do, it will cause the Individual Information page to refresh, showing the new information. (Caution: In ''some'' situations in ''some'' versions of PhpGedView, this may take you to the page of a different person or even a nonexistent person. This seems to be fixed in 4.1.3)<br />
<br />
==== Add an existing person as a parent (or a sibling) ====<br />
<br />
'''Note:''' This is an example of “Quick Update,” which many people feel should only be used by folks who understand its limitations. It does not support everything that should normally be done in an edit (SOURces, for example). The more detailed alternative is near the bottom of the “Close Relatives” tab.<br />
<br />
On the child’s (or sibling’s) Individual Information page, select “Quick Update” from the “Edit Menu.”<br />
<br />
Select the “Family With Parent” tab.<br />
<br />
Click “Add a new father” (or mother). If this person already has that parent linked, the option will not be available.<br />
<br />
This tab will also let you add siblings of the person, even if one or both parents are undefined.<br />
<br />
'''Note:''' The “Children” section is for adding people already in the database; “Add a new child to this family” will create a new person '''''and''''' make him or her a sibling.<br />
<br />
[[Category:How To]]<br />
[[Category:FAQ]]<br />
[[Category:PhpGedView]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Creating_relationships&diff=10873Creating relationships2008-04-23T16:59:31Z<p>MarekZ: Creating relationships moved to FAQ:Creating relationships: This is a FAQ item</p>
<hr />
<div>#REDIRECT [[FAQ:Creating relationships]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=File:Anniversary_Calendar.png&diff=10867File:Anniversary Calendar.png2008-04-23T14:34:32Z<p>MarekZ: Anivarsary Calendar</p>
<hr />
<div>Anivarsary Calendar</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=File:Fam_List.png&diff=10863File:Fam List.png2008-04-22T18:32:02Z<p>MarekZ: Family List header</p>
<hr />
<div>Family List header</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=File:Indi_List.png&diff=10862File:Indi List.png2008-04-22T18:31:15Z<p>MarekZ: Individual List Header</p>
<hr />
<div>Individual List Header</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=File:PlusMinus.png&diff=10855File:PlusMinus.png2008-04-22T03:37:56Z<p>MarekZ: Plus Minus</p>
<hr />
<div>Plus Minus</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=File:Sub_Diagrams.png&diff=10854File:Sub Diagrams.png2008-04-22T02:55:14Z<p>MarekZ: uploaded a new version of "Image:Sub Diagrams.png"</p>
<hr />
<div>Sub diagram</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=File:Arrow.png&diff=10852File:Arrow.png2008-04-22T02:53:46Z<p>MarekZ: Arrow</p>
<hr />
<div>Arrow</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=File:Zoom.png&diff=10851File:Zoom.png2008-04-22T02:53:23Z<p>MarekZ: Zoom</p>
<hr />
<div>Zoom</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=File:Link_to_charts.png&diff=10850File:Link to charts.png2008-04-22T02:52:44Z<p>MarekZ: Link to charts</p>
<hr />
<div>Link to charts</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Privacy&diff=10839Privacy2008-04-17T20:52:55Z<p>MarekZ: </p>
<hr />
<div>[[PhpGedView]] has been designed to give you many privacy options that can be different for each Gedcom installed on your site.<br />
<br />
The default privacy module that comes packaged with PhpGedView has the following features:<br />
<br />
* Option to hide details of living people<br />
* Option to hide the names of living people<br />
* Ability to limit the display of certain types of facts. For example you can hide all social security numbers, or all notes.<br />
* Ability to override default privacy setting on a user, individual, family, and source basis.<br />
* Five levels of access: public, user, editor, accept, and admin. Public accessible items may be viewed by all visitors to your site. User accessible items may only be viewed by authenticated users. Edit users can edit information online. Accept users can approve or undo changes made online by edit users. Admin accessible items are only viewable by users with admin status.<br />
* Option to only allow relatives to view the details of living people.<br />
<br />
Admin users easily can modify the file <code>privacy.php</code> by clicking on the Edit Privacy option on the Manage Gedcoms admin page.<br />
<br />
An alternative privacy module that will also hide all people who died less than 75 years ago, people who were married less than 85 years ago, and people who were born less than 100 years ago is available to download [http://sourceforge.net/tracker/index.php?func=detail&aid=898314&group_id=55456&atid=477081 here].<br />
<br />
''See also:''<br />
<br />
* [[Configuration - Access and Privacy| Configuring global privacy (for the whole site)]]<br />
* [[Privacy File|Configuring privacy in your Gedcom]] <br />
* [[Media Firewall|Confuguring Media privacy]]<br />
* [[Setting a Restriction| Setting a restriction on individual Event]]<br />
* [[FAQ:Privacy|Privacy FAQ]]<br />
<br />
[[Category:PhpGedView]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Research_Assistant_module&diff=10833Research Assistant module2008-04-17T03:22:36Z<p>MarekZ: </p>
<hr />
<div>{{stub}}<br />
This article needs a description about what the Research assistant module is. --[[User:Nathanhaigh|Nath]] 17:31, 31 October 2007 (EST)<br />
<br />
The Research Assistant allows users to create and manage “research tasks” where they enter descriptions of the research and track work progress. These research tasks can be associated with '''individuals''' or '''families''' from the genealogy data. Research tasks can be assinged to different researchers and organized into folders. The Research assistant has also tools to show missing information and the most probable places to look for it. <br />
<br />
<br />
<br />
[[Adding a Source|Adding a Source]]<br><br />
[[Adding a Folder|Adding a Folder]]<br><br />
[[Adding a Task|Adding a Task]]<br><br />
[[Auto Generate Tasks|Auto Generate Tasks]]<br><br />
[[Auto Search Assistant|Auto Search Assistant]]<br><br />
<br />
<br />
[[fr:Assistant de recherche]]<br />
[[da:Efterforskningassistent]]<br />
[[Category:Users Guide]]<br />
[[Category:Modules]]<br />
[[Category:PhpGedView]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Language&diff=10811Language2008-04-14T15:38:02Z<p>MarekZ: </p>
<hr />
<div>{{glossary | description = Assign the default language for the site. When the [[Allow User To Change Language|Allow user to change language]] option is set, users can override this setting through their browser's preferred language configuration, configuration options on their Account page, or through links or buttons on most PhpGedView pages. If the GEDCOM configuration allows the user to change languages, the user is limited to the languages selected in the main configuration. If the GEDCOM configuration does not allow the user to change languages the user is limited to the default language set in the GEDCOM configuration.<br/><br/>''Used in:'' [[Configuration - GEDCOM Basics#Language|Gedcom Configuration – Basics]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Use_FTP_clients&diff=10794Use FTP clients2008-04-13T22:53:18Z<p>MarekZ: </p>
<hr />
<div>Start FileZilla/Fetch and log in to your web space. Drag/copy all files and folders in "work" to "family". Simply double click on filenames and folders in the left-hand pane. You can monitor progress in the lower pane. (Mac users - what happens?)<br />
<br />
As a check, make sure you have the same number of folders, files and bytes in “family” as you have in “work”<br />
<br />
[[Image:Fig_1.jpg|center|450px|thumb|Figure 1]]<br />
<br />
There is some minor housekeeping required. Files and folders have “attributes” – these allow (or disallow) you from reading from, writing to, and executing their contents. If you still have your FTP connection open, find config.php in the right pane, then right-click on the file name and select “File attributes…”<br />
<br />
[[Image:Fig_2.jpg|center|300px|thumb|Figure 2]]<br />
<br />
The “numeric value” box shows you what is termed “chmod”, which reflects the attribute or permission allowed. Try clicking a few boxes on and off – for example, to allow users to write to the file config.php, click on the two empty “Write” boxes. chmod will change from 644 to 666. Then tick the 3 Execute boxes, and chmod will be 777. Leave them ticked for now – this file needs these permissions set this way. Later, when your site is set up and configured, you will be asked to come back to this point and make chmod 644 again.<br />
<br />
While you’re doing this, right click on the icon for the “index” folder, and make chmod equal to 777. Set this same value for the “media” folder.<br />
<br />
''See also:'' [[Setting File Permissions]]<br />
[[Category:How To]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Security_of_Config.php&diff=10793Security of Config.php2008-04-13T22:51:34Z<p>MarekZ: </p>
<hr />
<div>phpGedView requires you as the system administrator to control the file access permissions for config.php.<br />
<br />
==Make config.php writeable==<br />
<br />
To configure phpGedview via the web interface, you must make config.php writeable.<br />
<br />
===Unix===<br />
In Unix style environments, do this by setting file permissions for config.php to 777. One way to do this is to open a terminal, change to the phpGedView directory, and issue the following command.<br />
<br />
chmod 777 config.php<br />
<br />
==Secure config.php after configuration==<br />
For security, after configuration, you should remove write permissions from config.php. As long as write permissions remain on config.php, the phpGedView administration panel will present a warning.<br />
<br />
===Unix===<br />
<br />
chmod 555 config.php<br />
<br />
==See also==<br />
* '''[[Setting File Permissions]]''' <br />
<br />
<!-- Category links...DO NOT DELETE --><br />
[[Category:Administrators Guide]]<br />
[[Category:phpGedView]]<br />
<br />
<br />
<!-- Language links...DO NOT DELETE --><br />
<br />
[[fr:Sécurité de config.php]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Talk:Upgrading_from_4.0.x_to_4.1.x&diff=10770Talk:Upgrading from 4.0.x to 4.1.x2008-04-11T13:41:20Z<p>MarekZ: New page: Added the "Download Gedcom" step. It is good practice to have a backup copy handy anyway. It turned out that my 4.1 version did not correctly update the Gedcom file with Media objects, and...</p>
<hr />
<div>Added the "Download Gedcom" step. It is good practice to have a backup copy handy anyway. It turned out that my 4.1 version did not correctly update the Gedcom file with Media objects, and after re-import I lost about 50% of my Media references (not Media files, but Media Objects). Fortunately I had a freshly Downloaded Gedcom that saved the day. <br />
<br />
Added "Save the GoogleMap API" step = the Google Maps will stop working after upgrade and need reactivvation with original key. <br />
<br />
Added "Re-activate modules" step - some modules (Google Map, Message Forum.. do not work after upgrade. I am lookig for Wiki documentation on upgrading PunBB (there is an istallation article [[How to install PunBB Forum]]).<br />
[[User:MarekZ|MarekZ]] 23:41, 11 April 2008 (EST)</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Manage_GEDCOMs_and_edit_privacy&diff=10751Manage GEDCOMs and edit privacy2008-04-09T15:44:14Z<p>MarekZ: Redirecting to Manage Gedcoms</p>
<hr />
<div>#REDIRECT [[Manage Gedcoms]]<br />
<br />
__NOTOC__<br />
<br />
After selecting this option the Administrator will be presented with the graphical menu shown below. The options that can be access from this menu are shown on the left. With the exception of the Default GEDCOM selection box the same menu items will be displayed for EACH GEDCOM file present on the system.<br />
<br />
<table cellspacing=5 width=";75%"; border=";0";><br />
<tr><br />
<td width=40% valign=top><br />
*'''Menu Items'''<br />
**[[Default GEDCOM|Default GEDCOM]]<br />
**[[Add GEDCOM|Add GEDCOM]]<br />
**[[Upload GEDCOM|Upload GEDCOM]]<br />
**[[Create a new GEDCOM|Create a new GEDCOM]]<br />
**[[Admin Menu|Return to the Admin menu]]<br />
**GEDCOM file<br />
***[[Import GEDCOM|Import GEDCOM]]<br />
***[[Delete GEDCOM|Delete GEDCOM]]<br />
***[[Download GEDCOM|Download GEDCOM]]<br />
**Configuration File<br />
***[[Configuration File|Editing Configuration File]]<br />
**Privacy File<br />
***[[Privacy File|Editing Privacy File]]<br />
</td><br />
<td width=60% border=0 valign=top align=left><br />
[[Image:4_gedcoms.jpg|thumb|450px|left| Menu Dislayed to User -Click to Enlarge Image]]<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
<!-- Category links...DO NOT DELETE --><br />
[[Category:Administrators Guide]]<br />
[[Category:phpGedView]]<br />
<br />
<br />
<!-- Language links...DO NOT DELETE --><br />
<br />
[[fr:Gérer les fichiers GEDCOM]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=File:Import_Options.jpg&diff=10738File:Import Options.jpg2008-04-09T02:38:13Z<p>MarekZ: Import Options</p>
<hr />
<div>Import Options</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=File:Validate_Gedcom.jpg&diff=10733File:Validate Gedcom.jpg2008-04-08T21:58:05Z<p>MarekZ: Validate Gedcom</p>
<hr />
<div>Validate Gedcom</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Talk:Import_GEDCOM&diff=10724Talk:Import GEDCOM2008-04-08T13:32:07Z<p>MarekZ: </p>
<hr />
<div>I moved the intro section to the [[manage Gedcoms]] article. Plan to expand this article to show all the Import step options.</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=File:Current_Gedcoms.jpg&diff=10719File:Current Gedcoms.jpg2008-04-08T03:33:29Z<p>MarekZ: uploaded a new version of "Image:Current Gedcoms.jpg"</p>
<hr />
<div>Current Gedcoms</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=RSS_Format&diff=10712RSS Format2008-04-07T20:57:46Z<p>MarekZ: New page: {{glossary | description = The format to be used as the default feed format for the site. The numeric suffixes <u>do not</u> indicate version: they identify formats. For example, RSS 2.0 ...</p>
<hr />
<div>{{glossary | description = The format to be used as the default feed format for the site. The numeric suffixes <u>do not</u> indicate version: they identify formats. For example, RSS 2.0 is not newer than RSS 1.0, but a different format. Feed readers should be able to read any format.<br /><br />This [http://en.wikipedia.org/wiki/RSS Wikipedia article] contains comprehensive information and links about RSS and the various RSS formats.<br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#RSS Format|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Robots_Meta_Tag&diff=10711Robots Meta Tag2008-04-07T20:56:16Z<p>MarekZ: New page: {{glossary | description = The value to place in the Robots meta tag in the HTML page header. Some robots or web crawlers ignore this value. <br/><br/>''Used in:'' [[Configuration - Web S...</p>
<hr />
<div>{{glossary | description = The value to place in the Robots meta tag in the HTML page header. Some robots or web crawlers ignore this value. <br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Robots Meta Tag|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Publisher_Meta_Tag&diff=10710Publisher Meta Tag2008-04-07T20:55:39Z<p>MarekZ: New page: {{glossary | description = The value to place in the Publisher meta tag in the HTML page header. Leave this field empty to use the full name of the Genealogy contact. <br/><br/>''Used in:...</p>
<hr />
<div>{{glossary | description = The value to place in the Publisher meta tag in the HTML page header. Leave this field empty to use the full name of the Genealogy contact. <br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Publisher Meta Tag|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Page-type_Meta_Tag&diff=10708Page-type Meta Tag2008-04-07T20:53:44Z<p>MarekZ: New page: {{glossary | description = The value to place in the Page-type meta tag in the HTML page header. <br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Page-type Meta Tag|...</p>
<hr />
<div>{{glossary | description = The value to place in the Page-type meta tag in the HTML page header. <br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Page-type Meta Tag|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Page-topic_Meta_Tag&diff=10706Page-topic Meta Tag2008-04-07T20:52:37Z<p>MarekZ: New page: {{glossary | description = The value to place in the Page-topic meta tag in the HTML page header. Leave this field empty to use the title of the currently active database. <br/><br/>''Use...</p>
<hr />
<div>{{glossary | description = The value to place in the Page-topic meta tag in the HTML page header. Leave this field empty to use the title of the currently active database. <br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Page-topic Meta Tag|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Main_Website_URL&diff=10705Main Website URL2008-04-07T20:51:52Z<p>MarekZ: New page: {{glossary | description = Each PhpGedView page includes a link to your main Home page. The appearance of this link is controlled by the theme being used. You enter the actual URL to you...</p>
<hr />
<div>{{glossary | description = Each PhpGedView page includes a link to your main Home page. The appearance of this link is controlled by the theme being used. You enter the actual URL to your Home site here.<br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Main Website URL|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Main_Website_Text&diff=10704Main Website Text2008-04-07T20:51:20Z<p>MarekZ: New page: {{glossary | description = The legend used to identify the link to your main Home page.<br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Main Website Text|Gedcom Conf...</p>
<hr />
<div>{{glossary | description = The legend used to identify the link to your main Home page.<br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Main Website Text|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Keywords_Meta_Tag&diff=10703Keywords Meta Tag2008-04-07T20:50:40Z<p>MarekZ: New page: {{glossary | description = The value to place in the Keywords meta tag in the HTML page header. Some search engines will use the Keywords meta tag to help index your page.<br /><br />The ...</p>
<hr />
<div>{{glossary | description = The value to place in the Keywords meta tag in the HTML page header. Some search engines will use the Keywords meta tag to help index your page.<br /><br />The Most Common Surnames list that appears in the GEDCOM Statistics block on your Welcome page can also be added to anything you enter here. <br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Keywords Meta Tag|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=How_Often_Should_Crawlers_Revisit_Meta_Tag&diff=10702How Often Should Crawlers Revisit Meta Tag2008-04-07T20:49:54Z<p>MarekZ: New page: {{glossary | description = The value to place in the Revisit meta tag in the HTML page header. Some web crawlers ignore this value. <br/><br/>''Used in:'' [[Configuration - Web Site and M...</p>
<hr />
<div>{{glossary | description = The value to place in the Revisit meta tag in the HTML page header. Some web crawlers ignore this value. <br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#How Often should Crawlers Revist Meta Tag|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Enable_RSS&diff=10701Enable RSS2008-04-07T20:48:36Z<p>MarekZ: New page: {{glossary | description = This option lets you enable or disable the RSS feature.<br /><br />RSS lets users monitor your site for changes to the Index page without actually visiting your ...</p>
<hr />
<div>{{glossary | description = This option lets you enable or disable the RSS feature.<br /><br />RSS lets users monitor your site for changes to the Index page without actually visiting your site periodically. If too many users make use of this feature or if the refresh frequency set by these users is too high, RSS can use up too much bandwidth or server capacity.<br /><br />This [http://en.wikipedia.org/wiki/RSS_(file_format) Wikipedia article] contains comprehensive information and links about RSS and the various RSS formats.<br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Enable RSS|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Description_Meta_Tag&diff=10700Description Meta Tag2008-04-07T20:46:41Z<p>MarekZ: New page: {{glossary | description = The value to place in the Description meta tag in the HTML page header. Leave this field empty to use the title of the currently active database. <br/><br/>''Us...</p>
<hr />
<div>{{glossary | description = The value to place in the Description meta tag in the HTML page header. Leave this field empty to use the title of the currently active database. <br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Description Meta Tag|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Copyright_Meta_Tag&diff=10699Copyright Meta Tag2008-04-07T20:46:05Z<p>MarekZ: New page: {{glossary | description = The value to place in the Copyright meta tag in the HTML page header. Leave this field empty to use the full name of the Genealogy contact. <br/><br/>''Used in:...</p>
<hr />
<div>{{glossary | description = The value to place in the Copyright meta tag in the HTML page header. Leave this field empty to use the full name of the Genealogy contact. <br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Copyright Meta Tag|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Author_Meta_Tag&diff=10698Author Meta Tag2008-04-07T20:45:29Z<p>MarekZ: New page: {{glossary | description = The value to place in the Author meta tag in the HTML page header. Leave this field empty to use the full name of the Genealogy contact. <br/><br/>''Used in:'' ...</p>
<hr />
<div>{{glossary | description = The value to place in the Author meta tag in the HTML page header. Leave this field empty to use the full name of the Genealogy contact. <br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Author Meta Tag|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Add_To_Title_Header_Tag&diff=10697Add To Title Header Tag2008-04-07T20:44:52Z<p>MarekZ: New page: {{glossary | description = Anything on this line will be added to the TITLE tag in the HTML page header after the regular page title and before the PhpGedView credit. <br/><br/>''Used in:'...</p>
<hr />
<div>{{glossary | description = Anything on this line will be added to the TITLE tag in the HTML page header after the regular page title and before the PhpGedView credit. <br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Add To Title Header Tag|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Add_Most_Common_Surnames_To_Keywords_Meta_Field&diff=10696Add Most Common Surnames To Keywords Meta Field2008-04-07T20:44:04Z<p>MarekZ: New page: {{glossary | description = With this option set to <b>Yes</b> the surnames from the Most Common Surnames list will be added to the Keywords meta field. This can help search engines better...</p>
<hr />
<div>{{glossary | description = With this option set to <b>Yes</b> the surnames from the Most Common Surnames list will be added to the Keywords meta field. This can help search engines better find your site. <br/><br/>''Used in:'' [[Configuration - Web Site and META Tag Settings#Add Most Common Surnames To Keywords Meta Field|Gedcom Configuration - Web Site and Meta settings]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Theme_Directory&diff=10695Theme Directory2008-04-07T20:43:12Z<p>MarekZ: New page: {{glossary | description = The directory where your PhpGedView theme files are kept.<br /><br />You may customize any of the standard themes that come with PhpGedView to give your site a u...</p>
<hr />
<div>{{glossary | description = The directory where your PhpGedView theme files are kept.<br /><br />You may customize any of the standard themes that come with PhpGedView to give your site a unique look and feel. See the [[Modify your theme|Theme Customization]] article for more information.<br/><br/>''Used in:'' [[Configuration - User Options#Theme Directory|Gedcom Configuration - User Options]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Show_Contextual_Help_Links&diff=10694Show Contextual Help Links2008-04-07T20:41:09Z<p>MarekZ: New page: {{glossary | description = This option will enable links, identified by question marks, next to items on many pages. These links allow users to get information or help about those items.<...</p>
<hr />
<div>{{glossary | description = This option will enable links, identified by question marks, next to items on many pages. These links allow users to get information or help about those items.<br/><br/>''Used in:'' [[Configuration - User Options#Show Contextual ? Help Links|Gedcom Configuration - User Options]]}} [[Category:PGV Configuration Fields]]</div>MarekZhttps://wiki.phpgedview.net/en/index.php?title=Display_Theme_Dropdown_Selector_For_Theme_Changes&diff=10693Display Theme Dropdown Selector For Theme Changes2008-04-07T20:40:19Z<p>MarekZ: New page: {{glossary | description = Gives users the option of selecting their own theme from a menu.<br /><br />Even with this option set, the theme currently in effect may not provide for such a m...</p>
<hr />
<div>{{glossary | description = Gives users the option of selecting their own theme from a menu.<br /><br />Even with this option set, the theme currently in effect may not provide for such a menu. To be effective, this option requires the <b>Allow users to select their own theme</b> option to be set as well.<br/><br/>''Used in:'' [[Configuration - User Options#Display Theme Dropdown Selector for Theme Changes|Gedcom Configuration - User Options]]}} [[Category:PGV Configuration Fields]]</div>MarekZ