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)

[Rich]

Hello,

I am running this on a site that runs 3.5.x. The "x" means I have been upgrading as they are released and I just reinstall the template edits. I do not get java errors and i have several other java scripts running on my site.

I actually am posting just to say that if anyone wants to apply this to the journal modification, it works just fine for Comments. I will try out the new entries and add to this if that works as well.

Edit the: journal_commentpage template. Add A and B as described.

Add C after:

<input type="submit" value="$vbphrase[submit_new_comment]" class="button" />

For new entries, edit the: journal_submitentry template. make the A and B edits as described and add C after:

<input type="submit" value="$vbphrase[submit_new_entry]" class="button" />

Both work fine and are running on my site.

[ludachris]

Can someone please help me with the Javascript errors I'm getting in post #240.

[apollooooooo]

HELP!!!!!!!!!

I Downloaded the Script and Uploaded it to my Site it got to about 40% Durning the Install Then it Say there was an Database Error now Nothing in my Site is Workin ( Also i Tryed to login in to phpmyadmin to maybe try and repair the database but i get the following Error

Fatal error: Call to undefined function: pma_reloadnavigation() in /usr/local/apache/htdocs/phpMyAdmin-2.6.3/header.inc.php on line 135

[ludachris]

Just to let everyone know, this hack does not seem to work in 3.52 or 3.53 - I have it working on a 3.51 site with no problems, but the newer vb versions spit out javascript errors. I'd wait until this hack is updated to install it on a new version of vb.

[AaronBBrown]

Originally Posted by ludachris

Just to let everyone know, this hack does not seem to work in 3.52 or 3.53 - I have it working on a 3.51 site with no problems, but the newer vb versions spit out javascript errors. I'd wait until this hack is updated to install it on a new version of vb.

It works fine for me in both 3.52 and 3.53. I do have to rerun the install script whenever I upgrade VB, though.

[ludachris]

Originally Posted by AaronBBrown

It works fine for me in both 3.52 and 3.53. I do have to rerun the install script whenever I upgrade VB, though.

Well I installed it new in 3.53 and it doesn't work. Sorry, since I couldn't get any support I just assumed it didn't work for any new versions.

I tried uninstalling everything except the dictionary and reinstalling. I double-checked all of the template settings. Still doesn't work.

I guess my previous statement is partly true - it doesn't work for all people running 3.53. It might work for some, but obviously not all.

[SpadMan]

Worked for me in 3.5.2 and 3.5.3 as well. As described earlier in this thread, it had to be reinstalled each time I upgraded vBulletin.

[ludachris]

Originally Posted by SpadMan

Worked for me in 3.5.2 and 3.5.3 as well. As described earlier in this thread, it had to be reinstalled each time I upgraded vBulletin.

I wish that was the case for me - but as I said, I didn't install this hack until AFTER I upgraded my vb version, so this wouldn't apply to me. So I say again, there appears to be a bug in this hack. It's too bad the person who wrote it won't check this thread to get it worked out.

[ludachris]

Just for the hell of it, I uninstalled the untire hack including the dictionary, and reinstalled using the install script. I even went through and reinstalled the code in the templates. It does not work. This has to be a bug, as I've done everything right and I still receive Javascript errors. I even downloaded the files again to make sure I have the most recent versions.

Buggy hack. I'd advise people to wait before they go filling up their database with a big dictionary until this gets sorted out.

Sorry, just to clarify, I'm having trouble with 3.52.

[davidw]

I have 3.5.2 and what I had to do was uninstall the hack and then reinstall it (completely including template modifications) to get it to work - but I've not even had a single issue with it since the reinstall.