9 replies to this topic

[christian_w]

I'm witnessing a strange behavior of the platform pro theme ever since I updated to the newest version of Platform Pro:

 #boxes .dcol-pad {
	    background-color: #F3F3F3;
	    border: 1px solid #DEDEDE;
	    height: 120px;
	    margin: 5px;
	    padding: 5px;
	}

When I enter this code into the custom code section it does what it is supposed to do - it creates a greyish background to the boxes.

When I enter the same code into the base-child theme it is not recognized.

While at the same time a different line of code IS recognized. (For example: I changed the font-family to Arial, sans-serif via the child theme. When I delete this line of code, font-family styling falls back to the original PlatformPro version.)

I can easily recreate this behavior with any other lines of CSS.

I am running my blog on WP Version 3.1 and the newest version of the Platform Pro (1.3.0.2) + PlatformBase (1.3.1).

My blog is password-protected at the moment so I cannot provide a link here.

I'd very much appreciate your help.

Thanks
Christian

[arpowers]

Sounds like a specificity issue, I'll look at it.. In base.css just add `body` or `#page` in front of any CSS rule and it should work. e.g. `#page #boxes .dcol-pad`

[christian_w]

Thanks! I tried it but unfortunately it still doesn't work. Any other suggestions what might work?

[arpowers]

Ok, live link? What is Firebug telling you?

[christian_w]

The changes in base.css do not apply. According to Firebug the styling is

 #boxes .dcol-pad {
	    padding: 8px 0 0;
	}

.
Although it should be

 #body #boxes .dcol-pad {
	    background-color: #F3F3F3;
	    border: 1px solid #DEDEDE;
	    height: 120px;
	    margin: 5px;
	    padding: 5px;
	}

I disabled the password protection for the moment. The live link would be:
http://krimtheo.crim...gia.de/theorien

[Kate]

Hey Christian - Not sure what you mean by "it should be", but one thing I noticed is you're putting a "#" before body, where you really don't need to

[christian_w]

Hello Kate, of course you're right - I don't need the "#". But it doesn't change anything. When I wrote "should be" I was referring to the difference between what it says in Firebug currently and what it should say. As mentioned above my base.css file isn't recognized by the Parent theme anymore.

[cmunns]

Did you disable ajax saving. We have experienced some people having issues with ajax saving in Base and thus added an option for it

[arpowers]

@Christian, I think this is a CSS Syntax error which we don't see often. Related to the special characters in this word: ???“bersichtsseite

[christian_w]

Thanks Adam, thanks Andrew, I followed both your advises but neither worked for me. Finally I deleted and re-installed the Base-theme and everything is working again. Sorry, I should have tried that earlier. Thanks for your effort anyway.