Improve bw_trace_trace_startup()

[bobbingwide]

While debugging an issue with WooCommerce I realised that the values reported in $_REQUEST weren’t necessarily the same as those that might be later obtained from $_GET or $_POST. This is due to the fact that the earliest output from oik-bwtrace comes before WordPress has called wp_magic_quotes. It would be nice to be able to be able to see problem areas early on.

Proposed solution

• If trace debug also trace $_GET and $_POST if both are set and the merger of the array is different from the current value of $_REQUEST.
• If verbose tracing also trace $_COOKIE.
• Consider adding logic to repeat this in response to ‘wp’ or some other filter.

[bobbingwide]

This is now implemented in BW_trace_controller::trace_startup which is called from bw_trace_trace_startup. The change was made as part of #16.

The trace calls operate at different trace levels, depending on the data being traced.

Consider adding logic to repeat this in response to ‘wp’ or some other filter.

The logic is only invoked during this method.