Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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
Comment #1
jcmarco CreditAttribution: jcmarco commentedI have the same problem using FCKEditor
Sending a second comment you always get this error:
Comment field is required.
Comment #2
novovox CreditAttribution: novovox commentedSame problem. Anyone?
Comment #3
hadsie CreditAttribution: hadsie commentedtried this with the latest version of the module and comment_bonus_api but getting the same error
Comment #4
vb CreditAttribution: vb commentedCKeditor 3.1 - the same issue.
Comment #5
psampaz CreditAttribution: psampaz commented#4: same for me too
Comment #6
Captain Flint CreditAttribution: Captain Flint commentedSame for me too
Comment #7
petermilad CreditAttribution: petermilad commentedSame thing. me too!
I have no WYSIWYGs at all, no CK, no FCK, NOTHING!
Comment #8
darthf1 CreditAttribution: darthf1 commentedAre 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).
Comment #9
Samsoe CreditAttribution: Samsoe commentedI 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.
Comment #10
Fidelix CreditAttribution: Fidelix commentedAny 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.
Comment #11
VVS CreditAttribution: VVS commentedАналогично: при использовании CKEditor выводит "Поле комментария обязательно для заполнения."
Comment #12
DontBlink CreditAttribution: DontBlink commentedsame problem. please, the owner of this module, fix it fast as possible..
Comment #13
rjbrown99 CreditAttribution: rjbrown99 commentedHello. 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 :)
Comment #14
Fidelix CreditAttribution: Fidelix commentedI 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...
Comment #16
yngens CreditAttribution: yngens commentedI 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.
Comment #17
yngens CreditAttribution: yngens commentedchanging to bluemarine solved the issue, so i guess the problem could be the theme templates, if this helps anyone.
Comment #18
huzookaAt me, flushing the drupal's cache at settings/performance solved the problem.
Thank you for your comments:) Please someone check it, maybe it helps.
Comment #19
rjbrown99 CreditAttribution: rjbrown99 commentedThe "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.
Comment #20
garyjohn_2000 CreditAttribution: garyjohn_2000 commentedOkay, 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.
Comment #21
rjbrown99 CreditAttribution: rjbrown99 commentedI'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.
Comment #22
TimG1 CreditAttribution: TimG1 commentedHello 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
Comment #23
jazzdee CreditAttribution: jazzdee commentedexactly the same for me!
Comment #24
igorik CreditAttribution: igorik commentedsame 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.
Comment #25
drupalok CreditAttribution: drupalok commentedkind 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...
Comment #26
rjbrown99 CreditAttribution: rjbrown99 commentedI 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.
Comment #27
michiellucas CreditAttribution: michiellucas commentedNot working!
Is anyone working on this issue?
Comment #28
rjbrown99 CreditAttribution: rjbrown99 commented#27 please read #26. It answers your question.
Comment #29
florisla CreditAttribution: florisla commentedI'm encountering this error too, on FCKeditor.module version 6.x-2.1 .
Noticed two oddities:
NotFoundError: Node was not found
(in filemodules/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.
Comment #30
florisla CreditAttribution: florisla commentedThe error I experienced above (#29) was not ajax_comments related, but instead it was this: http://drupal.org/node/1770728 . Switching to ckeditor helps :-)
Comment #31
fan777 CreditAttribution: fan777 commentedFCKeditor -> 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.
Comment #32
SomebodySysop CreditAttribution: SomebodySysop commentedJust a note that (#31) also fixed this for me.
Comment #33
mariar CreditAttribution: mariar commented31 work for me...
Comment #34
emilymoi CreditAttribution: emilymoi commentedFYI, 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.
Comment #35
tassaf CreditAttribution: tassaf commentedNo solution for this problem till now?
Comment #36
qzmenkoIssue is closed because 6.x version is unsupported. Feel free to open new issue for 7.x or 8.x versions of module.