<blockquote>
  <p>Ideally I'd like to keep it separate as eventually the CP will be swapped out for a front-end solution, so any clues as to why this is happening? </p>
</blockquote>

<p>I think you're close.  Just so we're on the same plane, you're using the CP for users to edit their profiles but everything else is on the front end? Do you have a front end login form already setup? If not, get one setup at <code>counsellors/login</code>. </p>

<p>Don't set your <a href="https://craftcms.com/docs/config-settings#cpTrigger" rel="nofollow"><code>cpTrigger</code></a> and <a href="https://craftcms.com/docs/config-settings#loginPath" rel="nofollow"><code>loginPath</code></a> to the same values if you intend to keep the front and back end logins separate to begin with. That's issue number 1.</p>

<p>On the front end, you probably want to set <code>loginPath</code> to something like <code>counsellors/login</code> and you'll want to obviously uncomment your <code>postLoginRedirect</code> to <code>counsellors/dashboard</code> so after they login, they'll get shuttled off to that page.</p>

<p>Set  <code>activateAccountSuccessPath</code> to something like something like <code>members/activation-success</code> and then in that template,  you can do whatever you want there, either link back to the CP with a hyperlink so users can "finish" their profiles or use Craft's <code>{% redirect %}</code> code to send them to the CP.</p>

