Just a quick note. If you are using our Facebook Connect integration, please update your Facebook Connect API Key in your Comment Settings and use your Facebook APP ID instead.

Complete instructions are available in your Comment Settings page, and you can access your Facebook APP ID at https://developers.facebook.com/apps.

You may need to clear your browser cookies and cache when you’re done. We have some great instructions on how to do that here.

That should do the trick! Feel free to leave a comment with any questions about this change.

———
Update – If Facebook Connect still doesn’t work after you update your API Key to use your APP ID, then it’s likely that you will need to refresh cache for your comments. The easiest way to do that is to post a new comment and that should force the cache to refresh.

Posted by Michael Koenig in News

It’s been way too long since we last updated our blog – our apologies for the radio silence. I wanted to share a handy bit of CSS to help you further customize the way your readers can post comments to your site. While we offer a couple of different ways to comment – as a guest or using their Facebook, Twitter, WordPress.com, or IntenseDebate account – there wasn’t a way to disable guest commenting while still enabling Facebook Connect and Twitter Sign-in.

But, as you may know, we offer a super-easy way to add custom CSS to bring your own personal style to IntenseDebate through your Custom CSS page. By adding a handy snippet of CSS, you can hide the guest commenter information fields (Name, Email, URL), which will effectively remove the option to post comments as a guest.

Why is this cool?

I’m glad you asked. Currently commenters that post using Facebook Connect and Twitter Sign-in are considered guest commenters since they aren’t posting with an IntenseDebate or WordPress.com account. The issue is that if you disable guest commenting in your moderation settings by requiring readers to have an IntenseDebate or WordPress.com account, you would remove the options to post using Facebook Connect and Twitter Sign-in, which isn’t ideal.

So without further ado, here’s the CSS you can add to your Custom CSS page to get rid of guest commenting:

#idc-container-parent #idc-container .idc-postnav-label,
#idc-container-parent #idc-container .idc-c-m.idc-signup {
display: none !important;
}
#idc-container-parent #idc-container
.idc-postnav-list {
margin: 5px 0 8px;
}

That last little bit adjusts the margin to make up for the hidden fields so there isn’t a gaping space where the guest commenter fields used to be. Feel free to tweak that as you’d like.

Make sure you check out our CSS documentation, along with the rest of our guides to change the font size; text, background, and link colors; width of the comment section; and move the comment box to the top of the comment section.

Posted by Michael Koenig in features

Update 1-31-11: Upgrade complete! If you were running CommentLuv on your blog, then the plugin will automatically be reactivated. Thanks for your patience!

–

Update 1-28-11: You can add a URL field for Guest commenters in the comment form by enabling the option in your Comment Settings. Make sure you disable CommentLuv in your Plugins page to ensure that the URL field shows up properly.

We will have this updated and back in action soon! We appreciate your patience.

–

Howdy! It’s time for an upgrade to the IntenseDebate CommentLuv plugin.

We have temporarily deactivated CommentLuv on IntenseDebate while we change the tapes and switch over to the new version.

We will post a status update once the new version is installed. Our apologies for the inconvenience.

Posted by Michael Koenig in features,News

Time for an update folks! Version 2.9 of our WordPress plugin includes some great performance optimizations and other fixes:

• Better local sync queue management for faster, more reliable syncing
• Better option management to reduce the number of queries generated by the plugin
• Improved mobile device support (the iPad now always loads IntenseDebate and ID works with the WPTouch theme)
• Better compatibility with WordPress 3.0 (and previous versions) running in WP_DEBUG mode (avoid deprecated functions etc)
• Some syncing fixes that make sure your WordPress comments database matches the comments in IntenseDebate

Please note that this version REQUIRES WordPress 2.8 or higher (and has been tested all the way up to the latest 3.0.1). If you are running a version of WordPress below 2.8, we have NOT tested this version, and it’s likely not to work. Hey, it’s time to upgrade that thing!

We strongly recommend that you update to this version of the plugin as soon as it appears in your WordPress admin panel as it provides some great performance improvements. If you don’t have IntenseDebate installed yet, or would rather update manually, jump on over to our WordPress.org plugins directory page and grab a copy now.

Posted by Beau Lebens in WordPress Plugin

We released a cool new setting for reported comments (comments that your readers flag as inappropriate). You can now opt to have the comments automatically put into moderation for review. This handy option can help you and your readers keep your comments clean and debates friendly.

To enable this option, visit your Comments Settings, and check the box next to Send comments to moderation when reported (located at the bottom of the page). Make sure you save your settings. This setting excludes comments posted by site admins and moderators, as well as comments that you have already approved.

While you’re there you can also take advantage of our Auto-Delete setting for reported comments. With the Auto-Delete option, you can set a maximum number of times that a comment is reported before the comment is deleted. This is another super-handy feature for crowdsourcing moderation.

Both of these options are based entirely on your feedback, and we’re happy to deliver them!

Posted by Michael Koenig in features