Skip to:
Content
Pages
Categories
Search
Top
Bottom

[Resolved] Cannot override div#content .padder using child theme

  • Avatar of notpoppy
    notpoppy
    Participant

    @notpoppy

    I am in the early stages of building a new child theme based on the default Buddypress theme.

    The new theme includes a larger sidebar on the right-hand side. I specified new widths for the relevant tags in style.css in my child theme and this all worked fine.

    I also needed to correspondingly reduce the width of div#content .padder by increasing its right-hand margin from 225px to 325px. So I added the following to style.css:

    `div#content .padder {
    margin-right: 325px;
    }`

    However this alteration has had no effect on the site whatsoever. It’s as if it can’t see the lines I’ve added in style.css – although I’ve had no such problems changing other tags such as div#sidebar.

    I’ve inspected the code repeatedly using Firebug and can find no flaws whatsoever.

    Eventually I tried adding the following to header.php:

    `
    div#content .padder {
    margin-right: 325px;
    }
    `

    This worked – but of course it’s an unsatisfactory solution. Can anyone suggest why it might be failing to alter div#content .padder when I specify changes to it in style.css?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Avatar of notpoppy
    notpoppy
    Participant

    @notpoppy

    I’ve jut noticed that putting the code in header.php spoils the responsiveness of the theme – the main column no longer expands to fill the page on smaller screens.

    The upshot is my workaround solution is no good and I’m now even keener than before for a proper fix so someone please help me!

    Avatar of notpoppy
    notpoppy
    Participant

    @notpoppy

    Well I’ve just re-started the .css file from scratch, rebuilt it line-by-line testing every time, and now it works. I can’t see any different between the file I had originally which wasn’t working and the one which is now working correctly, but there it is.

    Anyway, consider this resolved now.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.