Custom Code --> Custom CSS --> CSS Rules Field Doesn't Work

[steffanantonas 0]

I've installed Platform Pro (v 1.2), and I've activated the Base childtheme (1.0.4) to customize my site. The only problem is that I can't get the CSS rules to take inside theme's control panel (Custom Code --> Custom CSS). I'm guessing this is a permission issue, but I can't find the right file to 777. I even went back and reactivated the platform pro theme, and set the dynamic.css file's permissions to 777. Didn't work. Please help before I lose all my hair. It also might be helpful to put up a list of all the files that need to be writeable in the FAQ. Thanks!

[cmunns 16]

It may not be a permissions thing as that code gets inserted into the header, what is a sample of the css that won't change, you may just need to be more specific with your selectors?

[steffanantonas 0]

It's basic stuff like... #body { padding-top: 15px; } #feature_slider .fcontent .dcol-pad { height: 450px; padding: 100px 30px 20px; } I can't seem to change ANY CSS

[Andrew 207]

A live link would help us investigate... Until then we can only guess... couple ideas: 1. Could be about specificity (rules not specific enough) 2. Is the dynamic.css file changing when you change design control rules? 3. Are your rules working with FireBug?

[steffanantonas 0]

Andrew, Here's a live link. A few answers to your questions - The dynamic.css file seems to be picking something, but it's gobbledygook, which I've never seen before. Check this out... Yes. Rules work with firebug. Thanks for your help.

[catrina 103]

That is strange. Have you tried viewing dynamic.css in another text editor (not Dreamweaver)?

[steffanantonas 0]

Catrina, This is a screenshot of my text editor. Mac shows the dreamweaver icon, but this is just txt.

[catrina 103]

Ah, I see. Maybe it's just the text editor display then. Which specific rules do you want to edit?

[steffanantonas 0]

Problem solved. No idea why this is, but it's so simple it's insane. All of my CSS rules I was putting in to the Custom CSS field looked like this (for example)... #body { padding-top: 20px } When I removed the "#", i.e. body {padding-top:20px} Everything worked and all the styles took. I was just following the convention of your own style sheet. So there, you go. Problem solved.

[steffanantonas 0]

Here's a tip for people having the same problem.... Styles that look like this (below) REQUIRE the "#" for the custom CSS to take (i.e. removing the "#" will result in no change): #soapbox .fboxgraphic { height: 255px; margin: 0 0 55px; overflow:visible; } but styles with no classes (like below), need to have no "#" in order to work: body { padding-top:20px } That's the way it works in my theme at least. I have NO idea why this makes a difference, but it does.