[wp-hackers] "Plugin could not be activated because it triggered a fatal error." But what is the error?
Dion Hulse (dd32)
wordpress at dd32.id.au
Fri Mar 12 06:58:47 UTC 2010
When a plugin's activation is blocked due to a fatal error, The page
you're redirected to SHOULD have a inline frame after the message which
will show the error message.
As long as WP_DEBUG is defined, you should be able to see the error..
On Fri, 12 Mar 2010 11:35:43 +1200, James Nachlin <jnachlin at sixapart.com>
> I have added a third line, based on looking at wp-settings.php.
> define('WP_DEBUG', true);
> define( 'WP_DEBUG_LOG', true );
> define( 'WP_CONTENT_DIR', '/Users/jnachlin/Sites/wordpress/wp-content/'
> But still no output anywhere from this "fatal error". If anyone can
> suggest a hack, like some code that preempts the "Plugin could not be
> activated because it triggered a fatal error" message, id be glad to
> hack. I can always de-hack.
> I'm lookin at about line 248 of wp-admin/plugins.php.
> James Nachlin wrote:
>> 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).
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
Dion Hulse / dd32
e: contact at dd32.id.au
More information about the wp-hackers