My Findings on coComment and Movable Type 3.2 Integration

coComment

After 12-hours or so of usage and debug­ging my MT tem­plates to prop­erly inte­grate with coCom­ment, I finally got some­where to say the least. If you need to catchup to what this is all about, you may read my pre­vi­ous arti­cle on what coCom­ment can do.

Any­ways, I finally got around fix­ing my Indi­vid­ual Entry Archive tem­plate. I did the following:

  • I for­mat­ted the TITLE-tag as stated in coComment’s Sup­port sec­tion,
  • fixed my old MT2.661 JS comment-related code to use the mt-site.js pro­vided on MT3.2,
  • and edited my CSS to reflect the change I have done with respect to the mt-site.js

Thing is, now I’ll have to fix the cookie part. It should be sim­ple. I think I just need to change the com­ment form’s vari­able to match that of mt-site.js. Then, match those changes in my CSS.

One other issue I found through this lit­tle exper­i­ment was that coCom­ment looks for the default markup in terms of the sub­mit but­ton. That is,

<input type="submit" accesskey="s" name="post" id="comment-post" value="Post" />

So keep that in mind for those of you who just cut-and-pasted your MT2.661 code dur­ing your upgrade to MT3.2. It’s just too bad that we can’t use our cus­tom image-buttons. So @Steph, if you are read­ing, could you please address this as well with the team =)

Also, place­ment of the coCom­ment JS code in the header is tricky and strict. I was try­ing to fig­ure out why the heck it wasn’t work­ing when I went on to try JS place­ment. I ended with the following:

&hellip;
<script type="text/javascript" src="<$MTBlogURL$>js/general.js"></script>
<script type="text/javascript" src="<$MTBlogURL$>js/mt-site.js"></script>
<MTIfCommentsAccepted>
<script type="text/javascript">
<!&#8212;
window.onload = function() {
individualArchivesOnLoad(commenter_name);
}

// coComment entry-specific variables
var postURL = "<$MTEntryPermalink$>";
var postTitle = "<$MTEntryTitle smarty_pants="1"$>";
//&#8212;>
</script>
</MTIfCommentsAccepted>
</head>

Last but not least, how do we tag key­words with mul­ti­ple words? I tried sep­a­rat­ing with com­mas, using double-quotes and plus-sign but to no avail. If you know, let me know. Help me, help you.

Other than that, coComment’s cur­rent ver­sion is rock solid of a tool for blog­gers. Enjoy!

4 Comments

Comments Feed
  1. Steph

    Read­ing you, but I’m not quite sure I get the prob­lem. Could you explain the prob­lem with your cus­tom image-buttons a bit more clearly for me? Thanks :-)

  2. sherwin

    @Steph: I made a test-page with my pre­vi­ous tem­plate includ­ing the cus­tom image-button for “Post” on the com­ment form. You may click here to go to the test-page itself.

    Note: I have dis­able the form’s action. But that shouldn’t be a prob­lem. You shouldn’t be able to see coComment’s over­lay next to the “Post” button.

    PS. Any­way to tag multi-keywords?

  3. Chris

    Regard­ing multi-keyword tags… How about “multi-keyword” or “multi_keyword”? Like you said, quotes and the plus don’t do the trick.

    Thank you for the test page with the image sub­mit but­ton prob­lem. I’ll try to get it to work there.

  4. sherwin

    NP Chris. Hope it all works out. It’ll add some value to those want­ing cus­tom but­tons on their search forms for sure. Thanks again!