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...Logins - Changing looks?Logins - Changing looks?
Previous
 
Next
New Post
11/19/2007 1:49 PM
 

For the DNN website that I am working on, we want to have the Account Login module appear on every page of the website. Simple stuff, right? Sure, but where we want it to appear is in the top right, and the default look (skin) of the module is just huge. We need default text instead of labels, and the whole thing to be about half the height that it is right now. Is there a way to edit that module, or can some of this be changed in the Language settings?

 
New Post
11/20/2007 2:16 AM
 

This module lets you create your own login to look however you want, so long as you put a pane in your skin where you want it to go. I've used it and it worked. I seem to recall that it couldn't use the enter key to submit the form, so you might want to check that with the developer.

http://www.snowcovered.com/snowcovered2/Default.aspx?tabid=242&PackageID=6255

I suggest using the "Ask a question" link to ascertain that it still works with the latest DNN. I can guarantee that it won't support the new live and open ID providers, but you may not need that.. and you can always link through to the normal sign-in if you need that.

Rob

 
New Post
11/28/2007 11:19 AM
 

Well, I've tried contacting that developer twice via Snowcovered but have no response as of yet.  I don't need the new ID providers, so that's not an issue. I just need to shrink down what is there. I may try to work with the source ASCX file for that module and see if I can alter the layout enough to fit my needs, and if that fails I may put out the cash for the module and try it. Just bugs me when people develop things like this and then abandon them, but it's not like there's anything I can do about it.

 
New Post
11/28/2007 6:05 PM
Accepted Answer 

Yes, that's the best reason for always asking questions on there. It's the only way to weed out dead modules and shi**y developers. That said, the guy who did that login module was really good when I first bought it. I gave him a list of fixes and he was keen and able to do all but one.

The core ascx can be changed to look like just about anything and I originally also made a lot of changes to that. Later I decided to only make it tighter and narrower as then it fit with a lot more skins in my multi-portal instance. In recent DNN's the login has changed completely and I have a note on my task list to tidy it up again.

Just while I'm here.. I'll quickly check that that module still works where I had it installed. It's still there but I hid it. Ok.. that was worth doing, because it doesn't work!

I'll check the event viewer..

InnerException: Could not load type 'DotNetNuke.Security.Authentication.AuthenticationController' from assembly 'DotNetNuke, Version=4.7.0.0, Culture=neutral, PublicKeyToken=null'.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: RSSimpleLogin.Controls.signinview.Login_Process
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Could not load type 'DotNetNuke.Security.Authentication.AuthenticationController' from assembly 'DotNetNuke, Version=4.7.0.0, Culture=neutral, PublicKeyToken=null'. ---> System.TypeLoadException: Could not load type 'DotNetNuke.Security.Authentication.AuthenticationController' from assembly 'DotNetNuke, Version=4.7.0.0, Culture=neutral, PublicKeyToken=null'. at RSSimpleLogin.Controls.signinview.Login_Process() at RSSimpleLogin.Controls.signinview.btnLogin_Click_NonImage(Object sender, EventArgs e) at System.Web.UI.WebControls.LinkButton.OnClick(EventArgs e) at System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

Looks like it's dead. I'll go and put a ticket in and see what happens.

Rob

 
New Post
11/29/2007 11:17 AM
 

Good luck with that ticket. Having the logging integrated is part of what makes this system as good as it is.

I went in and edited the two ascx files that are involved in the process and set them up to meet my needs. I only have a single portal, so I don't have the issues you do. Editing tables is easy enough, and when I threw in a little CSS to hide the annoying extra space at the bottom of the module it all came out well enough. I may convert it to a couple of divs if I get the urge, but for now this works. I find it a little annoying that when the authentication module detects that a user is logged in it just makes that module invisible instead of actually changing the output, but I can deal with it for now. It would be really nice to have a unified login system instead of the disparate skin token and separate module. Maybe i'll submit that for the wish list.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Logins - Changing looks?Logins - Changing looks?


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