Compatabilty issues with wordpress 4.7
December 20, 2016 at 14:12 #38569
we updated to 4.7 and now we are unable to get into wordpress back end.
we get this error.
<b style=”color: #000000; font-family: Times; font-size: medium;”>Fatal error</b><span style=”color: #000000; font-family: Times; font-size: medium;”>: Call to a member function do_all_hook() on a non-object in </span><b style=”color: #000000; font-family: Times; font-size: medium;”>/home/dianajuhnries/public_html/wp-includes/plugin.php</b><span style=”color: #000000; font-family: Times; font-size: medium;”> on line </span><b style=”color: #000000; font-family: Times; font-size: medium;”>837</b>
can you please help?
DianaDecember 21, 2016 at 14:13 #38576
Is your website online so I can have a look?
CheersJanuary 3, 2017 at 10:32 #38616
Hopefully you’ve been able to get back into the backend of your site by now. If not, here’s what you’ll need to do to make that happen. Use either a FTP program or the file browser in your web host’s control panel to go to the wp-content folder on your server. Look for the plugins folder there. Change the name of that folder to plugins1. That will manually deactivate all of your plugins.
After that, try logging back into the admin. If you can then do this. Create a new folder in your wp-content directory called plugins. Then move your plugins, one by one into the new plugins folder. Check the admin after each move. If it stops working when you move one, then the culprit has been found.
If you can’t log in after changing the plugins folder to plugins1, then open up the themes folder. Change the name of foxy to foxy1. That should manually deactivate the theme. Try logging in at that point.
If you get stuck, let me know.
BillJanuary 3, 2017 at 11:04 #38619
Hi Again Diana,
I did a bit more digging into your specific error message and discovered this happened to quite a few folks out there. It appears that for sites running some types of caching, updating to 4.7 caused the fatal error. There is a WordPress Trac topic about that at https://core.trac.wordpress.org/ticket/39146.
For some of the folks in that topic, they found deleting the object-cache.php file in the wp-content folder on their server fixed the issue. Some also had to roll back to version 4.6 to get back up and running. It looks like this is an issue that the core team will work on and hopefully fix soon with 4.7.1.
BillJanuary 11, 2017 at 04:27 #38669
Super helpful as always.
The topic ‘Compatabilty issues with wordpress 4.7’ is closed to new replies.