Products

Solutions

Resources

Partners

Community

Blog

About

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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...4.8.2 - Why is form autocomplete=off?4.8.2 - Why is form autocomplete=off?
Previous
 
Next
New Post
7/3/2008 11:48 AM
 

Is there any chance that it can eventually be defaulted to off, but settable by the host/admin? Really, the username/password is the only autocomplete that I care about, and it sounds like that's the only one that will be turned off?

Don't get me wrong, I think all of you devs do an amazing job and I really do appreciate it. Not trying to stir a pot or start a fire storm.

Thanks,

Rob

 
New Post
7/3/2008 1:26 PM
 

Rob, as per my post earlier in this thread

"This has already been resolved for 5.0 (the change was checked in 3 months ago). The attribute has been removed from the form in default.aspx. What now happens is that when an authentication control is loaded, the attribute is injected for the username and password boxes only. This should satisfy the need for security and xhtml compliance - please see .http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=7217&PROJID=2 "

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
7/3/2008 3:04 PM
 

stsong wrote
It appears that DNN cache does wonderful things for us. Autocomplete works now. Thank you.

Could you, or anyone expound on that please? I'm running 4.8.2, went into the default.aspx file and removed the autocomplete value in the forms, changed the webconfig file so it would reload, cleared the cache from the host menu, and reset IE and I still don't have the option to turn on auto complete.

Thanks,

Rob

 
New Post
7/3/2008 3:08 PM
 

cathal connolly wrote

Rob, as per my post earlier in this thread

"This has already been resolved for 5.0 (the change was checked in 3 months ago). The attribute has been removed from the form in default.aspx. What now happens is that when an authentication control is loaded, the attribute is injected for the username and password boxes only. This should satisfy the need for security and xhtml compliance - please see .http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=7217&PROJID=2 "

Cathal

Cathal,

I get that, I think. However, the way that I'm reading it, the Username/Password will still be blocked from being saved? You talk about removing the autocomplete="off" attribute from default.aspx, but reinjecting 'the attribute' when it comes to Username/Password, so I assumed that you would be keeping autocomplete turned off for the username/password. If I'm incorrect, I'm ecstatic! If I'm not, is there any chance that it could be a host-settable option?

Sorry for any confusion.

Rob

 
New Post
7/3/2008 5:43 PM
 

you're correct, autocomplete would be allowed portal wide except for the username/password fields on login screens.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...4.8.2 - Why is form autocomplete=off?4.8.2 - Why is form autocomplete=off?


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