I would not create additional login pages.

The login page uses the same skin as the site home page. So its style is controlled by the css in that skin.

I would think that using css you can make it look any way you want to. However, in my opinion the best thing to do is to keep things very simple on the login page and be more creative on other pages.

Joe

As long as that doesn't break anything I am not opposed to encapsulating the login control.

However there are easier strategies to solve this visual problem.

For example in my skin I have google ads so that they are on all site pages but some pages like login, user profile etc I don't want the google ads partly to avoid the browser message "this page contains both secure and insecure items". So my solution was to create a control called InsecurePanel (in mojoPortal.Web.Controls). This panel sets its own visibility property to false if the request is using ssl. I put an InsecurePanel in my layout.master file and I put my google ads inside the insecure panel.

<mp:InsecurePanel id="pnlGoogle" runat="server">
<script type="text/javascript"><!--
google_ad_client = "pub-2436514866607878";
google_ad_width = 120;
google_ad_height = 600;
google_ad_format = "120x600_as";
google_ad_type = "text_image";
google_ad_channel ="";
google_color_border = "f3f3f3";
google_color_bg = "f3f3f3";
google_color_link = "08619a";
google_color_url = "08619a";
google_color_text = "000000";
//--></script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>

</mp:InsecurePanel>

If your login page will use SSL then you can use the same control or you could create a custom panel that will not render if the request path contains Login.aspx or any other kind of logic.

Joe

Sounds good. I am on the verge of packaging up a new release and I may want to go ahead and make the release before applying the patch just to avoid any possibility of bugs introduced at the last minute.

Thanks,

Joe