• Resolved jmgriffing

    (@jmgriffing)


    I have two sites which our company manages that were discovered to have the same problem. It is possible to log into the dashboard, but other than the navigation, everything is blank.

    After searching online, I found the suggestion of resetting theme and plugins then deleting everything except content, putting a fresh install of the newest version’s files onto the server via FTP, then running upgrade.php. I backed up the old files to my desktop and did just that. When I go to http://financialworksms.com/wp-admin/upgrade.php, I get a 500 Internal Server Error.

    When I check the server log, it’s all along the lines of [21-Aug-2014 18:28:19 UTC] PHP Warning: require(./wp-blog-header.php): failed to open stream: No such file or directory in /home/financia/public_html/index.php on line 17

    The files are there. I’ve verified.

    I can delete the latest version files and restore the backup to my computer and things work fine, except for my original problem.

    Suggestions?

Viewing 5 replies - 1 through 5 (of 5 total)
  • If you have visually verified that the files are there, what are the permissions on these files? Do they have read permissions?

    Thread Starter jmgriffing

    (@jmgriffing)

    They do have read permissions. They’re -rw-r–r– with root as owner. No different than any other of our sites.

    644 permissions should be correct. What about the ownership/permissions on public_html itself?

    It seems you are running cPanel (judging by /cpanel loading off the domain you posted). In a default cpanel install the files would be owned not by root but by the user. public_html would be 750 and username:nobody, but everything inside public_html would be username:username.

    Thread Starter jmgriffing

    (@jmgriffing)

    Permissions on public_html itself are 750 and username:nobody.

    I went through and changed permissions. That at least resolved the 500 error. Now to go back to resolving my original problem with the upgrade.

    Thread Starter jmgriffing

    (@jmgriffing)

    Ok. Problem fixed. I realized a step I was forgetting.

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

The topic ‘Website Update Problems’ is closed to new replies.