Tuesday, November 15, 2005

Multiblogging with wordpress cont...

Now that we have our account set up and wordpress downloaded, let’s log in to our godaddy acount.It will make more sense if you  follow along while we create a database:

  • after logging in, click on  Hosting & Servers , then click  My Hosting Account
  • This opens our host manager. Click “open” next to your domain.  Mine looks like this:   (Thundereyez.com       open )
  • After the page opens you’ll see a menue on the left , click “account login” and add a login password (Read the information box carefully) This will not change your password to login to your godaddy account, but this allow us to upload files to our server. The password must contain a capital letter and a number, with minimumat least 6 words . For example:  9bearsinaRow,  no spaces.
  • click update and after the page reloads, go to the left hand side of the  menue “databases”and click “mysql”. Now we can create a database.
  • click “create new database
  • You need a user name for it. This name you will edit wp-config with, not login to anything. Since this is your first database, try “wordpress001”, (no spaces) and use the password we created earlier under “account login.”. Take a break while the sever creates the database.
  • Now,  that  the database has been created, you need to click on the database name and write down the
  • 'DB_NAME'= 'wordpress001'   (leave in the little ticks)
  • 'DB_USER'=  'wordpress001'    (leave in the little ticks )
  • We need the ‘DB_HOST’= 'mysqlxxx.secureserver.net '  (your number xxx will be different) localhost doesn’t work.
  • and the password we created earlier.
  • Now,let’s find the wordpress folder on your desktop and open the wp-config-sample.php file
  • This is the part we need to edit:
  • <?php
    // ** MySQL settings ** //
    define('DB_NAME', 'wordpress');     // The name of the database
    define('DB_USER', 'username');     // Your MySQL username
    define('DB_PASSWORD', 'password'); // ...and password
    define('DB_HOST', 'localhost');     // 99% chance you won't need to change this value
To be continued

No comments: