(My reply below.)<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Andrew Nacin</b> <span dir="ltr"><<a href="mailto:wp@andrewnacin.com">wp@andrewnacin.com</a>></span><br>
Date: Tue, Jul 13, 2010 at 11:32 AM<br>Subject: Re: [theme-reviewers] plugin - Log Deprecated Notices<br>To: Edward Caissie <<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>><br><br><br><div class="im">
On Tue, Jul 13, 2010 at 11:19 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span> wrote:<br></div><div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I just started using this plugin last night (briefly) ... it seems to work well and will be useful for reviews. Thanks.<br><br>Just wondering though, would it be possible to add a column showing where the call(s) are coming from?<br>
<br>Even if it is something as generic as theme (T) or plugin (P). The specific theme (and/or plugin) would be great just in case the reviewer forgets to clear the log before starting a new review.<br></blockquote><div><br>
</div></div><div>It currently should show a path to the file. The exceptions are when there's a bug, or when it's impossible to determine where it came from (when a deprecated function is the callback for a hook, it has no way of knowing when it was added, only that it was used, for example).</div>
<div><br></div><div>In the next version, I hope to allow you to filter by the originating plugin or theme. I don't want to do half-baked support that doesn't account for custom theme and plugin directories so it's taking a bit of time to fully strip those out.</div>
</div>
</div><br>