The official coComment weblog

The popular German-speaking blog platform twoday.net has improved support for coComment. The default skins now contain <% this.coComment %>, which injects the following code in the comment page:

<script type="text/javascript">
// <![CDATA[
// adds support for CoComment
  var blogTool              = "twoday.net";
  var blogURL               = "http://newcoco.twoday.net/";
  var blogTitle             = "newcoco";
  var postURL               = "http://newcoco.twoday.net/stories/2342992/";
  var postTitle             = "Another test story";
  var commentTextFieldName  = "content_text";
  var commentButtonName     = "save";
  var commentAuthorLoggedIn = true;
  var commentAuthor = "newcoco";
  var commentFormID         = "comment-form";
// ] ]></script>

(Example taken from our test blog over there.)

This code makes sure that coComment gets the correct information when capturing a comment.

If you are a twoday user and your template was customized, you can use the diff link to see where to insert the code.

Layout > Skins (HTML) > Change templates (HTML) > Comment editor (Comment.edit)

If you want all the comments on your blog to be captured (not just those of people using the bookmarklet or the Firefox/Flock extension), you need to add the following code in your template (just before or after):

<script id="cocomment-fetchlet" src="http://www.cocomment.com/js/
enabler.js"></script>

technorati tags:twoday, integration, cocomment, template, skin, code, integrate, knallgrau, blogplatform

Quite a few of you noticed problems between coComment and Flickr these last days:

• first, lots of HTML started showing up in comment RSS feeds
• then, people using the extension got ‘unresponsive script’ errors when they were visiting the Flickr website.

The Art of coComment requires us to do quite a bit of ad hoc parsing, and some changes Flickr made to their templates caused our parsers to choke. We’re happy to say that both problems have now been fixed. Our apologies for the inconvenience this may have caused some of you.

technorati tags:cocomment, flickr, problem, solution, script, template, resolved

A bit over a week ago, Lee Hopkins, an early coComment adopter, reported that coComment had stopped tracking his conversations.

The very next day, Christophe was at it to try and find what was going on. He quickly noticed that Lee wasn’t in fact logged into the coComment server (although Lee had been logging in as asked). Finally the problem was narrowed down to a cookie setting in ZoneAlarm, a popular Windows firewall that Lee was using. (The details of the one-on-one troubleshooting that went on behind the scenes have not been disclosed, so that part of the story will be left to your imagination.)

So, if coComment seems to have stopped tracking your comments, and you are using ZoneAlarm, click the Site List tab in ZoneAlarm and check the “3rd party” cookie control for cocomment.com:

That should do it! Let us know if this was useful for you.

Disclaimer: I don’t have ZoneAlarm, so if you have trouble finding the screen depicted here, ask in the comments and we’ll get more precise explanations for you. Thanks to Lee for the screenshot.

technorati tags:cocomment, zonealarm, cookie, troubleshooting, solution, thirdparty, tracking