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.
Antonia Says:January 9th, 2006 at 3:08 am
I see others have gotten this same error but, none of the solutions I came across seem to be working for me. I’m using 1.5.2 and I also had to install Aspell. I’m a newbie to all this stuff and I have no idea what to do. This is the error message:
System error: Aspell program execution failed (’user/bin/aspell-a–lang=en_US–personal=/var/www/html/journal/wp-content/spell-plugin/aspell.personal &1′)
samurai Says:January 8th, 2006 at 2:43 pm
Thanks for sharing your plugin.
I was wondering if there’s a way for this to work in WPMU without having new users set their own options.
Salute!
BetaCandy Says:January 6th, 2006 at 6:13 pm
I thought of that, but there is no slash there.
ColdForged Says:January 6th, 2006 at 4:49 pm
Sounds like the blog address in the general WordPress options has a slash at the end. Try removing it.
BetaCandy Says:January 6th, 2006 at 4:40 pm
I hope this hasn’t been asked and answered (I’ve gone blind reading all the comments, LOL). This plugin works great for posts, but in comments, it keeps getting the filepath wrong with a double slash in the middle:
http://thehathorlegacy.info//wp-content/spell-plugin/spellchecker.html
Causes it to get a blank screen and do nothing. I’ve seen other people having the blank screen, and tried several of those solutions, but nothing’s working. What am I doing wrong?
Big Dog Says:January 3rd, 2006 at 11:38 am
Hi,
I have had no problem using this plug-in in 2.0. Just thought you might like to know that, so far, it has been working OK
Asa Jay Says:January 2nd, 2006 at 4:34 pm
Just installed this tool. Had to change en_US to just plain en to match the files on my server, no big deal, glad the options allowed me to do that.
Got the spell check button, used it, and worked my way through the errors. The ADD button was available and I tried using it. All was well until the speller finished and closed. All “added” words were -not- added (I got an error message) and the post did not get updated with the fixes. All else appeared to work well.
Tried again, dismissing all “add” words instead of trying to add them. Similar result. No error message on add words since I didn’t try to add any words, but the post still did not update with the changes.
I tihnk this might be a bug, when used with Wordpress 2.0. For now, even if I have to fix the post manually, having the spell checker open and finding the errors, is a BIG plus in my book.
Here’s hoping you massage it a bit for 2.0
Thanks,
Asa Jay
anna. Says:December 26th, 2005 at 10:24 am
me again. looks like Im the only one hyper the Monday after Christmas. went to the WP support forum, read the thread about pspell…
sigh maybe I’m one of the few with a pspell installation intead of the excutable, maybe most of us just don’t know enough when we run into errors to figure out this is the type of installation we have.
shall retreat back into waiting mode until you get it fixed for us too. no pressure, aspell has too many installation paths and types for you to handle them all.
robert Says:December 26th, 2005 at 5:44 am
Okay -
I have aspell 0.60 installed -
WP 2.0 RC3 installed
I installed the spell-check plugin
When I first attempted to use the spellchecker I got an error that en_US.dat was not located.
Yep - that does not exist on the system.
Made the change in options-spellchecker from en_US to en. Saved the changes
Still get the same error. en_US.dat not available
Had to modify the file aspell.personal by hand to have en not en_US.
Now the spellchecker finds no errors, not even on a word “QFcnief”
Found note here about WYSIWYG editors. Turned that off - now it works.
Okay, so this would be a A+ plugin if it could check spelling with any editor.
Cheers
anna. Says:December 25th, 2005 at 5:57 pm
:) oops. my permissions for the files were set too high. now I’ve got a different problem - spell check runs but then I get a blank page. I think I saw something in the FAQ, but any help would be welcome