Validation

"end tag for element "div" which is not open"

Not sure if we're talking about the same error? I get this error on the reply node-page on a single story node, when the reply button has to be pressed in order to open the reply form. After pressing the reply button the sidebar shifts down. This bug happens on the left, right, and combination of left and right sidebar(s) (with the (combination of) search block/ who's online/ login/ navigation tested).

The shifting of the sidebars does not occur on the forum form.

It needs further testing, but preliminary testing shows that the code below fixes the problem for modules enabled left, right, and both left and right. So at present it does not appear to be a added blocks problem.

In page.tpl.php:

Replacing:

 </div> <!-- /#content-header -->
              <?php endif; ?>
              <?php print $content; ?>
            </div> <!-- /#content-inner -->	
          </div> <!-- /#content -->

With:

 </div> <!-- /#content-header -->
              <?php endif; ?>
              <?php print $content; ?>
            </div>
<? if (arg(0) == 'comment') { ?>
</div></div>
<? } ?>
 <!-- /#content-inner -->	
          </div> <!-- /#content -->

Fixes it, albeit temporarily. It might happen in other places as well (such as book or blog, but I don't have those installed).

Does anyone know which module/ code gets loaded in that area? I haven't been able to find it yet.

Hope it helps.

Edit: This is for the BlogBuzz II theme.

The fix doesn't work when reacting on a comment, and content type option is set to open comment form on new page.

Working:
On node example: http://www.ecodelphinus.com/?q=node/272
On reacting on node with comment form opening on new page example: http://www.ecodelphinus.com/?q=/comment/reply/272#comment-form

Not working:
On reacting on comment with comment form opening on new page example: http://www.ecodelphinus.com/?q=comment/reply/272/6

Page doesn't validate because of the two added extra div's.

</div></div> <!-- /comment-inner, /comment -->

Gets loaded in comment.tpl.php when replying on a comment, but does not load when replying on the article directly. This is what is causing the validation error on the reply pages.

1. Not sure if this is part of the cause. In comment.pages.inc in the Drupal core module 'comment'.

Is it loading different views? Could that be (part of) the problem?

on line 81 to 85:

          // Display the parent comment
          $comment = drupal_unpack($comment);
          $comment->name = $comment->uid ? $comment->registered_name : $comment->name;
          $output .= theme('comment_view', $comment, $node);
        }

on line 91 to 94:

 // This is the case where the comment is in response to a node. Display the node.
      else if (user_access('access content')) {
        $output .= node_view($node);
      }

2. Not sure if this has anything to do with it either, with Clean URL's turned on, the reply button on the node still shows the ?= path specifically ?=/comment/reply/'node id'#comment-form. Removing the question mark manually does not solve the problem. On the reply to comments it does show the Clean URL's. As well as everywhere else.

3. Everything displays fine in Garland. Also 2 does not occur in Garland.

In page.tpl.php replacing:

 <!-- /#content-header -->
              <?php endif; ?>
              <?php print $content; ?>
            </div> <!-- /#content-inner --> 
          </div> <!-- /#content -->

with:

<!-- /#content-header -->
              <?php endif; ?>
              <?php print $content; ?>
            </div> 
<?php
    
	$comment_reply_div = node_load(array('nid' => $comment->cid));
		 if (arg(0) == 'comment' && arg(1) == 'reply' && arg(3) == $comment_reply_div) {
 
?>

</div></div> 

<?php } ?>

<!-- /#content-inner --> 
          </div> <!-- /#content -->

Fixes the div validation, and the sidebar dropping down problem. Even though technically it shouldn't?

This has been tested against a base install of Drupal, and the forum module, and works on the install tested. This has not been tested with other modules such as the book and blog module.

Could not find the other validation errors in the theme mentioned in the op. YMMV.