User can change display name to existing one even if Site settings require unique display names

Description

Steps to reproduce:

  1. Create a first user

    • UserName: user1

    • DisplayName: MyName

  2. Create a second user

    • UserName user2

    • DisplayName: MyName

  3. Go to Site Settings and activate "Require Unique Display Names"

  4. Change user2 DisplayName to "OtherName"

  5. Logout and relogin with user2

  6. Go to profile and change the DisplayName back to "MyName"

What happens: it works

What should happen: an error message should show that says this DisplayName is already taken.

QA Test Plan

None

Activity

Show:
Ken Grierson
June 5, 2015, 10:19 PM

Verified fixed Platform 7.4.2 build 81 clean install & upgrade
See attachment

Charles Nurse
April 27, 2015, 10:19 PM
Eleonora Ikponmwosa
April 8, 2015, 10:15 PM

I've tested it on the latest build (7.4.1.243) - DisplayName can't be updated using already existing name when "Require Unique Display Names" is enabled.
Feature is working as expected.
However there is an exception that occurs during UserUpdateCompleted event.
This exception is thrown because Redirect is called with endResponse param set to True.
I've submitted a pull request to address thread abort exception.

Ken Grierson
December 29, 2014, 11:08 PM

This is not fixed in Platform 7.4.0 build 299
I can still EDIT the Username after having set "Require Unique Display Names" to TRUE and saved the change

I changed more than 1 UserName AFTER saving the change to "Require Unique Display Names"

For each UserName I did change this error appears in the log.resources file:

[ERROR] DotNetNuke.Modules.Admin.Users.EditUser - System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.AbortCurrentThread()
at DotNetNuke.Modules.Admin.Users.EditUser.cmdUpdate_Click(Object sender, EventArgs e)

Daniel Valadas
October 24, 2014, 3:10 PM

Had to redo the pull request which is now #179 because I did some other mistake using Git.

Complete
Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Ken Grierson

Reporter

Daniel Valadas

Story Size

Unknown

Severity

Minor

Triage

New

Fixed in Build

Includes Code Fix

No

Documentation Required

No