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...Skins, Themes, ...Skins, Themes, ...How to use the same XML file to all skins in a packageHow to use the same XML file to all skins in a package
Previous
 
Next
New Post
8/10/2009 4:22 PM
 

Hi everyone, i'm facing a problem with the XML reference to my skins, at first i've created a XML for each html file that i had in my package, but i need to change that, i want that all the skins in my package use the same XML file. Is that possible?? i'm using the DNN 4.9.2 version.

 

Example: Students.html                      -------------> school.xml

               Departments.html                -------------> school.xml

I have readed the Skinning documentaion of DNN, and there is a paragraph talking about that:

"A skin package can contain a global attributes specification named “skin.xml” ( or
“container.xml” for containers )  which applies to all skin files in the package. In
addition, you can also override the global skin attribute specification with a skin
specific attribute specification by providing a “skinfilename.xml” file. The skin
uploader will merge the skin attributes with the HTML presentation file to create an
ASCX skin file. The following XML fragment represents the structure of the
attributes file: "

I've tryed that in all possible ways but its not working. Please, if someone have the solution help me.

Thnks :)

 
New Post
8/10/2009 6:36 PM
 

You have to have one xml file per skin eg Students.xml Departments.xml

 
New Post
8/10/2009 10:13 PM
 

Or, just drop the HTML/XML parsing and work up the skins in ASCX files. I've recently switched myself, and I've got to say my life is a whole lot more simple now. Editing them live is much less of a hassle, as is keeping my source files consistant with the production files. However, I still cheat a bit on occaision. I have several layout templates I use frequently, and when I'm feeling particularly lazy, I just pass those through the parser and then use the ASCX to go from there. I'm hoping to move to developing on a localhost setup with Visual Developer but right now it's faster for me to just keep plugging them out by hand. However, if you're still getting acclimated to the DNN Skinning system, definitely stay with the HTML/XML parsing system for now. In the meantime, I'd just make the HTML/XML files, then copy-paste the contents of the 'master' XML file to their related skin xml files. It's a hassle, but AFAIK that's the only way to get there as DNN requires  SkinA.html and SkinA.xml .


Wells Doty Jr
Online Content Development
 
New Post
8/10/2009 10:29 PM
 

thanks guys for the fast feedback! For now i guess i'm gonna have to do it this way. Different xml files!

thnks again

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...How to use the same XML file to all skins in a packageHow to use the same XML file to all skins in a package


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