• Resolved tamerwin

    (@tamerwin)


    First, I’m a capable user, but not an expert. I’m not great at html, but I can navigate to where I need to go.

    I’ve been working on updating our company website, https://www.tamerwin.com, for a few days. The site has been in maintenance mode for about a week. I was just about done when I tried to edit the secondary footer in the Quest (Free) theme and I’m now completely blocked out of WordPress. I cannot reach the admin page and my website is a blank white screen. I tried to reinstall WordPress via FTP earlier and it did not fix my problem. I have backed up my SQL database but I’m afraid to delete that from cPanel. Up to being blocked out, everything was working great. Now all I have is a blank screen. No error messages.

    I have since deleted the theme and plugins. The currently installed plugins are twenty fourteen, twenty fifteen, and twenty sixteen.

    Can anyone guide me through the steps to repair the issue here? I need to get this up and running ASAP.

Viewing 5 replies - 16 through 20 (of 20 total)
  • Thread Starter tamerwin

    (@tamerwin)

    @motaz updated all files in those folders. Didn’t seem to change anything…

    New Error Log:

    Warning: DocumentRoot [/home/tamerwin/public_html/performancecenter] does not exist
    Warning: DocumentRoot [/home/tamerwin/public_html/performancecenter] does not exist
    Warning: DocumentRoot [/home/tamerwin/public_html/performancecenter] does not exist
    [Thu Jan 14 12:20:47 2016] [error] [client 173.88.175.70] File does not exist: /home/tamerwin/public_html/wp-admin/admin-ajax.php, referer: https://www.tamerwin.com/wp-admin/theme-editor.php?file=inc%2Ftemplate-tags.php&theme=quest
    [Thu Jan 14 12:16:47 2016] [error] [client 173.88.175.70] File does not exist: /home/tamerwin/public_html/wp-admin/admin-ajax.php, referer: https://www.tamerwin.com/wp-admin/theme-editor.php?file=inc%2Ftemplate-tags.php&theme=quest
    [Thu Jan 14 11:16:27 2016] [error] [client 173.88.175.70] mmap cache can’t open /home/tamerwin/public_html/wp-admin/wp-includes/load.php – Not a directory (pid 30749)
    [Thu Jan 14 11:16:25 2016] [error] [client 173.88.175.70] mmap cache can’t open /home/tamerwin/public_html/wp-admin/wp-includes/load.php – Not a directory (pid 30695)
    [Thu Jan 14 11:14:33 2016] [error] [client 173.88.175.70] mmap cache can’t open /home/tamerwin/public_html/wp-admin/wp-includes/load.php – Not a directory (pid 27493)
    [Thu Jan 14 11:14:11 2016] [error] [client 173.88.175.70] mmap cache can’t open /home/tamerwin/public_html/wp-admin/wp-includes/load.php – Not a directory (pid 26957)
    [Thu Jan 14 11:14:09 2016] [error] [client 173.88.175.70] mmap cache can’t open /home/tamerwin/public_html/wp-admin/wp-includes/load.php – Not a directory (pid 26893)
    [Thu Jan 14 11:05:14 2016] [error] [client 173.88.175.70] mmap cache can’t open /home/tamerwin/public_html/wp-admin/wp-includes/load.php – Not a directory (pid 12044)
    [Thu Jan 14 11:04:05 2016] [error] [client 173.88.175.70] mmap cache can’t open /home/tamerwin/public_html/wp-admin/wp-includes/load.php – Not a directory (pid 10192)
    [Thu Jan 14 11:03:55 2016] [error] [client 173.88.175.70] mmap cache can’t open /home/tamerwin/public_html/wp-admin/wp-includes/load.php – Not a directory (pid 9808)

    Your new error log file looks the same as your old error log file (including the times), so maybe you’re putting your files in totally the wrong place.

    What is the root folder for your domain? You should be able to see this in the domain management portion of your cpanel.

    Thread Starter tamerwin

    (@tamerwin)

    I don’t know how, but I just fixed it.

    Thanks everyone for your help. I’ve now learned the hard way to not mess with the theme editor!

    of course nothing is changed because this is the same messages not the new one, maybe you need to refresh the error_log first.

    I know it is the same ones because it has the same timestamp.

    Additionally if you deleted everything including files in the directory ‘wp-content’ then I agree with @ancawonka contacting your hosting provider to see if they can retrieve an old backup is your best option at the moment, especially if you don’t have a backup.

    Thread Starter tamerwin

    (@tamerwin)

    You all are right! From what I can figure, I was putting the files in the wrong place, I.E. a folder named wordpress and I also had duplicate copies of index.php

    I really appreciate all your help.

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘Site completely down. White screen of death’ is closed to new replies.