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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsSkinsSkinsCustom skin applying to login page (donCustom skin applying to login page (don't want it to)
Previous
 
Next
New Post
10/31/2011 5:39 AM
 
I build my first skin but made the mistake of taking a really complext html/css/javascript template and converting that to a skin.

Working now fine, with a few issues.

For time being the skin are only applied to a single page where I placed a module who's controls implements the styles from my skin.

All fine however:
* The module require me to have a logged in user.  I check in the module if that's true and if not, redirect the user to the login page.
   In this case, the skin style are applied to my login page (making it look really weird)
    I guess it won't be an issue when the skin have all it's bits and pieces together ,but for time being that's an issue.

Also, if logged in as Admin or Host the top control bar included renders all weird.  Once again my style seems to get applied there as well.  :-(
 
New Post
10/31/2011 6:42 AM
 
If you dont have a login page set your currentpage has the login module loaded inthe contentpane

what you want to do is add a new page "login"then add a the äccoutn login"module to the page. Now go to your site settings and change the login page to the page you ave just created.

Now when you login to a portal you go to that page and it wont load the login module in the current page

regardign the controlpanel

I figure you ahve bought a tempalte from a site like themforest or somethign alike. Usually these skins come with lot of predefined content as well as a reset css styles . these can interfere with other dotnetnuke content ( especially host and admin style )

An option is to use the oliverhine.com controlpanel. I use this in all my portals because of issues just as this
 
New Post
11/1/2011 12:57 AM
 
You are right one with your guess. Awesome theme from themeforest (which served me just great with asp.net mvc till date,since it give you full control over your markup).
Would have done it differently knowing what I know now, but can't start over (boss will blow a gasket).

Thanks for both tips, busy with that now.

This new login page. Is there any way I could use a returnurl with it?
 
New Post
11/1/2011 4:37 AM
 
If you set the login page in dotnetnuke site admin then this will be taken care of for you If you click login link then or if you go to a page that you need to be logged in for you will be transfered to this correct page

I use themeforest a lot as well, somet just need a bit more work to be made to function in dotnetnuke more correctly. Most html themes are based ont ehre wordpress coutnerparts and they just have some cleaner html output where .net just injects a few more divs for the panges etc
 
New Post
11/1/2011 7:09 AM
 
Gotcha.
Can't recall how I did it, but adding the login page on my local dnn site did not redirect.
However when I added it to our production site, it works as you said.

Using oliverhine.com controlpanel now...works great.

Now just for that installation packages...nightmare on it's own.
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsSkinsSkinsCustom skin applying to login page (donCustom skin applying to login page (don't want it to)


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