I Thought He Came With You is Robert Ellison’s blog about software, marketing, politics, photography, time lapse and the occasional well deserved rant. Follow along with a monthly email, RSS or on Facebook. About 7,250,102,767 people have not visited yet so it might be your first time here. Suggested reading: Got It, or roll the dice.

Blogger Classic Templates Bugs and XHTML

I've just migrated this blog from catfood.net to its own domain. In the process I needed to port the template from classic ASP to ASP.NET and I also wanted to end up with valid XHTML.

If you're using blogger on your own domain then you're using the classic templates. There is a known issue with the template tag that causes Blogger to emit unwanted JavaScript - this causes havoc, especially if you're using the tag in the section of a page.

Google recommends using the <$BlogPageTitle$> tag in the page title. This works, but it's not great from a usability or SEO perspective. For item pages you get the post title after the blog name and you probably want to put the post title first - the earlier that keywords appear in the title the better for search engine ranking.

Luckily there's an easy fix - just comment out the closing Blogger tag:

This doesn't interfere with the template rendering correctly and the JavaScript is then commented out on the rendered page. It's still an unpleasant bug, so if you use the classic templates please report it here and also star or comment on this forum topic to encourage Google to fix it.

If you use labels then Blogger includes them in a paragraph rendered with <$BlogItemBody$>. This means that wrapping <$BlogItemBody$> in a paragraph will cause XHTML validation errors for posts with labels because you can't nest another block element inside the paragraph.

The other XHMTL nasty I fixed was the post comments link. My template used the recommended Blogger code:
<p><a href="<$BlogItemCommentCreate$>"
<$BlogItemCommentFormOnClick$>>Post a Commenta>p>

This renders as:
<p><a href="https://www.blogger.com/comment.g?blogID=12345678&postID=1234567890123456789"
location.href=https://www.blogger.com/comment.g?blogID=12345678&postID=1234567890123456789;>
Post a Commenta>p>
And you end up with a gazillion cascading XHTML errors, all caused by the illegal ampersand. I fixed this by constructing my own comment URL using the <$BlogItemNumber$> tag (this emits the unique Post ID):
<p><a href="https://www.blogger.com/comment.g?blogID=12345678&postID=<$BlogItemNumber$>">
Post a Commenta>p>

Comments

Santina

Ditto above. Thank you!

Add Comment

All comments are moderated to weed out spam. Email address is optional and is only used to display your Gravatar.