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

wjroes’s picture

wjroes CreditAttribution: wjroes commented
Status: Active » Closed (fixed)

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.

wjroes’s picture

wjroes CreditAttribution: wjroes commented
Status: Closed (fixed) » Active

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?

wjroes’s picture

wjroes CreditAttribution: wjroes commented

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.

cr0ss’s picture

cr0ss CreditAttribution: cr0ss commented
Priority: Normal » Major

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?

cr0ss’s picture

cr0ss CreditAttribution: cr0ss commented

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.

sagannotcarl’s picture

sagannotcarl CreditAttribution: sagannotcarl commented

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.

muschpusch’s picture

muschpusch CreditAttribution: muschpusch commented

+1 on having some kind of fix / documentation for this.

prorokxp’s picture

prorokxp CreditAttribution: prorokxp commented
Version: 7.x-3.x-dev » 7.x-3.1

+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.

prorokxp’s picture

prorokxp CreditAttribution: prorokxp commented

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

bendikrb’s picture

bendikrb CreditAttribution: bendikrb commented
Issue summary: View changes

I had the exact same problem as #8 - and was about to go completely nuts before I saw this in commerce_kickstart.install_callbacks.inc:

    array(
      'module' => 'system',
      'delta' => 'main',
      'theme' => $default_theme,
      'status' => 1,
      'weight' => 0,
      'region' => 'content',
      'pages' => '<front>', // Do not show the block on front.
      'visibility' => 0,
      'cache' => DRUPAL_NO_CACHE,
    ),

This was not reflected when I checked admin/structure/block/manage/system/main/configure, but just saving the block one time fixed the problem.