[BinaryAccepted]

After searching your forum regarding the following error :

Sorry but 1 error was found when processing your comment.

Please correct this error and submit the form again:

• The comment entered has already been submitted. Please submit a new comment.

I located the thread :

http://www.commentics.org/forum/showthread.php?tid=320

that was last replied to 07-Sep-2011, 09:05 PM

The issue at hand is still there and can not be removed unless I clear my sessions, cookies, history, ect.

Even detected as an administrator the problem does not become resolved.

Is there a fix or removal of code I can do myself since the issue does not seem to be of any importance to be removed?

Best regards,
Me.

[Steven]

Are you only getting this error when you delete the comment and try to post it again?

I'll work on a fix for it. In the meantime you could remove it by opening:

/comments/includes/app/processor.php

And comment out this line:

PHP Code:

<?php 

cmtx_comment_resubmit($cmtx_comment); //check comment is new 

[BinaryAccepted]

Thank you for the quick fix. As for your inquiry. No, I receive the error regardless of what I do. I started deleting them when I began getting the error as I couldn't see any of the comments it was referring to through the database. I tried a few fixes that failed horribly then decided to preform a clean installation. To no avail I continue to have the issues.

[Steven]

The feature relies on a session to work. It may be because there is no session.

Did you add this at the very top of your page:

PHP Code:

<?php

session_start();

ob_start();

?>

[BinaryAccepted]

The session start is indeed added to the in the beginning of the index. If you want to examine it I can give you restricted access to the directory its located in and export the sql so you can examine it. I may have done something wrong which is very likely. Just let me know and I'll respond accordingly.

[starchild]

I get this same bug.

The comment out works for now, but a fix would be great.

Am using 2.1

[Steven]

It's fixed in the next version, v2.2.