I tried this WordPress spell check plugin two months ago, and I couldn’t get it to work. Its integration was clunky, and it didn’t support adding words to the dictionary. Wow… it’s improved a lot.
The only problems I had were trivial… one was that I have to replace bloginfo('url')
with bloginfo('wpurl')
(silly mistake by the creator of the plugin), and the other was that it tried to use the “en_US” dictionary, which wasn’t present on my server, and I had to change the setting and tell it to use the “en” dictionary and to handle my personal dictionary within the plugin.
The great thing is that it works both on the backend (when I write posts) and on the frontend (when you write comments)! Now there is no excuse for misspellings in your comments.
ColdForged says
Thanks for the heads up on the error. There’s an updated version to correct it. Of course, nothing is ever quite as easy since ‘wpurl’ doesn’t exist under 1.2 which I’m still trying to support :).
Glad you got it working.
Mark says
Hm, didn’t think about 1.2 How about doing
That should work on all versions.
ColdForged says
siteurl is an alias of url on 1.3 :). It’s fairly hopeless.
Robert says
Any ideas as to why I am getting the error “No word lists can be found for the language ‘en'”.
I get the same problem when I change the dictionary back to the default en_US. Also, what file is that URL problem in?
Thanks for the assistance!
Rob says
Hey…that’s pretty cool.
Mark says
Robert (Limeshurbet Robert), you can also try the “english” dictionary. Other than that, you’ll have to ask your host… aspell installs are hard to troubleshoot.
The URI problem is in the plugin file… in the two functions that insert the javascript code. I think there are 4 places to change it, altogether. But don’t worry about it. Your WP install isn’t in a
/wordpress/
subdirectory like mine, so it doesn’t matter for you.Robert says
Thanks Mark. I have a ticket open with my host on the aspell thing and it looks like I managed to grab the plug-in after ColdForged updated with with your fix. Hopefully I can get the spell-checker working soon.
ColdForged says
Just to follow up, of course this works just dandy under both. The thing that was throwing me is that bloginfo(‘siteurl’) is an alias for ‘url’, not get_settings(). That’s not semantically confusing or anything :). Thanks for the suggestion!
Mark says
Yes, it is very confusing. One thing passed to
bloginfo()
is another thing passed toget_settings()
. It’s likely all there for backward compatibility for really old plugins. Maybe by 1.6 we can drop some of this 1.2 and pre-1.2 stuff. Plugins aren’t that hard to update.P.S. This comment thread looks beautiful with all our giant colorful Gravatars!