I have configured my template to have in the content zone the content, sidebar first, and sidebar second. The sidebars are set to display next to the content giving me a three column layout. This config is correct on the home page but not any of the article content type pages (or basic pages for that matter). When you are viewing an article on the site the sidebar first and sidebar second zones end up under the content rather than beside it as I've specified in the settings. I have them set to display on all pages.
If you view it with the grid overlay turned on, the regions display correctly.
The site is
article page:
http://beta.upstreampumping.com/?q=article/mud-pump-belt-drive-basics
home:
http://beta.upstreampumping.com
So, how can I get them to display as they should without the grid overlay on?

Comments
I don't see a #zone-content
I don't see a #zone-content or #region-content being displayed in your css. Is the content zone set to static or dynamic?
I had a similar issue where I had set a margin in the content, which pushed the sidebar blocks outside of the 960 gs, causing them to be displayed under the content.
The zone is set to static.
The zone is set to static. Would that make a difference? I'm not sure I fully understand the difference.
I could see where the content might be pushing it aside for some of the articles but it happens on basic pages as well which have very little content on them.
Hmm.. Why are you still using
Hmm.. Why are you still using Omega 2.x while building a new theme?
Isn't Omega 3 still in beta?
Isn't Omega 3 still in beta? Maybe trying the beta would fix several issues I've run up against.
Omega 3.x is currently the
Omega 3.x is currently the recommended version. Even if it is in Beta, yes.
Try making it dynamic and see
Try making it dynamic and see what happens. What size is it set at now in your zone configuration? After prefix what is the width set to?
Since you're still using 2.x To make things easier, I suggest resetting your configuration back to default and creating a subtheme.css and then overriding what you need in that css file. This way you can tell what you're changing and only change what you need, instead of editing each of the included css files directly.
If you aren't too far along, you really might want to consider upgrading to 3.x
While it is in beta, it works beautifully and the interface improvements are really nice. It also includes responsive web aspects too.
If you upgrade to 3.x, you will have a styles.css already included in the starterkit you choose.
Are you using the html5 starter kit?
The content zone is set to
The content zone is set to 940 size and the Content is 8, sidebars set to 2 for each of them. Yes -- HTML 5 starter kit.
Good to know that the beta of Omega 3 works so well.
Omega 3 is the Recommended release...
While the tag for the release may be beta, the Omega 3.x branch IS the recommended release. If using drush to download Omega, this is what is downloaded, unless asking for a specific version...
For the majority of 2.x support & feature requests, the reply is simply: "Upgrade to 3.x".
If you are starting a new site, then without doubt, 100% of the time, Omega 3.x should be used. It is more flexible, more stable, and has a much higher performance benchmark than any prior version.
Jake Strawn (@himerus)
ThemeGeeks | Development Geeks
Omega - 960.gs