vB Spell :: Spell Checker in WYSIWYG and Standard Modes

There's also a vB 3.5 version: https://vborg.vbsupport.ru/showthrea...threadid=92202

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 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:
1. Download vbspell.zip and upload the files and run vbspell_install.php
2. Go to AdminCP > vBulletin Options > vB Spell and edit your usergroup permisisons.
3. For each template where you would like to add a vB Spell, do the following edits (Example: editpost, newreply, newthread, etc.)

Note: For those running PHP in cgi mode and get timeouts while installing the dictionary, you can download the file dictionary_sql_for_php_cgi.zip to import it to mysql through the mysql command line.

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="">
        <input type="hidden" name="toolbar" 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:

<if condition="$show['wysiwyg']">
        <input type="button" class="button" value="Spell Check" onClick="spellCheck('vbform', 'WYSIWYG_HTML', '2');">
<else />
        <input type="button" class="button" value="Spell Check" onClick="spellCheck('vbform', 'message', '1');">
</if>

Other templates:

Optional: Other Templates that contain edit boxes are:
USERCP_SHELL just add the first change (A) here in above the </head section. Required for pm_newpm and modifysignature.
editpost
Calendar Templates: calendar_edit
New Posting Templates: newreply, newthread
Modify User Options Templates: add the the first change (A) in USERCP_SHELL) and the rest (B and C) in modifysignature

Quick reply: . Put change (A) in showthread, above </head>. Then add change B to the beginning of showthread_quickreply. Then find

			<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" />

Add after it:

<if condition="$WYSIWYG == 2">
        <input type="button" class="button" value="Spell Check" onClick="spellCheck('vbform', 'WYSIWYG_HTML', '2');">
<else />
        <input type="button" class="button" value="Spell Check" onClick="spellCheck('vbform', 'message', '1');">
</if>

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: Fixed a bug with slashes in text.

Oct 17, 2005: v0.9.5 Cecks for primnary and secondary group permission. Also fixed quoted words.

July 10, 2005: v0.9.4 Added an error if accessing vB Spell directly, like from who's online page.

July 10, 2005: v0.9.3 Fixed a problem with capitalized first letter of words, so chosing a suggested alternative would not alter capitalization.

July 10, 2005: v0.9.2 Fixed a browser bug, fixed an installer issue effecting some, and fixed handling of some special characters.

July 9, 2005: v0.9.1 Learned words in cookies are no longer case sensitive. Abbreviations are ignored and not spell checked.

July 8, 2005. initial release, v0.9

Please click Install if you have installed this mod.

[tamarian]

Originally Posted by zendiver

Ok, I can understand that, so this is what I plan to do.
Dump the dictionary.sql into my database.
Then, do I run the install program?

My preference would be to first get the host to fix the query limit, since this will solve any future problems with the database. Once that fixed, you can just use the nstall script as usual.

If they don't want to do that, then your above work-around would work, provided that you don't run step #5

[zendiver]

well, they will not up the max limit so the dump is the way I am going to have to go, but now I forsee another problem. Once the dump is made, it already has the table name etc....so I will more than likely get errors running the install program.

[tamarian]

Originally Posted by zendiver

well, they will not up the max limit so the dump is the way I am going to have to go, but now I forsee another problem. Once the dump is made, it already has the table name etc....so I will more than likely get errors running the install program.

If you use phpMyAdmin, you can rename the table.

[zendiver]

I am doing that but won't it say that Table already exists when I run the installer, AFTER I complete the dump?

[NWN]

In newreply & newthread under 3.0.8

you need to look for this

PHP Code:

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


And then add this below for it show the buttens in the right spots.

PHP Code:

<if condition="$show['wysiwyg']">
        <input type="button" class="button" value="Spell Check" onClick="spellCheck('vbform', 'WYSIWYG_HTML', '2');">
<else />
        <input type="button" class="button" value="Spell Check" onClick="spellCheck('vbform', 'message', '1');">
</if> 


[tamarian]

Originally Posted by zendiver

I am doing that but won't it say that Table already exists when I run the installer, AFTER I complete the dump?

It's messy anyway, due to the host limit, but:

Originally Posted by tamarian

provided that you don't run step #5

[mustang_lex]

This is a great feature.

One question. How do I change the text background to white? For some reason its defaulted to red. and I like black text (with red highlight) with a WHITE background. where do I change that?

UPDATE: I found a work around. I removed the link to my CSS file and copyed the CSS content into the vbspell_iframe.php and removed my background image which was causing the problem. :ermm:

[Detomah]

I've had this down as installed for ages, but every time I go to do it, I stall and hold back and keep meaning to ask...

So....

What's this like on the old server loads and queries? Does it add a lot or very little?

[tamarian]

Originally Posted by Detomah

What's this like on the old server loads and queries? Does it add a lot or very little?

It's quite fast and light, but you might want to test on the server just to be sure.

It's optimized to ignore common words (any words excluded from your vB search indexing), and the dictionary is indexed, and the queries are indexed, so I haven't noticed any load issues.

You can convert the dictionary table to a HEAP/memory table, but it doesn't seem to be needed.

[scoles15]

It works great for regular posts and replies, but the spell check buttons shows an error and nothing happens