The GoDaddy Installation Fix

  • stonercreek

    (@stonercreek)


    19 years ago

    >>>>> The GoDaddy Installation Fix for WordPress 2.x <<<<

    (Background – After pulling my hair out for hours and pouring over numerous previous posts with only a part of the answer…I’ve decided to pull all of those bits into this one post which, I hope, will help you solve all GoDaddy installation problems…at least these steps did it for me. Like you, I was befuddled by the “wp-config is missing”, “wp-config already exists” merry-go-round.)

    MAKE SURE YOU DON’T SKIP A STEP…or you’ll have to start from the beginning. And yes, you can install to a sub-folder using this method.

    STEP ONE: Follow the Famous 5-minute Install through and including item #3 (changing the wp-config name). https://codex.www.ads-software.com/Installing_WordPress#Famous_5-Minute_Install

    STEP TWO: Open the wp-config.php file in Dreamweaver (preferably) or other HTML or text editor.

    STEP THREE: Fill in the DB_NAME, DB_USER (usually the same) and your DB_PASSWORD.

    STEP FOUR: Fill in the DB_HOST with the address given to you by GoDaddy. NOTE:’LOCALHOST’ WILL NOT WORK for GoDaddy!

    NOTE: To find the address you need to enter above, go into your GoDaddy Hosting Account and OPEN the CONTROL PANEL for the account you set up the MySQL database in. Once there click on MYSQL and then click on the USER NAME of the database you created. You’ll then see HOST NAME which will look similar to: mysql98.secureserver.net Whatever yours shows that is what you enter in STEP FOUR above.

    STEP FIVE: Once you have entered all of the above, save the file…and this is VERY important…making sure the file name is ‘wp-config.php’. Be careful as there are some text editors that will save this as a straight text file with a ‘txt’ suffix. It must have the ‘php’ suffix.

    STEP SIX: Upload all your files as outlined in item #5 of the Famous 5 Minute Install. DO NOT do item #6 of the Famous 5 Minute Install yet. (Note: Contrary to some previous posts…YOU CAN upload to a subdirectory.)

    STEP SEVEN: STOP! and before you do anything,read STEP EIGHT below BEFORE you do anything else. If you accidentally jumped ahead and tried to run the install as listed in item #6 of the Famous 5 Minute Install…you must now delete all of the files off of your server and start again with STEP ONE. Sorry.

    STEP EIGHT: Using CuteFTP or a similar FTP program that allows you to change the CMODS of server files and folders, change the settings of the folder that contains everything you just uploaded from “755 to “777”…even if it is the root directory. NOTE: This MUST be done BEFORE you attempt item #6 of the Famous 5 Minute Install.

    STEP NINE: Assuming you have done all of the steps above in order…you are now ready to move on to item #6 of the Famous 5 Minute Install. Take a deep breath and do it.

    STEP TEN: If it worked…Congratulations! But your not through…advance to STEP TWELVE!

    STEP ELEVEN: If it didn’t work and you find yourself looking again at that familiar error message saying cannot find wp-config.php…you need to totally wipe out everything you uploaded (including the subfolder you created). I know, sounds drastic, but it is necessary. Actually I had to do this twice before I achieved success. Why? I haven’t a clue.

    STEP TWELVE: Complete the Blog naming and email form and the rest of the online steps you are given until you reach the end and receive an email congradulating you on your new blog. PAT YOURSELF ON THE BACK…BUT DO NOT SKIP THE FOLLOWING STEP!!!!

    STEP THIRTEEN: Super-Incredibly Important!!!! Go back to your FTP program and change the CMODS of the folder you changed previously from ‘777’ back to ‘755’ and log out.

    I hope this has been of help. Here’s to less hair loss.

    (Insert all possible indemnifying disclaimers here that you have ever read or skipped over in the past)

    John Wesley

