Css code is very picky. Leave out a curly bracket and the browser will not read the rest of the code. Place a colon where a semi-colon should go and things get crazy.

I have had some display issues with the footer in my blogs. I had built a skin.css file and added it to the folder. I got the file path right and the skin was working except for the footer. I never could figure out why it didn’t work, but it was only the footer image that I could not get to display, so I passed it off as unimportant. I just shrugged as thought that was the way it was going to work. There are several levels of folders to a WordPress blog. I thought maybe it was something in one of the other folders that was causing the problem.

I just set up the new Live Sound Mixing Tips blog. While setting it up I was making some tweaks and adjustments. I was looking in my skin.css file that I had copied to the folder and noticed that there was a closing curly brace missing on my nav rule. I put in the missing brace and updated the file. When I checked the site I had my footer background image as I had often wished.

Somewhere along the line (a few times, I am sure) I typed a colon where the code calls for a semi-colon. That does not work, I promise.

I have been going through my other blogs making the correction and a few other tweaks this evening. I am beginning to be quite comfortable with the untheme theme. I will copy the fresh css files to my blog master copy, the one that I copy to a new location when I set up a new blog. That will save a lot of time the next time that I set up a blog.

I went a little further than I have with my other blogs on the Mixing Tips blog. Check it out and tell me what you think.