burtflaxton

Researching this all day I have found that my solution might be with WordPress MU. I will open a discussion there and post what follows there, here.

The site the company I work for has been with their current host for over 7 years. The website they have and current database is over 38 GB, with well over 500,000 items. Switching the current site to a different host is NOT an option, although I would love to do that, current management will not consider switching hosts. When I brought up the idea, they quickly considered changing web developers though. We pay these “assholes” around 38,000 a year for web hosting & database management, which is beyond me, but it is the situation. Yes it sucks, our webhost is in the frakin dark ages…

Now, I appreciate the responses, but I am still in the same position as I was yesterday.

Let me be more specific, so maybe one of you gurus can help me out if you have time.

If I was going to set up a blog on a different host how would wpconfig.php code look?

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'putyourdbnamehere');

/** MySQL database username */
define('DB_USER', 'usernamehere');

/** MySQL database password */
define('DB_PASSWORD', 'yourpasswordhere');

/** MySQL hostname */
define('DB_HOST', 'localhost');

When I set this up using my DB_NAME, DB_USER, DB_PASSWORD, and the IP address of the database for ‘hostname’, my blog cannot be reached when I place the /blog folder onto my webhost. This is the message I get go to http://www.mywebsite.com/blog

Directory Listing Denied
This Virtual Directory does not allow contents to be listed.

Now, I have set up at least 30 wordpress blogs for clients so I know quite a bit about installing and troubleshooting an install, but I am definitely stuck on this one.

I would imagine there is an alternative solution using subdomains, but I am not 100% how to do that since I have not ever attempted that.

Any help would be much appreciated.

*edit* could it just be that the current webhost the site is on does not allow remote connections? Or does that have nothing to do with this?