Draft module cant save body field if used with CKEditor - WYSIWYG HTML editor 6.x-1.1

CommentFileSizeAuthor
#7 fix_drafts_ckeditor.diff599 bytescompmstr

Comments

cayci’s picture

cayci commented

is there anybody to help
so which HTML editor is the right one for draft module?

njathan’s picture

njathan commented

I too am facing the same problem.... is this a known bug? is there a workaround?

darren.ferguson’s picture

darren.ferguson commented

Not a bug, it is not supported in the module, if someone wants to provide the patch then it can be included. Although yesterday a patch was made that might fix it

Hiroaki’s picture

Hiroaki commented

I thought CKeditor was supported in this module... this is weird.
I am using dev version, and my ckeditor body fields aren't saved as well....

"
The Draft Module provides support for the following rich text editors:
FCKEditor
CKEDITOR
TinyMCE
"

lotyrin’s picture

lotyrin commented
Title: CKEditor body field » CKEditor support broken

Perhaps the author should update the module description until this is working again.

Ole Martin’s picture

Ole Martin commented

I also need this

compmstr’s picture

compmstr commented
StatusFileSize
new fix_drafts_ckeditor.diff599 bytes

I looked through the code for this, and found the problem. The current code is moving the data from the field to ckeditor when saving, and moving the data from ckeditor to the field when repopulating, which is backwards.
Attached is a patch file to correct this issue.

To use the patch:
-Put the diff file in the drafts module folder
-Go to the folder in a terminal
-Enter the command: patch -p0 -i ./fix_drafts_ckeditor.diff

omaster’s picture

omaster commented

It would appear to me that people have not realised that it says it supports CKEDITOR. Not WYSIWYG
CKEDITOR within WYSIWYG is a completely different kettle of fish to just CKEDITOR standalone.

Anonymous’s picture

Anonymous (not verified) commented

I can confirm that the patch provided in #7 still works in Ckeditor 6.x-1.11 (the standalone version). The cache must be cleared though. As this is still a problem (as we learened the hard way when we upgraded to Ckeditor from Fckeditor) would it be possible to include the provided patch as an update to the module? There already is about a ton of bugs when upgrading to Ckeditor and this can be the last straw for new Drupalists.