Thread

I’m using EE 2.2.2 and the spell checking isn’t working.  I get this JS error:

function SP_suggestionMenu(suggestions, id)
        {
            words = suggestions.split(",");
...

index.php:1997
TypeError: ‘undefined’ is not an object (evaluating ‘suggestions.split’)

TTFN
Travis

Hi Travis,

What version of PHP are you running on that server?

Thanks,

Mark

PHP Version 5.1.6

Ah okay. I just asked as I know that the split function is deprecated in 5.3 and upwards.

When you say the spell checker isn’t working, what is it doing or not doing exactly?

Does any part of it work at all?

Is this site a brand new install or an update and do you have the optional requirements as outlined in the documentation here :

Spell Checking. In order to be able to use the spell check feature in ExpressionEngine, your server must have PHP compiled with pspell support or be able to contact remote servers though PHP. If you are unsure if this is the case, contact your Host or server admin.

Thanks,

Mark

The spell checking “window” unfurls below the content area, but

a) no highlighting of poorly spelled terms occurs,
b) clicking on a misspelled word doesn’t do anything (no alternative spellings appear)

Looking at the JS error console, I get the error quoted above.

This is a site I’m about to upgrade to EE 2.2.2 (I’m testing the upgrade right now when I discovered this), spellchecking has been working in EE1

TTFN
Travis

Hi Travis,

There is already a bug report here noted for the problem with the words not being highlighted. That will eventually take care of that issue for you.

With the other issue, do you have the optional requirements as outlined in the documentation that I linked to above?

Thanks,

Mark

Yes, I do.

Hi Travis,

I’m going to bring this up internally and ask about it for you. I’ll post back here as and when I get some information for you.

Thanks,

Mark

Travis, we’ve got a fix in for the style issue (Bug report), but I’m not replicating problems w/the spellcheck itself.  Is it across browsers?  And what’s some test content that throws the error?