3.5.1 Update Crashed Site

  • Resolved BGC

    (@bgc)


    13 years, 4 months ago

    I updated from 3.4 to 3.5.1 today and I can no longer access my site and can’t even get to the Dashboard. Here’s the error msg I get:

    Parse error: syntax error, unexpected T_STRING in /home/content/39/9841539/html/wp-config.php on line 97

    Not sure where to start here. I’ll delete my Theme folders and try to force it to Twenty Twelve (I’ll update as to what happens after I do). Short of that… I got nothing. Any help is appreciated.

    Thanks

Viewing 4 replies - 1 through 4 (of 4 total)
  • esmi

    (@esmi)

    13 years, 4 months ago

    Have you been editing your site’s wp-config.php file?

    Thread Starter BGC

    (@bgc)

    13 years, 4 months ago

    I haven’t, no. Site was up this morning, then I updated and then it was down.

    I deleted all themes except TwentyTwelve, no good.

    The only thing I can think of with the wp-config.php is that maybe one of the security plugins (better-wp-security and wordfence)may have edited it… but I’m really not sure, I could be thinking of something different – that was some time ago.

    Thread Starter BGC

    (@bgc)

    13 years, 4 months ago

    I used FireFTP to open the wp-config.php file and found the problem… I think, though I have no idea how it happend.

    94 | /** Sets up WordPress vars and included files. */
    95 | require_once(ABSPATH . ‘wp-settings.php’);
    96 |
    97 | ars and included files. */
    98 | require_once(ABSPATH . ‘wp-settings.php’);

    I’m not much of a coder but lines 97 & 98 seem to be a partial copy of lines 94 and 95. Don’t understand how it happened, but I tried to delete those to lines but my it says I “don’t have permission” to access it. Anyone know which permissions to change so I can fix this?

    Thread Starter BGC

    (@bgc)

    13 years, 4 months ago

    All set. Could change permissions and edit the file in my host’s FTP, but not FireFTP. Deleted those last 2 lines and the site was back up. No idea how or why that happened… w/e.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘3.5.1 Update Crashed Site’ is closed to new replies.