The GoDaddy Installation Fix

i did all these steps.. but the page wp-admin/install.php can`t open ( empty white page)
??

How is this so so so difficult? I currently have 4 sites running wp 2.0, 2.01 and 2.02 on Go Dadddy. I have helped friends install another 3 wp installs on GoDaddy as well. If a moron like me can install one then anyone can.

What did I do to put the sites on? I followed the directions on the Codex.

1. Change the config file, you need to get a mysql database, easy to sign up for it, wait for it to be created and then get the host it is on. Remember the name of the database is the same as the username you created. Localhost doesn’t work, but after you have created the database, click on the eye icon and you will see the name of the host. Easy as snot.

2. Use Core Ftp or any other ftp program and start uploading it. If you are like me, on a gprs connection, leave the house for a few hours or go eat dinner or whatever and come back when it has been uploaded. If you have a quick connection, like I do at the school I teach at, then grab a cup of coffee and watch the news on the telly.

3. When it has finished uploading, run the 5 minute install and all is done, no problems. no chmoding or anything.

Reading this thread is causing me to stratch my head as to why this is so difficult for y’all. I wish I could help out. I can only offer a tip: Maybe you are making things too difficult, try KISS.

Friends,

1. I have a virtual semi-dedicated server in GoDaddy. With the Plesk 7.5 I created my MySql, and see the information that the Plesk retourned: host is in mbaeducation@localhost.

2. In GoDaddy, I create a subdirectory named \httpdocs\wordpress\ – (\httpdocs\ is the GoDaddy root.

3. I changed the wp-config.php to mbaeducation + mbaeducation + password + localhost (see the item 1 above)

4. I transferred all .php files and others, to \httpdocs\wordpress\ (the ws-pro transferred, in ascii mode, including all subdirectories under the \wordpress\ directory, as \wordpress\wp-admin\, etc).

5. I run \wp-admin\install.php and he told me that don’t find the wp-config.php.

I have some experience in .php (but small), for this reason please help answering my question and/or explaining better this subject:

Question a – The wp-config.php must be installed in what path (see item 5 above)?

Question b – The chmod for the \wordpress\ directory is 755, this is correct?

Question c – It is impossible (by other reasons) to install the WP in my root directory, for this reason I installed in \wordpress\ and not in the root. This is correct?

This is a difficult to understand situation, I already installed some .php programs in other servers without any problems, and now, I followed exactly the WP installation instructions and allways I get the ‘don’t find the wp-config.php’ message, and this config file is really in the \wordpress\ directory, exactly as in the item 3 above.

Please kindly help!

Best regards!

Thanks, stonercreek. Your instructions on how to install wordpress on GoDaddy were very clear. Following them faithfully resulted in a one attempt successful install.

I really need some help with this! i’ve tried all day and looked thorugh all the posts about godaddy. i’m not too hosting & ftp literate but did set up WP on with another host. If anyone can give me some personal help at some point i’d be forever indebted and will send you a t-shirt! ( i run a t-shirt company https://www.peoplelikeucollective.com) My AIM name is PLUC 2006. I’m really getting desperate here!

Thanks!

Thanks a TON for the info. I’d been struggling for the past day on this. Couple things:

– GoDaddy support people aren’t too keen on these issues.

– I had to switch over to Linux from Windows based hosting due to the PHP stuff, but it works great now. (No fee, didn’t affect the rest of my stuff.)

– I used notepad to edit the wp-config.php file and it works just fine. (no need for any sort of web editor)

– Lastly, SmartFTP v2.0 is a great little freeware FTP program (for Windows) and you can do the CHMOD on the directories with it no problem.

I’m a total newcomer to all of this build a website stuff! I thought I uploaded Word Press to Go Daddy (finally) but then couldn’t find it at my site. I reviewed the instructions and realized that I didn’t create a database for WP at my site. I checked GoDaddy’s FAQs on how to do that but couldn’t find anything. Can someone please tell me how to create a database? Thanks sooooo much for any help given!!! Kate

Lost of great ideas here. But here’s what I did:

After signing up with GoDaddy and transferring my domain, I didn’t want to be restricted by their “QuickBlog”, so I chose WP. After reading the 5-minute Install and this post, I decided to just try it.

So at GoDaddy, I switched from Windows to Linux hosting and setup the MySQL database. So far so good.

I had originally wanted to have a main page and the blog. So, after unzipping WP, I renamed the folder “blog” and used GoDaddy’s FTP from their control panel to upload it. tried the admin page and it worked perfectly. Followed the install and I’m up.

But I since decided on just the blog with no main page. I used a simple PHP redirect so I didn’t have to shuffle the directories.

All in all, a very painless experience.

Thanks RyanS! I think its finally installed!!! This has been a huge learning experience!

When I tried to log in I got the following parse error:

Parse error: parse error, unexpected ‘}’ in /home/content/D/i/z/DizzyIzzie/html/wordpress/wp-content/themes/default/functions.php on line 409

I’m not sure what to do about it. If anyone knows please share-Thanks ever so much!!!

Ryan: But I since decided on just the blog with no main page. I used a simple PHP redirect so I didn’t have to shuffle the directories.

WP hates redirects ??
You may want to take a look at this tutorial: https://codex.www.ads-software.com/Giving_WordPress_Its_Own_Directory

UNCLECHE:
Though your post says you wish you could help out, I’m having a bit of trouble finding any evidence of such intent in your post. Was the purpose of your post to make us feel worse than we already do? If so, congratulations on your success.

STONERCREEK:
You’re an angel for documenting your install process on GoDaddy. After 5 days, repeated reading of reams of WordPress documentation in support and codex, repeating and verifying install steps and logins countless times, reading personal WP help blogs, watching 2 WP install .swf tutorials at least twice, plus being lucky enough to find your post, Word Press is finally connecting to my host.

Had to change a few things along the way:

GODADDY: Changed from Windows to Linux. GoDaddy documentation and support staff say they love .php, but Word Press didn’t work for me until I switched to Linux.

HOSTNAME: Wish the statement “99% won’t need to change localhost” could be removed or edited in wp-config.php file. Yes, GoDaddy does use a different database host name, as you mention in your post.

CHMODS: Initial CuteFTP help file search by CMODS found nothing, but searching by “777” showed it to be CHMODS.

CUTEFTP: Followed CuteFTP help file instructions “right-click on file to view properties; if it’s not there, you can’t change CHMODS”. For me, CuteFTP did not show options to change CHMODS, so I switched to SmartFTP, which let me change CHMODS with a simple right-click.

CASE SENSITIVE: Directory names at GoDaddy appear to be case-sensitive. When logging in via IE, GoDaddy folder name case appears to require exact match.

I’ve worked in tech support since 1996, figured out DOS by myself, am A+ certified, comfortable with command lines, work with XML tags and conditional statements every day, possess a reasonably logical mindset, and am a persistent, never-give-up troubleshooter with tech issues. Despite not being a tech novice, Word Press was one of the most time-consuming and frustrating install endeavors I’ve encountered in years.

Looking back, of course the install seems easy now. Should I ever need to repeat it, I imagine it will indeed be done in 5 minutes. If I only knew Monday what I know today…

Thanks again for sharing and educating those suffering through the “famous 5-minute install”.

Well I’m still trying to install and use Word Press at Go Daddy. I thought I had it the other day but keep getting parse errors. I’ve deleted and started over countless times and am ready to spend the money to switch to a different host (although I’d really like to conquer the Go Daddy install!)

If anyone has a suggestion on repeated parse errors I’d really appreciate hearing it.

TWITLET:
If your post is solely to vent some frustration, that’s understandable.

On the other hand, if you’d like some actual troubleshooting assist, then additional info would be helpful (and in fact impossible to proceed without it):

* What is the exact text in the parsing error?
* When exactly does the parsing error occur?
* Which template are you using?
* Did parsing errors occur only after editing the template?
* Which operating system did you choose at GoDaddy?
* Other than the parsing error, have you been able to install and connect to your database successfully?

MOSHU:

My bad. I really didn’t explain the very well and I’m going on 23 hours with no sleep right now, so bear with me if this gets….loopy. First, thanks for that link. I’m going to need that in the future.

Second, what I should have said was that there was no site to begin with. The first action I took on the site was to FTP WP to “mydomain.com/blog”. There was nothing except a GoDaddy place holder. Since I wanted to just type in “mydomain.com” rather than “mydomain.com/blog” every time, I made my main index.php a redirect to “mydomain.com/blog/index.php” and it works seamlessly.

twitlet:

Thanks and sorry for a late reply. I’d like to add a question to PinklyToe’s list:

*How are you uploading to Go Daddy? Is it CuteFTP (or similar) or Go Daddy’s FTP from their Control Panel?

For the record, I used their FTP. The only problem I’ve had since my install was an issue today with a plug-in I installed, but that was on me for not RTFA.

TWITLET:

Upon reading further up in the thread, I see you’ve already pasted your exact parsing error. Nicely done! The only good thing about errors is that they sometimes tell us exactly where the problem is, and fortunately that may indeed be the case here.

My interpretation of the error: WordPress is saying “I don’t understand one of the brackets in line 409 of the functions.php component of the default template.”

Great! Now we know exactly where the problem is, so how do we find it and fix it? There are only, like, fiddy billion brackets in a single template component, so just looking for one bracket won’t work.

The error was nice to tell us exactly which line the rogue bracket is on. It’s on line #409. Hmmm. the lines aren’t numbered in the WP admin panel, are they? Boy, that’s gonna be a pain to find line #409.

Just for grins, I changed my template to default, clicked on “Functions” in the right margin of Theme Editor window, then copied and pasted all text of Functions.php into an Excel spreadsheet which counted the lines for me.

Though I have less than 409 lines/rows in my Functions.php, you might have more lines if you’ve edited this component. It might be quicker for you to start looking from the bottom, then upward, at the Functions.php when hunting the naughty bracket.

So, how will you know which bracket is bad? If it were me, I’d want an untouched original to compare my “bad” one to. I’d locate an original, unedited Functions.php and compare mine to the original, starting from the bottom, then going up/backwards.

If you don’t have a backup of the original “default” template components, maybe there’s one available here at www.ads-software.com you can download to use for comparing against your existing Functions.php component.

Once you know what it’s supposed to look like, and if yours looks different, then you’ll know what to do to fix it.

If you’ve never edited your Functions.php, and if do you find an untouched original Functions.php, it might be quicker to just upload only an original Functions.php to your host, in the correct directory, to overwrite the one that’s misbehaving.

Keep in mind that if you’ve edited your Functions.php already and don’t want to lose the changes, then do NOT upload an original without making a backup copy first, as this would overwrite your edits.

If your first response on reading this is “But I’m not using the WordPress default template!”, then do post an update on what template you are using so we can further ponder the situation.