I've read all the tutorials and forums I could, and called godaddy support, before posting this. Even uninstalled WordPress and reinstalled. Same problem. When I go to wp-admin, I get a Parse error: syntax error, unexpected. With bunches of letters, numbers, and symbols following. Granted, I'm a novice. But, I'm not clueless (maybe?). Any help would really be appreciated.
[resolved] It's Been 24 Hours... (21 posts)
-
chandlerwhite
Posted 2 years ago # -
Posted 2 years ago #Frankly, if I don't get any help here I'm ready to go with Bluehost. I've had too many issues with godaddy over the past year, and something tells me the trouble's on their end. It's frustrating time and again to hear from their support staff, "I can't duplicate the issue." And then, of course, the problem is always on my side of the fence. When I first had the blogging notion I went with godaddy's Quick Blogcast. What a joke that was.
-
ClaytonJames
Posted 2 years ago #If you aren't already on a Linux server, you probably won't be sorry in the long run if you go ahead and make the change. Staying with GoDaddy is entirely up to you. Without seeing the exact message, (was there any reference to a particular file in the error string?) it's hard to pinpoint where things are actually hanging up. Although you installed more than once, file corruption or incomplete ftp transfer shouldn't be ruled out completely.
[EDIT] it took me a minute to find this. There is a GoDaddy support Representative that frequents this forum as well. Here is his/her link, if it helps at all. There is a help center link in the profile, but it sounds like you have gone that route already.
-
Posted 2 years ago #Thanks for your help. Here's the actual error string (I hope I'm not giving away anything I shouldn't)...
Parse error: syntax error, unexpected ')' in /home/content/26/4936126/html/wp-config.php on line 12
And thanks for the contact info re the godaddy support rep. I'll pick up matters again in the a.m. -
Posted 2 years ago #I'm not sure exactly where line 12 falls in your wp-config, but if you by chance used an apostrophe (single quotation mark) or a (double) quotation mark in one of your secret keys, I have read that it can cause parse errors sometimes. Good luck to you!
-
dtiger2k
Posted 2 years ago #Lines 2-18 in the wp-config.php file are comment lines unless they have been physically changed. Can you post the URL to the site here? Maybe I or someone can look at the parse error and figure out something for you.
-
Posted 2 years ago #Man, this is great. URL is panicattackology.net. I'll recheck the config, but I've checked it a jillion times. Thanks so much.
-
Posted 2 years ago #Hmm, I checked out the page but it doesn't help to much. It looks like a WordPress install by godaddy. I'm not sure with godaddy if you have the ability to create your own databases but if you do then the best approach might be to delete their install, download wordpress from this site, create your database and install it yourself.
The problem is that without seeing the files on your server it's hard to tell what's going on. As I stated above line 12 in that file from a normal install should be a comment line. I'm not sure what it is from godaddy's install.
-
Posted 2 years ago #Okay, time and again it's this line that the error message is causing the parse error...
define('DB_COLLATE', );
That's exactly how I have it written in the config.php file. -
Posted 2 years ago #I think it should look like this
define('DB_COLLATE', '');...any second opinions?
-
Posted 2 years ago #Your right Clayton, it needs the ' ' in there.
I was able to duplicate the error on my site by removing those ' '
-
Posted 2 years ago #I went back in and changed the lines to include the single quotes on COLLATE and LANG. Well, it's gone from bad to worse. Now I'm getting Page Not Found when I try to link to WP. Doesn't WordPress have tech staff review these forums?
-
Posted 2 years ago #Took out the single quotations and I'm back to parse error on line 7.
-
Posted 2 years ago #Doesn't WordPress have tech staff review these forums?
It's all volunteer in the forums, but yes, they sure do. I just don't really think it's a wordpress problem at this point. I did 4 installs this weekend with the current 2.8.4 download from here, and had no issues at all. Certainly those errors that you have weren't in my copy of wp-config-sample.php. I question the integrity of the file(s) completely at this point.
My next step would be to download a fresh copy of 2.8.4 from here, open wp-config-sample, fill it in with the correct database info, change the name to wp-config and replace the existing one with it. Not overwrite, replace.
That's just me though.
-
Posted 2 years ago #Looks like you have multiple issues with that config file and possibly your database as well. I agree with Clayton on atleast replacing the whole config file if not re-installing from a fresh DL from here.
-
and line 7 is probably this line.
define('DB_HOST', 'localhost');edit the next wp-config.php you create properly, and your errors will go away.
re remarks about database from the previous poster: nothing that the OP has said has indicated any issue with the db -- in fact, there isnt even a connection being made at this point, due to the errors, so I dont even know where you are getting that.
-
Posted 2 years ago #With regard to the problem being in the DB HOST. Could be, because WordPress is saying godaddy's host name should resemble ......secureserver.net, and godaddy is telling me it's ......hostedresource.com.
-
Posted 2 years ago #I found a page that showed a possible DB_HOST value for godaddy of: h41mysql52.secureserver.net. I'm not sure what kind of access you have to database tools but you might be able to find the exact host through your DB tools admin.
If I give you a contact number would you want to call and maybe work through this on the phone?
Daniel
-
Posted 2 years ago #Actually I just found this page http://help.godaddy.com/article/5111 that appears to say leave DB_HOST as localhost. Have you tried localhost there?
-
@chandlerwhite
Sounds like your site may have been compromised. I'm going to have our security team take a look and get in touch with you. In the meantime, change the FTP password to a strong password, uninstall and reinstall, then re-upload the site. -
Posted 2 years ago #After deleting everything I'd previously installed and starting from scratch on both the godaddy and WP sides of the fence; somehow, someway it all worked. Again, thanks to all who did their best to help me!
Topic Closed
This topic has been closed to new replies.
