I am getting many errors from users clicking on names on the interactive tree. Eventually details of the person appears but it looks as though somewhere there is a stray <br at the end of a path. I am fully up to date including latest patch and using the basic theme.
File does not exist: xxxxxxxxxxxx/phpgedview/<br , referer: xxxxxxx/phpgedview/individual.php?pid=I1788&ged=ESS_Copford.GED
Is this just on my installation or is it a common problem?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It might be a good idea for you to replace all of the PhpGedView program files with fresh copies. If you preserve the configuration file "config.php" and the contents of the "./index" and "./media" directories, you won't need to do anything special to get the fresh copy of PGV working.
You might also consider replacing your version 4.2.3 installation with the SVN version. Stephen Arnold has published the download URL for this version many times. If you do this, you should export your database to a GEDCOM file, then replace the PGV program files as noted above, then launch PGV, and then re-import the previously exported GEDCOM.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found a problem with the Treenav page in the Minimal theme, and this is fixed in SVN 7008. I don't think your problem is related to this:
On the Treenav page, when you click on one of the collapsed boxes, that box expands to give more information. One of the items in this expanded box is a link to the Family page, represented by a button showing parents and a child. In the Minimal theme, this button was missing and the error was noted in the log file as a "Missing index: family" error.
You should check your log file settings. If you don't archive your log file daily, it can get very large, particularly with the recent spate of hacking attempts. (One of my log files, archived daily, was over 250 Kb - just for one day.) When you encounter an error such as the one noted above, this error will be recorded in the log file, and that process can take a long time when the file is large.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This error message occurs in my pgv log and in server error log. The user does not see the problem. In the logs I think I also get the message you mention above "ERROR 8: Undefined index: family; 0 Error occurred on line 340 of file class_treenav.php in function getDetails1 called from line 90 of file class_treenav.php in function TreeNav2 called from line 41 of file treenav.php".
I am very loath to install the SVN version especially as you say GEDCOMs need reimporting - I have 89 GEDCOMs on one web site.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Antique
SVN contains 370+ code improvements and several dozen bug fixes with one very serious security issue, none of which can be 'patched'. I'm not sure a reimport is necessary from 4.2.3 to 4.3-svn, but it is properly recommended. I did not do one on my 5 gedcoms, but at some point or other, you will need to do so. -Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Taking the advice from this forum:
"
2009-12-28 19:37:41 GMT
Mac Not sure why you want to DL SVN as its a bit like playing with fire. Unless you are trained (and even if you are), you can be easily badly burned. There have already been 16 changes to the code since Greg's v4.2.3 stable release, many affecting the interface between text files and the database (storing more things in DB rather than configs). It is BETA software at best and always offers the potential for a disaster. You must maintain backups regularly and be willing to lose all your data if you mess with SVN. That said, the SVN tarball is large. Hope this helps, Stephen "
I don't think I will take the risk of updating to SVN software. Thankyou canajun2eh that has fixed one of the problems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Antique
Was 16, now over 370. Many of these changes were important fixes where the existing code in 4.2.3 actually corrupts the data (family problems for one). It is impossible, with this many fixes to safely snag one file here and one there and most are not as simple as Gerry's one-file and a couple of forward slashes solution. Using SVN regularly for production sites IS playing with fire and you must be prepared for the instance where the site goes down because of incomplete or incorrect code changes, loss of data due to code or table changes and more - but, when the SVN Tarball is a much better product than the now over-one-year "stable" release, and you are NOT running SVN as bleeding edge code, then there is no reason not to upgrade. Too many problems with 4.2.3, including the family unit destruction and the major security problem.
The resource is there and a 'new' release (4.2.4) would be nothing more than a rolled-out version of the tarball, with Gerry's recent tweaks to reports. -Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Antiqueone:
Yes, that's it. The download is about 16 Mb.
You need to use 7-zip to extract the 52 Mb "phpgedview-phpGedView.tar" file from this download, and then you use 7-zip on that extracted file to extract all of the latest files from the SVN directory. The one I just downloaded included the simple correction mentioned above, that I committed to SVN yesterday evening.
There isn't a great deal of danger in running the SVN version at the moment. There are very few changes, and I check everything to make sure at least my site is running properly before committing the updates to SVN.
I've been running SVN code in "production mode" from "day 1" and have only encountered problems two or three times, usually with other people's code. In each case, the problem was fixable in very short order so that my site was unusable for just a short time. Of course, I also run an off-line copy of PGV with the same data as the on-line version. I run into a lot more problems here, but that's to be expected since it's my "development" system, where the real bug trapping takes place.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am getting many errors from users clicking on names on the interactive tree. Eventually details of the person appears but it looks as though somewhere there is a stray <br at the end of a path. I am fully up to date including latest patch and using the basic theme.
File does not exist: xxxxxxxxxxxx/phpgedview/<br , referer: xxxxxxx/phpgedview/individual.php?pid=I1788&ged=ESS_Copford.GED
Is this just on my installation or is it a common problem?
I got the theme name wrong. It is called Minimal.
This seems to be a problem with your installation.
You can try my installation: http://keldine.ca/phpGedView
It might be a good idea for you to replace all of the PhpGedView program files with fresh copies. If you preserve the configuration file "config.php" and the contents of the "./index" and "./media" directories, you won't need to do anything special to get the fresh copy of PGV working.
You might also consider replacing your version 4.2.3 installation with the SVN version. Stephen Arnold has published the download URL for this version many times. If you do this, you should export your database to a GEDCOM file, then replace the PGV program files as noted above, then launch PGV, and then re-import the previously exported GEDCOM.
I found a problem with the Treenav page in the Minimal theme, and this is fixed in SVN 7008. I don't think your problem is related to this:
On the Treenav page, when you click on one of the collapsed boxes, that box expands to give more information. One of the items in this expanded box is a link to the Family page, represented by a button showing parents and a child. In the Minimal theme, this button was missing and the error was noted in the log file as a "Missing index: family" error.
You should check your log file settings. If you don't archive your log file daily, it can get very large, particularly with the recent spate of hacking attempts. (One of my log files, archived daily, was over 250 Kb - just for one day.) When you encounter an error such as the one noted above, this error will be recorded in the log file, and that process can take a long time when the file is large.
This error message occurs in my pgv log and in server error log. The user does not see the problem. In the logs I think I also get the message you mention above "ERROR 8: Undefined index: family; 0 Error occurred on line 340 of file class_treenav.php in function getDetails1 called from line 90 of file class_treenav.php in function TreeNav2 called from line 41 of file treenav.php".
I am very loath to install the SVN version especially as you say GEDCOMs need reimporting - I have 89 GEDCOMs on one web site.
Antique
SVN contains 370+ code improvements and several dozen bug fixes with one very serious security issue, none of which can be 'patched'. I'm not sure a reimport is necessary from 4.2.3 to 4.3-svn, but it is properly recommended. I did not do one on my 5 gedcoms, but at some point or other, you will need to do so.
-Stephen
The fix to correct the missing index is very simple, and you can do this without needing to install all of the SVN code:
Edit file "themes/minimal/theme.php", and remove the "// " from the front of line 89. This will activate the definition for the "Family" button.
Taking the advice from this forum:
"
2009-12-28 19:37:41 GMT
Mac Not sure why you want to DL SVN as its a bit like playing with fire. Unless you are trained (and even if you are), you can be easily badly burned. There have already been 16 changes to the code since Greg's v4.2.3 stable release, many affecting the interface between text files and the database (storing more things in DB rather than configs). It is BETA software at best and always offers the potential for a disaster. You must maintain backups regularly and be willing to lose all your data if you mess with SVN. That said, the SVN tarball is large. Hope this helps, Stephen "
I don't think I will take the risk of updating to SVN software. Thankyou canajun2eh that has fixed one of the problems.
canajun2eh
Your advice seems to have fixed both problems. Thanks very much.
Antique
Was 16, now over 370. Many of these changes were important fixes where the existing code in 4.2.3 actually corrupts the data (family problems for one). It is impossible, with this many fixes to safely snag one file here and one there and most are not as simple as Gerry's one-file and a couple of forward slashes solution. Using SVN regularly for production sites IS playing with fire and you must be prepared for the instance where the site goes down because of incomplete or incorrect code changes, loss of data due to code or table changes and more - but, when the SVN Tarball is a much better product than the now over-one-year "stable" release, and you are NOT running SVN as bleeding edge code, then there is no reason not to upgrade. Too many problems with 4.2.3, including the family unit destruction and the major security problem.
The resource is there and a 'new' release (4.2.4) would be nothing more than a rolled-out version of the tarball, with Gerry's recent tweaks to reports.
-Stephen
Is the download the one at:
http://phpgedview.svn.sourceforge.net/viewvc/phpgedview/trunk/phpGedView/?view=tar ?
It seems wrong because it is labelled GNU tarball.
Antiqueone:
Yes, that's it. The download is about 16 Mb.
You need to use 7-zip to extract the 52 Mb "phpgedview-phpGedView.tar" file from this download, and then you use 7-zip on that extracted file to extract all of the latest files from the SVN directory. The one I just downloaded included the simple correction mentioned above, that I committed to SVN yesterday evening.
There isn't a great deal of danger in running the SVN version at the moment. There are very few changes, and I check everything to make sure at least my site is running properly before committing the updates to SVN.
I've been running SVN code in "production mode" from "day 1" and have only encountered problems two or three times, usually with other people's code. In each case, the problem was fixable in very short order so that my site was unusable for just a short time. Of course, I also run an off-line copy of PGV with the same data as the on-line version. I run into a lot more problems here, but that's to be expected since it's my "development" system, where the real bug trapping takes place.
Antique
in the Trunk directory is the PGV directory:
http://phpgedview.svn.sourceforge.net/viewvc/phpgedview/trunk/phpGedView/
at the bottom of that page is the all inclusive PGV-SVN-Trunk tarball
http://phpgedview.svn.sourceforge.net/viewvc/phpgedview/trunk/phpGedView/?view=tar
Yes
-Stephen