Posted by wjroes on October 6, 2011 at 1:27pm
5 followers
Jump to:
| Project: | Omega |
| Version: | 7.x-3.1 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | major |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Hi guys,
For the life of me I am not able to figure out how to add a wrapper/container around just the content region.
I am creating a new subtheme based on the omega-html starterkit and leaving it quite default.
In my Content Zone I have a Sidebar First region followed by a Content region followed by a Sidebar Second region. Now I want to have a container around the Content region in the middle, but how?
region--content.tpl.php doesn't work unfortunately
Thanks,
Willem
Comments
#1
Well, apparently I was just looking in the wrong place. There is a region--content.tpl.php and it was in the right location as well. Duh!
I was looking in the alpha template section.
#2
Nope. I was wrong (again). I am still missing the actual content region. The content is there but it is not being (pre)processed as a region. It doesn't show up in Debugging Block overview. This is with the omega-html5 starterkit, but it is the same with the other starterkits.
What's going on? Anyone seeing the same?
#3
Maybe this will help someone else running into this...
Apparently this missing region happens when using the fluid layout. Content elements are just dumped in the content region without a container around it. In my case, with a left and a right sidebar and content in between, this caused the right sidebar to indent and/or disappear.
#4
I'm getting the same issue with Omega 3. Sidebars are getting proper wrappers with specific classes, so they are getting rendered right.
Unfortunately content region doesn't get any wrapper and simply messing the content zone.
If there is a way to avoid this issue?
#5
Just found the issue for me and I believe it should be described somethere at Readme:
- Main page content block should be placed at content region in case you want to render it properly within Omega grid settings.
Elsewhere you'll just get a rendered content without any wrapper.
#6
I just came across this after doing some hair pulling. I agree that having this in the documentation somewhere would have been really helpful. There are step-by-step descriptions of grid settings but nothing about why node titles don't show up by default when looking at node pages.
#7
+1 on having some kind of fix / documentation for this.
#8
+1 have the same problem. views page in my frontpage does not wrapped with content region. why?
I noticed that if I add an extra block to the Content region, then there is no problem. Seems like omega does not sees content block in frontpage, but for some reason it outputs this block directly to the content zone. very strange.
comerce kickstart. default installation. omaga-html5 starterkit.
#9
my main page content block is placed in content region.. but i still have this problem. it appears only on frontpage. if page is not frontpage, then there is no such problem