I will make sure the I get that added with my CnC of the Theme Review page.<br><br>Thanks for the input.<br><br><div class="gmail_quote">On Tue, Jul 27, 2010 at 10:06 AM, Ian Stewart <span dir="ltr"><<a href="mailto:ian@themeshaper.com">ian@themeshaper.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">> <?php $login_url = get_bloginfo( 'url' ) . '/wp-admin/'; ?><br>
><br>
> Then a simple 'echo $login_url;' statement afterward.<br>
><br>
> This, IMHO, in no way lends itself to a form except by default, thus using<br>
> WordPress' core login form functionality.<br>
<br>
</div>I think in this case wp_loginout() would work better.<br>
<br>
<a href="http://codex.wordpress.org/Function_Reference/wp_loginout" target="_blank">http://codex.wordpress.org/Function_Reference/wp_loginout</a><br>
<br>
In general, themes _should_ rely on WordPress wherever possible—unless<br>
there's a good reason not to. If there's a login form in a theme it<br>
should be using wp_login_form—unless there's a good reason not to. And<br>
so on.<br>
<br>
I think adding "where login forms are present" to that point might<br>
clear that up.<br>
<font color="#888888"><br>
--<br>
Ian Stewart<br>
<br>
<a href="http://ThemeShaper.com/" target="_blank">http://ThemeShaper.com/</a><br>
<a href="http://twitter.com/iandstewart/" target="_blank">http://twitter.com/iandstewart/</a><br>
</font></blockquote></div><br>