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)

[jesus likes pie]

Could be useful. Do you have the option not to spell check your posts? For example i was on a board and it annoyed the crap out of me to HAVE to go through every word that triggered an incorrectly spelled word.

So is it an option to just not spell check it?

[tamarian]

Originally Posted by jesus likes pie

Could be useful. Do you have the option not to spell check your posts? For example i was on a board and it annoyed the crap out of me to HAVE to go through every word that triggered an incorrectly spelled word.

So is it an option to just not spell check it?

Yes. It will only check spell the post if you click on the "Spell Check" button.

[theArchitect]

Originally Posted by tamarian

Yes. It will only check spell the post if you click on the "Spell Check" button.

I loved this in 3.0 and am glad to have it back in 3.5.0.

Only one problem. I have installed it and the checking of spelling is working. But it is not correcting the words. The corrections happen in the pop-up window but then when I click done and quit or just quit the post is not changed.

Any thoughts as to what I have done wrong?

[tamarian]

Originally Posted by theArchitect

I loved this in 3.0 and am glad to have it back in 3.5.0.

Only one problem. I have installed it and the checking of spelling is working. But it is not correcting the words. The corrections happen in the pop-up window but then when I click done and quit or just quit the post is not changed.

Any thoughts as to what I have done wrong?

What version of vB 3.5 are you running? Each beta is quite different

If you have beta-4, whivh page are you getting this with? What editor mode, and what browser and version?

[theArchitect]

Sorry.

I am running beta 4. And I get this with the WYSIWYG and standard editor in both the advanced mode and quick reply.

[tamarian]

Originally Posted by theArchitect

Sorry.

I am running beta 4. And I get this with the WYSIWYG and standard editor in both the advanced mode and quick reply.

And your browser? Have you tried on different browsers?

[theArchitect]

Originally Posted by tamarian

And your browser? Have you tried on different browsers?

Sorry. I am stuck between a number of projects.

I am on a Mac and running FireFox.

I have also tested it in the latest versions of Netscape, Opera, IE and Safari and all come up the same.

[tamarian]

Originally Posted by theArchitect

Sorry. I am stuck between a number of projects.

I am on a Mac and running FireFox.

I have also tested it in the latest versions of Netscape, Opera, IE and Safari and all come up the same.

Have you reverted all the temlates that need reverting after upgrading to beta4? The client scripts and tool bar templates have changed in beta4.

Feel free to PM a test account (regular user), and I'll check and see what's going on.

[theArchitect]

Just one more question about enabling it for quickedit. I must be missing the TFO because I can't work out where I should put the button line. I have got it working for quickreply but can't for quickedit.

Apart from that I have to say that this system totally rocks.

I would recommend everyone to put it on their boards. And for those server load Nazis who are worried about it pulling resources, you can enable/disable it per user group. So you could make it available to your paid members which gives them an added incentive to join up.