Hi.

I got it to work by copying all the css info to a file called "skinname".css
In this case I copied all the css on top of the
"Slingerland-Black-Red.html" file
 to a file called "Slingerland-Black-Red.css"

Normally it should also be possible to copy the CSS to skin.css, but I cannot get this to work.
I might be doing something wrong, I am well over my computer-time limit today....
I'll mail you my testskin

---

I'm working on a new portal in 4.3.5.  I modified my skin.css and copied it to my portal skin directory and it worked fine, I could see the changes.  However, when I reloaded the site, it would not loading the skin.css.  I have also copied a skin.css from another 4.3.5 portal and it would not load.  Then it would!!!

I can't seem to find the conditions under which the load is failing, but when I look at the loaded css files, the skin.css is definatley not there.

There is definatley something strange going on with css files in 4.3.5

My own experiences may provide some more insight to this thread. One disclaimer - The process I use for creating/modifying skins/containers may prove to be the thing that created my problems in the first place.  I don't mind if this is a discovery made along the way. 

Dev Environment - DNN 4.3.5/Server 2003/VWD 2005 Express/SQL 2005 Express

I created multiple skins and containers for one site. I chose to do it this way so that I could have ultimate flexibilty in page layout and container control within these layouts.  I orginally started out by trying to accomplish this flexibilty goal by creating one skin/one css file one container/one css file but as the site grew, I found the css files becoming unmanageable and confusing.  For me, it just works better to have these page layout goals seperated.  What's all this got to do with this thread?

I started running into problems with multiple containers.  I could not get the containers css files to act independently of one another but all containers would default to one particular container's css file, even though the containers were logically seperated by folder and by method (each container was seperately uploaded using the DNN tools provided and re-parsed when needed).  Also, the containeers ascx files were referencing the right css file.  I could see changes being applied in VWD when working on these files, but when I would save and set the container under page settings, it would not work, but seemed to be defaulting to one of the other container CSS files.  In fact, all containers were defaulting to one container's CSS file.

Earlier in the thread, someone mentioned the classes of the containers may need to be distinguished.  I  tried this and it worked:

First example container

/* ==============================
== Main container holder, set box borders and background colour
================================== */
.containerholder_right
{
    background-color: transparent;
    padding: 10px 0px 10px 0px;
    border-bottom: #999999 1px dashed;
}

/* ================0
== title section
===================*/

.actions_right
{
    text-align: center;
    padding-bottom: 10px;
}

2nd Example Container

/* ==============================
== Main container holder, set box borders and background colour
================================== */
.containerholder_left
{
    background-color: transparent;
    padding: 10px 0px 10px 0px;
    border-bottom: #999999 1px dashed;
}

/* ================0
== title section
===================*/

.actions_left
{
    text-align: center;
    padding-bottom: 10px;
}


This worked, but I didn't write all this to say I solved my problem for now, even though I hope it might help someone else.  I want to know what's going on so that my skin creation methods are not going to continue to cause problems down the road. Why wouldn't the css for the container in that containers folder get applied regardless of other seperate containers whose classes may be the same? I got the impression that in DNN the custom CSS file is the file that is read first and things moved up from there.  My classes in my containers are not duplicates of other classes in CSS files higher up the chain.  Is this the way it's suppose to work or is it particular to this version?  Long winded I know, but this was a major headache for me to figure out.

Paul