Skip Navigation

[Résolu] This error message keeps appearing intermittently since your last update.

This support ticket is created Il y a 4 années et 8 mois. 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.

Marqué : 

This topic contains 1 réponse, has 2 voix.

Last updated by Beda Il y a 4 années et 8 mois.

Assigned support staff: Beda.

Auteur
Publications
#584637

Fatal error: Uncaught Error: Call to undefined function WP_Installer() in /home/wp_ax5dpn/gptrove.net/wp-content/plugins/types-access/vendor/toolset/toolset-common/inc/controller/admin/notices.php:94 Stack trace: #0 /home/wp_ax5dpn/gptrove.net/wp-content/plugins/types-access/vendor/toolset/toolset-common/inc/controller/admin/notices.php(72): Toolset_Controller_Admin_Notices->screen_any() #1 /home/wp_ax5dpn/gptrove.net/wp-includes/class-wp-hook.php(298): Toolset_Controller_Admin_Notices->init_screens(Object(WP_Screen)) #2 /home/wp_ax5dpn/gptrove.net/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters('', Array) #3 /home/wp_ax5dpn/gptrove.net/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #4 /home/wp_ax5dpn/gptrove.net/wp-admin/includes/class-wp-screen.php(396): do_action('current_screen', Object(WP_Screen)) #5 /home/wp_ax5dpn/gptrove.net/wp-admin/includes/screen.php(232): WP_Screen->set_current_screen() #6 /home/wp_ax5dpn/gptrove.net/wp-content/plugins/jetpack/sync/class.jetpack-sync-sender.php(131): set_cur in /home/wp_ax5dpn/gptrove.net/wp-content/plugins/types-access/vendor/toolset/toolset-common/inc/controller/admin/notices.php on line 94

#584701

This error is due to (most likely) Jetpack performing background synchronizations.

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

You still seem to run 2.2.16

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