Support » Fixing WordPress » Broken backend (white screen)

  • About two weeks ago, I updated wordpress and several plugins. Everything seemed alright. I posted an article and left. The next day, I couldn’t access the backend no more. The screen was white. I re uploaded wordpress, and I was able to log in again. But the next day, it was broken again… I restored the site to the previous version when it was working. I didn’t update anything, and it worked fine for a couple days in a row. I thought, I’ll try to update the plugins. There, it broke again. I reuploaded WordPress, and it worked again. But the next day, it broke again. I tried to run debug (never did it before) but the screen remains white. I’ll restore the site to the previous working version but I am frustrated, I cannot find out the problem.

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • Moderator t-p

    (@t-p)

    I re uploaded wordpress,

    Have you tried re-uploading manually?

    I restored the site to the previous version

    Not recommended, because there are many possible caveats to this, some of which being it leading to insecure websites as security updates may be included in releases or site breakage as database changes have happened.

    Thread Starter krazygyal

    (@krazygyal)

    I reuploaded it manually via FTP, I can’t do it another way because I have NO ACCESS AT ALL to the backend. Though every time it breaks again at night so I have to reupload WordPress the next day. The only way to get it “fixed” was to restore to a previous version last week. It worked until I updated plugins.

    • This reply was modified 4 years, 2 months ago by krazygyal.
    Thread Starter krazygyal

    (@krazygyal)

    Just for information: the website was restored by my host (files + database)

    Thread Starter krazygyal

    (@krazygyal)

    Here’s the debug log:

    
    [23-May-2018 20:43:49 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 111
    [23-May-2018 20:43:49 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 119
    [23-May-2018 20:43:49 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 121
    [23-May-2018 20:45:30 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 111
    [23-May-2018 20:45:30 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 119
    [23-May-2018 20:45:30 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 121
    [23-May-2018 20:45:54 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 111
    [23-May-2018 20:45:54 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 119
    [23-May-2018 20:45:54 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 121
    [23-May-2018 20:46:02 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 111
    [23-May-2018 20:46:02 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 119
    [23-May-2018 20:46:02 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 121
    [23-May-2018 20:51:07 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 111
    [23-May-2018 20:51:07 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 119
    [23-May-2018 20:51:07 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 121
    [23-May-2018 20:55:18 UTC] PHP Notice:  Trying to get property of non-object in .../wp-includes/class-wp-query.php on line 3502
    [23-May-2018 20:55:19 UTC] PHP Notice:  Trying to get property of non-object in .../wp-includes/class-wp-query.php on line 3504
    [23-May-2018 20:55:19 UTC] PHP Notice:  Trying to get property of non-object in .../wp-includes/class-wp-query.php on line 3506
    [23-May-2018 20:55:19 UTC] PHP Notice:  Trying to get property of non-object in .../wp-content/themes/genesis/lib/classes/class-genesis-seo-document-title-parts.php on line 195
    [23-May-2018 20:55:19 UTC] PHP Notice:  Trying to get property of non-object in .../wp-content/themes/genesis/lib/classes/class-genesis-seo-document-title-parts.php on line 195
    [23-May-2018 20:56:27 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 111
    [23-May-2018 20:56:27 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 119
    [23-May-2018 20:56:27 UTC] PHP Notice:  Undefined index: field in .../wp-content/plugins/pods/components/Templates/includes/functions-view_template.php on line 121
    Moderator t-p

    (@t-p)

    First off, access your server via FTP/ SFTP , or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), navigate to /wp-content/plugins/ and delete/uninstall/rename pods plugin.

    It sounds like you might have something else happening here. Has your hosting environment recently changed, or do you utilize object caching?

    Thread Starter krazygyal

    (@krazygyal)

    I use WP Super Cache. I’m on the same host. They haven’t noticed any change, I didn’t switch plan either.

    My host is restoring my site to an older version (once more).

    They had re uploaded a clean copy of WordPress core files last night. I was able to log on. I just deleted three plugins that were deactivated. I didn’t update anything. I didn’t even post. Logged out. Today, the backend is broken again.

    So I’m going to restore to the older version and try to debug it properly. Even though I don’t really have a clue how to.

    The weird part here is that none of those posted notices will cause a blank screen. Have you tried setting WP_DEBUG to true and loading the page in question? I’m wondering if there’s some insight that could provide us to further assist you.

    Thread Starter krazygyal

    (@krazygyal)

    I couldn’t see the debug on the landing page, it wouldn’t load. It would just be blank and show up like this:

    I found this debug log in the debug log file via FTP.

    I re-uploaded wordpress, I have been able to log on. I deactivated all plugins and I activated Twenty Senventeen theme.

    It seems to be working now but I need to run debug properly to spot the issue.

    For information, php 5.6 runs on my server.

    • This reply was modified 4 years, 2 months ago by krazygyal.
    • This reply was modified 4 years, 2 months ago by krazygyal.
    • This reply was modified 4 years, 2 months ago by krazygyal.
    Thread Starter krazygyal

    (@krazygyal)

    I am going to re activate everything one by one hoping to find the issue.

    • This reply was modified 4 years, 2 months ago by krazygyal.
    Thread Starter krazygyal

    (@krazygyal)

    My backend broke again. I think I found the plugin that is corrupted. More info in this topic: https://wordpress.org/support/topic/invalid-header-26/#post-10347300

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Broken backend (white screen)’ is closed to new replies.