solidsquirrel

Hey – found the problem. Turns out “localhost” is a no-go for godaddy hosting accounts, but I figured it out. Thanks for the quick replies, guys!

I might as well post the wp-config.php file – Here’s what’s up there (minus the password, of course):

<?php

// ** MySQL settings ** //

define('DB_NAME', 'hotjuicyzebra');    // The name of the database

define('DB_USER', 'hotjuicyzebra');     // Your MySQL username

define('DB_PASSWORD', 'password'); // ...and password

define('DB_HOST', 'localhost');    // 99% chance you won't need to change this value

define('DB_CHARSET', 'utf8');

define('DB_COLLATE', '');

// You can have multiple installations in one database if you give each a unique prefix

$table_prefix  = 'wp_';   // Only numbers, letters, and underscores please!

// Change this to localize WordPress.  A corresponding MO file for the

// chosen language must be installed to wp-content/languages.

// For example, install de.mo to wp-content/languages and set WPLANG to 'de'

// to enable German language support.

define ('WPLANG', '');

/* That's all, stop editing! Happy blogging. */

define('ABSPATH', dirname(__FILE__).'/');

require_once(ABSPATH.'wp-settings.php');

?>

I considered removing the ‘s surrounding the database name/pass/location, but I don’t think that’s the problem.

edit: Oh wow, I just realized that maybe I should have removed the lines starting with // with the instructions… Hopefully that’s not the problem, or I’ll feel like an idiot.

Thanks for the reply –

I’m pretty sure the problem is on godaddy’s side – I can’t imagine anything would be wrong with the wp-config.php file. I’ll contact their customer support when I get home.

(By the way, I do have Linux hosting, but something seems off; There’s a section in the MySQL database control panel that gives an example of how a PHP file would access the database, and it looks different than the wp-config.php file.)