How to fix ‘WordPress error: Call to a member function do_action()’ in Plesk servers
In our role as Outsourced hosting support specialists for web hosts, we manage web servers with various control panels such as Plesk, cPanel, DirectAdmin, etc.
With our years of experience and expertise handling the various control panel related issues in servers. we’ve been able to resolve almost all errors in no time.
Recently we faced an issue related to the Plesk Version in the server and the latest WordPress version. While trying to install WordPress via the Plesk panel, we were getting the following error message:
PHP Fatal error: Call to a member function do_action() on a non-object in C:\inetpub\vhosts\domain.com\httpdocs\wp-includes\plugin.php on line 453
Here, we’ll see what causes ‘WordPress error: Call to a member function do_action()’ in Plesk servers and how we fix it.
What causes ‘WordPress error: Call to a member function do_action()’ in Plesk servers
WordPress has been upgraded to the version 4.7. WordPress 4.7 is not supported by all Plesk versions. WordPress 4.7 is supported starting only from these versions:
In Plesk servers with versions prior to these, trying to install the latest WordPress version via Plesk Panel or trying to access WordPress Toolkit, shows up the error:
PHP Fatal error: Call to a member function do_action() on a non-object
Upon investigation, we could see that our server had Plesk 12.5 and OS version Microsoft Windows Server 2008 R2, and the version of Plesk was 12.5.30 #48:
plesk -v Product version: 12.5.30 Update #48 Update date: 2016/10/01 04:07 Build date: 2016/02/03 17:00 Build target: Windows 2008/2012 Revision: 348480 Wrapper version: 1.2
To know the Plesk version information, you can either go to ‘Plesk > Home > System Overview’ or use the following command in command-line interface:
As support of WordPress 4.7 started only from Plesk 12.5.30 #54, our Plesk version was conflicting with the WordPress version and thus giving the error ‘PHP Fatal error: Call to a member function do_action() on a non-object’, while trying to install it.
[ Use your time to build your business. We’ll take care of your servers. Hire Our Hosting Support Specialists and boost your server performance. ]
How to resolve ‘WordPress error: Call to a member function do_action()’ in Plesk servers
To resolve the error related to WordPress, the fix is to update the Plesk version in the server via micro-updates. Plesk micro-updates can be installed either using command-line interface or Plesk panel.
1. Using command-line interface, the commands to update Plesk versions are:
- Plesk 11.x and 12.0 for Linux:
# /usr/local/psa/admin/sbin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component panel
- Plesk 11.x and 12.0 for Windows:
"%plesk_bin%\ai.exe" --console --select-product-id panel --select-release-current --reinstall-patch --install-component panel
- Plesk 12.5 and above for Windows and Linux:
plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
2. Plesk update can also be done via the Plesk web interface at “Plesk > Tools & Settings > Updates and Upgrades” option:
We installed the latest Plesk micro updates in the server via the command line, and got the latest Plesk version in our server.
plesk installer --select-release-current --reinstall-patch --upgrade-installed-components plesk -v Product version: 12.5.30 Update #66 Update date: 2017/06/24 02:00 Build date: 2016/02/03 17:00 Build target: Windows 2008/2012 Revision: 348480 Wrapper version: 1.2
After updating Plesk to the latest micro-update, the WordPress instance for the affected domain was ‘Synchronize’d through the Plesk UI. We then installed the WordPress software from the Plesk panel of the domain, and it was installed fine without any errors.
[ You don’t have to lose your sleep to keep your customers happy. Our friendly Hosting Support Specialists are online 24/7/365 to help your customers. ]
At Bobcares, our 24/7 server specialists constantly monitor all the services in the server and proactively audit the server for any errors or corruption in them.
This enables us to prevent a service downtime for our customers who are web hosts. By following a systematic debugging approach for service or other errors, we have been able to minimize the customer complaints involved.
If you would like to know how to avoid downtime for your customers due to service failures, we would be happy to talk to you.