ColdForged

1.3 was rebadged to 1.5. Apparently the Plugin Manager simply hasn’t been updated to reflect this fact.

7milesdown,

Do you have shell access on your site? If so, try running the “unzip” command directly from the shell. My guess would be your hosting provider doesn’t have this program or an alias to it. You may need to ask them what the name of their unzip executable is.

Ah the joy of namespaces and function redefinitions in the plugin architecture. callistawolf, there’s an incompatibility between the Plugin Manager and the Theme Manager plugin. As you’ve seen they both try to declare a function called “rmdirr”. PHP hates it when people do that.

You can fix this by opening either of the plugins — I’d suggest the Theme Manager plugin — in a text editor or the built-in theme editor if that’s even available with the problem and changing all occurences of the word “rmdirr” with something like “wptm_rmdirr”. I do mean all occurences… currently there are three that I see in the file. Once you do that you should be fine.

Ah. Well, it appears that the plugin can’t find the aspell executable. In the 1.1 version, it will look for it with a “which aspell.” That must not have located it. You might ask your hosting provider whether aspell is installed and where.

You misspelled “/usr/” in that path. Perhaps that’s the problem?

Most welcome! Glad you’ve found it useful.

Note that as of 1.1 the plugin is now compatible with the One-Click installation interface of the WordPress Plugin Manager. As such, it’s a lot easier to keep up to date with any new version. Jsut FYI.

No, not quite enough. However, as you can see in the comments, this looks like something that is relatively commonly seen. Try changing your language to something else, like english or simply en.

on first glance though i like that the personal dictionary is viewable/editable

Version 1.1 of my plugin has a viewable/editable personal dictionary.

the spellcheck plugin didn’t work for me (pop up window had buttons but no spelling results) until i chmod’ed the entire plugin directory (777).

Interesting, the 1.1 version should have a check for that in the configuration page. Did it not give an indication that the temporary directory was unwriteable?

I spent at least one hour trying to get the spell check to work last night.

It’s sometimes helpful to post problem reports on the author’s website so he could perhaps help out ?? (I don’t often read this forum). I’d certainly check to make certain that the Javascript isn’t being blocked as cianuro mentioned.

Remember that it’s generally pretty easy to pull up any site’s CSS and peek under the covers. For the site you mentioned, this is his blockquote code:

blockquote {

background: #e7fbfa url(images/quotes.gif) no-repeat top left;

padding: 10px 30px;

}

I apologize for not responding eragle… stupid me didn’t realize there was a second page. ??

Please note that a new version of the plugin was released yesterday that adds, among other things:

* An administration page within the WordPress Options framework for ease of configuration and adding words to the personal dictionary,
* an attempt at auto-detecting the aspell executable (for those of you with no shell access),
* Compatibility with the WordPress Plugin Manager for One-Click installs and automatic update availability.

To acquire, I’d seriously recommend going through the aforementioned Plugin Manager. Feel free to start here.

Thanks.

I forgot to mention removing the personal dictionary file between attempts at changing the language, though that may or may not help. I’m curious why it still complains about en_US.dat when you’re specifying an “en” language.

You can try a different language setting in that same config file. Try simply “en” or maybe “english”. That also depends on your aspell installation.

Your personal dictionary should be located somewhere that the web server has permission to write to. I can’t tell you where this is for your installation… perhaps you can create a directory under your home directory for it to use and chmod it to allow everyone write permission, then change the path in the spellConfig.php file to point there.

Hope this helps.