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, ...Skin File Management questionsSkin File Management questions
Previous
 
Next
New Post
6/18/2007 5:55 PM
 

Hello, I'm a newbie with DNN, but have some experience programming and theming for other CMS's.  I'm trying to work with skins.  I seem to be doing okay with creating the skin, but I'm getting somewhat confused with the file management issues for the skin.  I've searched the available documentation and it is always missing just a few choice pieces of information.

How do I modify (upgrade) an uploaded skin that is already in use? If I just upload it again, instead of overwriting it seems to create multiple skins with the same name.   Seems like perhaps you need to delete it and re-install it, but this isn't an option if it is in use. Perhaps instead, I could use FTP to upload new versions of the files, then click Parse Skin Package in the admin interface?  Or is there some other method I'm missing?  Would using the xcopy method work? 

The documentation of the xcopy method of uploading a skin is sparse (to say the least).  Do I understand correctly that I just use FTP to upload the zipped skin package to the DNN/Install/Skin directory and the rest is taken care of?  If the skin already exists will it update it, or create a new one?  I guess I should just try it, but they seem to be so difficult to delete I don't want to make any unnecessary extra skins.

If I want to delete a container that is in use, is there some way to quickly unlink all modules using that container so I can delete it?  Or do I have to go through each page and manually change the container in every case where it is being used?

Can I have a different default container for different skins?  It looks like if you choose DNN Blue, or DNN Gray in the "Skins" drop down (on the admin>> skins page), the affiliated containers pop up in the container drop down.  However the containers I tried to upload with my skin don't seem to have such a strong association.

Do I need an XML file with an ASCX skin?  I get the impression that they are only necessary with an HTML type skin.  My skins seem to work without, but maybe I'm missing something subtle.

Thanks in advance!

Phen

 
New Post
6/19/2007 3:16 AM
 

You can FTP the new skin, but use the unzipped files overwriting the originals, then if you used HTML skinning reparse the skin and you are done.

Please note that if you add a new CSS file to the skin (e.g. skinname.css) which wan't included before, you have to restart DNN or the link to the file will not be rendered. This is due to caching.

(Restart: login as Host > Host Settings > Advanced Settings > Other Settings > [Restart Application]

I think at the moment the only way to solve your container problem would be to assign a different one to a parent page and choose copy design form the page settings, this will overwrite the assigned container for all the pages below.

You are right the XML file is only for HTML skins

 
New Post
6/19/2007 5:59 PM
 

Thanks Timo!

I think that gives me a good start.

Phen

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Skin File Management questionsSkin File Management questions


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