After migrating PGV 4.3.0 to a new site on the same host I'm getting the following critical error:
==
ERROR 2: opendir(/home1/vojincom/ged_index/) [function.opendir]: failed to open dir: No such file or directory
0 Error occurred on in function opendir
1 called from line 49 of file gedcheck.php
Warning: opendir(/home1/vojincom/ged_index/) [function.opendir]: failed to open dir: No such file or directory in /home1/damjanac/public_html/damjanci/ged/gedcheck.php on line 49
ERROR 2: readdir(): supplied argument is not a valid Directory resource
0 Error occurred on in function readdir
1 called from line 50 of file gedcheck.php
Warning: readdir(): supplied argument is not a valid Directory resource in /home1/damjanac/public_html/damjanci/ged/gedcheck.php on line 50
ERROR 2: closedir(): supplied argument is not a valid Directory resource
0 Error occurred on in function closedir
1 called from line 57 of file gedcheck.php
Warning: closedir(): supplied argument is not a valid Directory resource in /home1/damjanac/public_html/damjanci/ged/gedcheck.php on line 57
==
The ged_index is not on public_html and I change location on config.php. I tried to look for these error at gedcheck.php but can't figure out anything.
TIA
Vojin Damjanac
Marina, CA
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After migrating PGV 4.3.0 to a new site on the same host I'm getting the
following critical error:
==
ERROR 2: opendir(/home1/vojincom/ged_index/) [function.opendir]: failed
to open dir: No such file or directory
On the old site there should be an '/index/' directory which has all of
the material relating to your gedcom's if you are not copying that setup
over, then you need to manually create a directory on the new site to
match the $INDEX_DIRECTORY= entry in the config.php file which would
seem to be ged_index in your case ...
Yes, I copied that directory to the new site and here is that line in
the config.php:
$INDEX_DIRECTORY='/home1/damjanac/ged_index/'; //-- Readable and
Writeable Directory to store index files (include the trailing "/")
But that is not part of the working website directory tree?
/home1/damjanac/public_html/damjanci/ged/gedcheck.php can't access
something outside the tree, so should be
/home1/damjanac/public_html/damjanci/ged/ged_index/
and
$INDEX_DIRECTORY='./ged_index/';
So that it is readable and writable from the web server.
When you're using an "index" directory that's not within the directory structure where PhpGedView is installed, it's best to NOT use an absolute directory location in the server's directory tree. Instead, the directory location should be specified relative to the directory where PhpGedView is installed.
Also, it's best to name the data directory for PhpGedView "index" no matter where it lives. You should also have a universally writable "index" directory in PhpGedView's directory tree, even if you don't intend to use it.
Example:
server/webroot/applications/PhpGedView (where PhpGedView is installed)
server/webroot/applications/PhpGedView/index (see last paragraph above)
server/datafiles/foo/bar/index (where PhpGedView's data files live)
In PhpGedView's configuration, the location of the "index" directory would thus be:
../../datafiles/foo/bar/index/
Each "../" backs up one directory level. You'll have to adjust these instructions to match your server's actual set-up.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After a lot of off-line communication with the user, we found that the database contained a pointer to the old location of the GEDCOM file. PGV was taking that old location instead of the correct (new) one that was specified in the site configuration.
I changed the contents of database table pgv_gedcom_setting to point at the revised location of the GEDCOM file, and everything started working as expected.
This is obviously a bug in PGV version 4.3.0. I'll fix that soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everybody,
After migrating PGV 4.3.0 to a new site on the same host I'm getting the following critical error:
==
ERROR 2: opendir(/home1/vojincom/ged_index/) [function.opendir]: failed to open dir: No such file or directory
0 Error occurred on in function opendir
1 called from line 49 of file gedcheck.php
Warning: opendir(/home1/vojincom/ged_index/) [function.opendir]: failed to open dir: No such file or directory in /home1/damjanac/public_html/damjanci/ged/gedcheck.php on line 49
ERROR 2: readdir(): supplied argument is not a valid Directory resource
0 Error occurred on in function readdir
1 called from line 50 of file gedcheck.php
Warning: readdir(): supplied argument is not a valid Directory resource in /home1/damjanac/public_html/damjanci/ged/gedcheck.php on line 50
ERROR 2: closedir(): supplied argument is not a valid Directory resource
0 Error occurred on in function closedir
1 called from line 57 of file gedcheck.php
Warning: closedir(): supplied argument is not a valid Directory resource in /home1/damjanac/public_html/damjanci/ged/gedcheck.php on line 57
==
The ged_index is not on public_html and I change location on config.php. I tried to look for these error at gedcheck.php but can't figure out anything.
TIA
Vojin Damjanac
Marina, CA
On 27/07/15 20:27, Mitar Miric wrote:
On the old site there should be an '/index/' directory which has all of
the material relating to your gedcom's if you are not copying that setup
over, then you need to manually create a directory on the new site to
match the $INDEX_DIRECTORY= entry in the config.php file which would
seem to be ged_index in your case ...
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
Yes, I copied that directory to the new site and here is that line in the config.php:
$INDEX_DIRECTORY='/home1/damjanac/ged_index/'; //-- Readable and Writeable Directory to store index files (include the trailing "/")
On 28/07/15 08:10, Mitar Miric wrote:
But that is not part of the working website directory tree?
/home1/damjanac/public_html/damjanci/ged/gedcheck.php can't access
something outside the tree, so should be
/home1/damjanac/public_html/damjanci/ged/ged_index/
and
$INDEX_DIRECTORY='./ged_index/';
So that it is readable and writable from the web server.
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
When you're using an "index" directory that's not within the directory structure where PhpGedView is installed, it's best to NOT use an absolute directory location in the server's directory tree. Instead, the directory location should be specified relative to the directory where PhpGedView is installed.
Also, it's best to name the data directory for PhpGedView "index" no matter where it lives. You should also have a universally writable "index" directory in PhpGedView's directory tree, even if you don't intend to use it.
Example:
server/webroot/applications/PhpGedView (where PhpGedView is installed)
server/webroot/applications/PhpGedView/index (see last paragraph above)
server/datafiles/foo/bar/index (where PhpGedView's data files live)
In PhpGedView's configuration, the location of the "index" directory would thus be:
../../datafiles/foo/bar/index/
Each "../" backs up one directory level. You'll have to adjust these instructions to match your server's actual set-up.
After a lot of off-line communication with the user, we found that the database contained a pointer to the old location of the GEDCOM file. PGV was taking that old location instead of the correct (new) one that was specified in the site configuration.
I changed the contents of database table pgv_gedcom_setting to point at the revised location of the GEDCOM file, and everything started working as expected.
This is obviously a bug in PGV version 4.3.0. I'll fix that soon.