IMPORTANT NOTE FOR WORDPRESS 2.0 USERS
This plugin doesn’t play well in WordPress 2.0. I’m well aware of this. Some day I may update it but it is nowhere near the top of my priority list. Support questions for 2.0 installations will not make it out of moderation.
Latest version is 1.18, released 06/23/05.
I’ve been looking for a spelling checker plug-in for WordPress for a while. Didn’t find anything to my liking, so I figured I’d create one myself. The fruits of those labors are now here!
The Spelling Checker plugin for WordPress
With this plugin a new button appears alongside the rest to pop-up a spelling checker derived from the Speller Pages SourceForge project. No more typos!
This is a 1.18 release and it has been tested on WordPress 1.5.1.2. Please direct any questions or problems to me in this post.



ColdForged Says:November 13th, 2005 at 9:22 pm
Try a different language, either
enorenglish.
ColdForged Says:November 13th, 2005 at 9:21 pm
Yes. WYSIWYG editors and the spell checker don’t work together well.
That’s because that folder,
spell-plugin, should be located in$WPROOT/wp-contentand not in thepluginssubdirectory. The only file that exists in thepluginsfolder is thespell-plugin.phpfile.
TJ Says:November 13th, 2005 at 8:50 pm
First install on WP 1.5.2, and there are immediate problems after activation when trying to access the configuration page.
Warning: main(…\wp-content/spell-plugin/spellInclude.php) [function.main]: failed to open stream: No such file or directory in …\wp-content\plugins\spell-plugin.php on line 36
Note the missing “plugins/” folder in that path. It seems to be caused bv line 36’s require((dirname(dirname(FILE)) which, with spell-plugin.php in the plugins/ folder, resolves to the parent of the parent - the wp-content/ folder.
If I fix that I then get similar errors from spellInclude.php.
If I fix spellInclude.php by adding an extra dirname( on line 7 then I can get the configuration page.
However I now find the temporary and dictionary folders are incorrect and I get big red warnings about them not being writeable - because the paths are missing the “plugins/” folder.
Is this just me or a hiccup in the package?

Dean Shareski Says:November 12th, 2005 at 6:24 pm
The spell check works fine but replaced words do not appear changed after closing spell check. I’m using a WYSIWYG editor as well. Might that be the problem?
Also is there a way for it to check text only rather than code?

Very Mom Says:November 12th, 2005 at 2:29 pm
Hi there, have just installed the Spell Checker and read the threads at the WP forums but I can’t seem to solve one [hopefully] final problem. I needed to chmod the spell-plugin folder to 777 as well as the plugins folder to get rid of the errors on the speller_setup page, I also enabled the manual personal dictionary. I am still getting the following error when I try to run the spell checker on a post:
Error executing ‘/usr/bin/aspell -a –lang +enUS -personal+/home/verymom/publichtml/wp-content/spell-plugin/aspel.personal &1′
Error: ?g?
I can’t make heads or tails of that one. I’m also gathering from the WP threads that a folder was supposed to be created inside the spell-plugin folder? Something for the personal dictionary? This has not occured, though I’m not sure if I’m reading that right.
Any help would be appreciated, thank you so much.

ColdForged Says:November 9th, 2005 at 4:16 pm
Go to line 153 of the file `wp-content/spell-plugin/controls.php. You’ll see this line:
if((!$current_options[’must_be_logged_in’]) || ($current_options[’must_be_logged_in’] && ($user_level >= $current_settings[’minimum_user_level_to_add’]))) {Change that to the following:
if( 0 ) {I really haven’t a clue why it’s failing, unfortunately.

Maxime Says:November 9th, 2005 at 3:28 pm
How to remove a button from the interface ?

phpguru Says:November 4th, 2005 at 12:04 am
Same problem as a couple of other posts. Spell Checker runs fine (after I changed the language to “en”) but never finds a misspelled word. In fact, misspell anything you like and the Spell Checker ignores what you write and returns the message “No misspellings found.” I got a shell prompt and typed “aspell -a –lang=en” and got to another prompt where I typed “crapp” (bad spell) and “works” (good spell) and got a good responce (see below). So there’s something wrong with the parameters you’re passing to aspell I’m assuming, or you’re geared for another version altogether. Thoughts on a fix??
Original thread:
[url]http://www.coldforged.org/archives/2004/12/08/spelling-checker-plugin-for-wordpress/comment-page-all/#comment-4398[/url]

rich Says:November 2nd, 2005 at 11:41 pm
Is there a way to remove the ‘add’ button from the interface?

rich Says:November 2nd, 2005 at 11:40 pm
how can I remove the ‘add’ button from the interface?