Forums

Setting theme css effects Concrete5 CMS values

Permalink
Hi Team

OK this is a little moan/ request for the CMS backend. Unless I have missed a bit completely and Am doing this all wrong!.

OK now I design lots of custom themes for concrete5 and I have come across this problem a few times now.

OK now what i did:
css 
button, input, select {
-moz-box-shadow:inset 0px 1px 6px -5px #304022;
   -webkit-box-shadow:inset 0px 1px 6px -5px #304022;
   blaa blaa blaaa ....
}


Now this sets my default theme forms and buttons to the css, so I don't have to set class on every section, unless i want it different.

But this effects the CMS/backend when I click on edit blocks the forms are unreadable as they are a mix of my css and the root css.

Ok that didn't work.

So next I put the css in a class or div .wrapper button, input, select { } which still over-rides the CMS css.

Then I decided to edit ccm.app.css Which by the way has no line brks (why god why...) i thought if i change 1 rule in their it might override local. Which it did on 1 block!!! not all so am not sitting here finding them all 1 by 1. After spacing the document out!

So ever I am doing this all wrong. .. or you need to lock down the CMS with its own CSS, so that this doesn't happen?

I thought using a wrapper would restrict it to the theme pages!!

Any Ideas? Any one?

ON another note the tinyMRC css could differently need some css locking down as I have off tern had problems with this.

Is there a way to create a defult.css with forms styles etc in-it which override the theme for the CMS only?

Sorry about the moan people, just every time i do a theme i have some issue like this with css messing around with the CMS css.


MAny Thanks Team...
I do love Concrete5 Mine you.

Also I have done so many templates for blocks now I would like to put them into a free add-on. If any one can help with that PM me.


and
carl101lee
 
mckoenig replied on at Permalink Reply
mckoenig
I usually put a

<body>
<div id='stage'>
rest of the markup goes here
</div>
</body>


in place. This way I could target the form fields like this:

#stage button, #stage input, #stage select {
styling goes here
}
carl101lee replied on at Permalink Reply
carl101lee
Hi Thanks

Thanks I actual tried that. But from what I understand, I was setting it wrong!

after I put this in my typogrpahy.css like this it seem s to work without effecting the CMS.

Sorry for the moan after a bit of reading I believe it was my CSS screw up. Ops best fixed the other sites two. 
.wrapper button { }


Don't Do This
.green button, input, select {}



using a wrapper around my doc and setting a default in the css to fall back on seems to have solved it.
mckoenig replied on at Permalink Reply
mckoenig
For what's worth, I highly recommend using LESS (http://www.lesscss.org) to write your CSS. It will make something like this so much more easy.