#mt3.2

My Findings on coComment and Movable Type 3.2 Integration

· 4 Comments
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!

coComment Helps Us Remember What We’ve Said

· 9 Comments

I was actu­ally think­ing of some­thing like this. I was going to make it my first RoR project but that might just be to ambi­tious. Any­ways, plain and simple,

coCom­ment is the only ser­vice that allows you to enjoy the full poten­tial of blog com­ments on the web. Before coCom­ment, the blo­gos­phere was not a global con­ver­sa­tion, but tons of frag­mented, hard to fol­low, and untrack­able discussions.

Using coCom­ment, you can now keep track of what you have been com­ment­ing on, dis­play your com­ments on your blog, and see what is new in the dis­cus­sions you are par­tic­i­pat­ing in (if other users are also on coComment).

One con (at the moment), is that “users can only track com­ments from blog posts that they have actu­ally com­mented on, and only com­ments left by other cocom­ment users are shown.“1 But this was a day or so ago. I have to check the new ver­sion out myself as I’ve just signed up a few moments ago.

Along with their news yes­ter­day about ver­sion 0.4c being released, the team also men­tioned the fact that there is now a Fire­fox exten­sion for coCom­ments. This addi­tion, for sure, will make things a bit eas­ier than hav­ing to use a book­mar­let on the user’s com­puter.

There might be one small gripe though. As I was tak­ing a look at coComment’s Blog Inte­gra­tion sec­tion which lists which browsers and blog/CMS/site-platforms it sup­ported, I read that Mov­able Type blogs must have the fol­low­ing format,

<title>blog name : article title</title> or
<title>blog name | article title</title>

Oth­er­wise, the com­ment (in coCom­ment) will show up as “(untitled)”.

So, see­ing that, there might be an issue of hav­ing every­one involved have a stan­dard way of tem­plat­ing their TITLE-tags. I, for one, see this as a big thing (so it ain’t “small” after all). If this is true, and hasn’t been addressed in it’s next iter­a­tion, coCom­ment is pretty much forc­ing every­one to do “this and that.” Then again, we’ll see how this plays out with Micro­for­mats. So if you are listening/reading this oh-Lords-of-coComment, please do let us know. (Then again, I just signed up and haven’t got­ten to play around with coCom­ment that com­pletely yet.)

All in all, the ser­vice is prac­ti­cal and very use­ful for those that like to read and inter­act with dif­fer­ent blogs. It’s great for coCom­ment to have got­ten around and imple­mented some­thing use­ful to the mil­lions that are very involved with interblog-interactivity. In it’s cur­rent state of ver­sion 0.4c, I just can’t wait to see the other fea­tures it will have when it rolls out from “beta”. Pretty much, like all the other “Web 2.0″ application-sites. =)

Con­tinue read­ing →

  1. Michael Arring­ton, coCom­ment visit to Sil­i­con Val­ley [↩]