[wp-hackers] "Plugin could not be activated because it triggered a fatal error." But what is the error?

James Nachlin jnachlin at sixapart.com
Thu Mar 11 19:36:24 UTC 2010

Thank you Dougal,

I have added those lines to wp-config.php.  I have even restarted the 

These are the first two non-comment lines of wp-config.php:
define('WP_DEBUG', true);
define( 'WP_DEBUG_LOG', true );

I do not see a log file in my wp-content/ directory.

Every folder between wp-content/ and / is chmod 777.

Is there some other option, maybe in php.ini, to allow php to write 
files (I am on OS X).

Thanks again,

Dougal Campbell wrote:
> On Mar 11 2010 2:12 PM, James Nachlin wrote:
>> Thanks Matthew and Austin for your answers.
>> I don't think that the missing semicolon was the [only] problem.
>> But the larger issue is that the server will have to start reporting 
>> clear errors.  If this plugin gets more complex, there will be no way 
>> to scan the entire set of code files looking for an error.
>> There must be a way that plugin developers view the errors their 
>> plugins cause.
> Try adding this to your wp-config.php:
>   define( 'WP_DEBUG', true );
>   define( 'WP_DEBUG_LOG', true );
> Then look for the 'debug.log' file in your wp-content directory (which 
> must be writable by your server).

More information about the wp-hackers mailing list