Support » Fixing WordPress » wp-admin/edit.php leads to blank page not All Posts

  • We are using WordPress 3.8.1 at

    THE SYMPTOMS: From the Admin dashboard Posts: All Posts (wp-admin/edit.php) returns a blank page. Additionally, Posts: Categories returns a Categories page with no categories listed (although the number of categories for the site are enumerated at the top of the page with many pages of categories). One of the plugins settings pages also returns a blank page. Pages also returned a blank page, but that part is resolved.

    WHAT I’VE DONE: First I disabled all of the plugins. Two plugins upon deactivation returned the function of displaying Pages. But deactivating all of the plugins resulted in no change for the page display of posts, nor categories. The posts are therefore available from the front end, but not the dashboard.

    I reinstalled wordpress. Then, out of frustration also replaced the wp-includes folder as well as the wp-admin folder with fresh folders from a new download of wordpress.

    Last, I restored from a Vaultpress backup.

    The theme is Pagelines (Pro version).

    I simply don’t know what to do next to get this working again. Thanks in advance for assistance.

Viewing 15 replies - 1 through 15 (of 29 total)
  • The white page you’re describing is usually the sign of a PHP error occurring on your site. Are you familiar with how to view the error logs on your site? Depending on the host, sometimes the error logs are only available when you log into your host’s control panel. Other times with cPanel sites, you can just look for a file called error_log at the root of the website.

    If you see any errors in there (particularly those that refer to the edit.php file you just mentioned), if you share those here, it will really help the volunteers here to help you.

    Scott Fennell


    Have you tried switching themes and disabling all plugins?

    Not familiar, but reading the Codex pointed me to enabling Debug in the config file, which I have done. I’m reading the debug log this morning.

    Yes, I disabled all of the plugins (more than once) and at least one problem was identified as being caused by a particular plugin.

    I have not tried switching themes because this is one of those cases where this is the theme that the client desires. That will be a last resort, but thanks so much for the reminder that a theme update could create conflicts as well.

    The Debug log is pointing to two plugins that are throwing most of the error messages. But then there is reporting regarding functions.php in the wp-includes folder. Not sure what that is about.

    Here are the strings about function.php:
    [25-Feb-2014 03:45:56] PHP Notice: is_home was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.) in /var/www/vhosts/ on line 3049
    [25-Feb-2014 03:45:56] PHP Notice: is_front_page was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.) in /var/www/vhosts/ on line 3049
    [25-Feb-2014 03:45:56] PHP Notice: is_feed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.) in /var/www/vhosts/ on line 3049

    Helping to understand what these particular returns from debug would be most helpful at this point. Thanks.

    Scott Fennell


    Enabling debug was a good step, nice work.

    Switching themes doesn’t have to be permanent, it can just be seen as a temporary debugging step so you can determine if it’s part of the problem.

    The debug messages that reference core files such as wp-includes are 99.9% sure being triggered by your plugins or theme — they’re not core bugs even though it kind of reads like that in the debug message.

    A codex search for any of those terms (is_feed(), etc) will give you a sense of what they mean, though that’s more just to satisfy you’re curiosity. You’re only going to fix this in one of two ways:

    1) Switch themes and disable plugins.

    2) Continue debugging until you find the code that breaking your site and fix the code.

    If you’re not up for #2, you might as well go to #1.

    Thanks. That helps me to understand the message re: functions.php. I’m going to continue on the path of removing plugins. I will also double back on the theme (Pagelines Pro) to be sure that the most recent version is installed and if there are still issues then switch themes. I so appreciate the time people take to help in these situations. Not fixed yet, but these suggestions offer hope!

    Got rid of several plugins which removed many lines of debugging errors.

    Now I’m down to 2: Here is the first error listing the plugin file. Following that is code from the plugin that I “think” is the right section of the file:

    Debug reported:
    [25-Feb-2014 17:06:30] PHP Notice: Undefined index: HTTP_ACCEPT in /var/www/vhosts/ on line 21

    From the plugin php file:

    function isMobile()
    // Check the server headers to see if they’re mobile friendly
    if (isset($_SERVER[“HTTP_X_WAP_PROFILE”])) {
    return true;
    // If the http_accept header supports wap then it’s a mobile too
    if (preg_match(“/wap.|.wap/i”, $_SERVER[“HTTP_ACCEPT”])) {
    return true;
    if (preg_match(“/iphone|ipad/i”, $_SERVER[“HTTP_USER_AGENT”])) {
    return true;
    // None of the above? Then it’s probably not a mobile device.
    return false;

    I ran it through a validator, but I’m not sure what needs to be fixed.

    Still have issues at

    Taking the next step, I tried to change themes from Pagelines Framework 2.44. When I activated the alternate theme, the site completely disappeared. All white. Could not log in to admin, the website itself would not load. So I manually restored a backup, because Vaultpress needs a working wordpress installation to restore a backup.

    What I’ve done:
    1. Used debug to identify errors
    2. Disabled all plugins
    3. Deleted plugins that showed errors in debug
    4. Optimized and repaired the database Myphp Admin at the host.
    5. Reset permalinks
    6. I’ve also placed new wp-admin and wp-includes folders.

    The general problem that I’m trying to fix is that edit.php does not load All Posts from the dashboard. It leads to a white screen.

    I have not been able to change the theme to see if it is the problem and I’m not sure how I would do that since changing the theme destroys the website and dashboard.

    Would it be possible to reinstall the theme on the back end with an upload?

    I’m sure I’m missing something. Just don’t know what I’m missing. All I can think to do now, is to repeat what I’ve already done to see if I’ve missed something. Any other ideas or approaches would be most appreciated. Thanks.

    At present, no errors are reported in the debug log. Still have the same problem of edit.php not loading (view All Posts).

    Scott Fennell


    what theme did you switch to? did you try a bundled theme such as twentythirteen?

    Did you enable debug mode in wp-config to show debug messages in the browser? that’s not appropriate for live sites but can sometimes be more intuitive than a debug log.

    I chose another Pagelines related theme. Now, after spending hours manually restoring the site because it crashed my installation, I’m a little paranoid about changing themes. I am suspecting that there may be a problem with the theme, however, since there are no errors being logged but I still have the same problem. I have requested assistance at Pagelines.

    I did not enable debug node to show messages in the browser. Rather I used the example in the Codex which hides the browser results, but logs the errors to the debug.log file; i.e. “The following code, inserted in your wp-config.php file, will log all errors notices and warnings to a file called debug.log in the wp-content directory. It will also hide the errors so they do not interrupt page generation.”

    So your suggestion is to enable debug in the config file allowing the errors to be created live on-site. I can do that. And will. Thanks.

    Scott Fennell


    (deleted- too many windows open)

    I set the display section of the debug code this way:

    ‘WP_DEBUG_DISPLAY’, true

    I didn’t see anything on the site from loading site pages, nor from the dashboard (e.g. loading edit.php) (

    I did get an error message in the log file, however, that I had seen before:

    Undefined index: HTTP_ACCEPT in /var/www/vhosts/ on line 21

    Scott Fennell


    If you’re still getting error messages from plugins, then you still have plugins running. You should remove all plugins as a temporary debugging step.

    Hurrah. I got an error message when I went to edit.php

    This was displayed in the browser window:

    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 524288 bytes) in /var/www/vhosts/ on line 1242

    I think that is the first time I was excited about getting an error message! OK if its a memory allocation problem can you help me with this, or point me to some information?

Viewing 15 replies - 1 through 15 (of 29 total)
  • The topic ‘wp-admin/edit.php leads to blank page not All Posts’ is closed to new replies.