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 test new skinHow to test new skin
Previous
 
Next
New Post
11/8/2006 12:51 PM
 
Sorry for the basic nature of this question, but I am really confused and searching the forums here did not uncover any useful posts!

I've just created a new dnn site using the starter kit (4.0.3) and added a new skin (again using the starter kit template). All went ok - the site runs ok and I renamed the skin folders as per the instructions that the starter kit popped up. 

My question is, how do I go about actually testing my skin as I develop it?  Do I have to install it before I can use it, and re-install it every time I make a change?  I am confused because as things stand, my list of host skins includes an entry called 'skinname' but of course that contains nothing because I renamed the folder that the starter kit template created as instructed.  I cannot find the skin I created (which I called TestSkin1) at either the host or portal level.  Do I need to do something else before I can use it and therefore test it?
 
New Post
11/8/2006 4:11 PM
 

Mike:  I hope that my reply helps.  What I normally do is modify my skin (the .css and/or .aspx files) and then repackage the skin for deployment (essentially, re-zipping the skin files).  I re-install the skin to my portal - you do this via the Admin/Skins menu - select the re-packaged skin and upload the file, DNN does the rest.

To test, I have one or two hidden pages on my portal where I apply the skin to make sure all is good before applying it for public use.

- Ron.

 
New Post
11/9/2006 5:41 AM
 

host skins are installed at /portals/_default/skins/<skinzipname>
admin skins are installed at /portals/<portalID>/skins/<skinzipname>
host containers are installed at /portals/_default/containers/<containerzipname>
admin containers are installed at /portals/<portalID>/containers/<containerzipname>
They are hidden from the DotNetNuke file manager to prevent unwanted modification

For development I use a local DNN installation, where I can easily tweak the files until it looks like expected. Notice, that changes on skin.HTML and skin.xml requires a reparsing of the skin / container, in order to take effect.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/9/2006 6:48 AM
 
Thanks to you both for your replies - it is starting to make sense now! 

I get the impression that most people prefer to edit their skin design as html (plus the xml of course) and then reload the skin in DNN to parse it in to an ascx.  This seems a bit long winded, as it means you can't immediately see the effect of making changes.  I tried editing my ascx file directly which certainly produced immediate changes, but it's difficult to see exactly what's going on.  Should I stick to editing an html version and let DNN create the ascx?

Thanks again,


Mike

 
New Post
11/9/2006 7:06 AM
 

How about trying this - if you feel more comfortable using html, then continue to do so..

Open one window and have it open on the Host/Skins or Admin/ Skins page - where ever you are saving files to.

Then have another window open with the skin file in it.

Open the html file directly where the skin is.. work on it, work on the xml file in situ -and then when you've saved it - drop the skin box down in the skins area, and downl the bottom of the page, you'll see - parse skin - click the *portable* radio button and reparse the skin..

Then click the other window where the skin is.. and preview it.

It's like working in ASCX mode, but, you're reparsing the html skin which means the skinning engine is doing it's job with the html file and modifying the ascx file for you instead.

I was thinking about how to skin a cat .. and there are lots of ways..

Give that at try - then you won't have to zip the skin all the time and you get your cake and eat it too.

Cheers

Nina Meiers


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...How to test new skinHow to test new skin


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