Wrong comments -- definitive proof right here

What, precisely, is wrong with the GET URL? This worked for months.

FYI, the system should never send "bad data back". The correct response is "No Comments" because that postid has, in fact, no comments.

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.

The URL is copied straight from FireBug, This is what YOUR Javascript is requesting to YOUR server.

In other words, I don't create this URL, the I.D.-injected javascript does

Still wondering what changed, and what ID is expecting. Nothing changed on this-end, and there's a raft of folks complaining about this problem....

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.

OK. But I can only leave this in the error-state for a couple of hours, OK? Starting right now.

http://k7waterfront.org/

I've enabled comments on the THIRD, FOURTH and FIFTH ITEMS DOWN, the one with the 7-days of sunny weather forecast. Scroll. See it?

Observe: "Comments (2)"

Should be" "No Comments" on all.

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.

OK, thanks, fixed that, have a look: Comments all-enabled now.

http://k7waterfront.org/

Problem: Comments (2) on postid 4042 -- August 28 2009 in fact belong on postid 4030 -- August 7 2009, the very last item on that page.

In other words, still getting wrong comment-count allocation among items.

Also, parenthetically, when did idcomments_post_url become a required (non-blank) parameter? Is that a bug too? I think it should be a bug since the postid uniquely identifies the post.

Just sayin'...

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.