Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Are you using Firebug or an equivalent tool?
No. Not sure what those even are.
Good call Andrew.
They are tools which help you visualize and edit your loaded page on the fly and see how they affect the display. You can easily see missing files, script errors, loading times, loaded resources, calll javascript functions, etc.
Chrome comes bundled with the developper tools by default. Right click an element and click Inspect.
Internet explorer has it also by default.
Here’s the link to firebug: http://getfirebug.com/
If it is the padding before the post title that you wish to shrink, you’ll need to apply your css like this
.entry-content h1 {
padding-top: SomeValue;
}
Hope this helps.
I’ll look more into the developers tools guys… I tried the
.entry-content h1 {
padding-top: SomeValue;
}
and it didn’t work.. I’ll keep pluggin away.. If anyone has another suggestion, please let it fly!!
Thanks
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
What did you replace “SomeValue” with?
.entry-content {
padding-top: 0px;
}
This problem was there before I got the bread crumbs to work also.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Oops I think Thimothe meant to say margin instead of padding.
When I right click with chrome and inspect the element, it says its “entry-content”
I replaced it with
.entry-content {
margin: 0px;
}
and still no dice.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Should be this:
.site-content .entry-content h1 {
margin: 0;
}
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Lol, I was just going to post the same picture! That actually worked. Now how did you know that code would work?
Thanks guys… I was trying everything I could out of my themes css… this gives me closure.
Thanks again!!
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
You see the black underlined “style.css?ver=3.6.1:686” in the screenshot? Click through to that and you can edit the stylesheet.
I added the recommended style to your (child theme) style.css file through the developer toolbar just to make sure you weren’t experiencing any syntax errors.
