[wp-hackers] WP Roadmap Project

[Viper007Bond]

You know you could have just used the "all" hook...

add_action( 'all', 'action_debug', 10, 100 );
function action_debug() {
    echo current_filter() . ' is currently being run and is being passed ' .
func_num_args() . " arguments.\n";
}

On Wed, Oct 29, 2008 at 8:51 PM, Stephen Rider <wp-hackers at striderweb.com>wrote:

> A while back I was trying to track the specific order of actions and
> filters.  (Working on a plugin).  I hacked the core files and added an
> error_log() to the beginning of the do_action filter, telling me which
> action/filter was just called.
>
> Worked like a champ -- answered my question in about 30 seconds of work
> rather than combing through the files tracing the execution order....
>
> Your project sounds like a very neat idea.  Mine was just quick -n- dirty.
>  :)
>
> You might also be interested in my deprecated calls plugin.
> <http://striderweb.com/nerdaphernalia/features/wp-log-deprecated-calls/>
>
> Regards,
> Stephen
>
>
> On Oct 29, 2008, at 4:54 PM, Chris wrote:
>
>  I'm currently working building what I hope will be a very valuable tool
>> for many WordPress developers. The tentative name of it is WP Roadmap.
>>
>> I often get frustrated when I can't find exactly the right action or
>> filter hook to use for a specific task. I'll pick one hook, but it is
>> activated too late. I'll pick another, and of course, it happens way too
>> soon. I thought it would be great if I had a reliable means of tracking what
>> happens in the execution of WordPress from start to finish to build a map of
>> sorts....
>>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
Viper007Bond | http://www.viper007bond.com/ | http://www.finalgear.com/