fusse

Now that was fast ?? I grabbed your updated version, installed and tested in my environment. Works like a charm so far.

Job well done sir! ??

So therefore: resolved!

tmpComment = tmpComment.replace( /<p class=”reply”>(.*?)<\/p>/, ” );
this after the depth-1 replace. don’t know how “good” this is but no errors and works and that’s fine with me in this case.

Anyways, this is still a stellar plugin even with them little hiccups ?? Keep up the good work!

I already have that setting enabled in Discussion… ??

I managed to fix my issue with replacing the depth-1 with depth-2 in the tmpComment – kinda what you did in your example but I did it here:
if(jQuery(‘#’+css_respond).parent().children(‘.children’).length) {
// There are replies, add comment to the end of the list
tmpComment = data.replace( ‘depth-1’, ‘depth-2’ );

and here:

tmpComment = data.replace( ‘depth-1’, ‘depth-2’ );
tmpComment = ‘<ul class=”children”>’+tmpComment+”;

I only use depth-2 and no deeper so it works for me. Now I just need to replace/strip away the Reply link from tmpComment depth-2 comment as that doesn’t apply to my site.

I tried your fix though and noticed that it doesn’t quite work still: when replying to first level comment, if there are replies that are depth-2 already, the reply gets depth-3 instead of depth-2 which it should be getting as it was a reply to the original depth-1 comment.

Okay nice! Thanks. I didn’t take too much time to look into the plugin itself. I guess, since the official fix ain’t coming soon, I will take a look myself and try to fix it.

Yes. Everything else is as it should apart from the class issue (not getting the depth-2 but depth-1). And page reload fixes this: so the data put to database is correct.

Tried. No change.

Thanks! Like I said in the beginning, if I disable the callback from the plugin options and make it use the wordpress default list comments (also disable the callback in comments.php), it will set the correct class and the reply message will be indented but then it of course looks wrong otherwise as it has different html layout.

Yea I had it like that before and forgot to change it back. (I tried that to see if it had any effect but it didn’t work).

So anyway, the change you made doesn’t affect the outcome at all. I can’t figure it out but the problem is that the reply is not getting the correct class. Don’t know why though…

https://gist.github.com/2299472

Update on my situation: We switched from iPower shared to a new VPS server (Knownhost) couple months ago. After the switch we haven’t encountered this issue once.

We switched to a new server just recently (from iPower, which we hated for many reasons and were relieved to switch from their shared and VPS hosting to a new much better host) and will have to see if we encounter this problem again with our new setup.

Compare the plugins with what?

I have already ruled out the plugins… none of them have any code to trigger comment_status to closed on all the database entries.
Only have one site that this is happening on.

Server OS Debian (dont know the version)
SERVER_SOFTWARE Apache/2
PHP 5.2.12