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.

457 Responses to “Spelling Checker plugin for WordPress”
Plugin looks great but there’s a bad relationship with special characters like accents (à ,á.è,é, ….).
There’s a solution?
Good question, I’ll have to investigate.
EDIT: After taking a look at the underlying code, this seems like a design decision of the Speller Pages project. I’ll mull it over some to see if there’s a way around it. Thanks for bringing it to my attention.
I get a script error saying “‘spellChecker’ is undefined.”
Sounds like it couldn’t find the js file… is your WordPress installation in a subdirectory? If so, modify the spell-plugin.php file to have the correct path to the javascript file. Search for “wp-content” and make sure that it goes to the right place.
<script language="javascript" type="text/javascript" src="/wp-content/plugins/spell/spellChecker.js">I may have to adjust how that path is derived in a follow-on release.
You run into the same problem that I did when I was writing a spell-check plugin. You must have aspell on your server, and that is not as ubiquitous as it should be, case in point my MacOS Z Panther server doesn’t have it, so this won’t work.
Nothing you can do about it really, just thought I would let you know about that limitation.
Good work on this though, very posh.
I corrected the path to my plug-ins directory, and now the pop up window displays the front page of my web log.
Check the paths in the spellChecker.js file as well, namely:
function spellChecker( textObject ) { // public properties - configurable this.popUpUrl = '/wp-content/plugins/spell/spellchecker.html'; this.popUpName = 'spellchecker'; this.popUpProps = "menu=no,width=440,height=350,top=70,left=120,resizable=yes,status=yes"; this.spellCheckScript = '/wp-content/plugins/spell/spellchecker.php';Yeah, I had named that as a prerequisite but it bears repeating. Is there an alternative executable that’s common on Panther?
Great plugin. Installed and worked first try – like a breeze. Anybody know of a way to make the dictionary ignore the XHTML tags themselves?
Another good question. Something else I’d like to work into a follow-on release. I’m trying to think up a methodology that would succeed for this, but nothing’s come to mind yet. Thanks for the input.
Have you checked out SpellBound?http://spellbound.sourceforge.net/
It’s a Firefox spell checker plug-in and works in any input or textarea.
The spellChecker.js points in the right directory. The top half of the screen will begin with “Spell check in progress…” and then go to the front page of my web log. The bottom half seems like it is displaying properly.
Hrm..
I know this may not be possible, [insert long shot here], but is there any way of being able to “add” words from the spell checker popup back into aspell?
Instead of requiring people to manually set the URI to WordPress, why not just do it for them using
<?php bloginfo('home'); ?>?
Also, on the regular Write screen, the Check Spelling button is in the bottom-left corner of the browser (way at the bottom). It appears correctly only on advanced edit screen.
Odd. Anyone else seeing Ron’s problem? Ron, you say the bottom half displays fine… do any spelling suggestions from the actual post show up?
They’re looking at that as a future feature of the base Speller Pages project. If they get that in there — or I get bored and feel like contributing — we’ll get it here
.
Exactly what I was looking for… I knew I was overlooking something simple. Thanks for the nudge.
So it does! Along with the “eval() Content” from RunPHP. Guess they fooled both of us. I have Advanced Controls as the default so didn’t notice it. Thanks for the heads up, I’ll fix it today.
I installed it as instructed and Word Press is in my root so I didn’t really have to alter anything. However, when I click on the “check spelling button” the spell checker interface pops up but the top frame after checking for errors always returns a blank page, even when misspelt words were in the post. This happens in both latest Netscape and IE and IE displays an error message:
Line: 44 Char: 1 Error: Object expected URL: http://www.jewlicious.com/wp-content/plugins/spell/spellchecker.php
Any suggestions?
I should also probably add that I am running WP 1.2
I’ll investigate, thanks for the detailed information. Looks like I’ll need to install a test 1.2 installation
.
Ron, you running 1.2, too?
I’m sure I’ve missed something silly, but I’ve installed the plugin (several times now), and although it appears to activated, no spell check button appears on the “write post” screen. I have tried several different path entries to the plugin files in each of the spell-plugin.php, spellchecker.php and spellChecker.js files. I also tried settting the full path to the aspell application.
I am running WordPress 1.3 alpha 5.
Help?
Check the bottom of the screen, does it appear there? If so, that’s a known issue that will be addressed today. If not, can you view the page source and look for the word “spell” in there somewhere and tell me what you see?
Thor: My spell check button appears where it should in advanced controls, but not so much in the standard editing page. But that’s been addressed already.
Coldforged: Viewing the page source for the compose screen, the word “spell” is not found, and the button is missing in action. Does the path have anything to do with the button’s appearing? I’ve tried using the absolute path with it making no difference for me.
ck: Unfortunately, the button does not appear either way.
The HTML portion of the bottom half shows up fine; however, there is no spelling suggestion from the post. (I had intentionally spelled some words wrong to test the plug-in.) I have gone through and corrected all of the paths that I found. I have also tried this in several browsers, to include Internet Explorer, Fire Fox and Netscape.
P.S. I am using Word Press 1.2.1.
No, basically if the plugin is installed in your “wp-content/plugins” directory and Activated in the plugins page, there shouldn’t be any way that it won’t appear on your “Write Post” page. I have a 1.3a5 as well as a 1.2 installation now, and it appears on both.
Ron and Thor, could you try the updated version listed here? Perhaps these adjustments will help you both. I have since tried it on a subdirectory 1.2 WP installation without difficulty, so I’m curious about what’s going on for you. We’ll get to the bottom of it somehow.
I tried the updated plug in and it seemed to be working, but then I got:
I put the updated plugin up, but it made no difference. As requested, I email the source file. Also, I tried updating my WordPress from the newest CVS; it made no difference.
Spell Checker for WordPress
Quite a few WordPress blogs mentioned today that there is a new spell checker plugin for WordPress: Spelling Checker. It is still in alpha and works only with WordPress 1.3 (which is also still in alpha).
This plugin is based on Speller Pages, a ser…
Spelling Checker plugin for WordPress
Someday I’ll be able to make posts without a single spelling error. I’ll be waiting for a Grammar Checker plugin…
Just keeps getting weirder. What happens when you try to run aspell from your command line on your host?
Note that I have tested it on 1.2 now and it appears to function.
I just installed the 0.2 version on WordPress 1.2, other than needing to install aspell, everything seems to work great, Thanks!
Excellent, thanks for letting us know!
Spell checker plugin
Yesterday, ColdForged released a spelling checker plug-in for WordPress. Just what I need! I’ve been looking for this!
What is it? The Spelling Checker plug-in for WordPress provides a built-in facility for spelling checks on posts from within…
coldforged.org » Spelling Checker plugin for WordPress
coldforged.org » Spelling Checker plugin for WordPress
Sweet! Now maybe John will leave me alone about my spelling!
Ron and ck:
Try out this version and see if it gets you through. Note the additional installation step of setting the aspell path. Let me know if this helps you, please.
Can you make a version that is in zip form?
Sure. Head to the page and enjoy.
I downloaded, edited, uploaded and reactivate the new .3 version. I’m now getting a JavaScript error relating to english.dat. That file does not exist on my host server, at least not where I’d expect it to be. There are other files that might be relevant, but I don’t know enough yet to determine that.
A very BIG thank you for your help yesterday, by the way.
Thor, the personal dictionary support is what’s killing you there, so I may have to back that out. I’m trying to come up with a more generic solution. In the meantime, anyone having similar issues with the personal dictionary can back it out by editing the “spell/spellchecker.php” file and changing $aspell_opts to the following:
[code lang="php"]$aspell_opts = "-a --lang=$lang";[/code]
I’ve since determined that ck’s problem is an overall incompatability with servers that run with PHP safe_mode on. I can get past half of it, but the actual execution of the aspell executable seems impossible right now. If I come up with a solution, I’ll advertise it. Until then, this plugin simply can’t support safe_mode PHP environments. Sorry.
The zip file link can’t be found.
Also what is the aspell_path?
Open up a terminal window to your web host. Type “which aspell”. It should respond with something like “/usr/bin/aspell”. It may say “/usr/local/bin/aspell”. It may say something else. Whatever it says before the “aspell” is the path. So, edit your wp-content/plugins/spell/spellchecker.php file and find the line that looks like this:
$aspell_path = '/usr/bin/';and make sure that that path matches your host’s path.
Aspell seems to be installed since it’s working.
Hmmm…I got this to work…no problems! VERY cool plugin I might add!
A big thanks from me…
Hey, my gravatar’s messed up here…
Spell Check your Comments
Cold Forged did a very nice encapsulation of spell checking as a plug-in for WordPress. I grabbed the code and incorporated it as a new option in my comments’ pages so you can spell check your comments–both the live comment, and the saved comment in …
It doesnÅ£t seamns to work with HtmlArea plugin. I don’t see spell buttons after activation
Doh! I assume you have a transparent one, eh? Never thought of that.
I’ll check it out, thanks for the heads up!
EDIT: Fixed in version 0.5. Be sure to read the release notes, though.
There’s a gzipped version of 0.5
Meant to add that I don’t see a zipped version of 0.5. Sorry for double posting but it’s a great plugin also.
This is great! Any way to make this work on comments?
It’s not so much that my commenters can’t spell as it is that… um, I can’t.
I am very relieved now, because I had just started working on my own spellchecker using aspell; I had no idea that Speller Pages was out there. One thing that I ran into is that you can use a ‘-H’ option if you are going to be checking any HTML (or any SGML, really) and it will filter through it.
Gah, again with the forgetting the zip version. My bad. Check again, it should be there now
.
Yes, there is, though Shelley remained mum in her method. Fear not, though, I’ll probably make it a standard feature of a future version if Shelley doesn’t dish
.
Didn’t know that! Thanks for the tip, I’ll have to check that out and incorporate it.
I use SpellBound 0.7.1 which is a FireFox extension… just a right click away, and works perfectly for me.
If in IE I use ieSpell… also just a right click away.
I’m not meaning to be a killjoy, but in what way is Spelling Checker better?
In no way. Use what works for you! But apparently a lot of people don’t know about those tools that you mention. Even if they did, some people don’t make that leap from “there’s a tool for my browser” and “I can use it for my WordPress installation.” But, give them a plug-in explicitly for what they’re trying to do — say, write a post in WordPress — and they find it useful.
Judging by the buzz and apparent popularity, there was seemingly an unfilled need.
I’m having similar problems as ck and others. I’ve installed versions .3-.6 on both a linux and Mac OS X box. In both cases I know that aspell works and have the correct path set for $aspell_path.
When I go to check the spelling, I get the pop, it Spell check in progress… message, then the top half of the window goes blank. When I view the source for that frame, I can see the suggestions for the misspelled words. (I’ve tried with both IE and Firefox)
The error that I get in IE is error on line 47, char: 7, Error: ‘wordWindowsObj’ is null or not an object
Any suggestions would be greatly appreciated.
I was also having problems. In several of the php files it assumes that wordpress is installed in the root directory of the website. Mine is installed in a subdirectory. I edited the paths by hand adding the extra directory level and got it to work. Seems like the plugin should detect what the WordPress root is then build paths from there on.
Nice work, Nat. Yes, Ken agreed to work with me to help track it down and I made that particular discovery last night but could only confirm it today. Yet another path I overlooked. Sorry about that. Thanks for helping!
Version 0.7 Alpha already incorporates significant changes to the path derivation, so it should be addressed then. That will be released tomorrow… not tonight only because the source is on my work machine repository and I can’t get to it
.
I am also getting the
'wordWindowObj' is null or not an object'error. Other than that, everything seems to be working. I am hoping I can get this to work!Thank you for your work on this, I have been looking for something like for a long time.
Spelling Checker is better for people like me because I travel at least 180 day s a year and do most of my web log accessing and posting on the road from public computers. Most of these do not have IeSpell or Fire Fox installed.
It tells me I need a word list.. specifically for the language en_US
HELP?!
Hmm… first try would be to remove any file named “plugins/spell/aspell.personal” if it exists. That will force the plugin to create a new personal dictionary. If that doesn’t do it, I would try to track down where your aspell install is and determine if it has a master word list. Try this to see if there is a master word list:
aspell dump masterIf there is you’ll get a load of stuff.
Another thing to try is to remove the entire “–lang=$lang” parameter from the file “plugins/spell/spellConfig.php” file. All instances of it and see if it makes any difference.
I’m no expert on all the myriad installation options of aspell, so it may take some experimentation on your part to determine options that work for you. Hope this helps!
Here’s the deal. I can’t trace my aspell install because my host doesnt offer shells. So I think that I got the config right (check freshpolitics.us to see) but it says there is no Word List. How do I install one?
If I can’t do those calls “which aspell” and “aspell dump” how can I figure this out?
No joy with the Add Word feature. I click the button, and… nothing happens. Just to check that a word was not being added, I closed the page with out saving, reopened and ran the spelling checker again. Same words found that I tried to add.
Checking the plugins/spell/ directory, no “aspell.personal” file is being created.
What have I missed?
Somehow I knew you’d be a troublemaker
. IM me when you get a chance… I know we had difficulties with aspell personal dictionaries with you before.
Unfortunately there’s no way to verify you have the aspell configuration correctly by looking at your site… you may have the other paths set up right such that the window comes up but still have an aspell configuration that is incorrect, as seems to be the case since it can’t find the word list. It may be time to get your hosting provider involved to see what their aspell support is. Ask them perhaps where their aspell master word list is located. Once you have that, then you can specify that in all of the aspell configuration variables as:
--dict-dir="path-to-the-word-list"Troublemaker. Yep, That’s me. Mostly out of not knowing any better, I guess.
I didn’t keep your IM address, sorry. I’ll keep plugin’ away. Send me an email if you think of something for me to try.
I’ve added your Spell Check plugin and it works GREAT! It was a bear for me to install aspell on my shared Linux webhost account, but I figured out how to do it without being root.
However, I can’t seem to get personal dictionary to work. I click on “Add” and when the spell check is done, it says “Failed to add 3 words to dictionary.”
Also, this plugin only works with IE – which is not good. I prefer Firefox, but I set firefox to open popups in tabs. When I try to check spelling using Firefox, it opens a new tab that says:
This page cannot be displayed
The window was not opened from another window.
Any suggestions for the 2 things?
THANKS!!!
Take a look in your “wp-content/plugins/spell” folder. First, do you have an add_failed.out file? Does it have any goodies in it? Second, do you have a file called “aspell.personal” in that same folder? If not, try running the following command in a shell and see what comes out:
aspell create personal --lang=en_US --personal=./aspell.personal < aspell_word_list.txtIf it Aborts or says anything about a core dump, you have a version of aspell that doesn’t support creating/merging of personal dictionaries. If that’s the case, let me know. I have a plan for the next version to have a fall-back option that will manually create/merge personal dictionaries in those cases… I just want to know what the demand is. If you are in the same boat, you’re only the second person to let me know
.
Hell, who doesn’t? I actually use Firefox almost exclusively, so I’m pretty sure it works with the standard install. Which plugin do you use to get your new windows into tabs? I use the Firefox 1.0 20041107 release, but no longer use any extensions to force new windows into tabs.
Very nice plugin. Installed in seconds (about 20 total) and it works great. Thanks!
ls -1 spelladdwords.php aspell-word-list.txt blank.html controlWindow.js controls.php netjs-devel.gif spellChecker.js spellConfig.php spellchecker.html spellchecker.php spellerStyle.css wordWindow.js
no aspell.personal nor add_failed.out
find ~ -name aspell.personal -print find ~ -name add_failed.out -printLooks like those files don’t exist anywhere in my space.
$ aspell create personal --lang=en_US --personal=./aspell.personal Sorry "create/merge personal" is currently unimplemented.No core dump. I installed aspell yesterday, and I downloaded it yesterday, so I would think I’m on the newest. My version is aspell-0.60.1.1.
On to the Firefox issue… forcing all windows into tabs is one of my FAVORITE things about Firefox over IE (and security of course!
)
The extension I’m using to do that is:
1) singlewindow 1.4 from http://www.mozthemes.tk 2) tabbrowser preferences 0.6.12 from http://www.pryan.org/mozilla/site/TheOneKEA/tabprefs/
Mark, download the latest version. Then open your spellConfig.php and change this line:
[code lang="php"]$broken_aspell_personal_dictionary = false;[/code]
to have a value of true. Then come back and let me know if you have a better time
. You and Thor are in the same boat, so this version is for you guys.
Yeah I don’t understand the dynamics of it… I run 0.50.3 and it supports creation/merging where “later” versions don’t. I can’t explain it.
I’ll try it later and see if I can reproduce it and figure out what’s going on. Thanks for the info.
Okay, I upgraded, and when I attempted to spell check, I got a popup that says:
Error executing ‘aspell -a –lang=en_US — personal=/ /wp-content/plugins/spell/aspell.personal < /tmp/aspell_data_QYqJqJ 2>&1`
Error: / aspell.personal: The language “en_US” is not known. This is probably because: the file “/ /aspell6-en-6.0-0/en_US.dat” can not be opened for reading.
$ ls -la ~/aspell/aspell6-en-6.0-0/*.dat -rw------- aspell6-en-6.0-0/en.dat -rw-r----- aspell6-en-6.0-0/en_affix.dat -rw------- aspell6-en-6.0-0/en_phonet.datShould I alter something in a config file?
Okay, I upgraded, and when I attempted to spell check, I got a popup that says:
Error executing ‘aspell -a –lang=en_US — personal=/ /wp-content/plugins/spell/aspell.personal < /tmp/aspell_data_QYqJqJ 2>&1`
Error: / aspell.personal: The language “en_US” is not known. This is probably because: the file “/ /aspell6-en-6.0-0/en_US.dat” can not be opened for reading.
$ ls -la ~/aspell/aspell6-en-6.0-0/*.dat -rw------- aspell6-en-6.0-0/en.dat -rw-r----- aspell6-en-6.0-0/en_affix.dat -rw------- aspell6-en-6.0-0/en_phonet.datShould I alter something in a config file?
I vi’ed spellConfig.php and changed $lang = ‘en_US’; to $lang = ‘en’;
This time spell checker ran, but I got the same error I got initially, “Failed to add words to dictionary.”
This time there IS an aspell.personal!
$ cat aspell.personal personal_ws-1.1 en 14 WordPress pre PHP html ColdForged MySQL src ul ol li br img blockquote blogThere doesn’t seem to be an add_failed.out file
As far as the SingleWindow incompatibility goes, it appears by my investigation to be a bug in the extension. He’s not forwarding the “opener” property to the new tab and I rely on that property to get at some needed information. I’ve forwarded something to his “guest book” so we’ll see what he says.
As far as the dictionary problems, I’m creating a minor revision to output more debug. The only things that would cause it to not be able to update the dictionary is: 1) unable to open the dictionary for writing, 2) unable to write additional lines to it, or 3) the dictionary doesn’t exist there. All of which seem hokey. Can you double-check permissions on that created file? Make sure everyone can write to it, maybe?
Which extension? I’m using 2 to control my tabs. I’ll disable the offending one.
I chmoded it to 666 but that didn’t fix it. So I chmoded it back. I don’t like giving the world write perms. Anyhow, it still didn’t work, even with the world having write perms.
Actually you don’t even have to disable it. Simply turn off the option that says “Open JavaScript links in new tabs” in the Single Window extension.
I’d like you to install a debug version. Grab this one and install it. Remember to set the $lang and turn on the “broken aspell” feature. Try it out and see if any new files show up in that spell directory. Hopefully it’ll show what went wrong.
Okay, I installed the new one, and made the changes, but it still doesn’t work
This time it doesn’t say that it had problems adding the words. It just doesn’t add them.
I don’t see any debug info. Where would I find that?
Thanks for your quick responses, by the way!!!
Hmm…
Would you mind sending me an email to sohmer@coldforged.org, please? This might be easier over a slightly more “interactive” medium. Thanks.
Well. Alrighty then. I’m not sure whether to be honored, embarrassed, or horrified! “Thor Code”? I know my problem was a pain in the… tush, but to actually have the fix named in my (dis)honor?
Anyway, I’m happy to report that the “Thor Code” works like a charm. Thank you for your hard work, Mr. ColdForged Dupuis.
I am experimenting with a new company. They put PHP in safemode but if I create a directory and name it a certain name, all files in the folder will run in outside of safe mode. So if the name of this folder is safemode-php. How can your plugin be modified or is it not possible still? Thanks!
Awesome! ‘Bout time we got you sorted out
.
Oy, that’s a tough one, Bink. It might be theoretically possible to get it functional under safe_mode, but it wouldn’t be trivial. The real problem — that I know of — is that the command that I use to perform the work, exec_shell(), is supposedly not available in safe mode. Now, we could use a different type of execution function but then we get to the problem that double-quote PHP replacement is not allowed in safe_mode, so I can’t pass it the name of the temporary file. We’d have to settle on a single file which has some reentrancy problems. Once you got over that hurdle we’d have to have an aspell installation in the safemode execution directory, which is minor if you have control over the machine.
The problem is, I don’t have a safe_mode environment to develop on so I can only theorize possible workarounds. Even if I did have one through the gracious permission of someone that does have an environment, I don’t know that I can come up with a workaround that would function without enormous effort and “hackery”
.
If you’re familiar with PHP development, you’re obviously more than welcome to diddle with the code to try to find something that works as it’s GPLed. If you do, I’d love to know how you did it.
I downloaded the zip file, and it says it doesn’t have a current archive, and won’t let me unzip it. what does that mean?
It means that your unzipper program hates you
. No idea, unfortunately. Try right-clicking on the zip file link and “Save as…” instead of directly clicking it perhaps? Try to tar.gz file and see if WinZip likes it any better? Without knowing more about how you’re trying to unzip the file, I don’t have any better suggestions.
Good luck!
I installed the plugin but I’m running into the problem of it just showing no a blank sheet in the top portion of the spell check popup even though there are obviously misspelled words in the posting. I have verified by aspell information (which aspell returns “/usr/bin/aspell” so I tried both “/usr/bin/” and /usr/bin”) but I can’t seem to get it checking. Any ideas what direction I need to head in? This looks like an awesome plugin, would love to get it up and running.
Matt, which browser are you running? If you’re running IE, can you pull up your page source and tell me what you see in there?
I had .7 running and when I upgraded to .9 I ran into the same errors as Mark.
I also seem to be having the same problem as Mark. I just installed 0.9 and confirmed my aspell path in spellConfig.php. I get the button and when I use it, a blank spell checker window appears even though I purposely mispelled a word to test it.
I am using WordPress 1.2.2 and have tried this from Firefox, Mozilla, and IE browsers on both linux and windows machines.
Are there any permissions that need to be set a particular way?
I have also checked my javascript console and have seen a number of errors:
syntax error (line 13) in spellchecker.php wordWindowObj is not defined (line 81, 115, 117) in spellchecker.php init_spell is not defined (no line or file)
I’m having the same issue as Matt. I verified my ASPELL path (/usr/bin/aspell), and I get a JS error stating:
Line 13: Syntax Error Line 147: ‘wordWindowObj’ is undefined Line 144: Object expected
Also, do you mean to change the $aspell_path in the spellConfig.php/spellconfig.php? Your FAQ says to change the variable in the spellchecker.php file. Is there suppose to be two configuration files?
Shalom.
Hi! Thank you for the great plug in. I have no problem with it at all in my admin. However in comments when you run it, the window comes up and says “Spell check in progress…” but nothing ever happens. I am certain I did something wrong, maybe you might know? Thank you in advance.
Hi its me again, i fixed it thank you! It was a simple mistake on my part. This is a fantastic plug in, you did a fine job, and thank you so much.
I haven’t given up on you folks having problems… I’m right in the middle of a move into a new house. Once that’s done I can see what’s going on in the 0.9 release. Have faith!
It seems like I have the same problem as Ron (or maybe something like it). I press the spell checker button; a pop up appears saying that spell checking in progress. A couple of seconds later a java script error occurs.
So I investigated a little and found this error in the middle of some java script code:
“Warning: fopen(/path/to/my/wp-installation/wp-content/plugins/spell/aspell.personal): failed to open stream: Permission denied in /path/to/my/wp-installation/wp-content/plugins/spell/spellchecker.php on line 67
“
It makes sense; of course my web server can’t create the aspell.personal file. So I created the file /path/to/my/wp-installation/wp-content/plugins/spell/aspell.personal and for some reason I had to write at least one word in it, so I wrote “testâ€. I saved the file and did a:
chown nobody:nobody /path/to/my/wp-installation/wp-content/plugins/spell/aspell.personal
nobody is the web server owner and I needed to change it to allow the webserver to read/write to the aspell.personal file. You can also make a chmod 777 of the file, but there might be some security issues there.
And now it works like a charm. I hope it can help some of you guys out there, it is indeed a great plug-in – and ColdForge: Congrats on you new home
Minor detail, the “Add button” doesn’t seem to work, even after changing $broken_aspell_personal_dictionary to true. But I have decided to not use my personal file
Same problem as Matt..aspell is installed and the configuration has been set properly. I still get a blank page at the top of the spell checking page.
Alrighty guys, all of you that are having the “blank page” problem please give the following a try. Modify your spellConfig.php file and change the location of your personal dictionary to be somewhere that the Apache server has write permission to. For instance if your home directory is appropriate, change the following lines:
$aspell_dict = dirname( FILE )."/aspell.personal";to this:
$aspell_dict = "~/aspell.personal";The “silent failure” will be addressed in the next version of the plugin along with generally improved configurability.
After setting write permission on the spell directory, the spell checker was able to create the default aspell.personal file. However, I then ran into a couple of other errors. I had to remove the aspell.personal file and set the following on the spellConfig.php file:
Then everything worked ok. Great plugin!
I love your spell checker plugin. I am wondering if it is possible to get other languages? (ie Spanish/German/French)?
I suppose it is possible, though the special characters present a unique challenge. By customizing the config I would think it would be possible to get it to work, but I have no way to test my theory.
how do i get a woad
Expect some new hits now that you have hit the autoinstaller.
I just plugged it in, and got the “can’t add words” error, but I’m not too worried.
What I was interested in is how would you go about forcing spelling checks? IOW, you can’t post unless you spell check it. It would cause spammers using auto attacks to get dumped en masse. A human can just ignore it and allow the bum words in. Sure, it won’t catch trackback spam, but it could thwart comment spam. Or, it could force honest words, thus making blacklists and Bayesian filters more effective.
Hmm, just figured out that that would cause a problem for those who can’t use JS (Like my wife. Long story:)
BTW, you’re tossing some extra space before headers somewhere. Errors when I post a comment.
I’d be happy to help you track down what’s going on there if you desire.
Seems like it should be possible. Maybe some Javascript to insert the Submit Comment button only after the spell checker returns.
Now With Spell Checking
Medicated Dad, now with spell checking.
(Hrm, but not on the ‘Blogit’ bookmarklet. Gotta go find that template) …
Blacklist plugin is misbehaving for some reason. Thanks for the heads up.
I’ve heard lots of people with getting extra spaces because of the Blacklist plugin. I think it’s either an extra or missing carriage return at the top or bottom of the list.
Oh my, I’m embarassed to ask this, but…how does one install aspell anyway? I went to their site, downloaded, expanded, stuck the files in the /usr/bin directory, and, as root, typed in./configure && make and got an error.
can anyone guide me to a resource for non-admin types on how to get this going?
TIA!
Jeff
Jeff,
What sort of error are you getting? Are you hosting this on your own machine or at some provider? First thing you may want to do is go to the command prompt and type “aspell” and see if the program is found. Or type “which aspell” to find the location. It might already be there.
If you are using Linux, and it is your machine, use your distribution’s package manager to install it.
I might be able to help you at: gmhowell (at the provider I use called) gmail.com
Actually in the latest version that’s the way the plugin auto-detects the executable. In future versions I may have a backup plan for those hosts that don’t have appropriate paths set up to search in various likely places for the executable.
George has some good points. If you can be a bit more specific on what you’re experiencing, we might be able to get you going.
I could never get anything higher than .7 to work, which is what I am still working on. I just upgraded to 1.1 and almost everything seems to be in order, except I get:
Line: 42 Char: 3 Error: Permission Denied Code: 0 URL: http://../../spell-plugin/spellchecker.htmlIt is probably something simple that I missed, but any help would be appreciated.
That sounds suitably odd. First, what version of WP are you running? Second, if you go to your WordPress options, what are the values for WordPress address (URI): and Blog address (URI):? Also, for 1.1 the installation changed in terms of heirarchy… did you install everything in the right place and then remove the old “wp-content/plugins/spell/” directory?
We’ll sort this out, I have no doubt
.
I am running Word Press 1.5-beta-1 2005-01-04. I corrected the WordPress address (URI): and Blog address (URI): (I recently moved it to the root of my site), and now I get:
Error executing 'usr/local/bin/aspell -a --lang=en_US --personal=/home/rjcarpen/public_html/wp-content/spell-plugin/aspell.personal< home/rjcarpen/public_html/wp-content/spell-plugin/aspell_data_H5YAwJ2>&1'and
Error: The language "en_US" is not known. This is probably because the file "/usr/local/bin/share/aspell/en_US.dat" cannot be opened for reading.Ha-ha! Much better. Now, change the “language” option to be simply “english”. I bet you’ll have better luck!
I changed the language to “english” and get the same result, except it calls for the english.dat file. “en_US” is what I use with v.7.
Well, hell. Do you have shell access by any chance?
Since I am not sure what that is, I am guessing not.
Hmm. I guess try “en” as the language. Somewhere, somehow there has to be a language that works appropriately.
That seemed to do the trick. Thank you!
My server administrator says that Aspell is outdated and not recommended. It is not installed on the server. We have Pspell. Will there be a future version using Pspell? How do I get stated converting to Pspell? Are there many functions and parameters to change?
That’s mildly humorous since pspell has been deprecated — the latest version was made in 2001 — and aspell is under continual development with the latest version released in December of 2004.
I don’t know what the difference is between pspell and aspell and I don’t have any pspell installation. I will investigate, though.
I seem to be having the same “Failed to add x words to dictionary problem”
I tinkered with permissions on my personal dictionary but no luck. Perhaps you know something else I can try?
Three things:
Let me just ask one more thing, Ted. Is this “we have pspell” as in the pspell PHP calls? In other words, the built-in PHP functions when you compile PHP with the pspell libraries? Such that “pspell_check” and “pspell_suggest” work? If that’s the case then I could see ways of doing it. Unfortunately my hosting provider doesn’t support pspell support so I have no way of running in such an environment.
Yes. I was referring to the Pspell PHP functions (Aspell functions are deprecated) and to add confusion, one version of the aspell library was called pspell. I see that you interface with the aspell library by calling unix command-line shell scripts because you can not access Pspell PHP functions. I have WordPress 1.2.1. I installed the Spellng Checker, set the options and get a “Check Spelling” button; but when I click the button nothing happens.
I installed the plugin and ran the setup link which showed everything was OK. When I tried to “Check Spelling” I get an “Error: ïQ”. I tried the aspell command in a shell and get the same error. If I remove the –personal it works fine. Is there a way to remove the personal dictionary from the call (I’m not sure what file[s] I would have to change)? I’m using WP 1.2.2 with aspell 0.50.5 and lang en_US. Perhaps my aspell version is the problem? Thanks.
Yes, some versions of aspell may indeed have problems with personal dictionaries. And yes, it’s relatively easy to disable the usage of the personal dictionary. For now, let me tell you from where to remove it. Later, I will include an option in the administration screen to disable usage of the personal dictionary for those like you that have difficulty. Thanks for letting me know.
So, edit the file “wp-content/spell-plugin/spellchecker.php”. Find this line, currently line 68 (note that I had to split the line to fit this format, but it’s one line):
and change it to be like this:
(Ignore the goofy backslashes… such are the joys of trying to get pretty code in comments.)
Okay, I got you. Phew! That makes sense. Yes, in investigating the interesting history of aspell/pspell it’s amazing we wound up with anything at all. Who could keep up with all that ambiguity?
Yes, it’s entirely possible to utilize the PHP pspell functions. However, it is — as you’ve discovered — a fundamentally different method of use. It does give me hope that this is a possible fix for the PHP safe mode people… if they’re running in safe mode, maybe they have the PHP pspell functions.
The only problem is that my hosting provider doesn’t have pspell included in the PHP installation. Hence, creating and testing any pspell version will be impossible. That’s something I don’t quite know how to get around right now.
Great plugin. A feature request though. Is it possible to make the words in the personal dictionary case insensitive? Because right now:
Exampleword != exampleword
My host is running the following aspell if it matters:
[vex]$ aspell –version @(#) International Ispell Version 3.1.20 (but really Aspell .33.7.1 alpha)
Thanks.
Great plugin. One problem though: when served as application/xhtml+xml it fails, and in standard browsers like Firefox, it won’t load.
Hi, I get the following issue;
Auto-detected the aspell executable. Using “/usr/bin/aspell”.
FATAL: The aspell executable could not be found in the location specified (/usr/bin/aspell). Please fill in the correct path to the aspell executable below. You may need to ask your hosting provider for this information if you do not know where it resides.
While here is the aspell binary;
root@fred [/usr/bin]# ls -al|grep aspell -rwxr-xr-x 1 root root 89392 Jan 24 2003 aspell* -rwxr-xr-x 1 root root 59 Jan 24 2003 run-with-aspell*
Help please?
Okay Bob, I admit it… I’m stumped
. Is it possible that the Apache process — or whatever userid PHP files are executed as on your server (which you seem to own if you have root access) — doesn’t have read/execute access to the /usr/bin directory? That’s the only thing I can think of at this point.
I’m having the same problem as Bob. I have access to aspell through:[1] /usr/bin/aspell /usr/include/aspell /usr/lib/aspell /usr/share/aspell
Yet I receive this: Auto-detected the aspell executable. Using “/usr/bin/aspell”.
Auto-detected the language. Using “english”.
FATAL: The aspell executable could not be found in the location specified (/usr/bin/aspell). Please fill in the correct path to the aspell executable below. You may need to ask your hosting provider for this information if you do not know where it resides.
I do have access to it, as another script I have works.[2] Thanks in advance for any help!
[1] http://www.lunarforums.com/forum/viewtopic.php?p=181767#181767 [2] http://simplewebdev.com/spell/spellcheck.php
Alright guys, I think I’ve figured it out. Please try version 1.12 and see if it helps you.
Just installed 1.12 as I am using WP1.5. Followed the directions, that didn’t work. Then used One Click Installation from Plugin Manager.
No spell check button showed up anywhere and I am unable to change the directory that aspell is located in.
The error is: FATAL: The specified aspell executable (/usr/bin/aspell) is not executable, meaning the web server process does not have execute permission. Either use a different aspell location or give the web server process permission to execute it.
I have changed the path by FTPing the file to my local system and using a text editor, vi in an SSH, and by typing the path into the setup system. None of these holds…as MAGICALLY, even though the perms were set to ’777′ for ALL files associated with this plugin, the path is changed back to /usr/bin/ while I have been typing in /usr/share/.
Someone please tell me what it is that I am missing?
Also, is it up to me to ADD the button to spell check? That certainly isn’t in the documents anywhere. When I check the code (spellInclude.php) it only has a check to see if it (WP) is 1.0, 1.1 or 1.2. Why isn’t it checking for 1.5?
The fix that I put in for the open_basedir problem with PHP apparently isn’t enough and you are the first person to report the follow-on problem, which is that the “is_executable()” function won’t work outside of open_basedir either. Hence, version 1.13 that gets rid of both checks. Serves me right for trying code in something to help people track down their executable, no?
No, it isn’t unless you want to add a button to your comment form. In which case the instructions are in the install instructions on the main plugin page.
Basically you weren’t getting a “Check Spelling” button because the plugin was not convinced it had a valid executable due to the aforementioned “open_basedir” crap. Hence, to avoid confusion, if it didn’t have an aspell executable it wouldn’t display a button for a feature that it felt wouldn’t work anyway.
Now I just get to try to support the ones who get a spell button but it doesn’t work because they don’t have aspell installed. Yay.
Punk rock! Thank you, thank you.
I’m kind of stumped. It’s been quite a while since I went through getting the plugin installed the first time around, and I forget everything that had to be done for my atypical install. Just think, I even had some code named after me ;-/
I recently went to update spell-checker, and now as soon as I copy the “spell-plugin.php” file into your “wp-content/plugins” directory, my site goes belly-up, with the following error messages:
“Warning: main(/usr/www/users/tfarrow/thorfarrow.com/journal/wp-content/spell-plugin/spellInclude.php): failed to open stream: No such file or directory in /usr/www/users/tfarrow/thorfarrow.com/journal/wp-content/plugins/spell-plugin.php on line 36
Fatal error: main(): Failed opening required ‘/usr/www/users/tfarrow/thorfarrow.com/journal/wp-content/spell-plugin/spellInclude.php’ (include_path=’.:/usr/local/lib/php’) in /usr/www/users/tfarrow/thorfarrow.com/journal/wp-content/plugins/spell-plugin.php on line 36″
I did follow the instructions… honest, I did!
Oh. My. Gawd. I’m so, like, SUCH a doofus. Tch! I swear I read the instructions more than once! I’ll blame the fact that I read, but didn’t comprehend, on my new meds. And yes, they’re prescription.
Sorry Brain.
Oops! I meant Brian! See what I mean about my new meds?
SpellBound
SpellBound is a spell checker for Firefox. It enables spell checking in web forms such as html textarea / input elements. This is something I really needed as I’d been relying on 3rd party document editors for spell checking previously. It works almo…
Hey there. I tried to install your fab plugin, but I got a blank window when I tried to go to the ‘speller_setup’ thing. I then looked in my directory, and there is no such file. I checked the .zip file, and there was no file. Also I assume it is a consequential problem, but I get a blank page when I try to post. I tried following your ‘FAQ 1)’ but I have no idea what it says, it’s so far over my head! Please help, and thanks very much in advance!
PS, also when I just posted that comment, Spam Karma popped up and asked me to type the characters in, but there was no picture to type from. Just thought you might like to know!
Sproke,
Probably the easiest way to install the plugin is through the WordPress Plugin Manager… that way it’s a simple One-Click install and you don’t have to worry too much about incorrect paths and such.
The install should look as follows:
Make sure those two things are correct and see where you stand.
Thanks for the heads up about the CAPTCHA.
Well do I feel Dumb! I completely missed that part in the instructions. I’m sorry to do that to you! Now I’ve just got another error coming up, but I’ll address that another time… have an exam tomorrow! Thanks for this wicked plugin!
Hey there Coldforged. I’ve finished my exam, and I’m keep to get your plugin working! I’m using WP 1.2.1, and the button is in place fine. However when I ask it to check words it comes up with this message “System Error: Aspell programe excecution failed (‘usr/bin/aspell -a –lan=en_US –personal =c:\domains\ordinarylife.co.nz\wwwroot\blog\wp-content/spell-plugin/aspell.personal &1`) “
It seems to be a smiliar message to what Ron was getting (reply 28&32) though the message is a little different, with the ‘c:\domain’ thing which seems to be slight variation of the path to the aspell file.
Help please! http://www.ordinarylife.co.nz
Eek, Sproke, looks like you’re installing on a Windows host. Is that possible?
Unfortunately, the plugin is dependent on being in a Unix environment with the aspell Unix executable. If that’s the case, sorry!
Just a heads up but the latest nightlys do not have auth.php in them. This makes it impossible to add words via the checker since auth.php is missing. The only way to add words at the moment is through the plugin interface.
Gah! Thanks for the info, cavemonkey50… will look into. Damned nightlies!
Hi – was told my checker had an error too. Using CVS from Friday night (I think) and I se this message:
“Error executing
/usr/bin/aspell -a --lang=en_US --personal=/home/virtual/site95/fst/var/www/html/T2/wp-content/spell-plugin/aspell.personal &1/usr/share/aspell/en_US.dat: The required field “name” is missing.”My plugin are listed here: http://www.tamba2.org.uk/T2/about-t2/
but it’s more of a “found an issue” post here rather than an Help!
I LOVE the horizontal details … mind if a copy that ?
Damn it, I’ll have to add that to the FAQ it comes up so often. I really thought it was here, but I guess it’s just on the WP support pages and such
.
To answer your question, that occurs when the language setting is not correct for your aspell installation. My suggestion would be to try “english” first and if that fails just plain “en”. You set that in the WordPress Options => Spelling Checker page.
Thanks!
Of course not, take whatever you want. We all get ideas from everywhere, right?
I downloaded the updated plugin and now the addition of words works fine. Thanks for the speedy update. B.T.W. Your ZIP file is missing. I had to download the TAR.
Thanks for the notice… created it.
After upgrading to 1.5 Strayhorn it seems that it’s broken again. using release 1.14 everything is installed as per the instructions yet the spell check page comes up blank in the top frame (spell check controls in the bottom)
I’m not seeing that behavior, Mike. Not in my clean 1.5 Strayhorn sandbox install or in my upgraded install you’re seeing here. Can you do it in IE and do a “View Source” in the upper frame and see what it says?
oops! sorry, looks like it’s on my end. aspell isn’t executing.
Works like a charm. Just wanted to say thanks.
Doesn’t work if your blog is in a subdirectory. You’re using bloginfo(‘url’) when you should be using bloginfo(‘wpurl’). It works only because sometimes those settings are the same.
Thanks for the heads up, new version available.
This may be something completely out of your control, but on the edit comment pages the check spelling button appears on the very bottom of the page, under the Firefox and other stuff. This also appears on the delete comment pages even though no editing takes place on that page.
I get a slightly different error during a spell-check:
“Error executing `/usr/loacl/bin/aspell -a—lang=en_US—personal=/home/invisine/public_html/weblog/wp-content/spell-plugin/aspel.personal &1′ Error: No Word lists can be found for the language ‘en’.
It also occurs if I use the default en_US. Any ideas?
I also noticed by looking at my PHPInfo page that my host has PSpell installed, but nothing for ASpell. They are essentially the same thing, are they not?
There is a major bug in spell-plugin.php in 4 places. bloginfo(‘url’) aka get_settings(‘home’), the blog URL, should be bloginfo(‘wpurl’) aka get_settings(‘siteurl’), the wordpress program directory. I made these changes and it works great. A fantastic plug-in!
I just saw a previous post on bloginfo(). What you need to write now is a grammar checker in multi-languages. Just kidding.
All I keep getting is a blank page when I attempt to check the spelling. I checked the error log in the spell-plugin folder and I keep getting this:
PHP Warning: shell_exec() has been disabled for security reasons in /home/nick/public_html/wp-content/spell-plugin/spellchecker.php on line 95After doing the one-click install via wp-plugin-mgr everything seems to go ok, however when I try and goto the config page spell …plugins/spell-plugin.php?speller_setup I get a 404 Page Not Found error. The file has 755 permissions and does exist, as I can goto ..spell-plugin.php and it loads a blank page. Any ideas?
If you have control over the php.ini configuration file, search for the “disable_functions” setting and remove the shell_exec function from the list. If you don’t have control over it — which is likely in a shared hosting environment — there’s not much to be done. It may be possible to get it working using something other than shell_exec, but I don’t currently have the spare time to experiment with it. If you’re bored…
Interesting. First, I’m assuming you’re on WordPress 1.5 Strayhorn. Second, I’m assuming you’re on version 1.15 of the plugin. If neither of these is true — actually just the plugin version — make it so… there’s a fix in 1.15 that may be directly affecting this. There’s a redirect for 1.3/1.5 that tries to load get_settings(“wpurl”) . “/wp-admin/admin.php?page=spell-plugin.php” when you bring up that page. Double-check that your wpurl option is set correctly.
Try “english” as the language.
This plugin does not use the built-in pspell functions of PHP but rather executes the aspell Unix executable from a shell and parses the results. Why that way? Twofold: one is the pspell-enabled PHP installations aren’t very common and the second is that my host is one that doesn’t support it so I have no environment to test in.
Not out of my control at all and will be fixed in the next release. Thanks for bringing it to my attention.
EDIT: I spoke too soon… there’s no ‘id’ on the Edit Comment button, so I can’t locate the element like I do the other ones. Yes, I could special-case it and do some other search, but I’d rather wait until WordPress is fixed so that there isn’t a hideous hack necessary. Filed a bug on WordPress with a patch so hopefully it will get in soon.
I enabled shell_exec in my php.ini file, retarted Apache, and VOILA! A different error message now. I just had to change my language to English for that one though.
Great plugin!
Awesome! I was afraid I was going to have to do some experimenting with new functions to get you up and running
.
I just upgraded to WP 1.5 last night and the spell checker stopped working. I tried deactivating, removing and reinstalling but it still isn’t working. I can get to the spell checker options w/out a problem. Nothing happens when I it the check spelling button. If I look at the error log in IE or Firefox this is the error:
Error: spellChecker is not defined Source File: http://techory.com/blog/wp-admin/post.php Line: 42
I currently have the spell checker running on another wp 1.5 blog on my site w/out any problems. I think it’s an older version of the plugin though. Is there anything that would cause this to happen? Remnants of a the previous install, or weirdness due to the version update?
Hmm, I don’t get that problem.
I’m getting the same Java console error that Scott reported above, for both the main post writing spell check:
Error: spellChecker is not defined Source File: http://blog.gpiper.org/blog/wp-admin/post.php Line: 53
and for the comments spell check:
Error: spellChecker is not defined Source File: http://blog.gpiper.org/blog/index.php/2005/02/19/changes-in-progress/#comments Line: 153
Ideas?
TIA, -ghp
Just to throw in my two cents, I’m seeing the same error as Glen and Scott. “spellChecker is not defined” I’m running Firefox 1.0 as a client, and WordPress 1.5 on an apache server
Alright guys, looks like the saga of the ‘siteurl’ versus ‘wpurl’ is destined to not end. Those of you — Tom, Glen, and Scott — having problems could you please look in your Options and tell me what you have for the following values:
That should help me settle this once and for all. Thanks guys for the help and reports and hopefully I should have this nailed in the next release (tomorr… err, today if I can get some good info).
I’m getting the same error as Tom, Glen, and Scott. Here’s my info based on your comment (180):
WordPress address (URI): http://www.thelevys1.com/wordpress
Blog address (URI): http://www.thelevys1.com/wordpress
complete path to spellchecker.js: “/srv/www/htdocs/wordpress/wp-content/spell-plugin/spellchecker.js”
complete path to web root: “/srv/www/htdocs”
Hope this helps.
WordPress URI: http://techory.com/blog Blog Address: http://techory.com/blog Path to spellchecker.js: /home/techory/public_html/blog/wp-content/spell-plugin/spellchecker.js Web root: /home/techory/public_html/
Thanks!
Cool plugin! It worked well once I updated the permissions of the plugin folder.
Might be nice to have an option to switch language in the spelling pop-up.
Thanks for the info, guys. I believe I have it fixed… go ahead and update via whatever mechanism you prefer.
Whatever you did worked! Thanks for the help and the great plugin!
It works here, too!
Thanks for the quick fix/update, ColdForged — you & your plugin both rock!
-ghp
That’s great news, guys! Glad I could get you sorted out.
Same error, but now the error reads like this (with english being truncated to ‘en’):
“Error executing `/usr/loacl/bin/aspell -a—lang=en_US—personal=/home/invisine/public_html/weblog/wp-content/spell-plugin/aspel.personal &1’ Error: No Word lists can be found for the language ‘en’.”
So en_US, en, and english do not work. Any other ideas? I do have a email in to my hosting provider as well but their response to an earlier question was the the dictionary was en_US or en_US-w_accents. Both are truncated to ‘en’ and throw the same error.
Robert, have you tried enabling the option that says “Enable manual personal dictionary handling for broken aspell installations.”? Try that one and see if you get any further.
I did try that with the same result.
I did track it down in th code so I know where the error is being thrown.
It looks to me like whatever is being returned by the call to aspell is being assumed as error output.
Like, duh.
No, I have tried all – all come back with the same error.
I did take the variable $chardesc and replaced $val in the error trap and the retured value was the letter E – that’s it, nothing else. I would assume that is an error.
I am somewhat familiar with PHP. If you have some debugging code you would like me to put into this function, I will be more than happy to. Maybe we can at least rule out the installation.
I do have an email into my hosting provider. This is what they replied with as to what the settings were:
language-tag current: en_US local-data-dir current: /usr/local/bin/aspell/
No shell, BTW.
I can’t find english aspell on my server. When I search for aspell on the server it just come up with aspell in Vietnamese, Hebrew and lot’s of other languages which I am far from fluent in
.
So I sent a mail to my host and they came up with that ispell -d english was there and worked, and if I really needed aspell.
My question therefor is, can I use ispell -d english or do I have to send my host a new mail and ask them if they could install aspell in the near future?
Well Sean, you can try using it by setting the aspell path to be the complete path to your ispell executable, but I seriously doubt that the parameters I pass in to aspell and the format of the return information will match what’s expected, nor would I be able to provide much guidance about what you should be passing in to ispell. If you’re bored or brave you can diddle with the parameters in the ‘wp-content/spell-plugin/spellchecker.php’ file (search for the line that starts with $aspell_opts in the print_checker_results() function). Make sure to turn on the aforementioned “Enable manual personal dictionary handling for broken aspell installations” option so that I don’t try to get aspell to add words to the personal dictionary.
That said obviously your best bet if you want to avoid pain and suffering would be to talk your hosting provider into installing aspell
. Good luck!
Doesn’t work in PHP-CGI mode, so I had to sacrifice it to get Exhibit working again. sigh …. and, how come my trackback didn’t work on here! heh
I installed the plugin, now I cannot “write” or edit a post
Help!
I have installed, deleted, reinstalled, ect.
Thanks for helping me get my problem fixed. Seems it was a “ME” problem and not a plugin problem.
First, I want to say thanks for the plugin. Glad you created it.
I installed the plugin, and did everything the directions said. I changed the permissions on the spell-plugin folder to 755. It is located in the wp-content folder. However, I keep getting the following message:
FATAL: The temporary directory you specified is not writable from the Apache task. Either select a different temporary directory (like “/tmp”) or make the directory you specified writable by the Apache task (chmod 755 the directory).
For grins, I changed the permissions to the folder to 757 and the fatal error messages went away. Any ideas as to how I can address this?
TIA
Are you having problems with the plugin now? The intent of the error — aside from the suggestion to chmod 755 — was to explicitly say “change the permissions so that the Apache task can write to the directory using whatever permissions are required in your environment.” It sounds like your web host doesn’t run PHP scripts as “you”, hence they run as Apache’s UID. You’ll therefore need to allow “others” to write to the directory as you tried with the 757 permission. As long as it works, this shouldn’t necessarily be a problem.
Whoa! That was quick!
But would not that be a major security concern to allow write and execute privileges to that directory?
Thanks again.
Someone would have to know that that directory existed and that it was writeable, but yes it could create problems. That’s why you have the option to change which directory you wish to store the temporary files and personal dictionary. That way you can have one directory somewhere in your installation that is writeable by anyone but that doesn’t contain anything else of value. Oh, and you certainly don’t need to provide execute privileges by any stretch… that was primarily for installations that run PHP scripts as “you.”
I just installed on a 1.5 install that is on a debian sarge machine. When trying the plugin I got a javascript error about “error: ?|x&uange ‘en_US’ is not known”.
When I try running the same command from the command line I get the following (running as sudo and non-sudo):
laurelpoint:/var/www/howellcottage.org/blog/wp-content/spell-plugin# sudo -u www-data /usr/bin/aspell -a –lang=en_US –personal=/var/www/howellcottage.org/blog/wp-content/spell-plugin/aspell.personal
Error: Ø °uage “en_US” is not known. This is probably becuase the file “/usr/share/aspell/en_US.dat” can not be opened for reading
Any suggestions?
Try “english” or “en” for the language parameter.
Changing to “en” was the fix; sorry for having to bother you about it. Thank your for the hint for fixing the problem.
FYI, the version of aspell that comes with Debian Sarge is currently 0.50.5-5. In addition the plugin was not able to spell check the HTMLArea 3.0RC1 based editor that I had installed (WP-HTMLArea by Akmal H AK ). The plugin does not seem to be available for download anymore, so maybe that is not a big problem and I should just look for an alternative.
Again, thanks!
My host does not current support aspell, but they told me that I could have a shot at installing it. Is there a particular version of that program that I should download (I need a compiled version), so that I can put it in the appropriate directory?
Bud, I imagine that the latest version — looks like 0.60.2 — that you find here would suit just fine. I’d be curious to see how you make out so keep us abreast of how it goes.
The method you are using to display the options page is an outdated one from the early 1.3 code days (the
is_plugin_page()method), and it breaks many 1.5 plugins that use the new method. You should probably update to fully support 1.5, since 1.3 users are on their own.What is a plugin that it breaks, Mark? I’d be curious to see what the effect is.
I’m torn about this because I was using the new method on the Paged Comments plugin but found that it was broken on a default 1.5 install and would only function reliably on 1.5.1. Granted I’m doing something moderately to completely funky with it, but it still worries me.
I am having troubling installing on 1.5. I saw that you fixed the directory issue in 1.5, but it’s still not working. First, it can’t find the spell-plugin folder on the spellInclude file, and then it can’t find the wp-config file.
Make sure you have everything installed in the correct directories:
spell-plugin.phpneeds to be in thewp-content/pluginsdirectory.wp-content/spell-plugin.Ah…got it. You’re a stud.
You speak heap big truth there. Glad you got it running.
Have installed the plugin and it’s great. However it doesn’t work too good with wysiwyg plugin (it will find misspelled words, but it won’t change them). Since spell check works well when the wysiwyg plugin disabled, I sought advice on their site and got a great solution for an “on/off” switch for wysiwyg from Josef WO. His solution is here:
http://wordpress.site.cz/wp-filez/wisihack.txt
I don’t know the call for how the spell checker is activated/de-activated, but is there a way to add something to that hack so that when wysiwyg is turned on, then spell check is turned off? And conversely, when wysiwyg is turned off, then spell check is turned on?
Basically this would just clean things up a bit for me so that the spell check button is not there when I am using wysiwyg.
Thanks
Here you go, ronzo… stick it in about the same place:
ColdForged,
Thank you!!!!!
I did make a few changes though. Since I wanted the spell check to switch on or off at the same time as the wysiwyg, I added a body onload javascript command at the top of the page to turn spell check off, since my write page by default starts with wysiwyg on, and also placed the javascript code at the top of the page.
Then I deleted the spell on and off buttons, and added the spell on and off commands to the wysiwyg commands. Now I have just one set of buttons to control both wysiwyg and spell check at the same time.
if you want to see the codes go here: http://www.sandybay.org/wordpress/on_off_hack.txt
Thanks again ColdForged, you made my day!
Now if I can only figure out how to turn Quicktags on or off at the same time with php or javascript – they don’t work in wysiwyg mode, but do work when wysiwyg is turned off.
Is it possible to use this without the use of shell_exec? It seems that many cpanel hosts have this function disabled for security reasons????
There must be another way to implement this…
Please let us poor cpanel users know
Thanks!
I’ll put it in the list of enhancements, Philip. There may be another way to get the needed functionality.
That bug in WP which made it that you couldn’t find the spot to put the check spelling button has been fixed in the latest nightlies. Could you add the quick fix so us users who are running the nightlies can enjoy the fix? Thanks.
Hi Coldforged,
I finally figured out how turn the Quicktags on or off, using javascript and css.
It took a while, but I sure learned a lot! I updated the link above in case anyone wants to see how I did it.
cavemonkey, I sure will. It’ll be in the next release, which will be sometime soon.
Nice work, ronzo. Sorry I didn’t read your question well enough to put it in a more appropriate format. Though sounds like you had fun learning as you went
.
cavemonkey, new version has been released with your change.
Thanks for the update.
Hey sorry to bug you again but on the confirm comment delete page the spell check button appears on the bottom. There is nothing you can edit on that page besides confirming the comment deletion, so the spell check button should not be there.
Hi. I love your Spelling Checker pulgin. I just installed it and it works great except on several posts I get a “error on page” message. I have no idea what is causing this. any ideas?
Unfortunately, without additional details it’s a little hard to determine the cause of your problem. What browser are you using? Does a different browser report other details (e.g. try IE if you use Firefox or vice versa)? If you use Firefox, which Javascript error is reported in the Javascript Console?
Hi ColdForged,
Thanks for writing this plugin. I’m excited to use it.
Like Sphinx7 above, I was uable to configure the plugin for the first time until I chmod’d wp-content/spell-plugin to 757.
In response to Sphinx7, you wrote:
Someone would have to know that that directory existed and that it was writeable, but yes it could create problems. That’s why you have the option to change which directory you wish to store the temporary files and personal dictionary. That way you can have one directory somewhere in your installation that is writeable by anyone but that doesn’t contain anything else of value. Oh, and you certainly don’t need to provide execute privileges by any stretch… that was primarily for installations that run PHP scripts as “you.â€
I tried to change the directory for the temp files, but even after chmoding that directory to 757, it didn’t work. The plugin only works for me if I have wp-content/spell-plugin as 757. (when I tried to take out the execute permission, I got an error message)
Leaving that folder as 757 makes me a little uncomfortable. Should I be worried?
Matt,
You can move your temporary anywhere that the web server process can write to. In fact, if your hosting hierarchy has the web root in a subdirectory of you home directory, you can make your temporary directory be a subdirectory of your root. For instance, if your home directory is
/home/matt, create a directory calledtmpin your home directory, change permissions appropriately for your installation which should be either 757 or 755, and set the temporary folder to/home/matt/tmp.This has the advantage of being unaccessible from the web server, meaning someone can’t type
http://www.mattsweb.com/tmp/somefileand load it.Thanks, coldforged. I’ve got it working now, and have the 757 folder above my public_html directory. I tried to do that before, but it didn’t work–I think I wrote the link (/home/matt/) incorrectly.
But now I’ve got the plugin going, and I feel safe. Thanks for the plugin and for your quick response. You rock!
The script is kind of working for mer … i get funny ? marks when i use a Swedish dict. (sv) this is with Ã¥ ä ö signs … think i have same problems as the guy in post 1
Yes Henrikf, that’s a limitation in the original Speller Pages project on which this is based and I know of no workaround. My apologies.
I just asked my ISP to configure their php –with-pspell, which they did, so I could install the spelling checker plugin on my new WordPress installation, only to discover that you use exec and so won’t work in safe mode.
Actually, since we run with exec_dir or whatever it is called set to “.” I may be able to work around that by putting a soft link or shell script with the name of every command that you exec into my wordpress directory. Safe mode doesn’t prevent exec calls, it just alters them to be prefixed by the exec_dir. So as long as ./foo does the right thing, an exec(“foo”) will work.
But even better would be to work with pspell without such kludges being necessary. Would access to a machine with pspell help you? Would you accept code contributions from someone who has pspell to test with?
Yes to both, actually. If you’re comfortable with PHP and wish to take a whack at it I would absolutely accept a contribution back into the base plugin for all those who have pspell installations. A pspell implementation would obviously be “cleaner” than the existing shell_exec method that’s so fragile in its needs in regards to safe mode and strange aspell installation issues.
As I mentioned up in comment 132, my own installation doesn’t support it. Having access to a test bed would be invaluable in getting the functionality up. Collaboration would also be a possibility.
Can we go to email on this? I can handle the PHP, but won’t have much time for another project during the next few months. It may be best to find a way for you to have access to my WP installation which is still just something I’ve set up for test purposes.
If you can’t see the email address I use to post this, you can find it on my home page at the URL I entered.
I got the plugin to work in safe mode! It would be better to get it to use pspell, and I intend to look at that, but in the meantime, I posted the details on my weblog.
You should be able to incorporate the few changes into your code to make it compatible with and without safe mode.
Can you please help me? I have 7 or 8 weblogs on my site and today the spell checker stopped working on all of them! I put the brand new spell checker on just one weblog (my own) to see if that helped. It did not. Below is the error message I got from my own weblog. All the others are similar. Note I changed the “en_US” to “english” to no avail.
Error executing ‘/usr/bin/aspell -a–lang=english –personal=/home/patrick/public-html/weblogs/wp-content/spell-plugin/aspell.personal &1′ sh:line 1: /usr/bin/aspell:permission denied
Thank you in advance. I should point out that all spell checkers worked perfectly until today.
Very easy to correct XHTML compliance problem:
The attribute “onClick” isn’t valid in the input tag.
The solution is to replace onclick for onselect in spell-plugin.php:
input type=”button” value=”Check Spelling” onselect=”openSpellChecker();” /> [...] input type=”button” value=”Check Spelling” onselect=”openSpellChecker();” />
Thanks for the plugin!
P.D. 1 It is possible to let the user choose the language of the spell checker in each post/comment? P.D.2 Sorry, but I didn’t found how to insert blocks of code in the comment
Very easy to correct XHTML compliance problem:
The attribute “onClick” isn’t valid in the input tag.
The solution is to replace onclick for onselect in spell-plugin.php:
input type=”button” value=”Check Spelling” onselect=”openSpellChecker();” /> [...] input type=”button” value=”Check Spelling” onselect=”openSpellChecker();” />
Thanks for the plugin!
P.D. 1 It is possible to let the user choose the language of the spell checker in each post/comment? P.D.2 Sorry, but I didn’t found how to insert blocks of code in the comment
I have it installed and I have no errors but when I purposely misspell a word, no misspelled words are found. This kind of defeats the purpose.
I’m installing on a Windows box with Apache 2.0.53, PHP 5.0.3 and WordPress 1.5.
I get the following error: “System error: Aspell program execution failed (‘path_to_aspell/aspell.exe -a –lang=en_US –personal=path_to_personal/aspell.personal &1′)
I’m a bit confused…
kazanjig, the plugin is only supported on Unix hosts. Sorry!
Hello,
Just a little suggestion. Enable user to configure multiple aspell languages and select them on the “Check Spelling” dialog.
Aspell Language Setting Ignored? Hi! I’ve set the aspell language to de_DE on the options screen. However, the plugin actually uses the English language for spell checking. (It only proposes English words.) My web host has installed both, aspell-de and aspell-en. Any ideas what’s going wrong? Regards, Christian
Likely won’t happen because it’s a fundamental change in the operation of the plugin. Once the spell check has been done there’s no more communication with the server (with the exception of the add word functionality). Providing that ability would mean coming up with new mode of operation that allows rechecking of spelling, meaning a new server query and subsequent parsing and field population. Aside from not having a multi-language aspell installation to test on, I also have very little personal incentive to work on it — I wanted a spell checker so I wrote one, I don’t need a multi-language one
— when there’s a ton of other stuff going on. Sorry!
Is there any possibility that there’s a different path to the executable for the German version? Do you have shell access to your hosting provider? If so, you can try running aspell from the shell with a language setting of de_DE and see if it does the same behavior.
I’ve downloaded and installed manually as the One Click Install gives me the following error:
Warning: exec() has been disabled for security reasons in /home/public_html/mule/wp-plugin-mgr.php on line 459 This package does not contain a plugin file (might be a standalone script) Please click here to see the directions for this plugin and proceed with additional install steps if necessary.
After I install it manually I get massive errors when I run the setup can and then it kill my whole wordpress installation until I remove all traces.
Stephen, sounds like your hosting environment is not a loving, nurturing place for advanced WordPress plugins
. Sorry, if
exec()is disabled, I know the stuff the spelling checker does will cause problems. Looks like you’ll need to find another alternative, like Spellbound… it won’t let you turn on spell checking for your commenters, but it will for yourself.Is there any plan to attempt a work around php_safe_mode?
I have the Firefox speller plugin, so it’s not really a major, but I have come across an increasing number of web hosts switching on safe mode in an attempt to keep php scripts under controll (most likely we can thank spammers for that).
My webhost has recently switched servers, and they have enabled safe mode.
Following on from my previous post, I upgraded my version of WordPress and re-installed spell checker. It seemed to install fine, however when I hit the “Check Spelling” button the pop up window gives me and Internal Server error plus a 404 not found error .
I then changed the permissions on the spell-plugin directory and the spell checker popped up after briefly flashing a 404 not found error, then the checker didn’t couldn’t to find a dictionary. Is there something I’m missing here?
Brendan, I did workaround safemode, as I mentioned in comment 236, with details in this entry on my blog. The changes I made are compatible with running not under safemode, so I think that ColdForged could put them into his version, and maybe feed it back to the original Speller Pages project.
The only limitation of my changes is that you have to be able to exec a shell script in the current directory (which is the wp plugins directory). Some ISPs may not only run safemode but also restrict exec more than that.
Stephen, where did you install the plugin files?
Sidney, I totally forgot about your safe_mode workaround! I read your comment here but that was a busy period and I totally neglected to follow up. I’ll take a gander at what you did and see if it can’t be rolled into the plugin. Awesome work!
I installed the files as instructed in the readme_install.txt:
Copy the “spell-plugin.php” file into your “wp-content/plugins” directory. Create a new directory in your “wp-content” directory called “spell-plugin” Copy the remaining files into this directory.
I have installed the plugin, and when I go to configure it, I get the following error msg:
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.
The directory in question is CHMOD 777 so it should be writable by the plugin. Is there something that I have forgotten to do?
Nope Rev. If that message prints out the directory that results from stripping the
"aspell.personal"filename off the “Name and path to aspell personal dictionary:” option is not writeable by Apache. Make certain that it’s a full pathname to a valid directory — easiest way is to select everything but the filename, copy it, open a shell and typecdthen paste the complete path in and see if it goes there — and then double-check permissions.Stephen, had you reconciled the previous problems with your hosting provider? You last said that your host had disabled
"exec"which would tend to imply that"shell_exec"— which the plugin requires — would also be disabled.TigerDE2: I had the same problem with my language setting being ignored. It seems that the version of aspell installed on my server is very old as the server is running Debian. $ aspell –version @(#) International Ispell Version 3.1.20 (but really Aspell .33.7.1 alpha) This version seems to have a bug where the locale setting ($LANG) is always used in precedence to the –lang command line option, and PHP scripts run as the default system locale.
Fortunately the fix turns out to be fairly easy, prepend “LANG=en_GB” (or equivalent) to the path to your aspell executabe. (“Name and path to aspell executable” option.)
ColdForged: Cheers for this excellent plugin. One small problem I did have though was that the link to the Configuration Page on the Plugins page gives a blank page. It was only when I spotted a reference to looking on the main WP Options page that I realised that the config page had moved. Cheers, — Nathan
I’ve followed the instructions in the readme for the manual install and I get this error:
Warning: main(/home/crowspea/public_html/blog/wp-content/spell-plugin/spellInclude.php): failed to open stream: No such file or directory in /home/crowspea/public_html/blog/wp-content/plugins/spell-plugin.php on line 36
Warning: main(/home/crowspea/public_html/blog/wp-content/spell-plugin/spellInclude.php): failed to open stream: No such file or directory in /home/crowspea/public_html/blog/wp-content/plugins/spell-plugin.php on line 36
Fatal error: main(): Failed opening required ‘/home/crowspea/public_html/blog/wp-content/spell-plugin/spellInclude.php’ (include_path=’.:/usr/local/lib/php’) in /home/crowspea/public_html/blog/wp-content/plugins/spell-plugin.php on line 36
Unfortunately, leaving the plugin on the server at all hoses the entire blog. Any idea what I doing wrong?
Thanks
Sounds like you didn’t follow the instructions in the readme. Locate the spellInclude.php file in your installation. If it isn’t in
/home/crowspea/public_html/blog/wp-content/spell-plugin/then it’s in the wrong place. Every file other than thespell-plugin.phpfile must be located in that folder.he he he–put the spell-plugin folder in plugins folder instead of wp-content.
But now I’m getting the same error as Robert above when I try to run the spell checker.
Did you try a different language setting like
enorenglish?Like Robert, it looks like I am out of luck. My server is running pspell.
Sorry for wasting your time. Guess I’m off to deactivate. Thanks though. It looked cool.
Hey, I’ve got your plugin installed, and it’s working great. I now don’t miss anything about Blogger!
I see on the options, though, that I should be able change from en_US dictionary to another one. I’d like to use a UK english dictionary, and was wondering how to do this? I’ve tried searching for answers elsewhere, but can’t find anything to help. I’ve also tried the obvious changing it to en_UK, but to no avail.
Any advice much appreciated!
Ah, looks like that got screwed up by my using an underscore. Markdown syntax for italics, right? Apologies for the excessive italicising. (If that’s even a word…)
Sorry, me again. Now got it sorted. I thought I had read all the previous comments carefully enough, but then searched and found Nathan’s solution. Amazingly enough, I think he’s actually running his installation on exactly the same web server as me! Apologies for the three pointless comments.
I’m having a real difficult time getting your excellent plug-in to work. It breaks my heart that I can’t get it to work. After spending hours browsing the posts and changing this and modifying that I deactivated it for the time being.
Thanks for sharing your talent with us,
Mark
PS: I use Opera 8 with Aspell (works perfect)
Brilliant plugin – if only I could get it to work.
Followed the instructions to the letter, asked my host and they said aspell was available, made sure the webserver had right access to the personal dictionary file, and generally tried every alternative possible.
Everytime I run the spell checker, a popup appears where it says ‘Spell checking…’ and then ‘Internal Server Error’ in both upper and lower frames.
What do I do?
This plugin is great. It works perfectly when I was using version 1.5 but after upgrading to version 1.5.1 . When I click on “check spelling”, there’s this error…
Error executing usr/bin/aspell -a–lang=en_US ….. /usr/share/aspellen_US.dat: The required field “name” is missing.
Is there a way to fix it so that it works?
Excellent news, glad to hear you got it working.
Do you have your web server serving XHTML are something else that’s slightly different? What appears in your Apache error log?
Odd that an upgrade would make it not work… I’ll have to see if there’s something squirrely in 1.5.1 (I haven’t upgraded yet). You can try using “en” or “english” for the language to fix it.
shell_exec() has been disabled for security reasons in /home/mindblee/public_html/wp-content/spell-plugin/spellInclude.php on line 114
Does that mean shell_exec() is disabled in all paths or just that one directory?
I reread earlier comments and I can see there’ snot much that can be done.
Thanks anyway and sorry for the trouble.
Keep checking back, DNA. There may be a way around it in the future. Sorry there’s nothing available for you now.
I’ve tried changing that to en or english but it still doesn’t work. Other than that, some how, it’s conflicting with OSA (anti spam plugin)… But thanks for the quick answer =)
Great plugin. I’m having difficulty with the “add word” feature from the spell-check popup. I can manually edit the dictionary from the configuration page, but clicking the add button does absolutely nothing.
Any idea? Thanks.
Hi, I re installed the plugin in and it worked =) but I could not add words to the personal dictionary, after adding those words the same error occurs.. but it works fine if I did not edit that page…
Installed it fine and I get this as an error message when I try to activate it
Warning: main(/usr/share/wordpress/wp-content/spell-plugin/spellInclude.php): failed to open stream: No such file or directory in /usr/share/wordpress/wp-content/plugins/spell-plugin.php on line 36
Fatal error: main(): Failed opening required ‘/usr/share/wordpress/wp-content/spell-plugin/spellInclude.php’ (include_path=’.:/usr/share/php:/usr/share/pear’) in /usr/share/wordpress/wp-content/plugins/spell-plugin.php on line 36
one thing to add my /var/www/wodpress is a link to /usr/share/wordpress on a debian box – could that be an issue?
My first check would be to make sure you installed it correctly. Does the
spellInclude.phpfile exist in that location? Thespell-plugin.phpfile is the only one that goes in thewp-content/pluginsfolder, the rest go in a folder calledwp-content/spell-pluginthat — unless you did the one-click install from the WPPM — you have to create.Yep I checked and all the files are in the right folder and place
/usr/share/wordpress/wp-content/plugins: spell-plugin.php
/usr/share/wordpress/wp-content/plugins/spell-plugin all the files including spellinclude.php
i do have my wordpress folder linked in my /var/www but that shouldn’t hurt it should it?
http://www.thunderpunch.net
odd this shows up in the error log
[26-Feb-2005 02:34:09] PHP Warning: Invalid argument supplied for foreach() in /home2/coldfor/public_html/wp-content/spell-plugin/spellchecker.php on line 16
http://www.thunderpunch.net/wp-content/plugins
Scott, please read my response again. The other files do not go in
/usr/share/wordpress/wp-content/plugins/spell-pluginthey go in
/usr/share/wordpress/wp-content/spell-pluginAhhh sorry I’m retarded today – very stupid of me and also the error log is a carry over from the tarball the file is dated feb
OK I got it working after some hacking of the spellcheck.php code. I read it’s giving me the error about en_US.dat not being open for data due to my php being in safe mode? So it looks like the personal dictioanry you built with the words in it to ignore is beraking things because of safe mode?
Hey there. I’m in WordPress 1.5.1 on Safari, and I can’t seem to get it working! My error is
I’ve tried every variation of english, en and en_US, and also tried that “enable manual personal” thing, with no luck. Any help would be greatly appreciated….
That’s an aspell installation error right there, nathaniel, and no amount of diddling with the plugin settings will help you, unfortunately. I’d ask your hosting provider why their aspell installation is broken.
Hi, I found out that in the newest archive the tarball does not contain the file spellplugin.php. So this archive is not working.
I also seem to have troubles with german umlauts (lang=de)
If I add a word to my personal dictionary that has an apostrophe in it, it breaks the spell checker. “Breaks” meaning, the window comes up, but it stays blank and there’s an “object expected” Javascript error.
Is anyone else having this problem? Is there a fix for it?
I am testing WordPress 1.5 and thought I’d try to install this plugin.
Everything seems to work.
If there’s only one word to add to the dictionary, it works no problem.
If there are 2, then the add button stays grey forever. The first word DOES get added to the dictionary!
add_failed.out is never created.
The javascript console in firefox says the following:
Error: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXMLHttpRequest.status]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: http://www.sohmer.net/test/wp-content/spell-plugin/spellChecker.js :: anonymous :: line 196" data: no] Source File: http://www.sohmer.net/test/wp-content/spell-plugin/spellChecker.js Line: 196Any ideas? Thanks!!!
Which version of Firefox is this?
Known problem that I have no solution to, unfortunately.
There is no
spellplugin.php, though there is aplugins/spell-plugin.php.Firefox 1.0.4
Interesting, it works GREAT with IE. Oh no! Please don’t make me go back to IE!!!
I have installed the latest version of the spell checker with WP 1.5.1.1 running Firefox 1.0.4. After correcting the aspell langage to en it works alright, execept that I cannnot add words from the spell checker. Adding them from the options menu works fine.
I saw a post mentioning auth.php. I did no receive this file in the .zip I downloaded. Should I have this file?
Great plugin.. very useful!
Hello,
This looks to be a great plug-in, but I’ve run into a few problems during installation. I can’t seem to get the Plug-In to show up as an option in my WP Plug-In manager. I downloaded the zip files and uploaded them accordingly. Any help would be great.
This is the second mention of this particular error. I don’t experience it in my 1.0.4 of Firefox, but I believe you guys. This was a serious problem with Firefox’s XMLHttpRequest handling in previous version of Firefox and it’s apparently made a bit of a comeback with 1.0.4 for some situations. I’ll try to investigate a workaround. I see you’re subscribed, so if I update to fix this I’ll post a comment here.
That was a WordPress file that is no longer in the distribution. No worries.
I would double-check that everything is installed in the correct location. The
spell-plugin.phpfile should be in yourwp-content/pluginsdirectory and all the rest of the files should be in a folder that your create calledwp-content/spell-plugin.Just a thought… My ISP provides squirrelmail 1.4.4 for our webmail access.
I noticed that my squirrelmail has a spell check and it allows me to add words to my dictionary regardless of the browser. I’ve never had a problem.
I don’t know anything about how suirrelmail implements spell check, but perhaps someone more knowledgeable does.
It may offer some insights.
I couldn’t figure out the instructions. I was confused. I couldn’t figure out if the personal dictionary was a file (the default setting for its path didn’t have a trailing /) or a directory (I got a error saying the personal dictionary directory isn’t writable). It would have been much easier for me if the error has said something to the effect of “the directory where the personal dictionary file resides is not writable”. Anyhow, great plugin!
Hi there! I have always used your Spell Check plugin and love it1 When I add the button to the comments so the user can spell check the style that all of my input buttons are supposed to pick up isn’t applied. I’d like it if the Spell Checker button is styled the same way as the submit button next to it. Is there a way to do this?
So long as it’s inserted in the right place in the code it should be styled as desired. As a workaround, you can pass in a CSS class to be applied to the button as a parameter to the
spell_insert_comment_button()function. You could then add that class as a selector for the desired style. Something like:[code lang="php"]< ?php spell_insert_comment_button("spellerclass"); ?>[/code]
[code lang="css"]#commentform input, .spellerclass { color: #ddd; }[/code]
Oh awesome it worked! Thanks a bunch ColdForged. i can once again flawlessly implement this awesome plugin
. PHP really confuses me lol. I need to take the time to learn it…Thanks again!
spell checks comment
Excellent, looks good. Oh and before you ask — just in case you ask — the reason the spelling checker doesn’t pop up is because you didn’t call the other function in your comments template.
[code lang="php"]< ?php spell_insert_headers();?>[/code]
Just in case
.
I get this error:
Error executing usr/bin/aspel-a--lang=english --personal= /cloaked/cloaked2/public_html/wpcontent/spell-plugin/aspel-wordlist.txt </cloaked/cloaked2/public_html/wpcontent/spell-plugin/aspel-wordlist.txt is not in the proper format.I know that this is trying to get me to make my personal dictionary in the proper format.
What is my personal dictionary and how can I get it in the proper format?
Thanks!
It’s created by the plugin — or by the aspell executable — when first configured. First thing to try would be turning on the “broken aspell installation” option in the speller options pages.
Did that. What I am having trouble with is that if I just leave the Name and path to aspell personal dictionary as a path with no file then I get the error:
But the folder I’ve set to both 777 and 755 with the same results. When I put the path indicating a file. i.e. aspel-wordlist.tx, the fatal error goes away but then I get the weird error.
P.S. Without indicating a file, the spellcheck button doesn’t show up.
Am I a problem or what?
Does that make sense?
Ah, there’s the problem. Make the name of the personal dictionary
aspell.personal. The wordlist file is used to generate the dictionary, it’s not the dictionary itself.Hi Coldforged! Great Plugin! An error:
Checked with the host, they’ve disabled access to aspell cause it’s “very inefficient and hard on the server”. Bummer. Maybe someday “when I’m rich” I can afford their Dedicated “Virtual” Hosting!
Still a great plugin! Installation was a breeze. Thanks.
Great Plugin–I installed it in a new blog today and it worked like a charm, however, I added it to my blog and I get a Javascript error message:
Error executing
/usr/bin/aspell -a --lang=en_US --personal=/home/down/public_html/wp/wp-content/spell-plugin/aspell.personal < /home/down/public_html/wp/wp-content/spell-plugin/aspell_data_vKFgAr 2>&1/usr/share/aspell/en_US.dat: The required field “name” is missing.I’ve retraced my steps and both installs are on the same server, in different hosting accounts, so I’m at a loss.
Any help would be appreciated.
Please see the first question on the FAQ.
When I try to check the spelling of my post, it says something about not liking the en_US. ANy ideas? Thanks, and I am looking forward to using this tool!
This is a similar issue as the one in comment #305. See the FAQ referenced in comment #306 and try the suggestions.
On one installation of the plugin, it worked fine, but on another I changed the Check Spelling setup language to “english” and it worked fine after that.
I’ve installed & activated the plug in. I’ve gone to the configuration site & confirmed it was installed properly (at least I think that’s where I went). I see the spellcheck button in my wp interface. But when I click it a popup window opens & I see this msg:
“Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@richardsilverstein.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.”
Any ideas what’s wrong?
Check your server error log — likely available in your CPanel or whatever user interface your web host provides — for likely errors. Nothing springs to mind.
Went thru about 5 pages in this thread and as yet have not found an answer.
Install of the plugin went well. When attempting to check an entries spelling the Javascript window pops up and starts the process. then is stops and gives a application error that in essence says the “aspell.personnel” file is “not in the proper format.” I changed all three variations of aspell language options with no luck.
Is this as I suspect a host server problem and if so how do I explain what they need to do to assist.
Thanks.
What’s in your
aspell.personalfile? What did you specify as the path to the personal dictionary in the options? Which languages have you tried?I get this error:
Error executing usr/bin/aspel-a--lang=english --personal=/cloaked/cloaked2/publichtml/wpcontent/ spell-plugin/aspel.personal/cloaked/cloaked2/publichtml/ wpcontent/spell-plugin/aspel.personal is not in the proper format.Yesterday, when I tried to use spell check the pop up window opened & I saw the interface but no text displayed in the window & I couldn’t perform a spell check.
I also use the TinyMCE wysiwyg editor plugin. Could there be a conflict w. it or some other coding issue do you think?
In answer to your questions: The aspell.personal file is empty. Path to that file is this /home/cranial/public_html/fullthrottle/wp/wp-content/spell-plugin/aspell.personal
I have tried all three variations of language (en_US, en and english) without a change, I still get the same error.
TO update my comment here of yesterday saying spellcheck wasn’t displaying any post text & thus couldn’t perform the check.
I disabled the wysiwyg editor plugin & the spellcheck still doesn’t work. Perhaps I should uninstall the plugin & reinstall? Or maybe deactivate & then reactivate?
Hi. First, thanks so much for this great plugin. I’ve been using it for about six months on my blog. I’m starting a new blog. I downloaded all of my old blog WP stuff and uploaded it to the new blog, hoping I could easily modify what’s there rather than going through the whole process of reinstalling everything. Unfortunately, that didn’t work. Since I have all of the files already in my WP install, can you think of something I can change to make it work on my new blog? I used Plugin Mgr before but that’s not working now. Thanks for any help and my best to you.
Have you tried enabling the “broken aspell installation option”? Do you have anything in the
aspell-word-list.txtfile? If not, I’d try downloading the plugin again and replacing that file with the one from the zip file.At this point I’d probably trash everything in your
wp-content/spell-plugindirectory and replace them with fresh version from the zip file (sounds familiar, no?).Hard to say, Richard. As I asked before, did anything show up in your error log following the “Internal Server Error”?
It’s hard to give recommendations without knowing how it didn’t work and what has and hasn’t been done to your install. Make sure the files are where they’re supposed to be, check to make sure the plugin is activated, visit the options pages for the plugin to make sure it thinks it’s happy. Those are the only things I can recommend.
I guess I didn’t make myself clear. Only the first time I had a problem with spellcheck did I get a server error. Now, I don’t get a server error. The spell check interface opens when I click the spellcheck button, but my post doesn’t appear in the pop up box & I can’t do the spell check on the post text.
I tried enabling the broken aspell installation option and it had no effect. I’ll try your other suggestions and let you know.
New version 1.18 released today.
For all of you subscribed to this post, a new version of the spelling checker plugin was released today. It suddenly occurred to me that I hadn’t investigated the problem with apostrophes and personal dictionaries sufficiently, so I investigated.
And subsequently found a solution. Now you can add words to your personal dictionary with apostrophes in them. For instance, try putting “ColdForged’s Spelling Checker Plugin” into a comment and spell check it here… you will find it is spelled correctly.
Visit the plugin page to download this version, and don’t forget to consider my Code For A Cure project if you find it helpful. Thanks.
I really want to use this plugin, but I keep getting errors. Stuff like:
failed to open stream: No such file or directory in /wp-content/plugins/spell-plugin.php on line 36
etc.
Why? I have followed the installation instructions to a T. Please let me know.
I swear I am following the installation instructions properly, but I keep getting this error. I get this as soon as I try to get into the wordpress admin section. I have to delete the spell-plugin.php file in order for it to go away.
What gives? Thanks for any help you can provide.
Warning: main(/home/jessehaf/public_html/darkdose.com/wp-content/spell-plugin/spellInclude.php): failed to open stream: No such file or directory in /home/jessehaf/public_html/darkdose.com/wp-content/plugins/spell-plugin.php on line 36Warning: main(/home/jessehaf/public_html/darkdose.com/wp-content/spell-plugin/spellInclude.php): failed to open stream: No such file or directory in /home/jessehaf/public_html/darkdose.com/wp-content/plugins/spell-plugin.php on line 36Fatal error: main(): Failed opening required '/home/jessehaf/public_html/darkdose.com/wp-content/spell-plugin/spellInclude.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/jessehaf/public_html/darkdose.com/wp-content/plugins/spell-plugin.php on line 36Sounds like you didn’t quite get the installation correct. See this comment and make certain the files are where mentioned there and you should have better luck.
I get these messages
first FATAL: The temporary directory you specified is not writeable from the Apache task. Either select a different temporary directory (like “/tmp”) or make the directory you specified writable by the Apache task (chmod 755 the directory).
(tmp director??)
next 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.
the /wp-content/spell-check folder is 755
advise please
I found on my webhost I had to CHMOD to 777 to get it to work, not 755
Hi,
I’m getting the following error message. I’m wondering if it might have been caused by a recent server upgrade. Do you know what’s going on?
Error executing
/usr/bin/aspell -a -- lang=english --personal=/home/matt/spell/aspell.personal < /home/matt/spell/aspell_data_zHJVmL 2>&1Error: 0U??uage “english” is not known. This is probably becuase the file “/usr/share/aspell/english.dat” can not be opened for reading
I’m using WP 1.5.1.3, and just tried re-installing the spell checker plugin.
I don’t see “english.dat” among the spell checker files…does this error indicate that the plugin is having problems locating a dictionary that’s supposed to be on my server? (the root folder of my account, as you’ve probably guessed, is “Matt”)
thanks very much in advance for your help.
doh. just saw this comment. I’ll try that solution and see if it works.
Yes, if they’ve diddled with their
aspellinstallation the plugin can stop working. You might try other language options to see if they work better (e.g. “en” or “en_US”).Thanks, ColdForged. It did turn out to be a problem with the aspell installation — namely, that it had been uninstalled. Luckily, my host is run by a friend of mine, and he reinstalled it for me. Now the plugin works beautifully.
When I had to post without it a few times, I realized how much I depended on it. Thanks so much for writing such a great plugin.
On the plug in page, the code for modifying for use for comments is returning an error on your web page. (it’s returning: [code lang=â€phpâ€] Parse error: parse error, unexpected TSTRING in /home2/coldfor/publichtml/wp-content/plugins/runphp.php(72) : eval()’d code on line 1 comments about this plugin.
Thanks so much, John. During my down time I had to turn off the code display plugin and neglected to turn it back on. It’s corrected. Thanks for the heads up.
Warning: main(/home/jacksonl/public_html/jacklog/wp-content/spell-plugin/spellInclude.php): failed to open stream: No such file or directory in /home/jacksonl/public_html/jacklog/wp-content/plugins/spell-plugin.php on line 36
Fatal error: main(): Failed opening required '/home/jacksonl/public_html/jacklog/wp-content/spell-plugin/spellInclude.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/jacksonl/public_html/jacklog/wp-content/plugins/spell-plugin.php on line 36
These are the errors showing after I have activated this spellchecker. I am using WP1.5.1.3 and latest IE. I had to manually delete the spellchecker to get my blog running again. I have followed all your instructions in the readme.txt file.
Can you tell me what is going on?
sxz
There are the errors I got when I turn on this plugin,
Sure! You didn’t follow all the instructions in the readme.txt file
. The error actually tells you what you need to know. The
spell-plugin.phpfile is trying to include thespellInclude.phpfile. It’s looking inwp-content/spell-pluginfor that file and not finding it. Hence, you probably installed the files in the wrong place, as did this guy and this guy and this guy and this guy.So, follow this advice — obviously adjusting for your own paths — and you should be fine.
(Sorry if I seem pithy… you answer the same question for 8 months and see where it gets you
).
I get an error similar to that in post 328 but it says error: 8. Any help would be appreciated. Thanks
hi all I know it maybe a very obvious mistake but i can’t find any solution to it. I installed the plug-in madethe spell-plugin folder as in the readme
when checking for spell i got this error
error executing /usr/bin/aspell-a –lang=eng
sh:line 1 : /usr/bin/aspell: No such file directory
any suggestion, please be precise cause I am totally newbie
thanx
julius
Did you try the advice I gave that guy?
If you do not have shell access with your hosting account, you may have to ask your hosting provider’s technical support whether the aspell executable is installed and what the path to it is.
it doesn’t seem like the Internal Server Error problem has been fixed
I am still getting it and dint think its a problem with my server. I run myriad scripts and never have a problem.
Any idea man?
I am still getting the Internal Server Error….any help with that??
I run myriad php scripts on my server so I dont think my servers is messed.
any help?
thanks
I’ve installed the plugin. I moved the plug-in file to the plugins directory and the rest to wp-content/spell-plugin. I’ve activated it and went to the configuration page, although it all seemed fine. However, I don’t get a check spelling button in my write post page. I don’t get an error either, It’s just I haven’t installed it. Any help would be appreciated.
When you visit the configuration page, is there anything in red at the top? The button will only show up if everything checks out okay on the configuration page, so perhaps something was not correct in the installation.
Thanks for the quick response
It’s giving me two errors.
1. personal directory permissions 2. temp directory permissions They are both wp-content/spell-plugin That folder is 755 all contents are 644
I have to fix that error code. Try making those folder 0777. If that makes you uncomfortable, you can follow my advice from this post.
That fixed it. It also works at 775.
Thanks very much for creating this plug-in.
I’ve been unable, however, to get it working on my site for a couple of weeks. Tried everything that I understand, including reinstalling, changing my folder preference to 0777, and trying my best to follow the read-me instructions carefully. Still get the following error (It’s long!):
Error executing ‘/usr/bin/aspell -a –lang=enUS –personal=/home/screenwr/publichtml/wp-content/spell-plugin/aspell < /home/screenwr/publichtml/wp-content/spell-plugin/aspelldata_4pp 2>&1′
Error: [down arrow]#R
I tried going through the help posts, but I’m a bit of a newbie and didn’t see one that seemed to address exactly the same problem. Can you help?
Thanks! WHL
Thanks for pointing that out. ^^;; I did get the plug-in installed, and this time it did not crash my site. However right now, I got this error message, and I have no idea what it means.
Error ececuting ‘/usr/bin/aspell -a –lang=enus –personal=/home/jacksonl/publichtml/jacklog/wp-content/spell-plugin/aspell.personal &1 ‘ Error:??
any ideas? ^^;;
Thanks very much for sharing this plug-in.
Hi.
Thanks for the plugin but this is the error I am getting sorry to bother you. Do you know what might be the problem? I changed all the permission for everything to 755 or 777.
Thanks,
Bill
Warning: main(/home/artch/wp-content/spell-plugin/spellInclude.php): failed to open stream: No such file or directory in /home/artch/wp-content/plugins/spell-plugin.php on line 36
Fatal error: main(): Failed opening required ‘/home/artch/wp-content/spell-plugin/spellInclude.php’ (include_path=’.:/usr/share/pear’) in /home/artch/wp-content/plugins/spell-plugin.php on line 36
Thank you… I got it… from message 280
You said, “cott, please read my response again. The other files do not go in
/usr/share/wordpress/wp-content/plugins/spell-plugin
they go in
/usr/share/wordpress/wp-content/spell-plugin.”
I’m getting the following error in my Javascript console (Firefox 1.0.6) when I try to load the spell checker: “Error: uncaught exception: Permission denied to get property Window.speller”. I get the popup window and in the bottom part of it I see all the buttons. However the top part stays blank and never fills in. Any ideas?
I guess I didn’t make myself clear. Only the first time I had a problem with spellcheck did I get a server error. Now, I don’t get a server error. The spell check interface opens when I click the spellcheck button, but my post doesn’t appear in the pop up box & I can’t do the spell check on the post text.
Ah, there’s the problem.
Hello,
I am running WordPress 1.5.1.3 on my server with your spell-plugin 1.1.8. It is much better than past tries and I like it. I did however notice one small problem. The plugin works great when there is a misspelled word. It does exactly as it should, and when there is no misspellings it says so. But sometimes it gives the error Object Expected in line 80 char 1. This error is in IE 6.
Thank you.
I posted back on the 22nd re this error:
Error executing ‘/usr/bin/aspell -a –lang=enUS –personal=/home/screenwr/publichtml/wp-content/spell-plugin/aspell < /home/screenwr/publichtml/wp-content/spell-plugin/aspelldata_4pp 2>&1′
Error: [down arrow]#R
Still getting it. I can’t for the life of me get this plug-in to work. Anyone have any advice?
Hi, First Thank You, for all your hard and most excellent work!
My host http://www.totalchoicehosting.com has removed aspell from their servers. They said it caused problems. They no longer support it.
Q: Is there some alternate to aspell that can be used? If so, what and how?
Thanks! Ron
I get the following error – which takes down my whole blog:
Warning: main(/home/republic/publichtml/wp-content/spell-plugin/spellInclude.php): failed to open stream: No such file or directory in /home/republic/publichtml/wp-content/plugins/spell-plugin.php on line 36
Warning: main(/home/republic/publichtml/wp-content/spell-plugin/spellInclude.php): failed to open stream: No such file or directory in /home/republic/publichtml/wp-content/plugins/spell-plugin.php on line 36
Fatal error: main(): Failed opening required ‘/home/republic/publichtml/wp-content/spell-plugin/spellInclude.php’ (includepath=’.:/usr/lib/php:/usr/local/lib/php’) in /home/republic/public_html/wp-content/plugins/spell-plugin.php on line 36
When I try to run the spell checker, the upper window says spell check in progress… then goes blank, IE says:
“Line: 41 Char: 1 Error: Object Expected Code: 0 URL: http://www.bachtalk.net/wp-content/spell-plugin/spellchecker.php“
I have verified that the aspell is installed cprrectly, the options autodetect it. Also, the dictionary is in a directory the server can write to. Any ideas?
Try a different language, either
enorenglish.Not by my plugin. However, there’s a relatively new AJAX based spell checker that uses the built-in pspell libraries of PHP. Only issue is if your host — which doesn’t sound overly accomodating — has enabled that support in your installation. Worth a shot. Otherwise, my only suggestion would be a browser-based implementation like SpellBound for Firefox. Obviously that doesn’t allow commenters to check spelling, but it’d work for you.
Please see this post.
I’ve seen it and thought it was gone forever. I’ll have to think
.
Hi, thanks, but sadly, I had it set to “en” already, and when I change it to “english,” I get an error “Q”. Tried “eng,” but that gave me an error “2 0″. Can’t figure this one out. Any other ideas?
Hello.
Will you be supporting pspell anytime soon? Looks like aspell is being removed from future versions of php.
“Note: This extension has been removed from PHP and is no longer available as of PHP 4.3.0. If you want to use spell-checking capabilities in PHP, use pspell instead. It uses pspell library and works with newer versions of aspell. “
http://www.php.net/manual/en/ref.aspell.php
Thanks,
justin
Wrong version of
. I don’t use PHP’s built-in spell checking libraries, I use the Unix aspell executable itself. That’s not being phased out of anything. However, if you’re interested in PHP’s
aspellpspell, there’s a new plugin out there that uses it (and things like Google’s spell checker service) that you can check out here.Do you happen to have shell access to your host? I know, probably too much to hope.
I get a ‘Not found on this server’ when I try to download.
Is it not available anymore?
Sorry, it’s back.
Hi,
I’m having a problem where the spell checker appears to be working properly, but it gives me the message “Spell Check Complete. No misspellings found” even when I intentionally misspell a word. So it looks good, but isn’t actually working!!
What’s going wrong? Hope you can enlighten me…
OK, things have changed a little. Went back to try again and now its picking up spelling errors, allows me to select the necessary changes and add to the dictionary etc in the dialog screen, but when I finish I get the message that the new words could not be saved and the spelling corrections I made have not been implemented to the post.
Here’s hoping you have the magic cure!!!
Thanks again.
Aaargh !!
I have been trying to get this to work for ages now…. It looks OK, seems to operate properly, but won’t actually pick any spelling errors!
I have followed all the instructions to the letter (I think)
I make an intentional spelling error, run the spell checker, and get the “No spelling errors found” message.
What’s going wrong????
I’m about to pack up my computer and go travelling for 8 months – so if ANYONE can give me some ideas sooner rather than later I would be eternally grateful.
I’m at a loss for that one. If you have shell access to your hosting account you can try to execute the
aspellexecutable from the shell and see what happens. It really sounds like aspell is not returning results in the format it expects.Thanks for the reply ColdForged
You mentioned “If you have shell access to your hosting account you can try to execute the aspell executable from the shell and see what happens.”
Sorry, but what does that mean? I have shell access ( although have no idea what its for) and executed the aspell file on my hosts server – what was supposed to happen ??
Sorry for being such a dumb ass!
First off, great site and plugin. However, when I try to use it, I get “Error executing ‘/usr/local/bin/aspell -a –lang=enUS 6 –personal=/usr/home/zoneforu/publichtml/jumboshrimp/wp-content/spell-plugin/aspell.personal&1′
Error: usr/home/zoneforu/publichtml/jumboshrimp/wp-content/spell-plugin/aspell.personal: the language “enUS” is not known. This is probably because: the file “/usr/local/lib/aspell-0.60/en_US.dat” cannot be opened for reading.”
What is en_US.dat? I can’t find it – which is strange.
Hi,
I did search the archives but I didn’t see any solutions to my problem.
A blank page returned after clicking the “check spelling” button, I suspected it’s the path problem and found that ” symbol replicate itself each time I push “update options” button.
for example, C:\Program Files\Aspell\bin\aspell.exe become C:\Program Files\Aspell\bin\aspell.exe become C:\Program Files\Aspell\bin\aspell.exe
is it a bug? how to solve this problem?
I’m running windows, wordpress 1.5.2, Aspell-0.50-3, checker 1.18
thanks, Oliver
Please see this comment.
Hi there! I downloaded and installed your plugin to my blog today and followed the instructions… and the “check spelling” button does appear on my post window but it doesn’t do or generate the actual window that does the spell check. It does nothing.
What do you think I’ve done wrong? Any help would be appreciated. Thanks! Ana
Hi there! I’m not sure if my comment went through the first time… so I’ll try again. Today I downloaded your plugin and tried to install it… which I did with success however, under “Write a post” section, all I get is the “Check Spelling” button but it doesn’t actually work. It doesn’t generate the spell checker.
Any idea what I could have done wrong? Any help would be appreciated. Thank You.
I’m getting: Error executing
/usr/bin/aspell -a --lang=en_US --personal=/home/andrewfe/www/wp-content/spell-plugin/aspell.personal </home/andrewfe/www/wp-conent/spell-plugin/aspell_data_f9plzM 2>&1Error:
…and then no error message.
I’m getting: Error executing
/usr/bin/aspell -a --lang=en_US --personal=/home/andrewfe/www/wp-content/spell-plugin/aspell.personal </home/andrewfe/www/wp-conent/spell-plugin/aspell_data_f9plzM 2>&1Error:
…and then no error message.
Don’t know. Check your Javascript console and see if there’s an error perhaps?
Try changing the language to
enorenglish.“en” was the trick! Thank you very very much.
I searched the website but could not find anything to help me resolve this:
Under [Options] [Spell Checker] I keep getting this 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.
I know my locations for /personal and for /tmp and valid, click on links below to see for yourself, I have CHMOD 755 / 757 / 777 and no luck on the personal folder. I did get the /tmp folder to work fine with a CHMOD of 777, but the personal folder is still causing problems.
http://www.sailorslog.net/blog/wp-content/spell-plugin/personal/
http://www.sailorslog.net/blog/wp-content/spell-plugin/tmp/
I use iPowerweb for my Internet provider, with a vDeck control panel. It may be an issue with the aspell feature under Apache, does this make sense. Perhaps I don’t have access to something I need from the provider.
If anyone thinks this is my problem, what exactly should I ask or request from iPower to fix this? I really want spell check as my spelling sucks, and I love Word Press. Any help will be appreciated.
Thanks in advance,
Patrick
Well I uninstalled it all and reinstalled it nd it works now, or at least the setp part worked. Now when I type a message, and click ‘check spelling’ I a little popup window opens, but then I get a lenghty error message that ends with ‘ Error: No word list can be found for the language “en_US”. This is what it autodetected, so does anyone have any suggestions?
Patrick
I am running WordPress 1.5.1.3 on my server with your spell-plugin 1.1.8. I did notice one small problem. The plugin works great when there is a misspelled word. It does exactly as it should, and when there is no misspellings it says so. But sometimes it gives the error Object Expected in line 80 char 1. This error is in IE 6.
How to solve this error?
I seem to be having an odd problem in that the config page for the spell checker thinks that it cannot write to the aspell personal directory but if I add words to the directory via the text area in the config page the words will appear within the personal dictionary file that I created. Since this creates a fatal error it looks like the plugin never gets fully activated. Any idea on how to fix this?
Its an excellent plugin, I have installed it and it works flawlessly but I have one major gripe with it and hence was forced to remove it from the comment area…I just don’t have enough place to put a button with so many characters.. ‘Check Spelling’ … I have place for around 8 chars … how can I change the button name to something else so that I can have it on the same line as the submit button…
The PHP function I use to check for directory writeability has some limitations in certain situations. Perhaps your install is one like that. You can work around this by opening the file
wp-content/plugins/spell-plugin.phpand going to line 311. It looks like this:[code lang="php"]if(!is_writable(dirname($speller_settings['aspell_dict'])))[/code]
You can change that line to:
[code lang="php"]if( 0 )[/code]
And it will skip that check.
Open the same file and go to line 586. It looks like this:
[code lang="php"] type="button" < ?php if($tab_index!='') echo 'tabindex="' . $tab_index .'" ';?> value="Check Spelling" onClick="openSpellChecker();" />[/code]
Change the
value="Check Spelling"to whatever text you want.Thanks for the tip. Changing that line fixed it and now I can spell check my posts.
Thanks, I was able to change the name of the button… but I dint know if its a bug or not but the checking of spelling is taking ages for me… a one line of text takes around a minute… http://www.arrogantly.com
I am trying to use your spell check plugin for my new word press installation. I used the shell access and verified that the path is correct: /usr/bin/aspell. In addition, I’ve tried every combination of languages you’ve suggested. It defaults to en_US. I’ve checked, double-checked and triple-checked my CHMOD settings on the filess. I’ve tried moving the tmp and personal folders around and I stil have the same problem. After reading all the comments and coming to a dead-end I contacted my web host to see if they were blocking me from using aspell, and they said it is available for use and that my patch is correct. In Firefox’s JavaScript Console I consistently get three errors.
1.) Error: syntax error Source File: http://upperallenfire.com/wp/wp-content/spell-plugin/spellchecker.php Line: 13 Source Code:
2.) Error: wordWindowObj is not defined Source File: http://upperallenfire.com/wp/wp-content/spell-plugin/spellchecker.php Line: 44
3.) Error: init_spell is not defined
Any help you can offer would be much appreciated! Thanks!
upperalenfire.com
Please HELP! I have installed and configured your plugin per your instructions and I am still getting errors. I consistently get three (3) errors in Firefox’s JavaScript Console:
1.) Error: syntax error Source File: http://upperallenfire.com/wp/wp-content/spell-plugin/spellchecker.php Line: 13 Source Code:
2.) Error: wordWindowObj is not defined Source File: http://upperallenfire.com/wp/wp-content/spell-plugin/spellchecker.php Line: 44
3.) Error: init_spell is not defined
I’ve read all the comments on here and tried all your suggestions in the FAQ. My problem is similar to your second FAQ in that when you click on Check Spelling it opens, but the top window stays blank – as if it can’t find aspell.
The options pickup /usr/bin/aspell as what it should be and I verified this through the Shell Access using the “which aspell” command.
I’ve checked, double-checked and triple-checked file permissions and moved the tmp and personal paths around to different places on my web server, all without any luck.
I’ve even contacted my webhost (they use cPanel) to see if they had some sort of security thing in place blocking me from using aspell, to which they said that they do not. They did verify that I do have the path correct to aspell.
I’m at the end of the line, I hope you are able to help! Thanks again! Brian – upperallenfire.com/wp
Oddness. this was workign on my old server, but a no go on my new one. I’ve used cpanel to chanve permissions, and i know the path is right. I get: Error executing
/usr/bin/aspell -a --lang=en_US --personal=WORDPRESS ROOT/wp-content/spell-plugin/aspell.personal < WORDPRESS ROOT/wp-content/spell-plugin/aspell_data_GUZzVF 2>&1Error: Xh�Please see this comment.
how can I remove the ‘add’ button from the interface?
Is there a way to remove the ‘add’ button from the interface?
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??
[code] @(#) International Ispell Version 3.1.20 (but really Aspell 0.50.5) crapp & crapp 7 0: crappy, crap, crape, crop, crappie, cramp, craps
works * [/code]
Original thread: [url]http://www.coldforged.org/archives/2004/12/08/spelling-checker-plugin-for-wordpress/comment-page-all/#comment-4398[/url]
How to remove a button from the interface ?
Go to line 153 of the file `wp-content/spell-plugin/controls.php. You’ll see this line:
[code lang="php"]if((!$current_options['must_be_logged_in']) || ($current_options['must_be_logged_in'] && ($user_level >= $current_settings['minimum_user_level_to_add']))) {[/code]
Change that to the following:
[code lang="php"]if( 0 ) {[/code]
I really haven’t a clue why it’s failing, unfortunately.
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.
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?
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?
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.Try a different language, either
enorenglish.I found a few more issues, and solved them.
On a Windows server, the paths in the temporary and dictionary text-boxes have escaped back-slashes which, every time you update the settings, double up once more, so it goes 2,4,6,8, etc! I changed them to forward-slashes to solve that (D:/Server/ instead of D:\Server).
I installed the Windows MinGW port of Aspell from http://aspell.net/win32/ and specified it in the path-to-executable (D:/Server/Aspell/bin/aspell.exe). DONT FORGET to also install a language dictionary. That means at least two downloads – the Full Installer and (for example) aspell-en-0.50-2-3.exe. Make Sure the language setting on the configuration page matches. For English I set minet to en or en_GB – it depends on the language files you install.
The permissions need adjusting so the MACHINE\NETWORK_SERVICE has “Full Control” permissions on the “aspell.personal” file in the plugins/spell-plugin/ folder.
The javascript link embedded in web pages has an incorrect path – it is hard-coded on line 564 of spell-plugin.php as “/wp-content/spell-plugin/spellChecker.js” – its missing the “plugins/” folder, so add that in.
Now the spell window will try to load, but fails because “plugins/” is missing from several paths in spellChecker.js, so fix those (do a search/replace).
Configure a System environmental variable. Right-click My Computer, choose Properties, Advanced, Environment Variables, System variables, New and add ASPELL_CONF with the value “prefix D:\Server\Aspell” (including the quote-marks) – this is where you installed aspell to.
Thank you, changing it to just “english” worked.
Coldforged, two questions.
My web host doesn’t appear to have the aspell plugin installed. Is that something I can do or must they?
Also, how does your plugin handle multiple simultaneous logins? We blog at my school and teachers want the kids to have spell checking capability. Each blog has about 30 users and many would be writing posts and checking spelling at the same time.
Thanks in advance,
-kj-
Bear in mind that what we’re referring to here isn’t a plugin but the actual aspell Unix executable on a Unix host. Just so we’re on the same page. It would be best if your host installed the aspell package but there may be a way for you to install it in your hosting directory itself. Here’s the manual for it.
It should be okay but I have no great way to test it aside from here live on this site in the comments, but I don’t know how many people utilize the spell checker nor do I often have multiple comments posted at one time. The plugin is coded to use a random named temporary file for each spell check which is the only concern for reentrancy in these cases (Apache handles keeping everything else about the connection straight).
To summarize, I think if you can sort out the aspell installation it should work for your requirements.
Thanks for clarifying. Looks like I’m SOL, my web host says they won’t install the executable, claiming it takes up too many resources. I’m going to try to rustle up support for it on the user forums. They run aspell on their dedicated servers, just not the low-end shared accounts (like I have). -kj-
I am getting the following error:
“Error executing ‘/usr/bin/apell -a –lang=enus –personal=/home/xxx/publichtml/wp-content/spell-plugin/aspell.personal < /tmp/aspelldataqpT9BF 2>&1′
Error: X
What does this mean and how can I fix it? I’ve tried everything and have talked to my hosting coming and came up with nothing!
Thanks!
Please see this comment.
Bingo!
Thanks so much! This has been racking my brain for weeks now…
Brian: I seem to have had a hard time of it getting Spell Check to work for me (it hasn’t worked for months).
I have the language set to ‘en,’ the files are CHMODed to 777, & I’ve deleted the previous installation of the plugin & tried reinstalling. But I’m still getting this error:
“sh: line 1:/usr/bin/aspell: no such file or directory.”
Under “Name and path to aspell executable,” is the setting supposed to be:
‘/usr/bin/aspell’ ?
I can’t think of what else could be wrong?
I did the one-click install.
That depends on your hosting environment. From the error you list apparently it is not the right path otherwise the plugin would be working (or, at least providing a different error).
If you have shell access, you can try to find the path to
aspellthat way. I don’t hold out much hope because that’s what the plugin tries to do itself. You could ask your hosting provider what theaspellpath is. It’s possible — since you seem to imply that it used to work months ago — that your hosting provider removed it. In that case you’re likely out of luck.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.
Looking forward to a version that does not require disabling PHP SAFE MODE. Looks like a great plugin otherwise!
Carlton : I suggest to developp it yourself. I think there is no version without disabling PHP SAFE MODE.
How can I get it to use the en_CA dictionary? Putting “en” works, but I want the Canadian aspell dictionary to be used.
BTW, enCA and enUS both work from the command line, but for some reason they don’t work in the spell checker plugin
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?
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!
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
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:[code lang="php"]if(!is_writable(dirname($speller_settings['aspell_dict'])))[/code]
to this:
[code lang="php"]if( 0 )[/code]
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.
I am with Dan, patiently waiting for a 2.0 update which I am sure will come.
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>&1Error (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?
I get the same error as JJK when checking spelling. Thanks in advance for your help.
Please see this comment.
Changed “en_US” to “en” in Options, and all is well. Thanks for the quick response!
Is it possible to have a list of the bugs and the method to fix it ?
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?
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?
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.
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.
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?
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
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.
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
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
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?
Sounds like the blog address in the general WordPress options has a slash at the end. Try removing it.
I thought of that, but there is no slash there.
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!
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′)
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.
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.
I just wanted to pop in and say hi… so… Hi!
So, Brian, what kind of bribe will it take to get you to move WordPress 2.0 compatibility up on your priority list?
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.
Yeah, what kind of a bribe$ will it take before you can make thi$ work in Wordpre$$ 2.0 with WY$IWYG enabled?
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.
Lee: You can probably fix that by changing “lang=en_US” to “lang=en” – not sure, but that worked for me.
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?
why bother creating a major plugin if you have no intention of continuing support? What a waste of my time. . .
Chris, it was already lang=en…
According to the error you provided, it’s set to
en_US:As Chris said, try
enorenglish.This plug-in is working just fine in my install of WordPress 2.0. I had to turn off the WYSIWYG editor, but it does not work with these in WordPress 1.5 either.
Thanks for the great plug-in. I would eventually love the see it modified so it will work with WYSIWYG editors.
I have created a new AJAX Spell Checker. See a demo and download the plugin for WordPress 2.0 here: http://matthew.delmarters.com/weblog/visual_spellcheck/trackback/
For some reason I can’t get the spell check button to show up for comments. In fact instead of the button, I see: ::HLIGHTBLOCK1::
I am trying to do this in WP2, but I don’t think that’s the problem. Any idea what is?
All you really need is a web browser, that can use aspell etc to do spelling checks in webpages “text box” while you type. Like Konqueror for example….
Not sure if anyone else noticed it, but there are certain special characters that break the spell checker. Specifically, if people c/p from a text processing program (which actually happens quite often) there’s a specific kind of apostrophe that’ll break the check and cause an “object expected” error.
I realize that this may (or may not) be a problem with aspell, but maybe it would be possible for the plugin to replace those characters before passing them on to aspell?