Over the next couple of weeks Blogger will gradually roll out redirects to country-code URL’s (or ccTLD’s) for all Blogger sites. Per Blogger’s support page:

If you’re in Australia and viewing [blogname].blogspot.com, you might be redirected [blogname].blogspot.com.au. A ccTLD, when it appears, corresponds with the country of the reader’s current location.

This update will unfortunately cause a major issue with our Blogger Widget installation, where the same post will show different sets of comments depending on which ccTLD your readers visit.

The good news is that Blogger sites using our Template installation are all set and will not be affected by this change. You don’t have to do anything, so kick back and relax.

The not-so-good news is that if you are using our Blogger Widget installation, you will need to switch over to our Template installation to ensure that everything runs smoothly. It really is essential that you do this. If it weren’t, we wouldn’t bother you. Don’t worry, we’re here to help and we hope to make this as painless as possible.

Please note:

• You won’t lose any of your existing comments if you follow the instructions below.
• Custom domains are not affected by this change. However, we would ideally like to discontinue our Widget installation. The Template install is much more stable, and future backend updates will most likely only apply for Template installations. We realize that it’s a pain, but it will be worth it in the long run.

Here’s how you can switch over to the Template installation:

1. You will first need to uninstall the Widget from your site. The following instructions are for the updated Blogger interface. If you are using the old Blogger interface, please switch over to the new interface temporarily. You can do that by selecting the “Try the updated Blogger interface” link at the top of your Blogger dashboard.

 

2. Go to your Blogger account and find the blog that you have the IntenseDebate Widget installed on in your blogs list. Click the down arrow, then click Layout.

   

 

3. Locate IntenseDebate in the sidebar and click the Edit link.

   

 

4. Select Remove from the edit screen, then select the orange Save arrangement button at the top of the page.

   

 

5. Next your will need to reinstall IntenseDebate using the Template installation method. To do that go to your Blog Tools tab in your IntenseDebate account. Select Reinstall and follow the installation instructions. You should be all set.

 

6. If you want to switch back to the old Blogger interface, click on the little gear symbol on the right side of the page below your profile picture. Then select the option to switch to the “Old Blogger interface” and you’ll be all set.

Again, we’re here to help. If you come across any issues, you can contact us here. Make sure you include the URL of your blog when you contact us.

We apologize for the inconvenience and appreciate your understanding. For more information about Blogger’s ccTLD redirect change please check out their support documentation here.

Posted by Michael Koenig in Blogger,News

Let’s face it, spam happens. While we’ve made a lot of improvements to our Akismet integration to catch future spam from sullying your comments with links to cheap prescription drugs, it’s possible that some spam might have slipped through in the past.

Don’t worry, we’ve got you covered.

There’s a nifty new option in your moderation page to re-check all of your approved comments for spam with the click of a button.

Just click on the “Re-check For Spam” button and we’ll do the heavy lifting for you, and run all of the comments on your site through Akismet again.

Think of all of the time that will save you. While we do that, you can take some time away from your computer and slow things down. Go relax with a beverage and rest your eyes for a bit. You can read an old-fashioned newspaper (you know, the kind that you can tear), or catch-up with a long-lost friend – after all, IntenseDebate is all about connecting people. 😉

When you get back, head over to your moderation page again. If we’ve found any spam, there will be a notification waiting for you. If there isn’t one, then your site is spam free.

Keep in mind that the more comments you have, the longer it will take for us to re-check them all. If you return to your moderation page while we’re still checking, then the “Re-check For Spam” button will be greyed-out and inactive.

You can learn more about the rest of our moderation tools at support.intensedebate.com/moderation and read our past posts on our moderation options here.

Posted by Michael Koenig in features

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