As a courtesy, note the deprecated function call as RECOMMENDED in the review.<div><br></div><div>Enforcement of WordPress 3.3 function deprecation will be implemented approximately one month following final release of WordPress 3.3, at which time we will finalize/go live with the WordPress 3.3 Guidelines revisions.</div>
<div><br></div><div>Chip<br><br><div class="gmail_quote">On Mon, Oct 24, 2011 at 10:22 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Please don't reply to digest emails.<br>
<br>
And no, I wouldn't ignore such things. 3.3 is in beta 2 and well on<br>
track for release very soon. It would be a good idea to future proof<br>
things.<br>
<br>
That message, BTW, comes to you courtesy of the "_doing_it_wrong"<br>
function in WordPress. If you trigger it, then you're doing something<br>
wrong.<br>
<font color="#888888"><br>
-Otto<br>
</font><div class="im"><br>
<br>
<br>
On Mon, Oct 24, 2011 at 10:13 AM, Paul de Wouters<br>
<<a href="mailto:pauldewouters@zoho.com">pauldewouters@zoho.com</a>> wrote:<br>
> Hi<br>
> Should I ignore deprecated notices relative to version 3.3?<br>
><br>
> Scripts and styles should not be registered or enqueued until<br>
> thewp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please<br>
> seeDebugging in WordPress for more information.<br>
> This message was added in version 3.3.<br>
> Should testing be done using the current stable version?<br>
> thanks<br>
</div><div><div></div><div class="h5">_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br></div>