CC BY-SA 3.0
2016-01-14T18:10:42.670Z
Thanks for this, marking as the accepted answer. Although, it does seem overkill for a simple custom dashboard/onboarding page — I'll submit a bug report to P+T and see if it's expected behaviour (the redirect).
Rob
CC BY-SA 3.0
2016-01-27T18:39:02.593Z
You might want to start a new question or email P&T directly.  You could create the user without CP privileges and then add them on at some point down the line but that seems overkill in your case since editing a profile on the front end is [straightforward enough](https://craftcms.com/docs/templating/user-profile-form).
RitterKnight
CC BY-SA 3.0
2016-01-27T19:03:35.113Z
Yeah sorry that question was a bit premature (I've deleted it now). I've sent them two support requests but heard nothing in 2 weeks, I imagine their flooded with requests. Front-end profile editing is in the backlog as they haven't the budget — a potential workaround is [Control Panel Nav](https://github.com/engram-design/CPNav) plugin, where at least I can remove dashboard and add a link to our own. Not ideal, but only option to avoid signup confusion.
Rob
CC BY-SA 3.0
2016-01-14T00:14:44.400Z
2016-01-14T00:14:44.400Z
RitterKnight
<blockquote>
  <p>See below updates and accepted answer for a full solution</p>
</blockquote>

<p>I finally discovered <code>postCpLoginRedirect</code> which solves my needs, even though I only need users to access their profile (which includes lots of custom fields, hopefully we'll have a few more permissions options in future for the cp).</p>

<p>Anyway, the issue I'm having is I want to redirect to a front-end dashboard which is at <code>{{siteUrl}}counsellors/dashboard</code>. This page has a <code>{% requireLogin %}</code> tag which redirects to the <code>cpTrigger</code>. And, as cp is enabled for default user groups, I understand <code>activateAccountSuccessPath</code>, <code>postLoginRedirect</code> are defunct settings.</p>

<ul>
<li>When logging in from the Craft <code>cpTrigger</code> the relative link string <code>/counsellors/dashboard</code> works fine.</li>
<li>But when used in combination with the <code>autoLoginAfterAccountActivation</code> it directs to the wrong path (relative to the admin trigger <code>login/counsellors/dashboard</code>)</li>
</ul>

<p>Ideally I'd like to keep it separate as eventually the CP will be swapped out for a front-end solution, so any clues as to why this is happening? Or what combination of settings are required to fix it?</p>

<p>settings:</p>

<pre><code>'cpTrigger' =&gt; 'login',
'postCpLoginRedirect' =&gt; '/counsellors/dashboard',
'activateAccountSuccessPath' =&gt; '/counsellors/dashboard',
'autoLoginAfterAccountActivation' =&gt; true,
'loginPath' =&gt; 'login' # Redirect to cp trigger
// 'postLoginRedirect' =&gt; 'counsellors/dashboard',
</code></pre>

<hr>

<h3>Updates 28/01/2016:</h3>

<p>If you're giving users access to Control Panel <a href="https://craftcms.stackexchange.com/questions/4106/activateaccountsuccesspath-doesnt-work-as-expected"><code>activateAccountSuccessPath</code> won't work, regardless of the path</a> — <a href="https://craftcms.stackexchange.com/questions/13416/how-can-i-set-the-activateaccountsuccesspath-for-users-with-control-panel-acce">a plugin is required to make this happen</a>.</p>

<p>So it seems for now at least, everything has to be built front-end as <a href="https://craftcms.stackexchange.com/questions/13207/postcploginredirect-wrong-redirect-when-used-with-autologinafteraccountactivatio/13208#13208">@RitterKnight suggests</a></p>

<ul>
<li>A big caveat is, no matter what, if a new registered user has access to the CP, <code>activateAccountSuccessPath</code> is ignored. You'll <a href="https://craftcms.stackexchange.com/questions/13416/how-can-i-set-the-activateaccountsuccesspath-for-users-with-control-panel-acce">need a plugin</a> to have newly activated accounts forwarded to your success page.</li>
<li>Another nice addition is to use the brilliant <a href="https://github.com/engram-design/CPNav" rel="nofollow noreferrer">Control Panel Nav plugin</a> (which really I think should be built into Craft)

<ul>
<li>If you're having users login directly from CP login, you can couple this with <a href="https://github.com/engram-design/CPNav/issues/17" rel="nofollow noreferrer"><code>postCpLoginRedirect</code></a> if you want to hide the dashboard from users.</li>
</ul></li>
</ul>

<p><strong>So to recap, full settings are now:</strong></p>

<ol>
<li><p>Front end registration, front-end success page, front-end login form, front-end dashboard;</p></li>
<li><p><a href="https://craftcms.stackexchange.com/questions/13416/how-can-i-set-the-activateaccountsuccesspath-for-users-with-control-panel-acce">A plugin to enforce</a> <code>activateAccountSuccessPath</code> settings</p></li>
<li><p><a href="https://github.com/engram-design/CPNav" rel="nofollow noreferrer">Control Panel Nav plugin</a> with a link to the custom dashboard;</p></li>
<li><p>The following config settings:</p></li>
</ol>

<p><code>
'loginPath' =&gt; 'counsellors/login',
'activateAccountSuccessPath' =&gt; 'counsellors/success',
// 'autoLoginAfterAccountActivation' =&gt; true, # Doesn't work
// 'postCpLoginRedirect' =&gt; 'myaccount#profile', # Optional
'postLoginRedirect' =&gt; 'counsellors/dashboard',
</code></p>

CC BY-SA 3.0
2016-01-13T23:52:25.600Z
So you're using the CP for users to edit their profiles but everything else is on the front end?
RitterKnight
CC BY-SA 3.0
2016-01-14T02:40:28.400Z
@RitterKnight Thanks for the answer. I was hoping I could avoid creating a front-end form for now, the custom front-end is just a dashboard for onboarding (planning to expand it out later). All user interaction is through CP profile editing. Idea was to use regular `cpTrigger` for all logins, but redirect them to the dashboard as a starting point — which seems like it should be possible, but perhaps not! So `loginPath` is intentionally redirecting `{% requireLogin %} to standard login, works as expected. `autoLoginAfterAccountActivation` doesn't seem to play nice with `postCpLoginRedirect` :(
Rob
<control-panel><form><login><settings><dashboard>
postCpLoginRedirect wrong redirect when used with autoLoginAfterAccountActivation
# postCpLoginRedirect wrong redirect when used with autoLoginAfterAccountActivation

(Asked by: username_0 on 2016-01-13)

See below updates and accepted answer for a full solution

I finally discovered postCpLoginRedirect which solves my needs, even though I only need users to access their profile (which includes lots of custom fields, hopefully we'll have a few more permissions options in future for the cp).
Anyway, the issue I'm having is I want to redirect to a front-end dashboard which is at {{siteUrl}}counsellors/dashboard. This page has a {% requireLogin %} tag which redirects to the cpTrigger. And, as cp is enabled for default user groups, I understand activateAccountSuccessPath, postLoginRedirect are defunct settings.

When logging in from the Craft cpTrigger the relative link string /counsellors/dashboard works fine.
But when used in combination with the autoLoginAfterAccountActivation it directs to the wrong path (relative to the admin trigger login/counsellors/dashboard)

Ideally I'd like to keep it separate as eventually the CP will be swapped out for a front-end solution, so any clues as to why this is happening? Or what combination of settings are required to fix it?
settings:
'cpTrigger' => 'login',
'postCpLoginRedirect' => '/counsellors/dashboard',
'activateAccountSuccessPath' => '/counsellors/dashboard',
'autoLoginAfterAccountActivation' => true,
'loginPath' => 'login' # Redirect to cp trigger
// 'postLoginRedirect' => 'counsellors/dashboard',


Updates 28/01/2016:
If you're giving users access to Control Panel activateAccountSuccessPath won't work, regardless of the path — a plugin is required to make this happen.
So it seems for now at least, everything has to be built front-end as @username_1 suggests

A big caveat is, no matter what, if a new registered user has access to the CP, activateAccountSuccessPath is ignored. You'll need a plugin to have newly activated accounts forwarded to your success page.
Another nice addition is to use the brilliant Control Panel Nav plugin (which really I think should be built into Craft)


If you're having users login directly from CP login, you can couple this with postCpLoginRedirect if you want to hide the dashboard from users.


So to recap, full settings are now:

Front end registration, front-end success page, front-end login form, front-end dashboard;
A plugin to enforce activateAccountSuccessPath settings
Control Panel Nav plugin with a link to the custom dashboard;
The following config settings:


'loginPath' => 'counsellors/login',
'activateAccountSuccessPath' => 'counsellors/success',
// 'autoLoginAfterAccountActivation' => true, # Doesn't work
// 'postCpLoginRedirect' => 'myaccount#profile', # Optional
'postLoginRedirect' => 'counsellors/dashboard',

**Tags:** control-panel, form, login, settings, dashboard

> **Comments:**
> **username_1**: So you're using the CP for users to edit their profiles but everything else is on the front end?  
> **username_0**: @username_1 Thanks for the answer. I was hoping I could avoid creating a front-end form for now, the custom front-end is just a dashboard for onboarding (planning to expand it out later). All user interaction is through CP profile editing. Idea was to use regular `cpTrigger` for all logins, but redirect them to the dashboard as a starting point — which seems like it should be possible, but perhaps not! So `loginPath` is intentionally redirecting `{% requireLogin %} to standard login, works as expected. `autoLoginAfterAccountActivation` doesn't seem to play nice with `postCpLoginRedirect` :(  

---

## 1 answers

### Answer by username_1 on 2016-01-14. Score: 2 | Accepted answer

> Ideally I'd like to keep it separate as eventually the CP will be swapped out for a front-end solution, so any clues as to why this is happening?

I think you're close. Just so we're on the same plane, you're using the CP for users to edit their profiles but everything else is on the front end? Do you have a front end login form already setup? If not, get one setup at `counsellors/login`.

Don't set your [`cpTrigger`](https://craftcms.com/docs/config-settings#cpTrigger) and [`loginPath`](https://craftcms.com/docs/config-settings#loginPath) to the same values if you intend to keep the front and back end logins separate to begin with. That's issue number 1.

On the front end, you probably want to set `loginPath` to something like `counsellors/login` and you'll want to obviously uncomment your `postLoginRedirect` to `counsellors/dashboard` so after they login, they'll get shuttled off to that page.

Set `activateAccountSuccessPath` to something like something like `members/activation-success` and then in that template, you can do whatever you want there, either link back to the CP with a hyperlink so users can "finish" their profiles or use Craft's `{% redirect %}` code to send them to the CP.

> **Comments:**
> **username_0**: Thanks for this, marking as the accepted answer. Although, it does seem overkill for a simple custom dashboard/onboarding page — I'll submit a bug report to P+T and see if it's expected behaviour (the redirect).  
> **username_1**: You might want to start a new question or email P&T directly.  You could create the user without CP privileges and then add them on at some point down the line but that seems overkill in your case since editing a profile on the front end is [straightforward enough](https://craftcms.com/docs/templating/user-profile-form).  
> **username_0**: Yeah sorry that question was a bit premature (I've deleted it now). I've sent them two support requests but heard nothing in 2 weeks, I imagine their flooded with requests. Front-end profile editing is in the backlog as they haven't the budget — a potential workaround is [Control Panel Nav](https://github.com/engram-design/CPNav) plugin, where at least I can remove dashboard and add a link to our own. Not ideal, but only option to avoid signup confusion.  

---

