• Martijnchel

    (@martijnchel)


    Hi,

    I got this fatal error when I upgraded to 3.1:

    Fatal error: Class ‘WP_List_Table’ not found in /usr/home/deb18228n2/domains/homecinemamagazine.nl/public_html/wp-admin/includes/list-table.php on line 76

    Restoring my backup does not even help..

    What can I do?
    Please help!

Viewing 13 replies - 16 through 28 (of 28 total)
  • zaccc

    (@zaccc)

    I will wait to fix a bug in WordPress. Every time when I worked upgarde, I deactivated all plugins. I copied the admin and includes folders and everything worked great until version 3.1.

    Dax

    (@daxpod)

    As an FYI for others still having issues. My host auto-upgraded my install but didn’t update the plugins first. BackWPUp was the module that caused me to get the error:

    Fatal error: Class ‘WP_List_Table’ not found in …/wp-admin/includes/list-table.php on line 76

    and on another installation be stuck in the upgrade loop.

    I just removed the plugin, downloaded the latest, and reinstalled it (after upgrading any other plugins as well). All is good.

    beertainment.tv

    (@beertainmenttv)

    @martijnchel

    I use WPeMatico too and got around the issue.

    Go into your plugins folder and rename the WPeMatico folder to whatever (I did WPeMatico2). The site should come back up.

    I then went back to the plugins page from the dashboard and WP told me WPeMatico was deactivated. Search for WPeMatico again from the Add New plugin screen and you’ll see an “Upgrade/Update” (don’t remember now) link instead of an install. Hit it and everything seems to be working fine again. It even kept my previous settings.

    Hope this helps.

    Thanks to: optimisticfriend

    Your instructions saved me a massive amount of work.

    One tip to everyone:

    You can RENAME each plugin one by one. Then you will magically see when you have it right. That is what I did. Worked great. Same idea as optimisticrfriend, but one at a time.

    govpatel

    (@govpatel)

    You archive same thing by renaming the plugins folder as whole create blank plugins folder and log in now they are all deactivated and go back in ftp and rename original back to plugins then activate one at time from admin.

    cpiggott

    (@cpiggott)

    https://www.techtoit.com/
    After updating the website,the site worked for around 12 hours, this morning woke up to Fatal Error. We have no back up of the site due to it being less than a month old. I renamed the wp-content/plugins folder and am now getting a D:\Hosting\7365051\html\wp-includes\kses.php on line 39 error. THing is i refresh the page and it is always a different fatal error. Im going to try one of the fixes above by reinstalling 3.1 but you guys have any idea of other fixes?

    jfryw

    (@jfryw)

    Facing the same problem of a site blank after the WP 3.1 auto update.
    This is how I got mine back.
    Using the ideas from this forum post I first changed the name of my wp-content/plugins folder. My site came up after that no errors. Then I changed wp-content/plugins back to the correct name and proceeded to rename each folder one at a time in the plugins folder to see which plugin caused the problem. After each rename I did a browser refresh of my domain. Finally came to a plugin called share-post. Renaming this plugin brought my site back. Interestingly, the plugin was not Activated in the WP-Admin Plugins. When share-post was renamed it basically did not exist and allowed my site to load correctly.
    Hope this helps.

    govpatel

    (@govpatel)

    @cpiggott

    D:\Hosting\7365051\html\wp-includes\kses.php on line 39 error.

    Are you getting wp-includes/filename error if so using ftp replace wp-includes folder from fresh download.

    Apparently this is a common issue with upgrading WP 3.1 on a Windows server. To cure it, open your index.php file and delete ./ from before `(./’wp-blog-header.php’);
    ?>` in the last line of code. This should sort it.

    Hey,
    we upgraded WP 3.1 on a Windows server and afterwards we wanted to put our website “under constructions” and thought that we could do that by changing the URLs. Now we can’t open the link to enter onto the admin-page anymore. The homepage itself is still available but completly changed (it looks this: https://www.fs-romanistik-bonn.de/?page_id=8) and doesn’t work anymore.
    We’re hoping to get a quick answer. Thanks in advance! ??

    Our problem has been solved under “how-to-end-troubleshooting” -> “can’t open the admin-page anymore”.

    I had the same issue:
    Fatal error: Class ‘WP_List_Table’ not found

    I found wpematico to be the issue. There was an update available, the latest version is good.

    To fix the issue I changed the plugin directory name by adding an under-score and then going to the plugin admin page. That will automatically deactivate any plugin that it can not find.

    Your plugin admin page url is:
    https://domainname.com/wp-admin/plugins.php

    If you’re not sure what plugin is doing it, I suggest changing the name of each plugin one at a time until you find the culprit.

    Great answers to what seems to be a common problem. I had the fatal error issue and per advice here was able to restore my site in a short time with minimum hassle. Thank you so much!

Viewing 13 replies - 16 through 28 (of 28 total)
  • The topic ‘Fatal error upgrade to WP 3.1’ is closed to new replies.