• Updated to the latest QM version this past Friday, the 13th (bad idea, I know), and I just found out that our site monitoring was picking up intermittent 500 errors all weekend. Looking into it, I see that WordPress and the Apache error log were kicking out the following error. I’ve disabled the plugin for now – appreciate any suggestions:

    An error of type E_ERROR was caused in line 312 of the file /var/www/html/wp-content/plugins/query-monitor/classes/Util.php. Error message: Uncaught Error: Class “QM_Component” not found in /var/www/html/wp-content/plugins/query-monitor/classes/Util.php:312
    Stack trace:
    #0 /var/www/html/wp-content/plugins/query-monitor/classes/Backtrace.php(275): QM_Util::get_file_component()
    #1 /var/www/html/wp-content/plugins/query-monitor/classes/Backtrace.php(209): QM_Backtrace::get_frame_component()
    #2 /var/www/html/wp-content/plugins/query-monitor/collectors/php_errors.php(272): QM_Backtrace->get_component()
    #3 /var/www/html/wp-content/plugins/query-monitor/vendor/composer/ClassLoader.php(578): QM_Collector_PHP_Errors->error_handler()
    #4 /var/www/html/wp-content/plugins/query-monitor/vendor/composer/ClassLoader.php(578): include(‘…’)
    #5 /var/www/html/wp-content/plugins/query-monitor/vendor/composer/ClassLoader.php(432): Composer\Autoload\ClassLoader::Composer\Autoload\{closure}()
    #6 /var/www/html/wp-content/plugins/query-monitor/classes/Util.php(312): Composer\Autoload\ClassLoader->loadClass()
    #7 /var/www/html/wp-content/plugins/query-monitor/classes/Backtrace.php(275): QM_Util::get_file_component()
    #8 /var/www/html/wp-content/plugins/query-monitor/classes/Backtrace.php(209): QM_Backtrace::get_frame_component()
    #9 /var/www/html/wp-content/plugins/query-monitor/collectors/transients.php(91): QM_Backtrace->get_component()
    #10 /var/www/html/wp-content/plugins/query-monitor/collectors/transients.php(59): QM_Collector_Transients->setted_transient()
    #11 /var/www/html/wp-includes/class-wp-hook.php(308): QM_Collector_Transients->action_setted_blog_transient()
    #12 /var/www/html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
    #13 /var/www/html/wp-includes/plugin.php(517): WP_Hook->do_action()
    #14 /var/www/html/wp-includes/option.php(1022): do_action()
    #15 /var/www/html/wp-includes/cron.php(884): set_transient()
    #16 /var/www/html/wp-includes/cron.php(994): spawn_cron()
    #17 /var/www/html/wp-includes/class-wp-hook.php(308): _wp_cron()
    #18 /var/www/html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
    #19 /var/www/html/wp-includes/plugin.php(517): WP_Hook->do_action()
    #20 /var/www/html/wp-settings.php(639): do_action()
    #21 /var/www/html/wp-config.php(101): require_once(‘…’)
    #22 /var/www/html/wp-load.php(50): require_once(‘…’)
    #23 /var/www/html/wp-admin/admin.php(34): require_once(‘…’)
    #24 /var/www/html/wp-admin/plugins.php(10): require_once(‘…’)
    #25 {main}

Viewing 3 replies - 1 through 3 (of 3 total)
  • I have exactly the same error after update.

    • This reply was modified 2 years, 1 month ago by JayFry.
    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Thanks for the reports folks, I’m looking into this.

    markesis

    (@markesis)

    Any update on this?   

    I see QM_Component was added in 3.11.0

    I am seeing the same issue in v3.11.2

    Thanks!

    Stack trace: #0 /srv/www/wordpress/wp-content/plugins/query-monitor/classes/Backtrace.php(275): QM_Util::get_file_component() #1 /srv/www/wordpress/wp-content/plugins/query-monitor/classes/Backtrace.php(209): QM_Backtrace::get_frame_component() #2 /srv/www/wordpress/wp-content/plugins/query-monitor/collectors/php_errors.php(272): QM_Backtrace->get_component() #3 /srv/www/wordpress/wp-content/plugins/query-monitor/vendor/composer/ClassLoader.php(578): QM_Collector_PHP_Errors->error_handler() #4 /srv/www/wordpress/wp-content/plugins/query-monitor/vendor/composer/ClassLoader.php(578): include('...') #5 /srv/www/wordpress/wp-content/plugins/query-monitor/vendor/composer/ClassLoader.php(432): Composer\Autoload\ClassLoader::Composer\Autoload\{closure}() #6 /srv/www/wordpress/wp-content/plugins/query-monitor/classes/Util.php(312): Composer\Autoload\ClassLoader->loadClass() #7 /srv/www/wordpress/wp-content/plugins/query-monitor/classes/Backtrace.php(275): QM_Util::get_file_component() #8 /srv/www/wordpress/wp-content/plugins/query-monitor/classes/Backtrace.php(209): QM_Backtrace::get_frame_component() #9 /srv/www/wordpress/wp-content/plugins/query-monitor/collectors/transients.php(91): QM_Backtrace->get_component() #10 /srv/www/wordpress/wp-content/plugins/query-monitor/collectors/transients.php(59): QM_Collector_Transients->setted_transient() #11 /srv/www/wordpress/wp-includes/class-wp-hook.php(308): QM_Collector_Transients->action_setted_blog_transient() #12 /srv/www/wordpress/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #13 /srv/www/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action() #14 /srv/www/wordpress/wp-includes/option.php(1022): do_action() #15 /srv/www/wordpress/wp-content/plugins/memberpress/app/lib/MeprCptModel.php(166): set_transient() #16 /srv/www/wordpress/wp-content/plugins/memberpress/app/controllers/MeprRemindersCtrl.php(56): MeprCptModel::all() #17 /srv/www/wordpress/wp-includes/class-wp-hook.php(308): MeprRemindersCtrl->schedule_reminders() #18 /srv/www/wordpress/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #19 /srv/www/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action() #20 /srv/www/wordpress/wp-settings.php(480): do_action() #21 /srv/www/wordpress/wp-config.php(85): require_once('...') #22 /srv/www/wordpress/wp-load.php(50): require_once('...') #23 /srv/www/wordpress/wp-blog-header.php(13): require_once('...') #24 /srv/www/wordpress/index.php(17): require('...') #25 {main} thrown in /srv/www/wordpress/wp-content/plugins/query-monitor/classes/Util.php on line 312
    • This reply was modified 2 years ago by markesis.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Error Class “QM_Component” not found after update’ is closed to new replies.