[wp-hackers] do_action transparency

[Ozh]

Or simply use PHP's debug_backtrace() to know wtf, whytf and whentf
something happens

On Mon, Sep 19, 2011 at 8:06 PM, Dagan Henderson
<Dagan.Henderson at epyllion.com> wrote:
> I'd start with either a log file or a debug server, such as Zend, to do a step by step analysis.
>
> -----Original Message-----
> From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Braydon
> Sent: Monday, September 19, 2011 11:03 AM
> To: wp-hackers at lists.automattic.com
> Subject: [wp-hackers] do_action transparency
>
> Scenario / Problem:
> Plugin A has a do_action hook for other plugins to execute code.
> Plugin B hooks into Plugin A and runs some groovy stuff.
> Plugin C hooks into Plugin A and runs code that breaks Plugin B groovy stuff.
> Multiply this scenario times 10 plug-ins and it becomes very difficult to know what plugin is executing code where.
>
> Question:
> Is there a way to make these actions transparent and to know what is executing for each action?
>
>
>
>
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
http://ozh.org/ - @ozh on Twitter
WordPress plugins? I wrote a book! http://amzn.to/plugindevbook