Hi,
it was hard to track the issue I was pointing out here, but now I think it's caused by node location module.

It adds a close DIV before what is stored in $content variable in node rendering, and this breaks the page layout.
If I disable the node location module, that div disappears.

To reproduce:

  1. activate node location module
  2. create a new content type
  3. in the content type configuration page, in locative information settings, leave all as default (i.e. minimum number of locations = 0, display settings: leave the 2 first check-boxes checked)
  4. create a new node of that content type
  5. Check the HTML of the page and you should find the guilty </div>
  6. just before what is contained in $content variable in $node

<div class="content">
<?php print $content; ?>
</div>

What you get in the rendered HTML is a redundant closed div before the content, like:

<div class="content">
</div>
Lorem ipsum dolor....
</div>

If you uncheck the 2 check-boxes at point 3, the DIV disappears

--
GP

Comments

yesct’s picture

Issue tags: +Location theming

is this related to #769094: locations.tpl.php bug
?

gp.mazzola’s picture

Yes, I think it is related.
In fact that closing DIV in the locations.tpl.php template is outside the if statement.
Thank you

--
GP

eporama’s picture

Status: Active » Closed (duplicate)

This is a duplicate of #769094: locations.tpl.php bug which is patched and RTBC

The two checkboxes that toggle whether or not the locations show at all in teaser and full view would remove the problem since you're not showing locations when they're unchecked. It also causes nesting problems when you do have multiple locations.