Honestly, any solution you come up with that allows non-admins to modify user accounts is going to have the same problems. The question is: do you need non-admins to truly manage users? If so, this is going to be your easiest solution. I understand your hesitation and do believe it's justified. While I think this is the easiest solution, my personal preference would be to create a module that limited what could happen. For instance, maybe a module that would require admin approval for some user changes (i.e. deleting users and/or modifying user roles). This would give you more control over what non-admins do. You're just going to have to weigh the pros and cons along with the need.

Hope this helps!

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com

This wouldn't be a hard module at all. Start by grabbing the ManageUsers.ascx control and edit it to work the way you want it. It should be pretty easy, honestly. Heck, you can probably simply take the ManageUsers.ascx file (and not the code-behind) and simply inherit from the ManageUsers class. All you really need to do is remove the controls you don't want (actually, you might have to make them not visible so youdon't break anything). All your deploy would be is your modified ManageUsers.ascx file, which you should probably call something like EditUserProfile.ascx, but that's really up to you.

I say give it a try. It should be pretty simple. If you have any problems, just check out some of the simpler modules to get an idea of things you might need to do for basic module support.

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com

Heh, thats funny...when you said Effority it rang a bell. But since I'm so incredibly nubie with DNN, it didnt ring very true. Anyway, the PA was already in my collection, so I uploaded it again. Seems either my DNN is messed up already, or effority doesn't work yet on DNN4;

 

Fout: effority.UserAccounts is op dit moment niet beschikbaar.
DotNetNuke.Services.Exceptions.ModuleLoadException: Could not load file or assembly 'MemberRole, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b7c773fb104e7562' or one of its dependencies. The system cannot find the file specified. ---> System.IO.FileNotFoundException: Could not load file or assembly 'MemberRole, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b7c773fb104e7562' or one of its dependencies. The system cannot find the file specified. File name: 'MemberRole, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b7c773fb104e7562' at effority.UserAccounts.UserAccounts.BindData(String SearchText, String SearchField) at effority.UserAccounts.UserAccounts.Page_Load(Object sender, EventArgs e) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. --- End of inner exception stack trace ---