WordPress.org

Ready to get started?Download WordPress

Forums

Fatal error upgrade to WP 3.1 (29 posts)

  1. Martijnchel
    Member
    Posted 3 years ago #

    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!

  2. optimisticfriend
    Member
    Posted 3 years ago #

    I rec'd the same error on one of my blogs today as well. I don't see a "list-table.php" file in the includes directory. It might be a plugin issue. If I find a solution I'll post it here....working on a fix for my site right now.

  3. Martijnchel
    Member
    Posted 3 years ago #

    Thanks. Please let me know!

  4. optimisticfriend
    Member
    Posted 3 years ago #

    Fixed my issue, which appears to be something to do w/ the plugins.

    This worked for me:
    1. Using an FTP program (such as FileZilla), I re-named the plugins directory on my site. It is at /wp-content/plugins/ [changed the name of "plugins"]
    2. I refreshed the site and rec'd a few errors for files accessed in my wp-content directory [I rec'd errors for advanced-cache.php, db.php and other files] - I noted the file names in the error messages after each refresh and changed the names of those files as well - one at a time after each refresh]
    3. I refreshed the site again - no errors and WordPress login loaded. Fixed!

    Subsequently, I renamed the plugins directory back to plugins. Then once logged into WP, I visited the plugins and turned them back on one at a time. No issues now.

    I hope this helps.

  5. Martijnchel
    Member
    Posted 3 years ago #

    Could you please help me with that?
    I changed the plugins name and now the website works. But where do I see the file names that I have to change?

    Thanks!!

  6. Martijnchel
    Member
    Posted 3 years ago #

    I see no errors when I load the website, but when I change the plugins name back it has the same error again.
    The only thing that is not working right now are the plugins.

  7. optimisticfriend
    Member
    Posted 3 years ago #

    You may not need to change any if the site works now. I continued to get errors after changing the name of the plugin directory. They were files loaded by the plugins such as db.php, etc. However, if you didn't continue to get errors likely nothing else to change.

  8. Martijnchel
    Member
    Posted 3 years ago #

    Wait! I restored back to 3.05, so now I upgrade to 3.1 again. I will probably get the errors now.

  9. optimisticfriend
    Member
    Posted 3 years ago #

    You'll need to turn the plugins back on from the admin panel in WP.

  10. Martijnchel
    Member
    Posted 3 years ago #

    Ok.. I have 3.1 installed now. I changed the plugins name and the website works.
    But, when I change the plugins name back it gives the same error again. What can I do?
    Without plugins it seems to work fine and without errors.

  11. optimisticfriend
    Member
    Posted 3 years ago #

    Try turning the plugins on one at a time to see if you have a conflict.

  12. Martijnchel
    Member
    Posted 3 years ago #

    I cannot turn any plugins on since the path to /plugins does not excist anymore. When I change it back to /plugins I get the error message.

  13. Martijnchel
    Member
    Posted 3 years ago #

    Suddenly I saw all the plugins back (after I changed the folder name back to /plugins) and I turned them on one by one!

    Anyone who has WPeMatico installed... delete it from your server!! WP 3.1 hates it!

  14. Vibranthealthsolution
    Member
    Posted 3 years ago #

    WOW, Thanks so much for your means to fix the upgrade issue for fatal errors, Optimisticfriend. I had the db.php error too and have been searching for hours and going through hostgator support trying to fix! Your Fix work, Fabulously!! :)

  15. govpatel
    Member
    Posted 3 years ago #

    2. I refreshed the site and rec'd a few errors for files accessed in my wp-content directory [I rec'd errors for advanced-cache.php, db.php and other files] - I noted the file names in the error messages after each refresh and changed the names of those files as well - one at a time after each refresh]

    It is not a good idea to make changes to any of core files as next update you will be back to where you were.

    90% of time its the plugins or the theme that are not compatible with the upgrade so deactivate all plugins and then update

  16. optimisticfriend
    Member
    Posted 3 years ago #

    Thx. Since I changed the name of the plugin directory it couldn't use the files; they were all plugin related files (not core files). Once WP loaded correctly, I just renamed the files back to their original names and everything works fine. However, I did turn on the plugins one at a time to determine which ones worked OK.

    The upgrade issue appears to be associated with plugins that have conflicts w/ WP 3.1

    Again, thx for the feedback.

  17. zaccc
    Member
    Posted 3 years ago #

    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.

  18. Dax Davis
    Member
    Posted 3 years ago #

    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.

  19. beertainment.tv
    Member
    Posted 3 years ago #

    @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.

  20. johnpent
    Member
    Posted 3 years ago #

    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.

  21. govpatel
    Member
    Posted 3 years ago #

    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.

  22. cpiggott
    Member
    Posted 3 years ago #

    http://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?

  23. jfryw
    Member
    Posted 3 years ago #

    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.

  24. govpatel
    Member
    Posted 3 years ago #

    @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.

  25. TimChase
    Member
    Posted 3 years ago #

    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.

  26. HELP NEEDED
    Member
    Posted 3 years ago #

    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: http://www.fs-romanistik-bonn.de/?page_id=8) and doesn't work anymore.
    We're hoping to get a quick answer. Thanks in advance! :-)

  27. HELP NEEDED
    Member
    Posted 3 years ago #

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

  28. Randy
    Member
    Posted 3 years ago #

    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:
    http://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.

  29. dwojta
    Member
    Posted 3 years ago #

    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!

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags