What exactly is broken about the editor? Is the editor also on other pages with autocomplete form items on them? I'm not convinced this is a bug with the BATax module.
Posted by luketsimmons on April 20, 2010 at 2:57pm
Version:
6.x-1.5
» 6.x-1.7
Hi,
I have experienced this issue too. The problem is that I have a content type where the module works fine alongside FCK, and then the other content types don't work :-(
The issue is that FCK creates the second textarea for which it applies the actually editor but then it stops.
I was hoping I could diagnosis the issue with the differences between the content types, but alas not! (Although node reference fields are also affected, as [nid:Array] appears in each one - but I've seen there is another issue for that)
I’ve got the same problem with TinyMCE (with the WYSIWYG API).
What happens is that when a term is selected by using the Enter key, TinyMCE completely disappears, it becomes a plain textarea.
When a term is selected by point and click with the mouse, nothing happens (with the textarea, that is) and everything seems to work as expected.
I can get the WYSIWYG stuff back by first selecting a different input format (in my case without WYSIWYG) and then the input format with WYSIWYG enabled again. Which is not a proper workaround, unfortunately.
Comments
#1
Hmmm, that definitely sounds odd to me. Are you using the WYSIWYG module with FCKEditor, or the FCKEditor module?
#2
This bug reproduced in my site,too. And I uesed the FCKEditor module.
#3
What exactly is broken about the editor? Is the editor also on other pages with autocomplete form items on them? I'm not convinced this is a bug with the BATax module.
#4
Hi,
I have experienced this issue too. The problem is that I have a content type where the module works fine alongside FCK, and then the other content types don't work :-(
The issue is that FCK creates the second textarea for which it applies the actually editor but then it stops.
I was hoping I could diagnosis the issue with the differences between the content types, but alas not! (Although node reference fields are also affected, as [nid:Array] appears in each one - but I've seen there is another issue for that)
Has anybody looked at this or has any ideas?
Thanks,
Luke
#5
Update on this, I've not updated my core to 6.13+ yet, ours is at 6.12 so it would appear this is issue relevant here - http://drupal.org/node/473112
I'm getting Firebug teaser.js issues so will update and see what happens.
Thanks,
Luke
#6
I’ve got the same problem with TinyMCE (with the WYSIWYG API).
What happens is that when a term is selected by using the Enter key, TinyMCE completely disappears, it becomes a plain textarea.
When a term is selected by point and click with the mouse, nothing happens (with the textarea, that is) and everything seems to work as expected.
I can get the WYSIWYG stuff back by first selecting a different input format (in my case without WYSIWYG) and then the input format with WYSIWYG enabled again. Which is not a proper workaround, unfortunately.
btw. using D6.17