Jon's dashboard

A comment on the question "commentluv" in IntenseDebate:

Looks great – Jon, on October 21, 2009 11:40

Jon replied on October 07, 2009 20:36 to the problem "Comments appearing on wrong post" in IntenseDebate:

From looking at the JS for our IntenseDebate comment section that your blog is outputting it appears that your posts don't have proper guids or the guid is not being properly output. This unforunately has the side effect of not having unique identifiers for your posts which is causing the same comment section to be loaded in multiple pages.

It's possible there is something wrong with your WordPress install or that another plugin/theme is conflicting. You should be able to resolve this by either resolving the conflict (finding out which other theme/plugin is messing up the post guid) or by editing the IntenseDebate plugin to remove the "&guid=" from the script src.

I know this is a little messy, and I apologize, but it's sort of the nature of the beast in this case.

Jon replied on October 07, 2009 15:06 to the question "Comment shows in widget, but not on page" in IntenseDebate:

We had a bad cache that prevented the other comment from being shown. I've cleared your cache and the other comment displays correctly now.

Sorry for the trouble.

Jon replied on October 06, 2009 15:27 to the question "What variables can I get from a logged in user?" in IntenseDebate:

Try checking the JS var:
commentObj.curUser.trueUsername

Which should give you the current logged in user's username.

Jon replied on October 06, 2009 15:20 to the question "Insert code snippets with proper indentation?" in IntenseDebate:

Unfortunately at this time we don't support any kind of syntax highlighting or code formatting. We do allow for use of the

(blockquote) tag which might be useful for this.

Jon replied on October 02, 2009 15:26 to the question "Plugin code fails - need to see plugin examples in action/live" in IntenseDebate:

Sure. We offer an IntenseDebate function to help with loading external scripts that isn't yet in the documentation (trying to catch it up, but not there yet).

IDC.load_js('http://domain.com/script.js');

This will simplify the loading a little bit.

As for making sure it's loaded, you have a couple possible options. If you control the external JS then you can add a callback function to the end of the remote JS to trigger whatever JS you want to run when it has loaded.

