wysiwyg compatibility

Thanks for the patch! Commited to 6.x. You may found changes in latest dev (from March, 8).

Automatically closed -- issue fixed for 2 weeks with no activity.

I have found some issues using Wysiwyg 2.x-dev (with TinyMCE) and AJAX Comments, where the wysiwyg editor is not starting in the comment form.

It is like ajax comments were not re-attaching, or detaching it, to the comment form correctly.
In fact if you click the "Disable rich-text" text added by wysiwyg and again "Enable rich-text" it works fine.
But this also shows that the ajax_comments_remove editors() and ajax_comments_attach_editors() from the ajax_comments.js is not executing the right options with the wysiwyg module.

Some more info.
If you open a node with comments, (and the option to have comments in the same windows), and you have the ajax_comments option "Form always expanded" on, then the first open form is right, but if you try to open other comment form replying to an existing comment then it doesn't start wit the wysiwyg editor (in fact is something start because the Disable rich-text is already there, but the rest is not starting right)
In the case you have the "Form always expanded" form off, the when you try to expand the new comment form then that one is already wrongly initialized.

Well, testing with ajax_comments 6.x-1.7 it works fine, so last commit from 24th March broke the attachment of wysiwyg editor!

Thanks for your investigation, Jose. I'll figure it out.

This is still happening just as jcmarco described, in the latest 6.x-1.x-dev. Any thoughts yet on how to fix it?

Following the same actions that Wysiwyg.js with Drupal.behaviors.attachWysiwyg(context) and adding a Drupal.wysiwygDetach($(this), params); before the Drupal.wysiwygAtach($(this), params); in the function ajax_comments_attach_editors(), then the attachment and detachment of new wysiwyg editors work fine, but in same forms when you try to send more comments or a new one, then you get this error:

Comment field is required.

I have been testing last AJAX Comment version, and there is still issues with Wysiwyg API.

First time you open comments, (in a new page or following node content) you are able to open the wysiwyg API element
wherever you click on any reply link, even with new comment once you have open the editor in any old comment.

And you can send the first comment, the first time perfectly.
But once you have send any of them, a new one o replying an existing one, then you find some of this two issues:

- the wysiwyg editor it's hung, I mean, the interface is attached but the editor is locked.
- or you see that the wysiwyg editor open the same menu one after the other as you click in a reply link

When you try to send any comment on this situation then you get this error:
Comment field is required.

Exact same issues as #9, above with wysiwyg/tinyMCE and latest dev of AC. Any progress? Anyone have an incantation that works?

same issue, thanks in advance to whoever can help.

I see the same problem described in comment #9. Wrote a bug report in April to http://drupal.org/node/437110 , but still no solution.

subscribing

Subscribing

subscribing

I cannot get *any* WYSIWYG module to play nice with AJAX Comments either.

Same issues as #9 as well, seen in these screenshots here testing with TinyMCE inside of WYSIWYG module.

1. First comment works fine.
2. After it's posted, clicking on any other reply link breaks the rich editor by adding it multiple times in the text editor box, and not letting me enter any text in it.

It has been 6 months since first reported. It looks like the problem won't be fixed until somebody contributes a patch.

Since the title of this thread is titled "wysiwyg compatibility", I have to ask - has anyone successfully enabled this module alongside a rich editor?

subscribing