Thread

Greg, it’s all up to date. And I’ve mentioned previously about testing this on both versions.

I’m getting really tired of all this back and forth. I need someone who can help me solve this problem. This isn’t directed at you, Greg, I’m just frustrated at this lengthy support process that is essentially just going around and around with different voices and no real traction.

Hi David,

My apologies, it wasn’t clear that you were already running version 2.1.3 from your last post:

I am currently running the 2.1.1 version because it’s less buggy for my client in other areas, but I can switch to 2.1.3 if needed.

I know that you’ve mentioned that comments are enabled but can you please confirm that the “Require membership in order to post comments?” preference for this channel is also set to ‘No’?

Cheers

Greg

Greg, yeah, it wasn’t on 2.1.3 but it is now.

The setting you asked about is set to No. Here’s a snap of my channel prefs, just so it’s perfectly clear.

http://imgur.com/u97jO

Hi Michael,

Can you please confirm whether moving the comments out of the channel entries tag worked for you?

Thank you.

I’ve just updated to the latest build, and I am getting that same error when trying to post a comment:

Fatal error: Call to undefined method CI_Security::secure_forms_check() in /Sites/site/ee-system/expressionengine/modules/comment/mod.comment.php on line 2647

I tried it with the comment form from the docs as well.

Hi Trevor,

I’ve been able to replicate this error so have submitted a bug report. Please follow that report for updates.

Cheers

Greg

Hi Greg,

I updated my site to 2.1.3 with the faulty April 7th build. Now when I try to update the site again, I get a blank white page. What are my options here, to update to the latest version? Comments aren’t working on my site (see comment #19), and I need to get it working ASAP.

I replaced modules/comment/ with the April 12th build, but that doesn’t fix the problem.

arilyn,

Update your whole EE site to the 20110411 build not just one module. Then see if issue persists

That fixed it, thanks.

Glad to hear it. Feel free to start a new thread if you have any more questions.