I needed to install this for a client but I noticed that the posbit_edit didn't work.

The reason why it doesn't work is because the vbspell script checks for form name "vbform". The post_edit form doesn't use this 'name'. In fact, I don't think it has a name.

Anyway, the fix is to find the array of form objects within the page. ie. how many <form> objects are found before the postbit_edit form. In a default vbulletin style, the number is 3 ... at least that's what it was for me logged in as admin. :)

So instead of...
document.form["formname"] - uses defined form names
we will have
document.form[3] - uses refrence number within array

If it doesn't work with '3' check with another number.

I can't test this on client site as a registered member so if someone can test and confirm this I would appreciate it. Thanks

Well, here's the fix:
OTHER RECOMMENDATIONS:
Check to see if field exist before ALTERing a table. For example, user table - if field exist ALTER will fail; thus, it may leave someone with missing fields

GREAT JOB

Any demo sites? Is anyone running this thing on their forum, I want to check it out.

Princeton: Works like a charm. Much thanks! :)

Tamarian: Any reason why the install script needs to be re-run after running a vBulletin update? And how much of the install script actually needs to be re-run? I'd rather avoid having to re-install the dictionary each time I run an update, since we are often adding a number of words/phrases that aren't already there as they are discovered and would like to be able to keep these customizations.

Post the details, and I'll add it to the first post so others can try it.

The reason is that this was released prior to product xml files. Converting it to product format is not difficult, but will mess up previous installations. At one point in the future I'll think of a way for a painless upgrade.

You can run the steps until the dictionary step, which does not need to be re-run.

I couldn't figure out how to get past step 5 for the life of me. I was desperate,so what I ended up doing was looking at the last word in the VBspell table, then going to the dictionary.dic file and copied the words after that one all the way down. Pasted it into a new file, named it dictionary.dic and uploaded it over the old one.Then ran step 5 again. It loaded the rest of the words and the install finished. Works great now. :)

me too, that would be great :)

What languages does this support? No dutch right?

We upgraded from 3.0.7 to 3.5.4. We had vBSpell in 3.0.7. We have veen trying to install the latest 3.5.3 vBSpell but with no luck. Here is the message we get:
Any suggestions?

How about having it in QR?

um.... everything is fine except that my browser times out on step 5...