Community Forums › Forums › Archived Forums › Design Tips and Tricks › Suddenly, my sidebars are all block-level.
Tagged: Agency
- This topic has 3 replies, 2 voices, and was last updated 11 years, 3 months ago by marybaum.
-
AuthorPosts
-
June 6, 2013 at 9:46 am #44334marybaumParticipant
What have I done at http://marginhancers.com?
No matter what I choose in the theme settings, and even though I have added the new selector that seems to be controlling the sidebar - the one the inspector shows is controlling everything AND NOT the sidebar divs that are in the CSS:
div#sidebar.sidebar.widget-area {
display: inline !important;
float: right;
font-size: 14px;
width: 280px;
}And, as you see, made the inline display important, something is totally brushing me off.
It wasn't like this until sometime yesterday.
It's not a plugin conflict - I just deactivated them all, and nothing changed.
I had added Bill Erickson's social defaults functions, but they're gone now, and I'd made a filter to get rid of the lists on archive views - but that's now also gone. So my functions file now only has StudioPress-written code in it, except for extra widget areas and image sizes, which have never caused this before. (And my renaming of the portfolio divs, functions and page).
So if targeting the browser's selector for the sidebars and adding !important; to the inline display isn't getting things back to normal, where do I go from here?
Mary
BTW - the home page is fine. This is only an issue on interior pages. MB
Sharing the good news about the wonders of modern CSS and the split-step. Either one should get you moving fast. ๐
June 6, 2013 at 10:54 am #44357David ChuParticipantHi,
Just some editing needed. Essentially, you need spaces between classes and ID's. Also, you have a sort of "stack" of things in a line that all refer to the same thing, and that won't ever work. Also, no "important" needed. Try this instead.#sidebar { display: inline; float: right; font-size: 14px; width: 280px; }
btw, your site loads very slowly, and a major reason for that is that your photos are much larger than they need to be. if you edited them down to the slots they're supposed to go into, this will be alleviated. Not critical, but will make your site more usable, and Google cares about loading speed as well.
Dave
Dave Chu ยท Custom WordPress Developer – likes collaborating with Designers
June 6, 2013 at 12:00 pm #44373marybaumParticipantThanks. I wish that had worked - but the user agent stylesheet is overriding that too.
It's as if there's something in the php somewhere that's forcing a block-level display on the sidebars, no matter what the css says - it's just ignoring all my sidebar CSS, period. Normally, !important; puts me back in charge, but not this time.
Here's a screen shot of my Inspect Element:
Notice that the browser isn't even pointing to the stylesheet at all when it comes to the sidebars - the user agent is controlling everything. In fact, when I look at Computed Styles and Show Inherited, there's no indication where the stylesheet override is coming from.
I agree my images are big. Now that I have the slider in the home content area, they can probably go down to 600px wide - I had been keeping the originals at 1024 so they wouldn't look awful as the featured images in a full-width slider.
Some linked images will need to stay big so people can read the copy in portfolio pieces, but I would think those would only load on click - until that happens, won't the anchor images just load?
Thanks again for your input ...
MB
Sharing the good news about the wonders of modern CSS and the split-step. Either one should get you moving fast. ๐
June 6, 2013 at 12:39 pm #44390marybaumParticipantI found the problem!
Apparently, when I gave my Cases In Point template the wrong name - it didn't match the php filename - that messed up the page layouts, too.
It's all fixed now!
Thanks for listening.
Mary
Sharing the good news about the wonders of modern CSS and the split-step. Either one should get you moving fast. ๐
-
AuthorPosts
- The topic ‘Suddenly, my sidebars are all block-level.’ is closed to new replies.