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.
badrad Says:December 2nd, 2005 at 5:49 am
I am with Dan, patiently waiting for a 2.0 update which I am sure will come.
ColdForged Says:November 30th, 2005 at 1:10 pm
Dunno Dan, if it works from the command line it should work from the plugin. Try getting rid of the default personal dictionary you have listed and setting the language then.
Not at this time. I don’t futz with betas, especially with plugins. Things are too crazy. Once it’s released and if I ever decide to upgrade I might update it, but I couldn’t say for sure.
Dunno. It’s possible the path isn’t what you think it is. Try modifying the
wp-content/plugins/spell-plugin.phpfile. Go to line 311 and change this:if(!is_writable(dirname($speller_settings[’aspell_dict’])))to this:
if( 0 )And see if it works. If yes, then there’s something weird about your setup, but you should be okay. If no, then there’s something weird about your setup and hopefully it’ll tell you a bit more
.
Not really but it sounds like a lulu
. Sorry, I really have no suggestions as I’ve never seen the like.
jjk Says:November 30th, 2005 at 12:33 pm
For whatever reason, I cannot get the personal dictionary to appear writeable. I keep getting the error:
FATAL: You forgot to make the personal dictionary directory writable. Please read the install instructions and chmod this folder to provide write privileges to the Apache task.
However, I have pointed the spell checker to /var/www/html/wp-content/spell-plugin/aspell.personal , and I have changed that whole spell-plugin directory to 777 with no effect. The directory is owned by my local user and is in the group apache. What am I doing wrong?
WordPress version 1.5.1.3, Spelling Checker 1.18
Dan Says:November 29th, 2005 at 1:17 pm
Hi, do you have any plans to tweak this to work with 2.0? The plugin still works with the plain text editor, but if the TinyMCE editor is enabled, the plugin reports not mistakes (it doesn’t appear to check the right text field).
This is by far the best spell check plugin I’ve found, so it’d be fantastic if it could be made to work with 2.0. I’d be happy to test it too.
All the best!
Charles M Says:November 24th, 2005 at 10:57 pm
Hi. I think I incorrectly upgraded to 1.18. When I went to activate the plugin on the plug-in page, my whole site just shows bland. I have manually deleted all of the filed from the wp-content and plugin directory and I got my page back. But whenever I re-try to install the plugin and go to the WordPress plugin activation page, the whole is blank again.
Any thoughts on what I dorked up?
Dave Says:November 22nd, 2005 at 5:54 am
BTW, enCA and enUS both work from the command line, but for some reason they don’t work in the spell checker plugin
Dave Says:November 22nd, 2005 at 5:51 am
How can I get it to use the en_CA dictionary? Putting “en” works, but I want the Canadian aspell dictionary to be used.
Maxime Says:November 19th, 2005 at 11:51 pm
Carlton : I suggest to developp it yourself. I think there is no version without disabling PHP SAFE MODE.
Carlton Bale Says:November 19th, 2005 at 4:37 pm
Looking forward to a version that does not require disabling PHP SAFE MODE. Looks like a great plugin otherwise!
Richard Silverstein Says:November 18th, 2005 at 4:39 pm
Brian: When the plugin was briefly working & then stopped working I was with Bluehost. I never got any error when it stopped working–it just didn’t work whenever I tried it.
Now, I’ve moved to Carthik Sharma’s server & since then I’m getting the error I mentioned. I’ve sent him an e mail asking if he can help figure this one out. Hopefully, he can.