Pauly
I'm going to assume you didn't try to import the gedcom into the revised tables - correct? But rather are setting up a new installation with v4.2.0 tables. From Google, a 500 error is:
Cause
The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site's server but the server could not be more specific on what the exact problem is.
Resolution
The 500 Internal Server Error is a "server-side" error, meaning the problem is not with your PC or Internet connection but instead is a problem with the web site's server.
Even though the issue is not yours to troubleshoot or resolve, there are a few things you can do:
1. Retry the web page by clicking the refresh/reload button or trying the URL from the address bar again. Even though the 500 Internal Server Error is reporting a general error on the web site's servers and not your computer, the server error may only be temporary.
Trying the page again will often be successful.
Note: If the 500 Internal Server Error message appears during the checkout process at an online merchant, be aware that duplicate attempts to checkout may end up creating multiple orders - and multiple charges! Most merchants have automatic protections from these kinds of actions but it's still something to keep in mind.
2. Come back later. The 500 Internal Server Error message is one of the most common error message seen when checking out during an online purchase so sales are often disrupted. This is usually a great incentive to resolve the issue very quickly.
3. If you can't wait any longer for the problem to be resolved or if you'd like to help out, you may want to attempt to contact the webmaster or another website contact and advise them of their server error.
Hope this helps, Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, the first problem was pretty simple. The 60 sec timeout was tripping a server timeout (probably 60 s as well). A shorter timeout allowed me to import it in pieces. It reported that the GEDCOM had been successfully imported.
However, someone wasn't told: navigating to most pages gives a GEDCOM set page saying "This GEDCOM has not yet been imported. "
I reinstalled everything (PHPGedView and database) & tried again with the same result.
Thanks again.
George
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Or it might have created more problems. PGV sets this to false on purpose. It forces you to reimport the gedcom, which re-populates various tables in the database.
Often code or database changes require this.
You really ought to re-import.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-01-21
Plus, you didn't comment on Stephen's question:
Pauly
I'm going to assume you didn't try to import the gedcom into the revised tables - correct?
Going back from 4.2.3 to 4.2.0 is not possible unless you completely delete all the tables and start fresh.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm trying to import into 4.2.0 a GEDCOM that was created using 4.2.3. I'm getting a 500 - Internal Server Error.
I edited the GEDCOM to remove all of the critical errors.
Any ideas as to what might be going on? Or what the next step should be?
Thanks,
George
Pauly
I'm going to assume you didn't try to import the gedcom into the revised tables - correct? But rather are setting up a new installation with v4.2.0 tables. From Google, a 500 error is:
Cause
The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site's server but the server could not be more specific on what the exact problem is.
Resolution
The 500 Internal Server Error is a "server-side" error, meaning the problem is not with your PC or Internet connection but instead is a problem with the web site's server.
Even though the issue is not yours to troubleshoot or resolve, there are a few things you can do:
1. Retry the web page by clicking the refresh/reload button or trying the URL from the address bar again. Even though the 500 Internal Server Error is reporting a general error on the web site's servers and not your computer, the server error may only be temporary.
Trying the page again will often be successful.
Note: If the 500 Internal Server Error message appears during the checkout process at an online merchant, be aware that duplicate attempts to checkout may end up creating multiple orders - and multiple charges! Most merchants have automatic protections from these kinds of actions but it's still something to keep in mind.
2. Come back later. The 500 Internal Server Error message is one of the most common error message seen when checking out during an online purchase so sales are often disrupted. This is usually a great incentive to resolve the issue very quickly.
3. If you can't wait any longer for the problem to be resolved or if you'd like to help out, you may want to attempt to contact the webmaster or another website contact and advise them of their server error.
Hope this helps, Stephen
OK, the first problem was pretty simple. The 60 sec timeout was tripping a server timeout (probably 60 s as well). A shorter timeout allowed me to import it in pieces. It reported that the GEDCOM had been successfully imported.
However, someone wasn't told: navigating to most pages gives a GEDCOM set page saying "This GEDCOM has not yet been imported. "
I reinstalled everything (PHPGedView and database) & tried again with the same result.
Thanks again.
George
Sorry to answer my own question -
I changed the gedcoms.php $gedarray setting from false to true.
This seems to have fixed things.
Why wouldn't this have been done automatically? I've uploaded other gedcoms without this problem.
<<This seems to have fixed things>>
Or it might have created more problems. PGV sets this to false on purpose. It forces you to reimport the gedcom, which re-populates various tables in the database.
Often code or database changes require this.
You really ought to re-import.
Plus, you didn't comment on Stephen's question:
Going back from 4.2.3 to 4.2.0 is not possible unless you completely delete all the tables and start fresh.
@fisharebest - There were some missing media paths - not sure why - but re-importing fixed this.
@kiwipgv - the import was into a new installation of PGV 4.2.0, including a new database.
Thanks to all for your help,
George