I've just installed this mod and I've gotten everything to work, except the spell check itself!

I uploaded the dictionary file, installed the product, but when I spell check a post it finds the errors but doesn't give any suggestions?!

Any help would be appreciated.

Installed OK on 3.6.2

It quickly flashes open in a new window in firefox which is annoying as it is so fast that you don't notice it and it does not remain on top of the forum window so you have to find it in the bottom nav bar of the browser.

Also does this need to learn all words? I just did a test and it did not give any options for any words really and so I had to click on learn for every second word. I did the normal install as this is the first time I have installed this hack. This meant I just ftp'd the dictionay file to the root and nothing more than that. I did not use anything in the dictionary-alt zip file. Was I supposed to use both?

Thanks for any assistance on this one

regards Richard

Help Please.............

Finally got this re-installed after upgrading forum.
I have the pop-under window problem as well as when the pop-up loads it says every other word in the post is incorrectly spell and no alternatives are offered at all.
Anyone?

Well I've compared the vbspell.js file in this version to the previous one for 3.5.3 I think it was and they are identical line by line. So does that mean that's not the problem or that it IS the problem?

Also, just for giggles and snorts i opened the vbspell template as if i was going to edit it, clicked the 'preview' button and low and behold look at the 'message' in it.... is this a 'fluke' or normal? (see attached screenshot)

Just curious - for those having the pop-under problem - what version of vb are you running?

Edited for spelling :P

3.6.2 here
but it doesn't really matter if it 'pops-under' since it doesn't offer corrections/suggestion, and recognizes correctly spelled words as incorrectly spelled/needed to be learned... In fact every word in this post would come up as needing correcting.

I'm wondering as I've had this working well (It's working on 3.6.1) - but I've seen where a couple people have 3.6.2 and have issues with it and if more people with 3.6.2 have issues with it then there may be an incompatibility with 3.6.2 and this hack. Possibly on more than one level.

one thought does occur to me. My host recently made some changes to the MySQL and there is now another 'column' in all my table sturctures called 'collation'. So my question is what should the collation be for the vbspell table (latin 1?) and also since I'm having to import the sql files splitting the actual dictionary up, when I import them which character set should I use, myPHPadmin gives me a drop-down of several to choose from... should it be the utf8 or another?

I got the pop-up problems when I changed from 3.5.x to 3.6.x, or when I changed from the last version (0.9.12) to this latest version (0.10.2b). As such, it is hard to say whether it was the latest vbspell that caused it, or the latest vbulletin that caused it. I can say that I get the same problems on 3.6.1 and on 3.6.2 as I had these problems before 3.6.2 came out.
Now as for whether this is caused by the javascript...? I have also compared the files of vbspell.js, vbspell.php and vbspell_iframe.php between the old and the current versions. Mostly the only changes are very minor, such as changing the name ?vBSpell? to ?vB Spell?. However, there are a few key changes which might be interesting.

10.2b:
}

9.12:
Looks like some minor changes with height and width changing to wx and hx. Does this make a difference?

Well, I decided to test the theory by simply renaming the 3 (current veriosn) files on my server and then simply copying the 3 files of the old version (vbspell.js, vbspell.php and vbspell_iframe.php) in their place. What happened? Absolutely nothing! No difference. I still get the pop-up happening behind the edit window, not in front. It seems to me that the idea of looking at the javascript may be a dead end.

I really have no idea, but I?d have to theorise that something has changed in 3.6.x to make this happen. I?d guess this could be something along the lines of code compliance and how browsers interpret this. For example, maybe the doc type has changed (it is currently ?XHTML 1.0 Transitional?)? actually, bad example, I just checked and 3.0.x is also XHTML 1.0 Transitional.

So, I have not brought any new useful information to this thread, but I can tell you this:

1. I have written to the author asking for them to have a quick check in here as although they are regularly in the forum, they have not been here for a while. It?s not fair to nag or judge the author of free software for a lack of support, but I wanted to know if they had finished with it and would be happy with someone else to pick up and run with it. Unfortunately, they have neither replied, nor posted in here.
2. It would seem on the surface that the javascript is not at fault, as the old version which used to work does not work in here.
3. I have not yet looked into the product.xml. I think that this is where it will have to be. (If no one else can solve this before I do)