vB Spell :: Spell Checker in WYSIWYG and Standard Modes

A 3.6 version by cynix2 is posted here:
https://vborg.vbsupport.ru/showthread.php?t=124578

What this does: vB Spell allows you to install a dictionary (English dictionary included) into your MysQL database, and provide a spell checking window that works in both of vB's editor modes, standard and WYSIWYG.

Background: Many of you liked PungoSpell, but didn't like recompiling PHP for it. Many liked PHPSpell, but didn't like the lack of WYSIWYG support and browser compatibility. vB Spell solved both problems, I hope, by combining the best of each.

Features:
o Supports most recent versions of browsers. Tested on IE, Firefox, Mozilla/Netsacpe, Opera and Konqueror (Konqueror implies Safari, but please confirm Mac folks)
o Learn Feature uses cookies, so it won't increase the database size
o Admin panel options
o Works in WYSIWYG toolbar, Standard toolbar, and no toolbar
o Can be added in full edit mode, quick edit and quick reply.
o Skips quoted text and other tags (PHP, code, etc.)
o Usergroup permisisons
o Template based interface, and uses your default style.
o Link buttons (Thesarus and Lookup) with links to Merriam Webster's online thesarus and dictionary links with the suggestion for misspelled words.

Installation:
Note: There is a french version of vB Spell, by cclaerhout posted here

1. Upload files and run vbspell_install.php
2. Go to AdminCP > vBulletin Options > vB Spell and edit your usergroup permisisons.
3. Template edits: (see alternative method, if you don't mind removing the ieSpell button made by vB : https://vborg.vbsupport.ru/showpost....9&postcount=48)

For each template where you would like to add a vB Spell, do the following edits (Example: editpost, newreply, newthread, etc.)

A. Find:

</head>

Add before:

<script src="vbspell.js"></script>

B. Find: (or anywhere in the body)

$navbar

Add after:

<form name="spell_form" id="spell_form" method="POST" target="spellWindow" action="vbspell.php">
        <input type="hidden" name="spell_formname" value="">
        <input type="hidden" name="spell_fieldname" value="">
        <input type="hidden" name="spellstring" value="">
</form>

C. Find the submit and preview buttons:

		<input type="submit" class="button" name="sbutton" value="$vbphrase[save_changes]" accesskey="s" tabindex="1" />
		<input type="submit" class="button" name="preview" value="$vbphrase[preview_changes]" accesskey="p" tabindex="1" />

Add below:

<input type="button" class="button" value="Spell Check" onClick="spellCheck('vbform', '$editorid', '2');" />

Other templates:

Optional: Other Templates that contain edit boxes are:
USERCP_SHELL just add A before the </head section and B after it. Required for pm_newpm and modifysignature.
editpost
Calendar Templates: calendar_edit
New Posting Templates: newreply, newthread

Quick reply: . Put change A and B in showthread, as the rest, and use this for step C:

<input type="button" class="button" value="Spell Check" onClick="spellCheck('qrform', '$editorid', '2');" />

Right after this (also in showthread):

			<input type="submit" class="button" value="$vbphrase[go_advanced]" accesskey="x" title="(Alt + X)" name="preview" tabindex="3" id="qr_preview" onclick="this.form.clickedelm.value = this.value" />

For quick edit in postbit_quickedit, use this for step C (A and B are in showthread):

		<input type="button" class="button" value="Spell Check" onClick="spellCheck('vbform', '$editorid', '2');" />

After this:

		<input type="button" class="button" tabindex="1" accesskey="p" value="$vbphrase[go_advanced]" id="{$editorid}_adv" />

History:
December 25, 2005: Security fix for cases where you allow HTML posts and they contain malicious code (Credit goes to Brendan Donahue for finding the issue and alerting TechGuy, and to TechGuy for alerting me to it)
November 2nd. 2005: Fixes a bug with slashes in text.
October 17. 2005: Check for primary and secondary group for permission. Bug fix for quoted words.
September 13, 2005: v0.9.9 Bugfix for JS on IE with RC3
July 15, 2005: v0.9.8 Bugfix for JS code mismatch with template.
July 14, 2005: v0.9.7 Initial release for vB 3.5 beta-4

Please click Install if you have installed this mod.

Scrrenshots: (from the 3.0.7, but it's identical)

[Princeton]

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:

<input type="button" class="button" value="Spell Check" onclick="spellCheck('3', '$editorid', '2');" />

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

[OrangeFlea]

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

[reismarktq2]

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.

[tamarian]

Originally Posted by reismarktq2

Princeton: Works like a charm. Much thanks!

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

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?

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.

[Ambie]

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.

[D|ver]

Originally Posted by Wildthinks

me too interesting... :squareeyed:

me too, that would be great

[dutchbb]

What languages does this support? No dutch right?

[kellee88]

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:

vb spell will not install. I get Warning: Invalid argument supplied for foreach() in /includes/class_core.php on line 2755

Unable to add cookies, header already sent.
File:/includes/class_core.php
Line: 2984

Any suggestions?

[Strat]

How about having it in QR?

[AlchemyX]

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