Title: PHP Fatal error Last modified: August 31, 2016 --- # PHP Fatal error * [derekakelly](https://wordpress.org/support/users/derekakelly/) * (@derekakelly) * [9 years, 12 months ago](https://wordpress.org/support/topic/php-fatal-error-76/) * PHP Fatal error: Call to a member function get_component() on null in /home/XXXXXXXXXXX/ public_html/wp-content/plugins/query-monitor/collectors/http.php on line 194 * [https://wordpress.org/plugins/query-monitor/](https://wordpress.org/plugins/query-monitor/) Viewing 15 replies - 1 through 15 (of 19 total) 1 [2](https://wordpress.org/support/topic/php-fatal-error-76/page/2/?output_format=md) [→](https://wordpress.org/support/topic/php-fatal-error-76/page/2/?output_format=md) * Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * (@johnbillion) * WordPress Core Developer * [9 years, 12 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7396925) * Can you provide some more information please? Which plugins do you have active in your site? Is there anything out of the ordinary about your site’s configuration( for example, custom locations for the content or plugin directory)? I’m unable to debug this without some more information. * Thanks. * Thread Starter [derekakelly](https://wordpress.org/support/users/derekakelly/) * (@derekakelly) * [9 years, 12 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7396987) * Hi John, * No custom locations. * Upon further review, there are actually 4 lines coming up in the wordpress debug with query monitor in it; * > [19-May-2016 18:32:05 UTC] PHP Notice: Undefined index: _qm_key in /home/XXXXXXX/ > public_html/wp-content/plugins/query-monitor/collectors/http.php on line 106 > [ > 19-May-2016 18:32:14 UTC] PHP Notice: Undefined index: start in /home/XXXXXXX/ > public_html/wp-content/plugins/query-monitor/collectors/http.php on line 191[ > 19-May-2016 18:32:14 UTC] PHP Notice: Undefined index: trace in /home/XXXXXXX/ > public_html/wp-content/plugins/query-monitor/collectors/http.php on line 194[ > 19-May-2016 18:32:14 UTC] PHP Fatal error: Call to a member function get_component() > on null in /home/XXXXXXX/public_html/wp-content/plugins/query-monitor/collectors/ > http.php on line 194 * I’m running an ecommerce site with WooCommerce. Here is part of the status report from that plugin that details all the plugins I’m running. (There’s a lot) * > ### WordPress Environment ### > Home URL: [http://carewaywellness.com](http://carewaywellness.com) > Site URL: > [http://carewaywellness.com](http://carewaywellness.com) WC Version: 2.5.5 > Log Directory Writable: ✔ WP Version: 4.5.2 WP Multisite: – WP Memory Limit: > 1 GB WP Debug Mode: – Language: en_US > ### Server Environment ### > Server Info: Apache/2.2.24 (Unix) mod_hive/5.0 mod_ssl/2.2.24 OpenSSL/1.0.0- > fips mod_auth_passthrough/2.1 mod_fastcgi/2.4.6 mod_bwlimited/1.4 mod_fcgid/ > 2.3.6 > PHP Version: 5.6.21 PHP Post Max Size: 32 MB PHP Time Limit: 45 PHP > Max Input Vars: 10000 SUHOSIN Installed: – MySQL Version: 5.5.31 Max Upload > Size: 24 MB Default Timezone is UTC: ✔ fsockopen/cURL: ✔ SoapClient: ✔ DOMDocument: > ✔ GZip: ✔ Multibyte String: ✔ Remote Post: ✔ Remote Get: ✔ WCS_DEBUG: ✔ > ### Active Plugins (51) ### > Custom Bulk/Quick Edit Premium: by Michael Cannon– > 1.6.1 LayerSlider WP: by Kreatura Media – 5.6.2 Auto Hide Admin Bar: by Marcel > Bootsman – 1.0.3 BAW Login/Logout menu: by Juliobox – 1.3.3 Careway Customizations: > by Derek A. Kelly – 1.8.5 Child Theme Configurator: by Lilaea Media – 2.0.3 > Conditional Woo Checkout Field Pro: by Scott DeLuzio – 3.0.10 Contact Form > 7: by Takayuki Miyoshi – 4.4.2 Custom Facebook Feed Pro Personal: by Smash > Balloon – 2.6.6.3 Easy Columns: by Pat Friedl – v2.1.3 Enhanced E-commerce > for Woocommerce store: by Tatvic – 1.0.18 Envato Market: by Derek Herman – > 1.0.0-RC2 Insert Headers and Footers: by WPBeginner – 1.3.3 Insert HTML Snippet: > by xyzscripts.com – 1.2 WPBakery Visual Composer: by Michael M – WPBakery.com– > 4.11.2.1 MailPoet WooCommerce Add-on: by Sébastien Dumont – 3.0.2 Optin Revolution > Pro: by Optin Revolution Pro – 1.2.8 P3 (Plugin Performance Profiler): by GoDaddy. > com – 1.5.3.9 Print Friendly and PDF: by Print Friendly – 3.4.5 Cart Product > Feed: by ExportFeed.com – 3.1.4.5 Really Simple CAPTCHA: by Takayuki Miyoshi– > 1.9 SG CachePress: by SiteGround – 2.3.4 Simple 301 Redirects: by Scott Nellé– > 1.07 Theme My Login: by Jeff Farthing – 6.4.4 UpdraftPlus – Backup/Restore: > by UpdraftPlus.Com DavidAnderson – 1.12.6 WooCommerce Subscriptions Remove > Deprecation Handlers: by Prospress Inc. – 1.0 WooCommerce Cart Notices: by > WooThemes / SkyVerge – 1.5.0 Follow-Up Emails: by 75nineteen Media LLC – 4.4.13 > WooCommerce Authorize.net CIM Gateway: by WooThemes / SkyVerge – 2.2.1 WooCommerce > Only Ship to Continental US: by Patrick Rauland – 1.0 WooCommerce Product CSV > Import Suite: by WooThemes – 1.10.10 Woocommerce Products Per Page: by Jeroen > Sormani – 1.2.2 WooCommerce Predictive Search PRO: by A3 Revolution – 3.3.1 > WooCommerce Shipment Tracking: by WooThemes – 1.4.3 WooCommerce Simply Order > Export: by Ankit Gade – 2.0.7 WooCommerce Subscriptions: by Prospress Inc. – > 2.0.14 WooCommerce Table Rate Shipping: by Mike Jolley – 2.9.2 WooCommerce: > by WooThemes – 2.5.5 WooSlider – WooCommerce Products Slideshow: by WooThemes– > 1.0.10 WooSlider: by WooThemes – 2.3.0 WooThemes Helper: by WooThemes – 1.6.2 > Wordfence Security: by Wordfence – 6.1.7 Yoast SEO: by Team Yoast – 3.2.5 WP- > DBManager: by Lester ‘GaMerZ’ Chan – 2.78 WP – Meet the Team Shortcode v3: > by phpbits – 3.0 WP reCaptcha Integration: by Jörn Lund – 1.1.10 Yoast WooCommerce > SEO: by Team Yoast – 3.2 MailPoet Newsletters Premium: by MailPoet – 2.6.17 > MailPoet Newsletters: by MailPoet – 2.7.1 * I’m running a premium theme called 123 Medicine * [MrBrian](https://wordpress.org/support/users/mrbrian/) * (@mrbrian) * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397056) * So does it break the whole site, break a certain functionality/page, or is it just an error randomly showing up in your logs? It’s likely and incompatibility with another plugin, in which case you can try disabling plugins 1 at a time until the error no longer appears. * Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * (@johnbillion) * WordPress Core Developer * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397058) * [@derekakelly](https://wordpress.org/support/users/derekakelly/) It sounds like something is filtering HTTP API requests on the site, and conflicting with QM some how. * Are you able to do as MrBrian suggested above and disable your plugins one by one? * If not, if you could install Xdebug on the server then it’ll show you a full stack trace for the fatal error which will help pinpoint the cause of the problem. * Thread Starter [derekakelly](https://wordpress.org/support/users/derekakelly/) * (@derekakelly) * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397061) * [@mrbrian](https://wordpress.org/support/users/mrbrian/) my site has been somewhat slow, so I enabled debugging and have been going through it resolving whatever I can in hopes of increasing performance. * I will have to disable the plugins in the middle of the night or create a staging site to test it on. Since it’s an active ecommerce website, I’d rather not risk losing any sales. * [@john](https://wordpress.org/support/users/john/) Blackbourn I can ask my hosting provider if they’ll install it for us, we’re using a Cloud VPS so they might. * — * I have been using this plugin for a long time and every so often go in and check debug. first time I’ve noticed anything from Query Monitor. * Although there are several new plugins I’m now using that came bundled with my theme * Thread Starter [derekakelly](https://wordpress.org/support/users/derekakelly/) * (@derekakelly) * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397068) * I’ve yet to hear back regarding Xdebug. * So, I created a staging site with my hosting provider’s built in staging tool. It’s essentially an exact copy of my production site. Well, it’s supposed to be… I have been trying to recreate this issue on my staging site without any luck. It however is still coming up on my production site. which is odd… * Thread Starter [derekakelly](https://wordpress.org/support/users/derekakelly/) * (@derekakelly) * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397069) * I’m also finding that I am getting gzinflate errors from at least 3 different plugins. Could this have something to do with it? * Thread Starter [derekakelly](https://wordpress.org/support/users/derekakelly/) * (@derekakelly) * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397078) * My host will install it if i want, but they’ll have to disable mod_hive. Which isn’t really a big deal, as I can manually set any of the config options it allowed me to change via my cpanel. * I did a little bit more reading in regards to Xdebug. I read that it’s not recommended for a production site. Would I be putting myself at risk by doing this? * Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * (@johnbillion) * WordPress Core Developer * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397081) * Xdebug is primarily a debugging tool, but you can run it on a live site for a short time, find the cause of the errors, and then ask your host to disable it again. * Thread Starter [derekakelly](https://wordpress.org/support/users/derekakelly/) * (@derekakelly) * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397082) * Ok cool, thanks for the info John. I’ve given my host the go ahead to install it. * Thread Starter [derekakelly](https://wordpress.org/support/users/derekakelly/) * (@derekakelly) * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397110) * Now they want $100 to install it… And would likely want more money to disable it. Sorry, but we won’t be able to have Xdebug installed.. * Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * (@johnbillion) * WordPress Core Developer * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397111) * Wow, sorry to hear that. * Only thing I can suggest then is to attempt to narrow down when the error occurs, and then deactivate the other plugins on your site one by one to narrow down which plugins do or don’t cause it. * Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * (@johnbillion) * WordPress Core Developer * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397112) * Oh, another thing to check. Do you have any mu-plugins on the site that might be performing or filtering HTTP API requests? * Thread Starter [derekakelly](https://wordpress.org/support/users/derekakelly/) * (@derekakelly) * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397117) * the only one I had loaded was P3 (Plugin Performance Profiler), which i disabled and I was still getting the errors. * So, I disabled every plugin and slowly brought everything back online. I believe the problem is from the Envato Market plugin. [http://envato.github.io/wp-envato-market/](http://envato.github.io/wp-envato-market/) * Since I disabled the plugin, I haven’t gotten those notices at all but I am now getting a new php notice. * `[02-Jun-2016 17:47:25 UTC] PHP Notice: Undefined index: cache_misses in /home/ xxxxxxxx/public_html/wp-content/plugins/query-monitor/collectors/cache.php on line 51` * I have tried purging my cache several times, I’m using my hosting company’s cache plugin. [https://wordpress.org/plugins/sg-cachepress/](https://wordpress.org/plugins/sg-cachepress/) * I am also getting this notice in regards to visual composer [http://imgur.com/3ntT9FM](http://imgur.com/3ntT9FM) perhaps it’s related? * Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * (@johnbillion) * WordPress Core Developer * [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/#post-7397118) * Thanks for the update. The `cache_misses` issue is something I can fix in QM. I’ll give the Envato Market plugin a whirl and see if I can reproduce the problem. Viewing 15 replies - 1 through 15 (of 19 total) 1 [2](https://wordpress.org/support/topic/php-fatal-error-76/page/2/?output_format=md) [→](https://wordpress.org/support/topic/php-fatal-error-76/page/2/?output_format=md) The topic ‘PHP Fatal error’ is closed to new replies. * ![](https://ps.w.org/query-monitor/assets/icon.svg?rev=2994095) * [Query Monitor](https://wordpress.org/plugins/query-monitor/) * [Frequently Asked Questions](https://wordpress.org/plugins/query-monitor/#faq) * [Support Threads](https://wordpress.org/support/plugin/query-monitor/) * [Active Topics](https://wordpress.org/support/plugin/query-monitor/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/query-monitor/unresolved/) * [Reviews](https://wordpress.org/support/plugin/query-monitor/reviews/) * 19 replies * 4 participants * Last reply from: [richardwardza](https://wordpress.org/support/users/richardwardza/) * Last activity: [9 years, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-76/page/2/#post-7397148) * Status: not resolved