I don't let my users delete individuals, period. If there's a good reason to delete, I make the INDI-ID an unattached, unknown and keep it for use at a future date (like ADMIN - unlinked new INDI). I find that there is little understanding when they delete that the person is connected in many ways. I would suggest you write down the INDI they wished to delete, then try to disapprove the change rather than approve it. Then you can, yourself, decide what they were trying to achieve with the deletion. Perhaps they simply needed to move the INDI to another family, which should have been done with the FAM record > Change Family Members function, rather than deleting. If they already added a replacement person (new) where this one belonged, consider using a MERGE function on the two INDI records rather than a deletion.
BTW, there were significant improvements in approval/deny management between 4.2.2 and 4.2.3. You really give thought to using the SVN tarball and making another installation, using your current version as a backup.
-Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am running 4.2.2.
Tonight, a member made changes. When I went to approve them, I got an error message:
Fatal error: Call to a member function getType() on a non-object in D:\…\PhpGedView\blocks\review_changes.php on line 117
How do I fix this error?
OOPs, posted to wrong thread.
Anything to do with these previous threads?
https://sourceforge.net/projects/phpgedview/forums/forum/185166/topic/3216058
https://sourceforge.net/projects/phpgedview/forums/forum/185166/topic/3351253
Both had to do with non-existent INDI records. I suspect you have the same issue in some fashion.
-Stephen
No.
I remembered an earlier suggestion to edit out the old data from the pgv_changes.php.
That stopped the error, but now I get:
Fatal error: Maximum execution time of 30 seconds exceeded in D:\…\PhpGedView\includes\classes\class_pgv_db.php on line 838
Seems to stem from a user deleting an individual and my attempt to approve it.
I don't let my users delete individuals, period. If there's a good reason to delete, I make the INDI-ID an unattached, unknown and keep it for use at a future date (like ADMIN - unlinked new INDI). I find that there is little understanding when they delete that the person is connected in many ways. I would suggest you write down the INDI they wished to delete, then try to disapprove the change rather than approve it. Then you can, yourself, decide what they were trying to achieve with the deletion. Perhaps they simply needed to move the INDI to another family, which should have been done with the FAM record > Change Family Members function, rather than deleting. If they already added a replacement person (new) where this one belonged, consider using a MERGE function on the two INDI records rather than a deletion.
BTW, there were significant improvements in approval/deny management between 4.2.2 and 4.2.3. You really give thought to using the SVN tarball and making another installation, using your current version as a backup.
-Stephen