DB Export Utility - Fatal Error! Help please!
Brought to you by:
canajun2eh,
yalnifj
Menu
▾
▴
Hello,
I'm preparing to upgrade from 4.1.5 to the latest version. I've done the obvious cleaning and downloaded a backup. Next I downloaded db_export.php and put it in the root folder. I had a look at the utility so that I understood more clearly what the upgrade instructions were telling me (you've got to forgive an old fart for being slow!).
What I got was a 2 row table. The column headings are - Table; Rows; Backup file (spanning 2 colums); Action (spanning 2 columns); Result.
Table - pgv_blocks
Rows - 21
Backup file - ./index/pgv_blocks.sql; not present
Action - export; convert to UTF8
Result - Fatal error: Call to undefined function safe_get() in /home6/ancestry/public_html/timsilver.me.uk/phpgedview/db_export.php on line 78
What have I done wrong / what do I need to do?
Tim
Tim
I'm not sure what you are doing, or why you "downloaded db_export.php and put it in the root folder".
What are you trying to do, exactly?
Step 1) To get a copy of the GEDCOM only, use the DOWNLOAD link in the Manage GEDCOMS admin area.
To protect your database, use PhpMyAdmin or the CPanel to make a copy of your entire database for reinstallation in case of a corruption problem. You should both of these periodically anyway, whether you are upgrading or not.
Step 2) Have you confirmed your server meets ALL the requirements for running 4.2.5? PDO, adequate memory allocation, MySQL version and PHP versions at or higher than the minimum required? If so, after you do Step #1, then you can upload your new download of the upgrade. If you control your DB, you can actually create a duplicate of your existing DB under a new database, or if restricted to the number of DB's then duplicate it under a new prefix in the same DB. Then upgrade that new prefix with the new files, leaving your previous installation untouched. If you have a problem, you can always go back to the other tables.
On major upgrades as these, it is almost always wise to create an entirely new instance. Don't forget to re-import your GEDCOM after setup. Clear as mud?
-Stephen
okbigkid,
Oh B***** this old fart is trying to avoid a major disaster and is out of his depth!
I'm sure I read somewhere that the db had to be converted from Latin to UTF8 - something to do with this - http://wiki.phpgedview.net/en/index.php?title=Database_import/export/conversion_utility. Which is why I downloaded db_export.php - and I wanted to see what it looked like.
I'd already checked with my host and everything hunky dorey for upgrade
When you say
do you mean MySQL?
Sorry to be so thick!
Tim
1) Converting your database to UTF-8 collation from Latin (or whatever) is not a bad idea. You can use Greg's utility in the Patches section to do this, BUT, be sure you have a DB backup.
2) Instance - a completely separate installation
a) An entirely new directory for the 4.2.5 files, leaving the previous version untouched (and operable in the case of disaster)
b) Either a new prefix on an existing database, OR a new database. If new, and you have users in the 4.1 install, you may wish to clone your existing installation to create the new installation (database) upon which you will act with the new directory of 4.2.5 files. Again, this way you don't lose anything from the previous version. There are some table structure changes that the new 4.2.5 installation will make to the database and you can not return to using your previous version of PGV with the new data structure.
Hope that helps, Stephen
Continuing being thick - I rename my existing phpgedview folder to say, phpgeview_orig and then install 4.2.5 and 'import' my backup?
Tim
Tim
No apologies necessary. What are you doing about the database? Do you have a lot of users and need to protect their u/n, p/w, favorites, messages, and news? If so, you need to move these across (so to speak) by creating a clone and then specifying this new database as the home for your new installation. Depending on how you manage your DNS, you will want to perhaps rename the existing to PGV_4.1.x and name the new folder/directory the one that you use for access. That way you won't have to change the Apache httpd.conf or vhosts.conf files.
-Stephen