This appears to be the same as GitHub issue #7.
Tony, could you provide some environment information for me please?
* What PHP version are you running?
* What’s your error_reporting level set to in your php.ini file?
* What’s the return value of error_reporting() in WordPress? (You can put something like add_action( 'init', function() { var_dump( error_reporting() ); } ); into a plugin to get it).
PHP Version 5.3.27
error_reporting: Local Value=4983; Master Value=22519
With a bit of luck this should be fixed in the latest version. Let me know how you get on.
A workaround is to disable the conflicting plugin (using old-style constructor) before activation. Reenabling it after activation doesn’t cause the fatal error.
Does the latest version work for you or are you still getting the fatal error on activation?
I’ve been always using ersion 2.5.3
The latest version is 2.5.4.
FYI – I’m getting a similar error on activation.
Fatal Error Class ‘QM_Backtrace’ not found in /… (one of my very basic plugin’s constructors)
using the current version of this plugin, WP 3.8, and PHP 5.3.3
Thanks Jason. I’m currently stumped by this issue. When I have some free time I’m going to investigate it on a WPEngine server that I have access to because it’s reproducible on there apparently.
Stay tuned!
Quick question for Jason, Tony, and anyone else reading this thread.
Do you have an opcode cache enabled on your site? For example, APC, eAccelerator, Xcache, or Zend Opcache? You can usually find this information in phpinfo().
Many thanks,
John
No – we do not currently have an opcode cache enabled.
This should be fixed in the latest version.
