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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Is "SkinningDefaults" section in dotnetnuke.config new?Is "SkinningDefaults" section in dotnetnuke.config new?
Previous
 
Next
New Post
7/17/2008 11:02 AM
 

HI all

I just traced down a real PITA problem with the upgrade to 4.08.04. When I hit the site, i was just getting a "object reference not found error" I downloaded the source, put in some debugging lines and put the new dotnetnuke.dll in my sites BIN folder.

I found that in the dotnetnuke.config file there seems to be a new section called <skinningdefaults> Which can look like this.

  <skinningdefaults>
    <skininfo folder="/DNN-Blue/" default="Horizontal Menu - Fixed Width.ascx" admindefault="Horizontal Menu - Fixed Width.ascx" />
    <containerinfo folder="/DNN-Blue/" default="Image Header - Color Background.ascx" admindefault="Image Header - Color Background.ascx" />
  </skinningdefaults>

My dotnetnuke.config file did not have this, but the source version of DNN did. Is this new? It was not in my old copy of this file either. The class "skindefaults" in skindefaults.vb was looking for this section and was not present and was then bombing.. I put it in, and now it works.

If this is new, kind of important to point it out.

THanks

Harold

 

 
New Post
7/17/2008 11:23 AM
 

Hi Harold,

This element appeared somewhere around version 4.6; I don't recall exactly, but that's the right neighborhood.

I've helped a number of people with this problem (this is probably the 5th+ thread I've participated on with respect to this topic), so I'm (obviously) suspecting that there is a problem with 4.8+ upgrades from pre-4.6 installations.

Perhaps someone from the core team could chime in here -- is the upgrade process supposed to handle this correctly and failing, or is this an upgrade omission?  Gemini is doing its usual error-out when I search "skinningdefaults," so I'm not sure if this is a known issue. 

If it's not, I'll create it.

Brandon


Brandon Haynes
BrandonHaynes.org
 
New Post
7/17/2008 1:30 PM
 

Hi Brandon,

Thanks for the response! I was dead in the water for days over this...It had updated my db at first, but then I could not navigate to the home page afterwords.

THere really needs to be more documentation on changes  in the web.config file.

 

Thanks!

Harold

 

 
New Post
8/15/2008 3:53 AM
 

MAN, Brandon, you are ALL OVER the posts and threads that i'm uncovering while attempting to troubleshoot 3 new dnn installations i've done today that all end in unspecified errors! you ROCK.

i'm trying to work at the problem from different directions, and thought about the config files, and came into this post... one thought that was promted here was that skin related issues could be at hand.. i checked my dotnetnuke.config in the 4.8.4 installation and 4.8.3 install and the lines were there for the skininfo folder, however, does anyone know how they work? if I wanted to reference a different skin here, what's the path structure... the default shows just /DNN-BLue/   if it had been instead "_default/DNN-Blue/" then i would have known instantly what to do, but this is what, relative path? set auto to "_default" ??

following that trian of thought, i checked and the "_default" folder is not showing when I check the site thorugh FTP or Expressions(/FrontPage), and remembering that frontpage treats all "_xyz" files and folders as hidden/special, this could be the problem with my particulart instalations, they're all host locaitons with frontpage extensions running. this hasn't been a problem in installations that were eitehr pre 4.8, and/or ones that started off as 4.2 and 3.X installs that were upgraded later to 4.8.2.

 

 
New Post
8/15/2008 11:02 AM
 

Hi Ryan,

Appreciate the compliment!

The dotnetnuke.config xml file is hydrated into two SkinDefaults objects (Components/Skins/SkinDefaults.vb).  Both are stored as public properties of the Globals module (DefaultSkin and DefaultContainer). 

Looking at Globals.DefaultSkin, it appears that this object is referenced exactly twice in the DNN core, both in PortalSettings (Components/Portal/PortalSettings.vb, on or about line 733 and 735).  I see no references in the DNN presentation layer.

Both references are essentially the same, using AdminDefaultName and DefaultName respectively.  The latter reads:

 

Me.ActiveTab.SkinSrc = "[G]" & SkinInfo.RootSkin & DefaultSkin.Folder & DefaultSkin.DefaultName

SkinInfo.RootSkin is defined in Components/Skin/SkinInfo.vb, and is hardcoded to return the value "Skins".  Since the SkinSrc above contains a "[G]" prefix, it is hardcoded as a global skin and will therefore use the global skin directory.

So, the bottom line is that the default skin must be located in the "/Portals/_default/Skins" directory.  Whatever is specified in the folder attribute of dotnetnuke.config will be appended to this value.

I haven't fooled around with FrontPage extensions in some time, but although your FTP utility might be hiding these directories, I would not expect this to effect how .NET treats the directory (I suppose you could check the permissions to verify).

Have you started a thread that relates specifically to the issue you're experiencing?

Brandon


Brandon Haynes
BrandonHaynes.org
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Is "SkinningDefaults" section in dotnetnuke.config new?Is "SkinningDefaults" section in dotnetnuke.config new?


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