Comment Relish Back in Action

Published July 17th by Ben in Blog Optimization 6

Well, after a day of errors and asking for some help, I’ve finally been able to activate Comment Relish once again. Apparently the original plugin was called every time a page loaded. Not only would that put a pretty decent load on the server, but once it hit an error, it would return the “Email not sent” error message every time any page tried to load. Before you start being impressed with me, you should know I don’t deserve any of the credit. Patchlog.com figured out the fix and has in fact released a new optimized version. If you’ve had any problems with the plugin or just want to be safe rather than sorry, I’d suggest using this new version.

Thanks Patchlog!

P.S. For those of you who have had problems with the original version of Comment Relish, here’s the fix for it. I hope it helps!

TAGS:

Comments

MichelleVan August 1st, 2007

Perfect. on my way to download it now.
You might want to put this fix as a trackback to the comment relish blog where I found you. Probably bring you a bit of traffic.

Thanks bunches.
MichelleVan August 1st, 2007

I just put the link to your post on the blog mastermind forum. I hope you get some hits…:)
Blogging Experiment August 1st, 2007

Great idea Michelle! I’ve added the trackback to this post.

Glad I could be of some help and thanks a ton for the link!
MichelleVan August 1st, 2007

I give up. it crashed again, I tried emailing you but my email came back. Any ideas? (
Blogging Experiment August 1st, 2007

hmm, you might want to check with your host and explain to them what’s going on and pass along the code for the plugin that’s crashing.

I’m not sure why your email bounced… I just tested it on my end and I’m still receiving it. BlogEx [at] bloggingexperiment.com right?
Melissa Cleaver April 11th, 2010

I’m trying to use this plugin, but all I ever get when I configure it is the “You do not have sufficient permissions to access this page” error. I’ve scoured the internet looking for a fix, but nobody seems to have one even though a ton of people are having this problem. This is the only plugin that I’ve ever encountered this error message with. Can you please help? Thanks!