You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to see the results of selected filters in the trace log.
Proposed solution
Add a Filter results to trace text area field to the action options admin page in which the names of the filters to trace are specified, comma separated.
For each filter listed attach bw_trace_results() to trace the returned value. This will trace the returned value and optionally, when tracing at BW_TRACE_DEBUG will also trace the other parameters passed.
Notes:
Some filters such as gettext and gettext_with_context are invoked many hundreds of times per transaction. You could get a lot of output.
The text was updated successfully, but these errors were encountered:
and also to automatically close the GitHub Issues
* Added: Ad-hoc tracing of filter functions for selected hooks ( Issue #3 )
* Added: Ad-hoc tracing of parameters to selected hooks ( Issue #2 )
* Added: Ad-hoc tracing of the global post object on selected hooks ( Issue #2 )
* Added: Ad-hoc tracing of filter results ( Issue #6 )
* Added: Ad-hoc tracing should allow selection of the hook priority ( Issue #10 )
* Added: BW_TRACE_VERBOSE ( 64 ) level, which is even more detailed than BW_TRACE_DEBUG ( 32 )
* Changed: Enhanced output from Count action hooks and filters ( Issue #7 )
* Changed: Functions traced should allow OO methods invoking trace ( Issue #8 )
* Fixed: Ensure BW_TRACE_level constants are defined ( Issue #4 )
* Fixed: Fix for problem with symlinked file's drive letters ( similar to TRAC #33265 )
* Fixed: Only trace $errcontext when tracing with BW_TRACE_VERBOSE ( Issue #5 )
* Fixed: Strings containing commas in the trace summary file should be wrapped in quotes ( Issue #9 )
bobbingwide
changed the title
Add ad-hoc tracing of filter results
Add ad hoc tracing of filter results
Oct 1, 2015
It would be nice to see the results of selected filters in the trace log.
Proposed solution
Add a
Filter results to trace
text area field to theaction options
admin page in which the names of the filters to trace are specified, comma separated.For each filter listed attach bw_trace_results() to trace the returned value. This will trace the returned value and optionally, when tracing at BW_TRACE_DEBUG will also trace the other parameters passed.
Notes:
Some filters such as
gettext
andgettext_with_context
are invoked many hundreds of times per transaction. You could get a lot of output.The text was updated successfully, but these errors were encountered: