Is PHP in Safe Mode a show stopper?
I’m trying to install WP on my shared, Windows web server. Godaddy.com is my host. After creating a MySQL database using what passes for a control panel provided by my ISP, I edited the wp-config file as follows:
define(‘DB_NAME’, ‘wordpressblogdb’); // The name of the database
define(‘DB_USER’, ‘wordpressblogdb’); // Your MySQL username
define(‘DB_PASSWORD’, ‘****’); // …and password
define(‘DB_HOST’, ‘mysql57.secureserver.net’); // 99% chance you won’t need to change this value
The host info comes from the ISP, so I assume it’s correct.
After uploading all the files using FrontPage, the install.php page returns this:
Your PHP installation appears to be missing the MySQL which is required for WordPress.
In searching the forum for this error I see that others have had it, but many of them are trying to do a local install and are having some PHP or MySQL config issues that I don’t think apply here, because I can’t configure PHP or MySQL (other than managing a db) on my server.
I asked my ISP about this, and they swear they support the required version of PHP and MySQL, BUT they also say PHP on Windows accounts (which is what I have) runs in safe mode.
Before I start trying to figure out whether this is a MySQL connection problem I’m wondering if PHP in safe mode is a show-stopper all by itself.
I have no idea why my host insists on running PHP in safe mode on Windows accounts. Since I use FrontPage for some other database stuff I have some ASP pages and thus do not really want to move to a Linux account (which, apparently, does not have the safe mode limitation, if indeed it is a limitation). Is there any fundamental reason a host can’t offer full PHP, MySQL, and ASP support on a hosting platform? I’d probably rather switch hosts than abandon my use of FrontPage.
Thanks to those who read this far.
- The topic ‘Is PHP in Safe Mode a show stopper?’ is closed to new replies.