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.
Jim Says:January 21st, 2006 at 8:11 pm
why bother creating a major plugin if you have no intention of continuing support? What a waste of my time. . .
Nathan Waters Says:January 18th, 2006 at 1:12 am
hi
I’ve been finding that using WP2 and this spell check plugin, that the spell checker picks up all the HTML tags in the post and asks if they are spelled correctly etc.
Is there a way to make it so that HTML tags are not checked?
Chris Says:January 17th, 2006 at 1:11 am
Lee: You can probably fix that by changing “lang=en_US” to “lang=en” - not sure, but that worked for me.
Lee Yee Yang Says:January 15th, 2006 at 2:00 am
Alright. I’m a newbie at WordPress and pretty lousy at spelling too… This might be a re-post of a problem someone’s already had and fixed, so excuse me.
I followed all the instructions in the zip file, activated the plugin, chmoded to 777 etc… Then when I type in “fcuk” for a test drive, I get the following:
“Error executing
/usr/bin/aspell -a --lang=en_US --personal=/home/barsketc/public_html/square/wp-content/spell-plugin/aspell.personal < /home/barsketc/public_html/square/wp-content/spell-plugin/aspell_data_6LA19p 2>&1Error: ���{8″
Help, anyone?
P.S. I’m running WPver2.0.
Chris Says:January 13th, 2006 at 10:49 pm
Yeah, what kind of a bribe$ will it take before you can make thi$ work in Wordpre$$ 2.0 with WY$IWYG enabled?
Thor Says:January 11th, 2006 at 1:35 pm
I turned off the rich text editor on my WordPress 2.0 installation, and the spell checker plugin works just fine. It’s just the rich text editor that the spell checker doesn’t play well with. This is no big deal for me, since I was thinking about turning off the rich text editor anyway.
Thor Says:January 11th, 2006 at 1:17 pm
So, Brian, what kind of bribe will it take to get you to move WordPress 2.0 compatibility up on your priority list?
Mavis Says:January 11th, 2006 at 1:14 am
I just wanted to pop in and say hi… so… Hi!
samurai Says:January 9th, 2006 at 8:55 pm
Was wondering if anyone got this successfully installed on wpmu, so that newly created blogs do not have to re-configure the plugin. I’ve looked through the replies and cannot find any info on this. Any help would be greatly appreciated
Thanks.
BetaCandy Says:January 9th, 2006 at 12:02 pm
I’ve also changed permissions on several files from 644 to 755 (spellchecker.php, spellcheck.php), but I get the feeling that has nothing to do with it. I’ve deactivated a bunch of other plugins and even uninstalled Mudbomb’s WYSIWYG just in case, even deactivated, it was somehow conflicting. And I’ve looked at my comment template to see if there’s anything strange in it (I do have code for Skippy’s Gravatars plugin, but I don’t think I see anything that would cause the double-slash.