I love this theme. Thank you for sharing it.

However, I'm facing a bit of a problem with it. In some of installations all the content is displayed with a big gap, like an empty column on the left. I tried this across 3 of my installations, and I faced the issue in all of them. It occurs with some of my custom content types, but it also occurred with the default article and basic page types in one case too.
I tried making a fresh copy of the content, but faced the same issue.
I've got Drupal 7.8 installed. I'm using tundra, artica, touch pro, skinr, colorbox and display suite (but I haven't made any changes to the display suite settings.)
The alignment issue occurs in content with and without images.

Please help.

CommentFileSizeAuthor
c2.png215.16 KBchats
c1.png38.62 KBchats
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

chats’s picture

I tried to use skinr to fix the alignment, but that didn't work.

JurriaanRoelofs’s picture

Status: Active » Closed (works as designed)

Hi, that space appears in nodes that have an image field. The empty space is where the image should go.
If you want nodes without that space you have to use a node type that doesn't have an image field.

toomanypets’s picture

In case someone stumbles across this in the future...

Problem

This theme applies special theming logic to any content type that contains a field named "field_image" regardless of the field type and regardless of whether or not the field is empty. For example, let's say you create a new content type "foo" and add a text field named "field_image". Now create a new "foo" node, populating the title and body, but leave the "field_image" field empty. When you display the node, the body content is pushed to the right, leaving an empty area on the left that is 240px wide (200px reserved for "field_image", plus 20px margin on both sides).

I logged a separate issue (#1759220: Content types with field_image defined render incorrectly when no image is present) with a recommended code change to prevent this behavior (a) when the field type of "field_image" is anything other than "image" and (b) when "field_image" is empty.

Work Around - Option 1

This work around should only be used if all of the following are true:

  • You wish to manually place image field content within the body instead of relying on automatic image placement
  • You are working with a new site without any content, or don't care about deleting existing images stored in a field named "field_image"

Instructions:

  1. Delete the field named "field_image" from the content type with which it is associated
  2. Create a new image field named anything other than "field_image"

Work Around - Option 2

To retain the automatic image placement with a field named "field_image", but to prevent the empty white space when no image is present on the node, create a subtheme and override touchpro_preprocess_node():

function my_subtheme_preprocess_node(&$vars) {
  if ($vars['teaser']) {
    $vars['title_suffix']['post_icon'] = array(
      '#markup' => '<div class="post-icon"><a href="'. $vars['node_url'] .'" rel="nofollow"></a></div>',
      '#weight' => 100,
    );
  }
  if (!empty($vars['field_image']) &&
        $vars['elements']['field_image']['#field_type'] == 'image') {
    $vars['classes_array'][] = 'node-imagefield';
  }
}

This will restrict the special handling to cases where ("field_image" is not empty) and ("field_image" is an image field).