On Sun, Sep 12, 2010 at 5:53 PM, Chris <<a href="mailto:chris@thematic4you.com">chris@thematic4you.com</a>> wrote:<br>> The Carrington Core uses a user level in its add_submenu_page() call. The user levels<div>> were replaced in WP 2.0 and deprecated with WP 3.0 (checked this against WP 2.9.2),</div>
<div>> but debug tells me deprecated since 2.0.<br><br>They were deprecated in 2.0. We just didn't report it until 3.0 because that's when we introduced deprecated argument reporting. There's also some older widget functions for example that were replaced in 2.8, but we didn't actually add them to deprecated.php until 3.0. Those functions will report 2.8.<div>
<br>> In this case I would recommend to replace the user level with a role / capability. At this</div><div>> time I don’t see this as an requirement.</div><div><br></div><div>Yes, it is a requirement currently, as the theme cannot have any deprecated calls.</div>
<div><br></div><div>I said that deprecated calls should be<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "> properly evaluated for severity specifically with user levels in mind (among other things). Using user levels is an egregious error and I would want a theme that uses them rejected every time.</span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">On the other hand, if the theme uses clean_url() instead of esc_url() (as but one example), please don't reject that theme. I'm just glad they're sanitizing their outputs.</span></div>
</div>