Trying to access the configuration page from the Admin menu in version 4.2.4, but I get a 404 error on reaching the page whatever I try. All other pages on the Admin menu seem to work just fine.
Any ideas what could be the problem?
Last edit: Sverre 2013-12-31
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It looks as if your PhpGedView installation is damaged. There should certainly be a script called "install.php" in the PhpGedView installation directory on your server.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In either case, there's no need to make a backup of the database or of the GEDCOM first, and there's no need to re-import the GEDCOM after the installation. The database is the same for either version. All you're doing is replacing the program code while retaining the data and configuration files.
To download the most recent SVN version, which hasn't been updated in several months, don't use the download location in the above Help topic. SourceForge changed the SVN repository structure. Instead, click on SVN at the top of this page, then click on trunk, then click on phpGedView, then click on Download Snapshot. The system will respond with a message about checking the snapshot status and either begin the download immediately or tell you that it can't find the snapshot. If it's the latter, wait about 15 minutes and try again. This happens when nobody else has tried a snapshot download recently.
If you follow the above download instructions, you'll end up with a ZIP file that contains a lot of junk as well as the desired "SVN" version of PhpGedView. What you want will be in the directory "phpGedView". Everything else is garbage. I don't have enough authority to get SourceForge support staff to clean up the PhpGedView SVN repository.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I ran the update procedure, and now have an install.php file in my main directory. I still get the same 404 Error when trying to access configuration. :(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you're still getting a 404 error after ensuring that the required install.php file is present, it's possible that your service provider has implemented some sort of "security" that prevents access to such script files.
You need to contact your service provider for help with this problem. Before you do so, however, you might try clearing your browser's cache or possibly using a different browser.
You also need to make sure that the access permissions are set properly on all script files. Try setting the permissions to 755 for everything except the entire contents of the directories "index" and "media" and the file "config.php". These last three should be set to 777. Once the PhpGedView configuration is set properly, the "config.php" file should be set to 644.
Last edit: Gerry Kroll 2013-12-31
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Very hard for us to know without seeing the site.
Perhaps you should try a new installation of the software and when setting up the CONFIG, use the same access data.
If the install.php was missing, what else might be also?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Stephen:
The user did a re-install of PGV into the same directory, after deleting all of the existing program scripts while retaining the data directories and the configuration file. This should have worked. Since the 404 error still occurs (the user checked for the existence of the install.php script), we're left with the conclusion that the service provider has denied access to the "install.php" script through a mechanism outside the control of PGV.
Sverre:
Please e-mail me directly: gkroll at keldine dot ca
I'll create a set of files that uses a script name other than "install.php" (I'll use "foobar.php"). If this works, we will have proven that the service provider is interfering with the proper functioning of PhpGedView. You'll need to tell me which version (4.2.4 or 4.3.0) you are currently trying to get to work. You should be using the 4.3.0 (a.k.a. "SVN") version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Gerry - Happy New Year
Yes, I saw he allegedly did a reinstall, although I would have suggested a new folder and installation to test the setup, but pointing to the same DB. I don't know how he uploaded or transferred the files and whether or not all files were properly replaced, overwritten, etc.
-Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The original installation was made through Softaculous provided by my hosting service. As per the instructions given above, I've uploaded the 4.3.0 SVN version using FTP after deleting all files but those the instructions told not to.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My own copy of PGV is a different port, but it should redirect the same way.
The bit I'm not quite sure on is the extra element in your path ... /slekt is
that included properly in the config.php file?
So the final solution to this problem proved to be to create a new .htaccess file in the PHPGedView directory that overrides the access block to install.php from the top directory.
Thanks a lot for the help, guys!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For what it's worth: The problem wasn't with PhpGedView, but with a "security" plug-in to Wordpress. This security plug-in, among other things, created a .htaccess file in the top-level directory on the server that prevented access to any scripts named "install.php" anywhere within the directory structure.
The solution was to create a .htaccess file in the PhpGedView directory that reversed the "Deny from all" inserted into the top-level .htaccess file by that Wordpress plug-in.
The user will have to implement the same fix into all other softwares installed into subdirectories within the main Wordpress directory. This includes Webtrees.
Here's a snippet from the top-level .htaccess file:
<files install.php>
Order allow,deny
Deny from all
</files>
The following .htaccess file was installed into the PhpGedView directory to override the top-level directive:
<files install.php>
Order allow,deny
Allow from all
</files>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Trying to access the configuration page from the Admin menu in version 4.2.4, but I get a 404 error on reaching the page whatever I try. All other pages on the Admin menu seem to work just fine.
Any ideas what could be the problem?
Last edit: Sverre 2013-12-31
I see that the link on the Admin menu page links to "install.php?step=4", which seems rather odd. I also have no "install.php" in my catalog.
It looks as if your PhpGedView installation is damaged. There should certainly be a script called "install.php" in the PhpGedView installation directory on your server.
Is there a good way to fix that beyond uninstalling and reinstalling the whole thing?
Follow the instructions in this Help post:
https://sourceforge.net/p/phpgedview/discussion/185166/thread/e5fccd90/
to either replace the existing version 4.2.4 installation or to upgrade to version 4.3.0. You should upgrade to version 4.3.0.
In either case, there's no need to make a backup of the database or of the GEDCOM first, and there's no need to re-import the GEDCOM after the installation. The database is the same for either version. All you're doing is replacing the program code while retaining the data and configuration files.
To download the most recent SVN version, which hasn't been updated in several months, don't use the download location in the above Help topic. SourceForge changed the SVN repository structure. Instead, click on SVN at the top of this page, then click on trunk, then click on phpGedView, then click on Download Snapshot. The system will respond with a message about checking the snapshot status and either begin the download immediately or tell you that it can't find the snapshot. If it's the latter, wait about 15 minutes and try again. This happens when nobody else has tried a snapshot download recently.
If you follow the above download instructions, you'll end up with a ZIP file that contains a lot of junk as well as the desired "SVN" version of PhpGedView. What you want will be in the directory "phpGedView". Everything else is garbage. I don't have enough authority to get SourceForge support staff to clean up the PhpGedView SVN repository.
I ran the update procedure, and now have an install.php file in my main directory. I still get the same 404 Error when trying to access configuration. :(
If you're still getting a 404 error after ensuring that the required install.php file is present, it's possible that your service provider has implemented some sort of "security" that prevents access to such script files.
You need to contact your service provider for help with this problem. Before you do so, however, you might try clearing your browser's cache or possibly using a different browser.
You also need to make sure that the access permissions are set properly on all script files. Try setting the permissions to 755 for everything except the entire contents of the directories "index" and "media" and the file "config.php". These last three should be set to 777. Once the PhpGedView configuration is set properly, the "config.php" file should be set to 644.
Last edit: Gerry Kroll 2013-12-31
I have unfortunately tried all those suggestions to no avail. I'll get in touch with my hosting provider.
Thanks a lot for the help anyway! :)
Very hard for us to know without seeing the site.
Perhaps you should try a new installation of the software and when setting up the CONFIG, use the same access data.
If the install.php was missing, what else might be also?
Stephen:
The user did a re-install of PGV into the same directory, after deleting all of the existing program scripts while retaining the data directories and the configuration file. This should have worked. Since the 404 error still occurs (the user checked for the existence of the install.php script), we're left with the conclusion that the service provider has denied access to the "install.php" script through a mechanism outside the control of PGV.
Sverre:
Please e-mail me directly: gkroll at keldine dot ca
I'll create a set of files that uses a script name other than "install.php" (I'll use "foobar.php"). If this works, we will have proven that the service provider is interfering with the proper functioning of PhpGedView. You'll need to tell me which version (4.2.4 or 4.3.0) you are currently trying to get to work. You should be using the 4.3.0 (a.k.a. "SVN") version.
This worked like a charm. I'll let my provider know that and see if they've got anything to say about it.
Gerry - Happy New Year
Yes, I saw he allegedly did a reinstall, although I would have suggested a new folder and installation to test the setup, but pointing to the same DB. I don't know how he uploaded or transferred the files and whether or not all files were properly replaced, overwritten, etc.
-Stephen
The site is http://midthjell.com/slekt
The original installation was made through Softaculous provided by my hosting service. As per the instructions given above, I've uploaded the 4.3.0 SVN version using FTP after deleting all files but those the instructions told not to.
My web host insists that there should be nothing on their end preventing access.
Sverre wrote:
Try http://midthjell.com/slekt/login.php?url=install.php
My own copy of PGV is a different port, but it should redirect the same way.
The bit I'm not quite sure on is the extra element in your path ... /slekt is
that included properly in the config.php file?
--
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
Appears the problem might be the Wordpress installation at the root of midthjell.com that has a .htaccess file that blocks access to install.php
So the final solution to this problem proved to be to create a new .htaccess file in the PHPGedView directory that overrides the access block to install.php from the top directory.
Thanks a lot for the help, guys!
Thanks for letting everyone know.
For what it's worth: The problem wasn't with PhpGedView, but with a "security" plug-in to Wordpress. This security plug-in, among other things, created a .htaccess file in the top-level directory on the server that prevented access to any scripts named "install.php" anywhere within the directory structure.
The solution was to create a .htaccess file in the PhpGedView directory that reversed the "Deny from all" inserted into the top-level .htaccess file by that Wordpress plug-in.
The user will have to implement the same fix into all other softwares installed into subdirectories within the main Wordpress directory. This includes Webtrees.
Here's a snippet from the top-level .htaccess file:
<files install.php>
Order allow,deny
Deny from all
</files>
The following .htaccess file was installed into the PhpGedView directory to override the top-level directive:
<files install.php>
Order allow,deny
Allow from all
</files>