457 Comments

• Jim says:

  1/21/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:

  1/18/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:

  1/17/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:

  1/15/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>&1 Error: ���{8″

  Help, anyone?

  P.S. I’m running WPver2.0.
• Chris says:

  1/13/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:

  1/11/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:

  1/11/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:

  1/11/2006 at 1:14 am

  I just wanted to pop in and say hi… so… Hi!
• samurai says:

  1/9/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:

  1/9/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.
• Antonia says:

  1/9/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:

  1/8/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:

  1/6/2006 at 6:13 pm

  I thought of that, but there is no slash there.
• ColdForged says:

  1/6/2006 at 4:49 pm

  BetaCandy said: it keeps getting the filepath wrong with a double slash in the middle

  Sounds like the blog address in the general WordPress options has a slash at the end. Try removing it.
• BetaCandy says:

  1/6/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:

  1/3/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:

  1/2/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:

  12/26/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:

  12/26/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:

  12/25/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
• anna. says:

  12/25/2005 at 5:50 pm

  Brian, I get the by now much hated Internal Server Error. My error log says the following:

  [Sun Dec 25 14:41:59 2005] [error] [client 85.141.146.147] Premature end of script headers: php-script, referer: http://www.teambio.org/wp-content/spell-plugin/spellchecker.html

  I’m pretty sure I have aspell installed, it was one of my criteria for the webhost Yes, so I can finally use this plugin.

  Ideas?
• Doug says:

  12/21/2005 at 2:04 pm

  I have the spell checker installed and it acts like it is working, but it misses obviously misspelled words. Can you give me any clues to why this might be happening.
• MiCHA says:

  12/21/2005 at 3:26 am

  If you want to use spell checker with a language other than English, you may need to add “–encoding=utf=8″ to $aspell_opts in spellchecker.php. Otherwise some special non-latin chars may not be interpreted correctly.
• TomW says:

  12/17/2005 at 11:59 pm

  This is a terrific plugin.

  I can add words to the personal dictionary from the plugin options page, but when I use the Add button in the speller window it only appears to work. At the end I get a message about the # of words that it failed to add. I’m also not finding the add_failed.out file you mention.

  Any thoughts on how to debug this?
• JP says:

  12/16/2005 at 2:23 pm

  Getting this error when trying to use the spell-checker (wp 1.5.2):

  Error: the file “…/aspell-word-list.txt” is not in the proper format.

  Hu?
• David says:

  12/10/2005 at 4:57 pm

  Is it possible to have a list of the bugs and the method to fix it ?
• Tom says:

  12/8/2005 at 4:28 pm

  Changed “en_US” to “en” in Options, and all is well. Thanks for the quick response!
• ColdForged says:

  12/8/2005 at 1:15 pm

  jjk said: This is probably becuase the file “/usr/share/aspell/en_US.dat" can not be opened.

  Please see this comment.
• Tom says:

  12/8/2005 at 1:00 pm

  I get the same error as JJK when checking spelling. Thanks in advance for your help.
• jjk says:

  12/4/2005 at 10:13 pm

  Now that I have managed to move past the issue of the personal dictionary being writeable, I get aspell errors. Specifically, I get the errors

  Error executing /usr/bin/aspell -a --lang=en_US --personal=/var/www/html/wp-content/spell-plugin/aspell.personal < /tmp/aspell_data_rjrCBo 2>&1

  Error (some garbage images) uage “enUS” is not known. This is probably becuase the file “/usr/share/aspell/enUS.dat” can not be opened for reading (another garbage image)

  And yes, “becuase” is spelled like that in the error message. I am using aspell-0.50.5-6 on Fedora Core 4. Do you have any idea what’s happening?