When I try to add comment and I have FCK enabled, I get "Comment field is required." validation error. When I disable editor, everything works ok.
BTW, version 1.7 doesn't work at all for me (you press 'Submit' button on comment form and nothing happens)
I can provide testing account on the website with the problem if it can help you.

Comments

jcmarco’s picture

I have the same problem using FCKEditor

Sending a second comment you always get this error:

Comment field is required.

novovox’s picture

Same problem. Anyone?

hadsie’s picture

tried this with the latest version of the module and comment_bonus_api but getting the same error

vb’s picture

CKeditor 3.1 - the same issue.

psampaz’s picture

#4: same for me too

Captain Flint’s picture

Same for me too

petermilad’s picture

Same thing. me too!
I have no WYSIWYGs at all, no CK, no FCK, NOTHING!

darthf1’s picture

Are you working with the WYSIWYG API, or the FCKeditor module? Because the WYSIWYG API with FCKEditor gives the above error. But when you use the FCKeditor module (http://drupal.org/project/fckeditor) it works fine (for me).

Samsoe’s picture

I have this problem too after I change theme. But only when i try to submit comment as admin, no problem for authenticated user. And.. I'm using FCKeditor Module.

EDIT>
I just tried to change admin to use authenticated user FCKeditor profile (Drupal Basic) and now it works. It should be FCKeditor problem.

Fidelix’s picture

Priority: Normal » Critical

Any news on this?
The module is unusable, so i'm setting this to critical.

I tried CKeditor (standalone) and CKEditor with the WYSIWIG module. Everything is the newer version (not dev).
Comments cannot be posted.

VVS’s picture

Аналогично: при использовании CKEditor выводит "Поле комментария обязательно для заполнения."

DontBlink’s picture

same problem. please, the owner of this module, fix it fast as possible..

rjbrown99’s picture

Priority: Critical » Normal

Hello. I have been added as a co-maintainer of the module. A few comments -

1) Please move to the latest -dev release first. I'm not looking at anything before that as there were a number of bugs fixed from other issues in the queue. The latest dev as of this writing did not address CKEditor or FCKeditor but it did fix a bunch of other things that may or may not play into this.

2) This seems to be related to the following issue: #784504: Support for CKEditor. Is this a duplicate? Have you tried any of the patches from that issue, specifically #15?

3) What modules are we talking about here? fckeditor? wysiwyg? Are we dealing with the FCKeditor or CKeditor? Additional specifics could help, but again please try -dev and the patches from the above issue first.

4) I'm marking the priority as normal. It may be unusable with the FCKeditor, but it is usable in its default state with the default textarea forms. The issue is with integration with a third-party module. I'm also thinking this is a dupe of the other issue.

5) I only speak English, so I can't review anything posted in a different language :)

Fidelix’s picture

I tried DEV. No success.

It does indeed seem to be a duplicate of #784504: Support for CKEditor, however, "Name field is required." is the field being required, but i guess the problem is the same.

I tried all the patches there, without success...

yngens’s picture

Title: FCKeditor 2.6.4 in comments - "Comment field is required." error » "Comment field is required." error

I am not using any kind of wisywig editors and still having this issue. So it is not necessarily about FCK or the editors, but the module itself or how it interacts with some other modules.

yngens’s picture

changing to bluemarine solved the issue, so i guess the problem could be the theme templates, if this helps anyone.

huzooka’s picture

Status: Active » Needs review

At me, flushing the drupal's cache at settings/performance solved the problem.
Thank you for your comments:) Please someone check it, maybe it helps.

rjbrown99’s picture

Status: Needs review » Active

The "needs review" status is only applicable if patches are attached to the issue. There is no patch to review, so I am setting the status back.

garyjohn_2000’s picture

Okay, using the latest -dev version of ajax_comments, comments_bonus_api, and ckEditor (not with the WYSIWYG module; its the standalone ckEditor module).

Page gets loaded, I can't type anything into the ckEditor. I've enabled previewing the comments, and soon as I click Preview, I get the "Comment field is required" error. But, the ckEditor editing area becomes available to typing now. I can type in, copy-paste text, everything works like silk. Subsequent clicks on Preview work like a bliss. Saving the comment works too, once I can feed some text into the ckEditor.

Something fishy, somewhere...gonna play around the ckEditor settings and Input Filters now, and might even take a look at the Preview button handler code, will report back if I find anything worth reporting.

rjbrown99’s picture

I'm not sure how into coding you are, but I did add a bunch of comments and documentation to the code in -dev. That may help in your troubleshooting.

TimG1’s picture

Hello everyone,

Getting same error. "Comment field required".

WYSIWYG-6.x-2.4
CKEditor 3.6.1.7072
Comments bonus API 6.x-1.x-dev (2011-Feb-25)
AJAX Comments 6.x-1.x-dev (2011-Feb-25)
Pressflow Drupal 6.x-22

Thanks for reading,
-Tim

jazzdee’s picture

Hello everyone,

Getting same error. "Comment field required".

WYSIWYG-6.x-2.4
CKEditor 3.6.1.7072
Comments bonus API 6.x-1.x-dev (2011-Feb-25)
AJAX Comments 6.x-1.x-dev (2011-Feb-25)
Pressflow Drupal 6.x-22

Thanks for reading,
-Tim

exactly the same for me!

igorik’s picture

same problem, latest ajax comment + comment bonus api, + wysiwyg + ckeditor.
using zen theme

I disable this module after I found this, and based on this issue (3 years old)
when it looks like nobody is interested in fixing this.

drupalok’s picture

kind of a work-around is to set the text format for the text field to plain text

admin/structure/types/manage/[contentType]/comment/fields/comment_body

still this should be fixed... its such a great module...

rjbrown99’s picture

I am still a module maintainer, and I am not facing this issue myself and I do not have time to debug or fix it. If a patch is posted to this issue and is tested by some of the folks here, I'd be happy to roll the fix into the tree and issue a new release. Otherwise until it impacts someone with a development background that is bothered by it enough to create the patch, unfortunately it will remain broken.

michiellucas’s picture

Not working!

Is anyone working on this issue?

rjbrown99’s picture

#27 please read #26. It answers your question.

florisla’s picture

I'm encountering this error too, on FCKeditor.module version 6.x-2.1 .

Noticed two oddities:

  1. The error occurs when using Firefox, but not when using Chromium
  2. When loading the edit form, a JavaScript error occurs: NotFoundError: Node was not found (in file modules/fckeditor/fckeditor/editor/js/fckeditorcode_gecko.js) Since gecko is the rendering engine of Firefox, this seems to indicate the problem is located there.

I'm going to upgrade both FCKeditor.module and FCKeditor itself and will report my findings here when done.

florisla’s picture

The error I experienced above (#29) was not ajax_comments related, but instead it was this: http://drupal.org/node/1770728 . Switching to ckeditor helps :-)

fan777’s picture

FCKeditor -> Default (<- for example) -> Cleanup and output ->Enter mode: -> Set to "<\br>". It solved the problem for me. The Default value of this field is set to "<\ p>" and FCKeditor cuts a comment.

SomebodySysop’s picture

Just a note that (#31) also fixed this for me.

mariar’s picture

31 work for me...

emilymoi’s picture

FYI, I had this issue with the D7 version of ajax comments. I was using version 2.1 of the wysiwyg module. I updated my wysiwyg module to 2.2 (latest as of today) and the problem went away.

tassaf’s picture

No solution for this problem till now?

qzmenko’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

Issue is closed because 6.x version is unsupported. Feel free to open new issue for 7.x or 8.x versions of module.