Posted by nod_ on January 22, 2013 at 8:33am
6 followers
| Project: | CKEditor - WYSIWYG HTML editor |
| Version: | 7.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
| Issue tags: | Edit D7 Backport |
Issue Summary
When a field is changed on a form, Drupal triggers a 'formUpdated' event on the form element that changed (or trigger a change event on the textarea). See Drupal.behaviors.formUpdated in misc/form.js.
Edit module relies on this event to update the state of it's interface.
Comments
#1
The attached patch will work better once the
onchangeevent will be available: http://dev.ckeditor.com/ticket/9794In the meantime the onchange plugin might be helpful.
#2
#3
works great :) thanks a lot.
#4
Thanks for reviewing ;)
http://drupalcode.org/project/ckeditor.git/commitdiff/a5eaedb
#5
Just tagging as part of the larger Edit module D7 backport; don't mind me. :D
#6
Sadly, this patch seems to connected with my issue #1909150 -- full details on my setup there. If there is any content inside the underlying textarea, then the CKEditor instance will not appear, and I'm left with a regular textarea. I don't really understand what's going wrong, but I keep getting this error message on page load:
"Uncaught TypeError: Object # has no method 'editable' ckeditor.utils.js:93"
Line 92 in sites/all/modules/ckeditor/includes/ckeditor.utils.js references this issue number. I appreciate any help!
#7
Oops, indeed it could not work with old 3.x, fixed:
http://drupalcode.org/project/ckeditor.git/commitdiff/9308f1e
#8
That does seem to fix the error message, but doesn't resolve my other issue. I can't be certain my other issue was caused by this bug -- may well be another module or my custom code. Thanks for the prompt response!!
#9
Automatically closed -- issue fixed for 2 weeks with no activity.