Usually it is not possible to select which executable you want on a per directory basis on shared hosting service unless you have a really good provider. I have seen a few times that you can specify in the administration of your site for which file extensions which php version should be used so check whether you find any setting there.
The easiest way to find out which php version is running is to upload a phpinfo file. Just create a textfile named phpinfo.php with the following content:
<?php
phpinfo();
?>
Upload the file and call it in your browser. You will get loads of information, the PHP version is right at the top.
The phpinfo() call shows I am running 4.4.4. (Thanks for that!). It also shows the memory limit configured to 80MB.
So I am running out of ideas. I am running php 4.4.4, and MySql4, and I did a completely middle of the road install (just chose the default values). Where do I start looking at what is causing the error 500 as soon as the installation is finished?
Many of the other php scripts in the installation run without error.
I wonder is there a list of the files that get modified when the installation / setup is performed?
If I had this I could also easily revert to the unconfigured version without uploading the whole 40MB? I cannot upload a single tarball and extract it (I have no shell access).
Thanks for everyone's help. I see from reading the archive that this is not a totally unique problem, though a lot of the hints in the other threads suggest modifying the .htaccess file. I have no .htaccess file in my top-level directory.
Here is one possible reason for the failure. My ISP is running a fairly secure system, and files with world writeable permissions are deemed insecure and thus not opened. If a php script tries to open a file which is world writeable, the suExec environment stops the script and returns error 500.
I noticed that the file var/news_site/storage.log has perms set tp 666. I'm going to turn off the world writeable bit and see if things improve. However, I am wondering what the root cause of this might be, and if the umask for such files might be changeable somewhere, or if this might be considered a bug.
Any other insight is really appreciated!
dvb
You must be logged in to post messages in this topic!