Viewing 15 replies - 16 through 30 (of 52 total)
  • Thread Starter stonercreek

    (@stonercreek)

    Shweels –> Thanks and congrats!
    egwg —-> You are correct some FTP clients don’t allow you, or make it difficult, to change the “numerical” permissions.

    You will or should, however, see 9 check boxes. Note their current positions (that configuration is what gives you the “755”) as you’ll need to return them to that state after installation.

    To change to “777” make sure ALL are checked.
    Don’t forget to change them back in step 13. Good luck

    kellyf1

    (@kellyf1)

    egwg – Sounds like you are on the windows hosting plan. the CHMOD command is a linux/unix command and I know my FTP client can’t change it on the windows plan.

    slargent

    (@slargent)

    thanks for the help Stonercreek… I will try this out once I change the OS to Linux.

    Quick question, I have heard of problems with the rich text editor… After you followed these steps do you still have any ‘show stopping’ issues???

    holocron

    (@holocron)

    Stonecreek>> My holy grail is that you don’t need to follow your steps that include the CHMOD adjustment. You need to get the mysql server correct in place of “localhost” in the wp-config.php file. Other than that, there is nothing other special to do with GoDaddy hosting.

    I just tried your process three times. And it works. But it works to follow the typical 5-minute install as well. I tried that several times. No difference in how it worked.

    The only thing I still see as a problem is that the rich text editor does not want to fuction on GoDaddy. You’re supposed fix above does nothing for that issue.

    Thread Starter stonercreek

    (@stonercreek)

    holocron —> I really appreciate your words.

    holocron –>
    slargent –> As for the “rich text editor” fix, I fear you have read something into my instructions I didn’t intend. If you are referring to STEP FIVE above…it was meant as a caution in general and not aimed specifically at a ‘rich text editor’ fix. As noted it is prefered to use a program to edit a php file that actually recognizes a php file for what it is and cautions that some text editors will save the output as a txt file which of course will not work. I did not intend to suggest a fix to that problem…only to watch out for it.

    holocron –> The above follows every step of the Famous 5 Minute Install…with the additional steps needed to work around specific GoDaddy issues. And as you can see from the notes above, it apparently is working.

    As for the CHMOD recommendations being invalid…I beg to differ. I too have had no trouble, as you noted, in installing previous versions of WP. But with version 2.x, for which these instructions were written, the ‘writes’ must turned on for a successful installation…which they are not, by default, in new GoDaddy accounts.

    kellyfl –> Wonderful point and VERY important! Using the Linux I didn’t realize Windows guys were seeing something different!

    slargent –> You might just give GoDaddy support a call and see if they will change it for you.

    holocron –> I’m pleased you have had no trouble in installing WP. And thanks for your help. For many who have posted hundreds of notes about their frustrations, there apparently is something different about 2.x and the above instructions appear to help those who find themselves stuck.

    holocron

    (@holocron)

    I’m just noting that I’ve had no problems installing 2.x on GoDaddy Linux servers (free and paid). And I still, based on my expierence, believe that no additional steps are required to install 2.x on GoDaddy Linux servers beyond those noted in the 5 min install.

    Beyond that, I was curoius if your extra steps resolved the issue of the rich text editor not working on GoDaddy installs. And your extra, and I believe unnecessary, steps no nto resolve that issue.

    egwg

    (@egwg)

    Kellyf1 –>You were correct. I was signed up with the ASP/Windows account but I went ahead and got it changed to PHP/Linux. It works fine now.

    stonercreek –>Great step-by-step instructions. Very easy to follow and painless.

    renawong

    (@renawong)

    stonecreek->
    I created and uploaded my website using FrontPage. My hosting is with Goddady.com. I’ve just switched the operating system from Windows to Linux and the FrontPage server extensions are installed.

    My confusion lies here. I understand that I cannot use an FTP to upload my web pages created in FrontPage. However, is it possible to install WordPress blog as a sub-directory (mydomainname.com/blog) using an FTP like Filzilla? Would doing so affect the other web pages of sub-directories created in Frontpage?

    Rena

    moshu

    (@moshu)

    Normally you should be able to have your WP install in a subdir without “messing” with the rest of the site.
    And if you don’t open any WP files in FP, you should be OK.
    Yes, when uploading WP, use a “normal” FTP client like filezilla.

    renawong

    (@renawong)

    Thanks, Moshu. I have put off installing WP due to my doubts and confusion. I went through WP installation guidelines on WP website several times and yet I could not find answers to my questions.
    Anyway, I’ll try to install WP according to stonercreek’s installation instructions.

    Rena

    otteralum

    (@otteralum)

    Okay. I have tried the following with no success — looking for ideas.

    1) Ensured correct wp-config DB_HOST location — even deleted mysql, recreated it and tried again.

    2) Tried walking through the CHMOD instructions in tis post — twice

    3) Attempted to comment-out lines 53 and 54 in the wp-settings file as sugegsted in another post.

    4) Attempted all of the above on a linux-php server account and an upgraded cgi account.

    I’m going nuts and very close to dumping wordpess — (I should dump godaddy, but hey I have a year to go on the contract) thoughts?

    otteralum

    (@otteralum)

    Never mind — I’m a massochist and tried it all one more time for sh-ts and giggles — it worked. I think it was the wp-settigns fix that did it. Thanks all for your support.

    view2az

    (@view2az)

    I am having the same issues installing wordpress on my GoDaddy site. It was setup as an .ASP site, and apparently as that I cannot update the CHMOD and therefore cannot install this. I have done everything else. So do I need to change it in GoDaddy to another kind of system to get this to work?

    I found a fix for those using a sub-directory.

    If you open the install.php file you will notice these lines throughout:

    if (!file_exists('../../wp-config.php'))
    require_once('../../wp-config.php');
    require_once('../../wp-admin/upgrade-functions.php');

    Change ../../ in every instance to ../, so you get this:

    if (!file_exists('../wp-config.php'))
    require_once('../wp-config.php');
    require_once('../wp-admin/upgrade-functions.php');

    It should be that when you visit the install.php file it will now find the wp-config file. You may need to do this same thing to every instance of ../../ to get through the installation. They occur all the way down to the very bottom of the script.

    I used Dreamweaver to perform a global change – every single instance of ../../ was changed to ../ throughout my “blog” sub-directory.

    It works beautifully ??

    One more important note…

    I noticed the admin section was NOT finding it’s corresponding CSS file. You can correct this by opening the admin-header.php file and deleting this line:

    <?php echo get_settings('siteurl') ?>

    from this code:

    <link rel="stylesheet" href="../wp-admin/<?php echo get_settings('siteurl') ?>wp-admin.css?version=<?php bloginfo('version'); ?>" type="text/css" />

    so you get this result:

    <link rel="stylesheet" href="../wp-admin/wp-admin.css?version=<?php bloginfo('version'); ?>" type="text/css" />

Viewing 15 replies - 16 through 30 (of 52 total)
  • The topic ‘The GoDaddy Installation Fix’ is closed to new replies.