Port wysiwyg spellcheck to D7

Community - please review the patch and post results here. I can roll a D7 version after one or two positive reviews.

It works. If I understand how it is supposed to work correctly. The button appears inside TinyMCE button configuration (WYSIWYG administration). If selected it appears inside the node body's editor as it should. Pressing this button deactivates the TinyMCE context menu, marks spell errors with red. Clicking on the words using the right mouse button brings the suggestions list. Selecting one replaces the misspelled word with the correct one.

Checked with latest dev. WYSIWYG (D7), drupal 7 rc1 and TinyMCE latest.

Tested in Firefox 3.6.12 only.

Thanks for the blessed efforts.

i'm good with this review.

Drupal 7.0
Wysiwyg 7.x-2.0
Tinymce 3.3.9.3
Spellcheck 2.0.4

Button NOT appearing. The option does appear in the wysiwyg settings and I've checked it.

I couldn't get the Drupal 6 version to work either though (on a D6 site of course), so maybe I'm doing something wrong? Everything is in the right place. Wysiwyg and Tinymce work fine, just no spell check. (I know this isn't the thread for this but on D6 I got the button but no function.)

I've created 7.x-1.x-dev branch in CVS and applied the patch in #0 to it.

http://drupal.org/node/472926/release
http://drupal.org/node/1048880

Note that I did not test it at all yet.

@sleepingmonk and all
Please file issues against 7.x-1.x-dev code separately. I won't follow up #4 here. This thread should only be for discussion related to "Port wysiwyg spellcheck to D7".

Just a note that I did a D7 installation and tested the code. Found a problem - there was a change in Wysiwyg plugin API. Fix was committed, now it should work.

For those who have issues with the spellcheck button not working in the browser, check the rpc.php access (URL now is in the INSTALL.txt and on the project page).

I install, all seems to be OK and then when I enable the button in the Wysywig configuration the TinyMCE editor does not appear at all. Disabling the button causes the editor to return to normal behaviour.

@matthewdolman
Thanks for reporting. Could you report this as a separate issue against 7.x-1.x-dev? That will help tracking and addressing it better. While at it, I suggest opening Javascript/error console and pasting any errors from it.

Release created - 7.x-1.0. Thanks for contributions and testing. Please post any new issues separately.