The snippet is the unadulterated Login Snippet version 1.5.2 rc1 (which is the most recent at the moment).
The snippet call is like this:
[[Login? &loginTpl=`FormLogin` &errTpl=`FormLoginError` &loginResourceId=`4` &logoutResourceId=`1` ]]
The sample html in the loginTpl came from the Clarity pack:
<div id="loginForm">
<div class="loginMessage">[[+errors]]</div>
<div class="loginLogin">
<form class="loginLoginForm" action="[[~[[*id]]]]" method="post">
<fieldset class="loginLoginFieldset">
<label class="loginUsernameLabel">[[%login.username]]
<input class="loginUsername" type="text" name="username" />
</label>
<label class="loginPasswordLabel">[[%login.password]]
<input class="loginPassword" type="password" name="password" />
</label>
<input class="returnUrl" type="hidden" name="returnUrl" value="[[+request_uri]]" />
<input class="loginLoginValue" type="hidden" name="service" value="login" />
<span class="loginLoginButton"><input type="submit" name="Login" value="[[+actionMsg]]" /></span>
</fieldset>
</form>
</div>
</div>
I wanted to get this working in a vanilla capacity before I added my own custom login validation rules...
The only goofy thing here is that the Snippet is called twice: once in the page content and once in the sidebar (it’s the exact same Snippet call).
I’ve tried using my manager user here, but no go. My admin user is a member of the Administrators user group, and when I edit that User Group, I have 4 contexts (?) added:
[table]
[tr]
[td]
Context[/td]
[td]
Min Role[/td]
[td]
Access Policy[/td]
[/tr]
[tr]
[td]mgr[/td]
[td]Super User - 0[/td]
[td]Administrator[/td]
[/tr]
[tr]
[td]mgr[/td]
[td]Member - 9999[/td]
[td]QuipModeratorPolicy[/td]
[/tr]
[tr]
[td]web[/td]
[td]Super User - 0[/td]
[td]Administrator[/td]
[/tr]
[tr]
[td]web[/td]
[td]Member - 9999[/td]
[td]Resource[/td]
[/tr]
[/table]
Does that look normal?
I think maybe the easiest way to test functionality and to get your feet wet with the new permissions schema is to try logging into the front-end using your manager username... yes?