Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Default User Account options that DNN really needs - SuggestionDefault User Account options that DNN really needs - Suggestion
Previous
 
Next
New Post
8/17/2010 9:13 AM
 
Jon Edwards


www.shebangwebsites.co.za
Joined: 4/4/2008
Posts: 325

So after much testing, brainstorming, and hair-pulling, I've learned that its actually best not to poke around too much with DNN's default user account and account registration settings... This is because, it seems, DNN is a grump old b#st#rd that doesn't like change.

I had made some changes to how users register by using Dynamic Registration by DataSprings, along with some changes in the web.config (requiresUniqueEmail="true"). Basically, the intended end result was to have the users sign up with some custom fields, but more importantly, for their username to be their email address... Big problems, long story, no real help on the forums...

So, here's my suggestion for some critical enhancements that the Core Team should look at making pretty soon:

  1. In the User Accounts Settings manager, create a checkbox field for "Registration requires unique email" - so that this doesn't need to be configured in the web.config (this should be native, not something that's a user-un-friendly thing to have to do).
  2. Also in there, give option to "Use email address as username" - Come on, that should be simple enough..?
  3. My feeling is that these options should possibly be moved to "Site Settings" - makes a bit more sense to me... as the Registration Mode options, Account Login Page, Account Registration Page settings, etc are all there...
  4. From a styling point-of-view, the Login, Registration and Forgot Passwords modules should all give better styling capabilities - possibly with tokens and templating...
  5. I have also made reference to the Skin Object options for "Login" and "Register" here.

I think these are noteworthy suggestions...

Your thoughts..?

Shebang Websites - A product of Mogridge Design
Hey, we're partnered with UntangleMyWeb.com
 
New Post
8/17/2010 8:48 PM
 
cathal connolly


cathal connolly's Avatar

www.cathal.co.uk
Joined: 4/9/2003
Posts: 9676
Hello,
This is an area I've wanted to look at for a while now, as we support a relatively large set of configuration options, but are missing some other items (such as sending via secure SMTP etc.). Some of what we can do is constrained by the provider model (which is mostly why key settings are in web.config), but I think we need to draw up a matrix of what's possible to help people configure as well as fill in any gaps we can.

As to the enhancements
1. this could certainly be done, but has some hidden danger. If a user changes this setting on a site that's already running it locks out anyone without a unique email. As such it's intended to be set before an install - i'm not sure if exposing it as a setting would add to support requests (e.g. why can't my user log in)  rather than help. This is the reason why we haven't changed it in recent versions - though there was some discussion of changing it for the default install package.

2. simple enough - feel free to log it as an enhancement request at support.dotnetnuke.com

3. i agree that we could do with moving common settings around a bit as the introduction of authentication providers involved moving various settings. There needs to be some thought on this as some settings are at the application level, some at the authentication provider level, and some at the site level. I'll let the UX people chip in and help with the relocation of items such as this. Personally speaking I'd like a "Security" page that stored any security related details i.e. users, authentication providers etc.,

4. totally agree - in fact I'd suggest that ll of those need to be rewritten to not have unnecessary postbacks (the login control in particular does little with it's postback), and i'd like to see it ajax-ifed so that it pops out. Improving the initial user experience and look (as well as reducing page load through unnecessary viewstate) would be great. I'd like to see all of these controls be templatable i.e. similar to the user profile control. I know in the past there was an argument that this might not be popular with module developers who've filled these obvious gaps, but I see this as pretty core functioinality, so definately something i'd debate with the engineering team.

Thanks,
Cathal
Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
 Page 1 of 1
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Default User Account options that DNN really needs - SuggestionDefault User Account options that DNN really needs - Suggestion


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out