Can you do that for specific deprecated functions, or are they treated as a whole?<div><br></div><div>Chip<br><br><div class="gmail_quote">On Tue, Mar 22, 2011 at 4:33 PM, 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;">If we modify the theme-check to make it recommended, then sure.<br>
<br>
-Otto<br>
<br>
<br>
<br>
On Tue, Mar 22, 2011 at 4:16 PM, Edward Caissie<br>
<div><div></div><div class="h5"><<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>> wrote:<br>
> Can the upload script be modified to allow for one version backward<br>
> comparability ... In this instance the function is noted as being deprecated<br>
> in 3.0 just make it a RECOMMENDED note?<br>
><br>
> Sent from my iPhone ... Cais.<br>
> On Mar 22, 2011, at 4:33 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
><br>
> My general rule of thumb has been not to allow backward-compatibility beyond<br>
> one major version. So, I think 3.0 backward-compatibility is acceptable. :)<br>
> Chip<br>
><br>
> On Tue, Mar 22, 2011 at 3:18 PM, Otto <<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>> wrote:<br>
>><br>
>> On Tue, Mar 22, 2011 at 2:30 PM, Edward Caissie<br>
>> <<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>> wrote:<br>
>> > On Tue, Mar 22, 2011 at 3:02 PM, Sayontan Sinha <<a href="mailto:sayontan@gmail.com">sayontan@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> This function was deprecated in 3.1 and even in 3.0 the replacement<br>
>> >> get_users() is not present.<br>
>> ><br>
>> > See this link:<br>
>> > <a href="http://core.trac.wordpress.org/browser/trunk/wp-includes/user.php/#L632" target="_blank">http://core.trac.wordpress.org/browser/trunk/wp-includes/user.php/#L632</a><br>
>><br>
>> No, I see what he means. If he includes backward compatible 3.0<br>
>> support for get_users_by_blog, then it fails the theme check, making<br>
>> his theme 3.1-required.<br>
>><br>
>> Suggestions? We could remove that from the theme checker.<br>
>><br>
>> -Otto<br>
>> _______________________________________________<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>
><br>
> _______________________________________________<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>
><br>
> _______________________________________________<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>
><br>
><br>
_______________________________________________<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>