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)

[tamarian]

Originally Posted by shiva

The instructions are wrong for that.

You should have both A and B in the showthread template.

Add the code (to replace "C") at the bottom of the showthread_quickreply. It doesn't look very nice, but it works.

Are they still wrong?

It should work without editing showthread_quickreply. Check the latest edit of the template instructions, and if it's still wrong let me know

[jesus likes pie]

Originally Posted by shiva

The instructions are wrong for that.

You should have both A and B in the showthread template.

Add the code (to replace "C") at the bottom of the showthread_quickreply. It doesn't look very nice, but it works.

Thanks

[Gary King]

I get this error on the vbspell.php page when spellchecking:

Notice: Only variable references should be returned by reference in /home/garyking/public_html/maloria.com/includes/class_core.php on line 1736

Notice: Only variable references should be returned by reference in /home/garyking/public_html/maloria.com/includes/class_core.php on line 1683

Notice: Only variables should be assigned by reference in /home/garyking/public_html/maloria.com/includes/class_core.php on line 1423

Anyways, I simply added error_reporting(0); on the page, since they seem to only be Notices.

[tamarian]

Originally Posted by Gary King

I get this error on the vbspell.php page when spellchecking:

Anyways, I simply added error_reporting(0); on the page, since they seem to only be Notices.

Ah, this is because I forgot to update debug code before uploading

In vbspell.php and vbspell_iframe.php

Chenge this:

PHP Code:

error_reporting(E_ALL); 


To this:

PHP Code:

error_reporting(E_ALL & ~E_NOTICE); 


I've update the zip file in case anyone else if getting this.

[lierduh]

Not sure if you need to do this.

After upgrading to RC1. The spellcheck popped up as a blank page.
I had to uninstall and reinstall using the installation script before it started to work again.

[tamarian]

Originally Posted by lierduh

Not sure if you need to do this.

After upgrading to RC1. The spellcheck popped up as a blank page.
I had to uninstall and reinstall using the installation script before it started to work again.

No need to do this. I think that was due to the new JS code in vB RC1. A hard refresh of the browser should fix this.

[lierduh]

Originally Posted by tamarian

No need to do this. I think that was due to the new JS code in vB RC1. A hard refresh of the browser should fix this.

Things I tried before doing that (IE 6):

1) Refresh at Edit Post page.
2) Ctrl-Refresh at Edit Post page.
3) Delete all offline contents.

My problem could be caused by other reasons. I thought too I wouldn't need to reinstall.

[tamarian]

Originally Posted by lierduh

Things I tried before doing that (IE 6):

1) Refresh at Edit Post page.
2) Ctrl-Refresh at Edit Post page.
3) Delete all offline contents.

My problem could be caused by other reasons. I thought too I wouldn't need to reinstall.

Hmmm, I'm wondering if this might be template dependant. When I tested RC1, I only tested one template (new thread). I'll do more tests to see if anything might cause a problem with RC1.

Let's hear from others if the RC1 upgrade went fine, or if they also had problems. If anyone else encountered problems, let me know which templates work and which ones didn't. But at leat we know that a re-install will fix the problem, if it happens

[lierduh]

Originally Posted by tamarian

Hmmm, I'm wondering if this might be template dependant. When I tested RC1, I only tested one template (new thread). I'll do more tests to see if anything might cause a problem with RC1.

Let's hear from others if the RC1 upgrade went fine, or if they also had problems. If anyone else encountered problems, let me know which templates work and which ones didn't. But at leat we know that a re-install will fix the problem, if it happens

I forgot to confess. I reverted all templates after RC1 and inserted spellcheck stuff afterwards.

[lierduh]

I have noticed spellcheck removes all the line breaks. Is this an intended feature?