I was flipping through the codex today and saw this on <a href="http://codex.wordpress.org/Widgets_API#Function_Reference" target="_blank">http://codex.wordpress.org/Widgets_API#Function_Reference</a> and I'm wondering if the page can get some eyes on it at some point:<div>
<br></div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
Note: It is advised not to use the functions starting with "wp_" as these could change in subsequent releases. This is why we use register_sidebar_widget() instead of wp_register_sidebar_widget().</blockquote><div>
<br></div><div>When functions get added, we make sure they always work in a backwards compatible way, or we deprecate it and come up with a new function, so I'm not sure why we're advising plugin authors to avoid these, or why we suggest they may arbitrarily change.</div>
<div><br></div><div>In this case, wp_register_sidebar_widget() and wp_register_widget_control() are for the 2.8+ widget API. If you wanted to be compatible with pre-2.8, you would use the older functions, register_sidebar_widget() and register_widget_control(). (In 3.0, these functions, which have more or less been deprecated since 2.8, now officially spit out a deprecated function notice.)</div>
<div><br></div><div>The preferred situation would be to check if wp_register_sidebar_widget exists, and if so, use that, and if not, register via the old API. That way you're never using deprecated functions, yet the plugin can still support legacy versions.</div>
<div><br></div><div>It would be great if this page can be updated at some point. Let me know how I can help.</div><div><br></div><div>Thanks for all you do,</div><div>Nacin</div>