Skip Navigation

[Resolved] Receiving frequent PHP Fatal Error on all sites; appears to be Jetpack conflict

This thread is resolved. Here is a description of the problem and solution.

Problem:
With Toolset Types and Jetpack active I see often this error in the logs:

PHP Fatal error: Uncaught Error: Call to undefined function WP_Installer() in types/vendor/toolset/toolset-common/inc/controller/admin/notices.php:94

Solution:
It's solved in the current stable release.

This support ticket is created 6 years, 7 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Tagged: 

This topic contains 21 replies, has 3 voices.

Last updated by sarahP 6 years, 5 months ago.

Assisted by: Beda.

Author
Posts
#582120

Check out this support thread: https://toolset.com/forums/topic/call-to-undefined-function-wp_installer/

The reported error is almost exactly the same as mine, except for #6, the error is in woocommerce instead of Jetpack. So, the issue appears to happen with more than just Jetpack. Maybe this will help further troubleshoot?

#582331

There are now some errors in the log, but not the ones we are looking for:

PHP Warning:  mysqli_real_connect(): (HY000/2002): No such file or directory in .../wp-includes/wp-db.php on line 1548

Thank you also for that other thread, I will keep an eye on it.

It is still not clear how this error happens.
I will keep the error log under observation as well.

#582481

You found that error on the test site?

I received a very similar error yesterday on my site:
PHP Warning: mysqli_real_connect(): (HY000/2002): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) in /home/SITE/public_html/wp-includes/wp-db.php on line 1548

It occurred several times within an hour. None today; just the usual error (16 times so far). Could there be some connection? Strange that you saw these errors after I connected to Jetpack and imported my Toolset settings.

#582511

Here's one more thread reporting the same error, but they specify that ajax forms are generating the error: https://toolset.com/forums/topic/after-last-update-all-my-ajax-forms-gives-error-in-the-first-run/. Are there any ajax forms on the Test Site? I can't think that I have anything using Ajax on my example site (especially since it is behind a Coming Soon page, but maybe there is something behind the scenes). For what it is worth, I see the error much more frequently on my live sites than on the Coming Soon site.

I went back to the Test Site and added a Jetpack Subscribe and WP Views widget to the sidebar in case these make a difference.

#582915

This issue is finally isolated and resolved.

The fix will be available in the upcoming release (due next week, approximately)

Please let me know if I can help you in anything else!

#584707

This error was due to Jetpack performing background synchronizations.

We add a fix for this error in the Types version that has been released yesterday.

Can you update to 2.2.17 and re-check?
The particular error should not exist anymore.

Note that only this particular errors has been addressed.
You may still find errors in CRED screens related to Toolset.
If so, please open a new report for any other kind of error you may find.

Thank you!

#585030

Yes, it appears to be resolved! I updated both Types and Views on my sites (updating just Types but not Views 2.5 ended up with new errors!) and kept an eye on the error logs over the course of several hours. The error has not appeared since.

Thank you!

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.