Title: Php Fatal error
Last modified: August 22, 2016

---

# Php Fatal error

 *  Resolved [duhvillage](https://wordpress.org/support/users/duhvillage/)
 * (@duhvillage)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/php-fatal-error-44/)
 * [Sun Jan 25 01:05:53 2015] [error] [client 50.159.101.7] PHP Fatal error: Call
   to undefined method DirectoryIterator::getExtension() /wp-content/plugins/query-
   monitor/query-monitor.php on line 65
 * [Sun Jan 25 01:06:45 2015] [error] [client 50.159.101.7] PHP Fatal error: Call
   to undefined method DirectoryIterator::getExtension() in wp-content/plugins/query-
   monitor/query-monitor.php on line 65
 * This is happen when ever I try to activate on all my sites, I just downloaded
   the new version and the installed and activated.
 * [https://wordpress.org/plugins/query-monitor/](https://wordpress.org/plugins/query-monitor/)

Viewing 8 replies - 1 through 8 (of 8 total)

 *  [Auss](https://wordpress.org/support/users/auss/)
 * (@auss)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/php-fatal-error-44/#post-5709830)
 * I am getting this as well, and it looks like it is due to our PHP version being
   below 5.3.6 still on this server.
 * I can see from the [PHP docs here](http://php.net/manual/en/directoryiterator.getextension.php)
   that the ** DirectoryIterator::getExtension** function requires PHP version 5.3.6
   or higher.
 * If you are able to upgrade your PHP version, then it should resolve this. Otherwise,
   I would like to see Query Monitor potentially still support older PHP versions
   for those of us lagging a little behind like me! 😀
 * Hope that helps some. 🙂
 *  [Auss](https://wordpress.org/support/users/auss/)
 * (@auss)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/php-fatal-error-44/#post-5709834)
 * It looks like some considerable changes were made in the most recent update to
   the plugin (which is awesome – yay upgrading stuff! 😀 ), and this code change
   was one of them.
 * I confirmed that running the previous version is working well. The one from: 
   [https://github.com/johnbillion/query-monitor/releases/tag/2.6.8](https://github.com/johnbillion/query-monitor/releases/tag/2.6.8)
 * **[@author](https://wordpress.org/support/users/author/) Would you say that running
   the previous version is a good idea, or do you think that we should take another
   approach towards getting Query Monitor to work on older PHP Versions?**
 * Thanks!
 * _I love this plugin by the way. It’s still my go-to resource for troubleshooting
   backend slowness. 🙂_
 *  Thread Starter [duhvillage](https://wordpress.org/support/users/duhvillage/)
 * (@duhvillage)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/php-fatal-error-44/#post-5709858)
 * Thanks You Auss you are the Best. Saved my bacon 😉
 *  Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/)
 * (@johnbillion)
 * WordPress Core Developer
 * [11 years, 6 months ago](https://wordpress.org/support/topic/php-fatal-error-44/#post-5709916)
 * Thanks for the reports folks. This issue is being tracked here: [https://github.com/johnbillion/query-monitor/issues/93](https://github.com/johnbillion/query-monitor/issues/93)
 *  [Daniel Iser](https://wordpress.org/support/users/danieliser/)
 * (@danieliser)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/php-fatal-error-44/#post-5710046)
 * Just an FYI here this plugin won’t activate on WP Engine hosting. Hope you can
   get this resolved for backward compatibility soon. Thanks.
 *  Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/)
 * (@johnbillion)
 * WordPress Core Developer
 * [11 years, 6 months ago](https://wordpress.org/support/topic/php-fatal-error-44/#post-5710047)
 * Yeah WP Engine is using an incredibly outdated version of PHP.
 * This is actually fixed in the `develop` branch on GitHub by the way, but I’ll
   be pushing a release to WordPress.org in the next few days.
 *  [MichaelApproved](https://wordpress.org/support/users/michaelapproved/)
 * (@michaelapproved)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/php-fatal-error-44/#post-5710048)
 * I can confirm that 2.6.10, in the develop branch, works for me on a WP Engine
   account that was having this error.
 * Thanks for making the fix available so fast and for creating this plugin!
 *  [Auss](https://wordpress.org/support/users/auss/)
 * (@auss)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/php-fatal-error-44/#post-5710049)
 * Thanks a ton, John! 🙂

Viewing 8 replies - 1 through 8 (of 8 total)

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/)

## Tags

 * [PHP Fatal error](https://wordpress.org/support/topic-tag/php-fatal-error/)

 * 8 replies
 * 5 participants
 * Last reply from: [Auss](https://wordpress.org/support/users/auss/)
 * Last activity: [11 years, 5 months ago](https://wordpress.org/support/topic/php-fatal-error-44/#post-5710049)
 * Status: resolved