James

I’d like to know about this too, a friend keeps getting caught by the spam filter, and I’d like to take him off somehow.

BRILLIANT work clowny

Thank You! ??

(I found it around line 239)

OK, now I have no idea what went wrong, I just tried altering the settings and I’m getting the error again. It was working fine last night. I get the threaded comments and everything, but no changing the settings.

The only editing I did was to the briansthreadedcomments.php CSS section, and changed a couple colors around.

Alright, I did it and everything’s working fine, so thanks for all the help again, haochi ??

Now I have a new issue, the comments look plain, I know this will probably require custom coding, but is there any way I could apply my theme’s colors, styles, etc. to the new comments.php page?

I’m not very familiar with php, so I’m not sure just how much work needs to go into applying everything to the new format.

Thanks for all the help so far, haochi :).

I did notice that extra comments.php file, but I wasn’t sure what to do with it. I did everything up to step 2 so far.

I just wanted to make sure I do this right. So do I *replace* my current comments.php file with the one the plugin provides? Or do I take the code and insert it into my current php file? I’m still a little confused about this part…

I looked at the install.txt file that came with the plugin, but it didn’t say anything about hard editing the comments.php file.

Was it somewhere else?

So is it just not “completely compatible” with 2.5 then? We’re stuck with the one setting it provides?

It still displays the archives and everything, but the settings don’t work, so your stuck with the default displays.

Also, I didn’t see it on the list of non-compatible plugins.

I’m having the same problem, and no one seems to know what is wrong with it.

Still nothing?

Would I have gotten more help if I posted this in the plugin section? If so, could a mod please move it there?

Nope, I couldn’t find anything. I have NO IDEA what’s causing this problem.

I’m having a similar problem, whenever I try upgrading my plugins, I get the error as posted above, it mentions the error right after “Unpacking the update”. I’ve deactivated them, tried automatically upgrading then, and still nothing for the plugins (I get the same error).

I did look at the list however I couldn’t find the plugin I’m using (SRG Archives) on the non-compatible portion of the list.

Would other plugins we have installed cause this specific plugin (SRG) to not work properly too?

If so, I’ll relook at it and see what could potentially be causing the problem then.

And if we’re not using it?………

And where do we find that? As I said, I never installed that plugin manually.