I'm doing an upgrade to the latest version, and want to be sure i'm not missing something.
When doing a backup, the zip file contains several files (in the INDEX directory) which i can not locate anywhere in the phpgedview directories.
These files are: autenticate.php, blocks.dat, favorites.dat, messages.dat and news.dat.
1. Can someone please tell me where these 5 files are located in the phpgedview directory structure?
2. Is there a script which restores the content of the zip file to the appropriate directories?
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dietmar
PGV's backup utility is hardly a panacea and leaves much to the lacking. The best way to backup in preparation for an upgrade or new installation is discussed in the WIKI, but boils down to the following:
1) Download and/or Export a copy of your GEDCOM(s) currently under management by PGV. Do so AFTER being sure to approve all outstanding changes/additions. (I mention the DL/Exp option as AND as I do both, retaining one copy on my local machine and one copy in the INDEX folder on the server.
2) Using a SQL-management program, like phpMyAdmin, do a SQL dump of your existing database. This will allow you to not only retain and restore the DB should it become corrupted, but it contains the gedcoms as well as the other tables that are NOT included in any other backup: Users, Messages, Favorites, News, ETC.
Now, with the confidence that you can return to the existing situation without difficulty, perform your upgrade. There is nothing wrong with creating a new DB and performing a fresh installation of the new SW, and then you can restore the tables needing updated data that is not refreshed from the GEDCOM import from either your previous installation or the SQL-dump (user tables, news, favorites, messages, etc).
Chances are, if you do an in-place upgrade, you'll never need any of this, but it sure is comforting to know its available. You should perform a SQL-dump backup regularly to protect all your data, particularly as we continue to move many of the previous text-based config files into DB-tables.
Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks much Stephen, and i will take your advice!!
But I have searched the WIKI and have NOT found a good description of the upgrade process. The page referencing backup and upgrades has nothing in it: http://wiki.phpgedview.net/en/index.php?title=Perform_maintenance.
Can you send me a WIKI link describing the IN-PLACE upgrade process…
Dieter
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
BTW - I just edited the page (to swap the order of "accept pending changes" and "disable on-line editing"), and noticed that someone had posted support requests as embedded HTML comments.
This really is the wrong place to ask for help. These questions are likely to sit there for all eternity without being noticed by anyone……
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks.
But, can someone please answer my question regarding the locations of:
autenticate.php, blocks.dat, favorites.dat, messages.dat and news.dat in the PGV directory sturcture.
I cound not seem to locate them.
Dietmar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Years ago, before the world discovered databases, PGV stored data in .dat files in the index directory.
When PGV moved to database storage, routines were written to import data from these .dat files into database tables and back again. This allowed people to upgrade from "file based" PGV to "db based" PGV.
Someone decided these import/export routines could be used to create "backups of table contents in the index directory" to enable file-based backup.
These routines still exist - and have been renamed "backup". God knows if they still work. They really ought to be removed.
These .dat files don't exist unless you create them - and you shouldn't.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The "authenticate.php" and "xxx.dat" files don't exist any longer. They disappeared when PGV was changed from version 3.x to 4.0 and became "database only". They were in the "index" directory.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry to belabor this. Version 4.2.2 was my initial PGV installation. When doing a "backup", it creates a file authenticate.php. I have looked at this file, and found it contains current info about my authorized users, etc. If this file is no longer used, where is my current user info stored? I have done a backup of MySQL localhost.sql, as recommended, and can not find any user info there.
Please clarify where the current user info/passwords are stored.
Thanks, Dietmar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dietmar
Asked and answered in the - NOT A GOOD IDEA, previously advised, as well as the "restore the tables needing updated data that is not refreshed from the GEDCOM import from either your previous installation or the SQL-dump (user tables, news, favorites, messages, etc)."
As instructed, Ignore the PGV Backup routine and get on with it. This backup is terribly OLD information with little pertaining to v4.2.+
Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm doing an upgrade to the latest version, and want to be sure i'm not missing something.
When doing a backup, the zip file contains several files (in the INDEX directory) which i can not locate anywhere in the phpgedview directories.
These files are: autenticate.php, blocks.dat, favorites.dat, messages.dat and news.dat.
1. Can someone please tell me where these 5 files are located in the phpgedview directory structure?
2. Is there a script which restores the content of the zip file to the appropriate directories?
Thanks.
Dietmar
PGV's backup utility is hardly a panacea and leaves much to the lacking. The best way to backup in preparation for an upgrade or new installation is discussed in the WIKI, but boils down to the following:
1) Download and/or Export a copy of your GEDCOM(s) currently under management by PGV. Do so AFTER being sure to approve all outstanding changes/additions. (I mention the DL/Exp option as AND as I do both, retaining one copy on my local machine and one copy in the INDEX folder on the server.
2) Using a SQL-management program, like phpMyAdmin, do a SQL dump of your existing database. This will allow you to not only retain and restore the DB should it become corrupted, but it contains the gedcoms as well as the other tables that are NOT included in any other backup: Users, Messages, Favorites, News, ETC.
Now, with the confidence that you can return to the existing situation without difficulty, perform your upgrade. There is nothing wrong with creating a new DB and performing a fresh installation of the new SW, and then you can restore the tables needing updated data that is not refreshed from the GEDCOM import from either your previous installation or the SQL-dump (user tables, news, favorites, messages, etc).
Chances are, if you do an in-place upgrade, you'll never need any of this, but it sure is comforting to know its available. You should perform a SQL-dump backup regularly to protect all your data, particularly as we continue to move many of the previous text-based config files into DB-tables.
Stephen
Thanks much Stephen, and i will take your advice!!
But I have searched the WIKI and have NOT found a good description of the upgrade process. The page referencing backup and upgrades has nothing in it: http://wiki.phpgedview.net/en/index.php?title=Perform_maintenance.
Can you send me a WIKI link describing the IN-PLACE upgrade process…
Dieter
I did find a WIKI page which seems pretty good: http://wiki.phpgedview.net/en/index.php?title=Upgrading
Dieter
http://wiki.phpgedview.net/en/index.php?title=Upgrading
BTW - I just edited the page (to swap the order of "accept pending changes" and "disable on-line editing"), and noticed that someone had posted support requests as embedded HTML comments.
This really is the wrong place to ask for help. These questions are likely to sit there for all eternity without being noticed by anyone……
Thanks.
But, can someone please answer my question regarding the locations of:
autenticate.php, blocks.dat, favorites.dat, messages.dat and news.dat in the PGV directory sturcture.
I cound not seem to locate them.
Dietmar
Years ago, before the world discovered databases, PGV stored data in .dat files in the index directory.
When PGV moved to database storage, routines were written to import data from these .dat files into database tables and back again. This allowed people to upgrade from "file based" PGV to "db based" PGV.
Someone decided these import/export routines could be used to create "backups of table contents in the index directory" to enable file-based backup.
These routines still exist - and have been renamed "backup". God knows if they still work. They really ought to be removed.
These .dat files don't exist unless you create them - and you shouldn't.
The "authenticate.php" and "xxx.dat" files don't exist any longer. They disappeared when PGV was changed from version 3.x to 4.0 and became "database only". They were in the "index" directory.
Sorry to belabor this. Version 4.2.2 was my initial PGV installation. When doing a "backup", it creates a file authenticate.php. I have looked at this file, and found it contains current info about my authorized users, etc. If this file is no longer used, where is my current user info stored? I have done a backup of MySQL localhost.sql, as recommended, and can not find any user info there.
Please clarify where the current user info/passwords are stored.
Thanks, Dietmar
Your users/passwords are stored in the database, in a table called pgv_users.
Dietmar
Asked and answered in the - NOT A GOOD IDEA, previously advised, as well as the "restore the tables needing updated data that is not refreshed from the GEDCOM import from either your previous installation or the SQL-dump (user tables, news, favorites, messages, etc)."
As instructed, Ignore the PGV Backup routine and get on with it. This backup is terribly OLD information with little pertaining to v4.2.+
Stephen
Thanks all, I have now successfully upgraded to 4.2.3.