I am attempting to setup a WordPress 3.0.1 site on my server manually, so that my WordPress index.php is stored in the root folder, but my WordPress installation is in its own subfolder. I have done this dozens of times with prior versions of WordPress, and several on the very same server with the very same configuration under which I am experiencing this error.
- I downloaded the .zip file direct from WordPress.org via wget, then unzipped it, and subsequently renamed wordpress/ to cms/.
- I then moved the index.php file from cms/ to the root directory and edited index.php to read:
- Then I duplicated wp-config-sample.php to wp-config.php, edited it to reflect my verified DB login info, and added:
define('WP_HOME', 'http://mydomain.com/cms'); define('WP_SITEURL', 'http://mydomain.com');
- Upon visiting mydomain.com (which obviously isn't the actual domain), I'm redirected to http://mydomain.com/wp-admin/install.php which results in a 404 error.
- If I manually visit http://mydomain.com/cms/wp-admin/install.php, I see the install page, however, it is not styled by CSS.
- When I view the source, I see that the CSS is referenced at
<link rel='stylesheet' id='install-css' href='http://mydomain.com/wp-admin/css/install.css?ver=20100605' type='text/css' media='all' />
This seems to indicate that the WP_HOME parameter in my wp-config.php file is being ignored by the installer.
- I have tried this under two different domains on the same server and experienced the same exact problem. I did not, however, experience this problem with WordPress 3.0 using the same exact installation method just two weeks ago.
- If I install WordPress into the root folder (without the cms/ subdirectory) everything works fine. However, this obviously makes my install more vulnerable to hack attempts and is thus undesirable.
Has something changed that WordPress no longer supports subdirectory installs, is this a bug in WordPress 3.0.1, or am I missing something?