This is my revised login code from the snippet to avoid the user being redirected to the login page (or perhaps I've missed a setting somewhere!!).

Would this be a suitable replacement for the current snippet?

@inherits Umbraco.Web.Macros.PartialViewMacroPage

@using System.Web.Mvc.Html
@using ClientDependency.Core.Mvc
@using Umbraco.Web
@using Umbraco.Web.Models
@using Umbraco.Web.Controllers

@{
    // You have to set the login node ID otherwise you'll have an infinite loop if someone hits the login page first
    var loginNodeID = 1072;
    var loginModel = new LoginModel();
    var loginStatusModel = Members.GetCurrentLoginStatus();

    Html.EnableClientValidation();
    Html.EnableUnobtrusiveJavaScript();
    Html.RequiresJs("/umbraco_client/ui/jquery.js");
    Html.RequiresJs("/umbraco_client/Application/JQuery/jquery.validate.min.js");
    Html.RequiresJs("/umbraco_client/Application/JQuery/jquery.validate.unobtrusive.min.js");
}

@* NOTE: This RenderJsHere code should be put on your main template page where the rest of your script tags are placed *@
@Html.RenderJsHere()

@{
    @*  if we don't have a session variable and have a request URL then store it *@
    if (HttpContext.Current.Request.Url != null && HttpContext.Current.Session["redirectURL"] == null) {
        if (CurrentPage.Id != loginNodeID) {
            HttpContext.Current.Session["redirectURL"] = HttpContext.Current.Request.Url.ToString();
        }
    }
}


@if (loginStatusModel.IsLoggedIn)
{
    var redirectUrl = (string)HttpContext.Current.Session["redirectURL"];

    var currentUrl = HttpContext.Current.Request.Url.ToString();
    if (HttpContext.Current.Session["redirectURL"] != null) {
        // clear the session variable for future logins
        HttpContext.Current.Session["redirectURL"] = null;
        HttpContext.Current.Response.Redirect(redirectUrl);
    }
    else {
        // Nothing in the session so we will go home 
        HttpContext.Current.Response.Redirect("/");

    }
}


@using (Html.BeginUmbracoForm<UmbLoginController>("HandleLogin"))
{
    <fieldset>
        <legend>Login</legend>

        @Html.ValidationSummary("loginModel", true)

        @Html.LabelFor(m => loginModel.Username)
        @Html.TextBoxFor(m => loginModel.Username)
        @Html.ValidationMessageFor(m => loginModel.Username)
        <br />

        @Html.LabelFor(m => loginModel.Password)
        @Html.PasswordFor(m => loginModel.Password)
        @Html.ValidationMessageFor(m => loginModel.Password)
        <br />

        <button>Login</button>
    </fieldset>  
}

Oops double post

"* Add to the CreateRegistrationModel Member API an option to specify a group that the user is added to on register."

• I encountered the exact same limitation. It would be great if a Membership Group could be specified when using Members.CreateRegistrationModel()

with the help of the amazing Casey Neehouse, i was able to add a class to app_code to assign a new member to a role when created.

using Umbraco.Core;
using Umbraco.Core.Events;
using Umbraco.Core.Models;
using Umbraco.Core.Services;

namespace MyApplication.Events
{
public class MemberEvents : ApplicationEventHandler
{
protected override void ApplicationStarted(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext)
{
Umbraco.Core.Services.MemberService.Created += MemberService_Created; 
}
 
void MemberService_Created(Umbraco.Core.Services.IMemberService sender, Umbraco.Core.Events.NewEventArgs<IMember> e)
{
sender.AssignRole(e.Entity.Id, "Site Visitors");
}

}

}

is working on a reply...