You could also define a variable in the external JS and then have the dependent JS check for that variable before running (setting a timeout function to recheck later if it's not fully loaded).

Or, one last possibility would be to just put the initial load in an earlier event (the first load event loads JS and the second funcs one calls it for example). This last approach doesn't guarantee successful load, but will probably work in 99% of all cases anyways.

Hope this helps.

Jon replied on September 30, 2009 18:14 to the question "Footer text no longer parsing HTML?" in IntenseDebate:

Ah, sorry about that. I believe I've fixed that as well. Sorry for the trouble.

Jon replied on September 30, 2009 14:25 to the question "Footer text no longer parsing HTML?" in IntenseDebate:

Yes, but by accident. When we released the update to the settings page we accidentally blocked HTML parsing. I've corrected this now and apologize for the trouble. You'll have to resave your HTML on the settings page for it to parse correctly.

Thanks for bringing this to our attention.

A comment on the question "Plugin code fails - need to see plugin examples in action/live" in IntenseDebate:

Sorry for the confusion. You can activate any of those example plugins (or any of our plugins) by going to our plugins directory (http://intensedebate.com/plugins). This will allow you to add any of them to your site so that you can see them in action. It will also include all the plugin JS in our script so that you can take a look at the raw source.

I'll try to take a look and see if I can tell where the plugin you mentioned is out of sync with the actual plugin code. Do you happen to know where the syntax error is? That might be helpful...it's probably just an error in converting it to the documentation.

Sorry for the trouble – Jon, on September 28, 2009 20:21

Jon replied on September 25, 2009 17:05 to the question "Plugin code fails - need to see plugin examples in action/live" in IntenseDebate:

I'm not sure I follow exactly what you mean. You can try adding custom plugin code to any site you're an admin on by going to the plugin editor (http://intensedebate.com/pluginEditor). Is this what you're looking for or have I misunderstood the question?

Thanks.

Jon replied on September 21, 2009 03:26 to the question "Intensedebate -> Facebook Connect -> incorrect website redirect" in IntenseDebate:

Yes, it does seem odd.

Is there a public URL I could take a look at to see if I can find anything that might be causing it? It's possible it's just a bad cache or stale data from the old URL, but it would be helpful to be able to try it if that's possible.

Thanks.

Jon replied on September 21, 2009 01:00 to the question "Intensedebate -> Facebook Connect -> incorrect website redirect" in IntenseDebate:

Please double check your FB application settings. In particular, under the connect tab make sure you have the correct Connect URL and Base Domain. On the IntenseDebate side, please make sure you have the proper Blog URL set. This is found on the settings page after selecting the correct site from the "Sites" drop down at the top of the page.

If these are both set correctly (to the new domain) or if this doesn't correct the issue please let me know.

Hope this helps.

Jon replied on September 11, 2009 22:25 to the question "Comments not showing up in blogger site! HELP! :-(" in IntenseDebate:

I think most of your concerns can be fixed by simply using our generic JS install code instead of the Blogger widget. The Blogger widget is a lot easier to setup, but doesn't really allow for much customization unfortunately.

The generic method is basically just a couple of lines of JS you can drop on to your page instead. You can find the code for your blog here:
http://intensedebate.com/update/gener...

The top block of code will generate the comment section wherever you put it (inline, not in an iframe, and loaded automatically - not behind a comment link) and the second one will generate the comment link (with the comment count). I should mention that we only allow one full comment section to be loaded on a page at the same time. So if you have several posts displayed at the same time you should use the comment link code instead (and have that open the comment section). From your link it didn't look like you have more than one post on a page, but I wanted to mention it in case you run into that.

Hope this helps!

Jon replied on September 04, 2009 19:07 to the question "Wrong comments -- definitive proof right here" in IntenseDebate:

It should have always been required, but we aren't giving a proper error message. It won't always fail. In fact, it will probably work a lot of times without it, but we will have mixups and bad results sometimes without it.

Again, I apologize for this error on our part. It was a bug and I take full responsibility for it. Thanks for bringing it to our attention.

Jon replied on September 03, 2009 03:47 to the question "Wrong comments -- definitive proof right here" in IntenseDebate:

It appears you're using a custom function to add our javascript (IDebate) which is then passing in an empty url parameter
idcomments_post_id = idPassed;
idcomments_post_title = titlePassed;
idcomments_post_url= "";
var commentScript = document.createElement("script");
commentScript.type = "text/javascript";
commentScript.src = "http://www.intensedebate.com/js/getCommentLink.php?acct="+idcomments_acct+"&postid="+idcomments_post_id+"&posturl="+idcomments_post_url+"&posttitle="+idcomments_post_title;

As I said above, we should have a better response for this indicating the error, and that is definitely a problem on our end, but this is why you're getting a different number of comments back. I'll be sure to get this corrected and I apologize for the trouble.

Jon replied on September 03, 2009 03:25 to the question "Wrong comments -- definitive proof right here" in IntenseDebate:

There must be a bug or an error in our JavaScript then. Would you mind giving me an example or two of where this is happening so that I can take a look and try to get to the bottom of it? I apologize for the inconvenience.

Jon replied on September 03, 2009 03:04 to the question "Wrong comments -- definitive proof right here" in IntenseDebate:

Sorry, I guess that wasn't very clear.

I mean the actual url sent in the request is bad. The parameter:
"&posturl=&posttitle=" it should be passing the location.href value by default if you don't provide a value in the JS. Because this value is invalid though we're actually just loading the first post in your account in its place. I admit this is not how it should work. Instead of returning the wrong post we should just error out and give you an error message. I intend to fix that and apologize for the bug.

Jon replied on September 03, 2009 02:43 to the question "Wrong comments -- definitive proof right here" in IntenseDebate:

Your example above is not passing a valid url in the request. Because of this you're getting junk back (you'll get 2 comments for just about any postid if you try it).

We should handle this better and give a proper error message. I'll be sure to do that, but that is why you're getting bad data back out.

Jon set one of Jon's replies as an official response to "change.gov comments don't expand" in IntenseDebate

Jon replied on September 02, 2009 06:03 to the problem "change.gov comments don't expand" in IntenseDebate:

Thanks for pointing that out. It should be fixed now.

Sorry for the trouble.