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 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. 🙂
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
@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. 🙂
Thanks You Auss you are the Best. Saved my bacon 😉
Thanks for the reports folks. This issue is being tracked here: https://github.com/johnbillion/query-monitor/issues/93
Just an FYI here this plugin won’t activate on WP Engine hosting. Hope you can get this resolved for backward compatibility soon. Thanks.
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 ww.wp.xz.cn in the next few days.
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!
