[wp-hackers] Plugin could not be activated because it triggered

[Robin Adrianse]

Just a side note, but I believe there may be clues in the error_log.

But I think we should implement a custom, temporary error handler for
activating plugins so we can actually show something to the user, because a
blank screen and a cryptic message about a "fatal error" being "triggered"
doesn't help much, when you think about it ;).

On 6/21/07, ozgreg <wphackers at galleryembedded.com> wrote:
>
> I been getting a small number of "Plugin could not be activated because it
> triggered a fatal error." posts in the WPG2 forum.
>
> Unfortunately change http://trac.wordpress.org/changeset/5239 executes a
> ob_end_clean() thus removing any error message making it impossible to debug
> what in their Wordpress Environment is causing the problem..
>
> The issue is we need the error output, my suggestion would be to have a
> link in the plugin cannot be activated error message that allows the plugin
> activation to be simulated and the error output be displayed, but I am open
> for suggestions..
>
> PS: Just a minor point,  I feel the assumption in the ticket, "Don't die
> because of output by badly-written plugins upon activation." is not ideal,
> if the WP plugin is a simple hello world then yes you should not be getting
> an output,  however take a plugin that integrates a another third party
> application and that assumption goes straight out the window because you
> have a whole lot of other factors to deal with.
>
>
>
>
> -------------------- m2f --------------------
>
> Gallery2 Embedded Forums (http://www.galleryembedded.com/forums/)
> -------------------- m2f --------------------
>
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>