Changing Username On Front End To Another Account Email We have a front end form for a logged in user to change their Username (email). In our testing, it does not appear to check against and prevent selecting an email address that's already taken (like happens on a login form). However, our Create Account from - which is almost identical - works.

This Form (our create account form) works and catches duplicate emails and returns an error:

&lt;form id="createForm" method="post" accept-charset="UTF-8"&gt;

    {{ getCsrfInput() }}
    &lt;input type="hidden" name="action" value="users/saveUser"&gt;
    &lt;input type="hidden" name="redirect" value="{{ siteUrl }}account/signup-sent"&gt;
    &lt;div class="input"&gt;
        &lt;label&gt;Email &lt;span&gt;*&lt;/span&gt;&lt;/label&gt;
        &lt;input id="signupEmail" name="email" placeholder="Email" value="" data-parsley-type="email"&gt;
    &lt;/div&gt;
    &lt;div class="input"&gt;
        &lt;label&gt;Confirm Email &lt;span&gt;*&lt;/span&gt;&lt;/label&gt;
        &lt;input id="confirmEmail" placeholder="Confirm Email" value="" data-parsley-type="email"&gt;
    &lt;/div&gt;
    &lt;div class="input"&gt;
        &lt;label&gt;Password &lt;span&gt;*&lt;/span&gt;&lt;/label&gt;
        &lt;input name="password" id="password" type="password" placeholder="Password" value=""&gt;
    &lt;/div&gt;
    &lt;div class="input"&gt;
        &lt;label&gt;Confirm Password &lt;span&gt;*&lt;/span&gt;&lt;/label&gt;
        &lt;input name="confirmPassword" id="confirmPassword" type="password" placeholder="Confirm Password" value=""&gt;
    &lt;/div&gt;
    &lt;input type="hidden" name="fields[accountReceiveEmails]" value=""&gt;
    &lt;div class="checkbox"&gt;
        &lt;input type="checkbox" name="fields[accountReceiveEmails][]" value="yes" id="emailOptin"&gt;
        &lt;label for="emailOptin"&gt;&lt;span class="checkbox"&gt;&lt;span&gt;&lt;/span&gt;&lt;/span&gt;Yes, I would also like to receive offers, discounts and news for Cadex products by email.&lt;/label&gt;
    &lt;/div&gt;
    &lt;footer&gt;
        &lt;button&gt;Create Account&lt;/button&gt;
    &lt;/footer&gt;
&lt;/form&gt;


This is our form for users logged into their account. It does not return an error when a user tries changing their email to one that already exists in another account:

&lt;form id="profileCredsForm" method="post" accept-charset="UTF-8"&gt;
    {{ getCsrfInput() }}
    &lt;input type="hidden" name="action" value="users/saveUser"&gt;
    &lt;input type="hidden" name="redirect" value="account/profile/saved"&gt;
    &lt;input type="hidden" name="userId" value="{{ currentUser.id }}"&gt;
    &lt;div class="input"&gt;
        &lt;label&gt;Current Password &lt;span&gt;*&lt;/span&gt;&lt;/label&gt;
        &lt;input id="currentPassword" name="password" placeholder="Current Password" value="" data-parsley-required="true"&gt;
    &lt;/div&gt;

    &lt;div class="input"&gt;
        &lt;label&gt;New Password&lt;/label&gt;
        &lt;input name="newPassword" id="newPassword" type="password" placeholder="New Password" value=""&gt;
    &lt;/div&gt;
    &lt;div class="input"&gt;
        &lt;label&gt;Confirm New Password&lt;/label&gt;
        &lt;input name="confirmNewPassword" id="confirmNewPassword" type="password" placeholder="Confirm New Password" value=""&gt;
    &lt;/div&gt;

    &lt;div class="input"&gt;
        &lt;label&gt;New Email&lt;/label&gt;
        &lt;input id="email" name="email" placeholder="New Email" value=""&gt;
    &lt;/div&gt;
    &lt;div class="input"&gt;
        &lt;label&gt;Confirm New Email&lt;/label&gt;
        &lt;input id="confirmNewEmail" placeholder="Confirm New Email" value=""&gt;
    &lt;/div&gt;

    &lt;button type="submit"&gt;Update&lt;/button&gt;
&lt;/form&gt;


We've tested this repeatedly, changing an email to one for another existing account and no error is returned, the form submits and the email is sent to confirm the new email address.

Also, as an aside, the confirm link in the follow up email seens to ignore the activateAccountSuccessPath set in our config. Is that expected behaviour?

Thanks.
Just answering this for anyone else who sees this. The case above was confirmed by Brad Bell and was fixed in Craft 2.6.2984. So, going forward, the scenario described above should return an error to handle.