homepage Welcome to WebmasterWorld Guest from 54.167.138.53
register, free tools, login, search, pro membership, help, library, announcements, recent posts, open posts,
Become a Pro Member

Home / Forums Index / Code, Content, and Presentation / Content Management
Forum Library, Charter, Moderators: ergophobe

Content Management Forum

    
Problem with wordpress.org authentication keys--parse error
getting a parse error-unexpected t string message: unable to locate problem
taboo




msg:3956793
 7:42 pm on Jul 21, 2009 (gmt 0)

Please help! This is very elementary but I am in the process of trying to download wordpress.org. Unfortunately I am getting the message parse error-unexpected t-string...line 45. I have looked over this for ':' errors and ' " ' errors but can't find what is wrong. Can somebody please help me with this?

45: define('AUTH_KEY', ''cHNS_y(:]I}qv(V3$3/;t$AK;q^0d]3Y8h wPPA`dm5¦,x6d/n^{j{;^GiXl{_s+');

46: define('SECURE_AUTH_KEY', ''p])8w?t8)a?+BamBE¦K-B 7ejWm<M6B=yBSk/0}KSx&cuqq},.d3[R,pyxN+K]#j');

47: define('LOGGED_IN_KEY', ''D=FUt J]k1&W57LCuY6pDW+`v<.HQy(vZr^[LpnCEdh8/^t.0&1%gM&Acg<O>Zy-');

 

lorax




msg:3957804
 2:00 am on Jul 23, 2009 (gmt 0)

Welcome to WebmasterWorld!
I'm not sure why you're getting that error. I've never seen it. That looks to me like your server has been compromised or is not configured to a standard setup - in which case you should visit the WordPress Forums and see if they can help you get it sorted.

ergophobe




msg:3957834
 3:26 am on Jul 23, 2009 (gmt 0)

I don't think so Gregg - unexpected T_STRING is a PHP error and taboois on the right track - it's usually an unclosed quote, bracket, missing semi-colon or some such thing.

In any case, all the lines you just posted all have unmatched quotes. The second terms all start with a double quote and close with a single. So that's a problem.

Also, T_STRING errors can also be the result of syntax errors above the flagged line. In other words, an unclosed quote several lines up doesn't immediately cause a problem, but the parser gets down to your opening quote on line 45 and takes it as a closed quote. At that point, it is not expecting a T_STRING, so it blows up.

So even though there are syntax errors in lines 45-47, I expect there's one more unclosed quote above line 45, but that's just a guess.

BTW, this might help in the future:
[us2.php.net...]

ergophobe




msg:3957836
 3:30 am on Jul 23, 2009 (gmt 0)

This might help too:
[webmasterworld.com...] - PHP Troubleshooting 101.

Trip down memory lane - seems like a lifetime ago I wrote that one.

Global Options:
 top home search open messages active posts  
 

Home / Forums Index / Code, Content, and Presentation / Content Management
rss feed

All trademarks and copyrights held by respective owners. Member comments are owned by the poster.
Home ¦ Free Tools ¦ Terms of Service ¦ Privacy Policy ¦ Report Problem ¦ About ¦ Library ¦ Newsletter
WebmasterWorld is a Developer Shed Community owned by Jim Boykin.
© Webmaster World 1996-2014 all rights reserved