New Posting Features - vB Spell

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: This mod was originally developed by tamarian for vB 3.5.x. With the release of 3.6.x the installer stopped working for fresh installs and the template changes were considerably out of date, tamarian gave me permission to release a 3.6.x version with updates.
This version should work with both 3.5.x and 3.6.x series.

Features:

• Supports most recent versions of browsers. Tested on IE, Firefox, Mozilla/Netsacpe, Opera and Konqueror (Konqueror implies Safari, but please confirm Mac folks).
• Learn Feature uses cookies, so it won't increase the database size.
• Admin panel options.
• Spell Check button appears anywhere there is a WYSIWYG Enhanced or Standard Editor Toolbar [includes quickreply but not quickedit].
• Skips quoted text and other tags (PHP, code, etc.).
• Usergroup permisisons.
• Template based interface, and uses your default style.
• Link buttons (Thesarus and Lookup) with links to Merriam Webster's online thesarus and dictionary links with the suggestion for misspelled words.

Installation:

• Unzip main package.
• Upload the contents of the 'upload' folder to your forum home directory.
  Regular Install:
  • Unzip dictionary-reg.zip.
  • Upload DICTIONARY.DIC to your forum home directory.
  Alternate Install
  • Unzip dictionary-alt.zip.
  • Import the SQL files to your database.
• Import product-spellvb.xml.
• Go to AdminCP > vBulletin Options > vB Spell and edit your usergroup permisisons.
• Template changes are now automatic. [accept for quickedit]

Q: What is the Alternate Install method for?
A: If you are having problems with the Regular Install (such as your dictionary import freezes at x%) then you should consider using the Alternate Install. If neither of these methods work for you then there might be an issue with your server host.

Upgrading:

• Unzip main package.
• Upload the contents of the 'upload' folder to your forum home directory.
• Import product-spellvb.xml.

To manually force the quickedit template to work with this mod:
postbit_quickedit
Find

		<if condition="is_browser('ie')">
			<td><img src="$stylevar[imgdir_editor]/separator.gif" width="6" height="20" alt="" /></td>
			<td><div class="imagebutton" id="{$editorid}_cmd_spelling"><img src="$stylevar[imgdir_editor]/spelling.gif" width="21" height="20" alt="$vbphrase[check_spelling]" /></div></td>
		</if>

Replace with

		<td><img src="$stylevar[imgdir_editor]/separator.gif" width="6" height="20" alt="" /></td>
		<td><div class="imagebutton" id="{$editorid}_cmd_spelling(null)"><img onclick="spellCheck('3', '$editorid', '2');" src="$stylevar[imgdir_editor]/spelling.gif" width="21" height="20" alt="$vbphrase[check_spelling]" /></div></td>

History:
0.10.x NyNe versions
v0.10.3b - 06/22/07:
Compensated for an issue brought up in this post.
v0.10.3 - 06/22/07:
Added a check to the product installer so it would not remove the vbspell table after just having created it.
Added $vboptions[bburl] to all template code that asks for files (this *might* fix the PhotoPost issues - no promises).
v0.10.2b - 08/26/06:
Fixed error in product installer (removed table prefix).
Changed all <? to <?php for php5 compatibility.
v0.10.2a - 08/26/06:
Removed alt product installer.
Product installer included now checks for dictionary file, if dictionary file is not found it continues installing.
Product installer no longer drops dictionary table before installing.
v0.10.2 - 08/22/06:
vbspell template is now XHTML 1.0 Transitional.
Fixed a version check for vbspell template (made compatible with 3.5.x).
vB Spell window should now open on top of other windows.
Removed table prefix for vbspell sql table (product installer includes code to remove old tables).
Included alternate installation method (Credit goes to Replicators for the SQL Install method).
v0.10.1 - 08/21/06:
Beta release for 3.6.x series.
Switched to product/plugin based installer.

0.9.x tamarian versions
v0.9.12 - 12/25/05:
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).
v0.9.11 - 11/02/05:
Fixes a bug with slashes in text.
v0.9.10 - 10/17/05:
Check for primary and secondary group for permission.
Bug fix for quoted words.
v0.9.9 - 09/13/05:
Bugfix for JS on IE with RC3.
v0.9.8 - 07/15/05:
Bugfix for JS code mismatch with template.
v0.9.7 - 07/14/05:
Initial release for vB 3.5 beta-4.

NOTE: The above section says NyNe versions, because I go by the name NyNe everywhere accept here.

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

[Chadi]

Is anyone going to help?

[davidw]

Please correct me if I am wrong but, in the installcode:

			<installcode><![CDATA[
$db->hide_errors();
// Create vB Spell Table
$db->query_write("CREATE TABLE IF NOT EXISTS vbspell (
  word varchar(30) NOT NULL,
  sound varchar(10) NOT NULL,
  UNIQUE KEY word (word),
  KEY sound (sound)
) TYPE=MyISAM");

// Remove Old vB Spell Table
$db->query_write("DROP TABLE IF EXISTS " . TABLE_PREFIX . "vbspell");

// Add Dictionary Terms
if (is_file("./DICTIONARY.DIC")) {
$start_time = time();
$last_time = 0;
$words_processed = 0;

$FileSize = filesize("./DICTIONARY.DIC");
$fp = fopen("./DICTIONARY.DIC","r");

while (!feof($fp)) {
	$data = trim(fgets($fp, 4096));
	if ($data != "") {
		$words_processed++;
		$db->query_write("REPLACE INTO vbspell VALUES('" . addslashes($data) . "', '" . metaphone($data) . "')");
		$end_time = time() - $start_time;
		if ($end_time > $last_time) {
			$loc = ftell($fp);
			$percent = round(($loc / $FileSize)*100, 0);
			echo construct_phrase($vbphrase['processing_x'], "$words_processed... (".$percent."%)") . "<br />\n";
			vbflush();
		}
		$last_time = $end_time;
	}
}
fclose($fp);
}
$db->show_errors();
			]]></installcode>

Why is this

// Remove Old vB Spell Table
$db->query_write("DROP TABLE IF EXISTS " . TABLE_PREFIX . "vbspell");

listed right after the create table? - the way that appears, anyone who sets that up will immediately create a table and then remove it. What should be the case is the Remove old vb Spell Table FIRST, then the Create if not exists. Although on paper, it would appear that it would not delete a regular non-prefixed vbspell table, it does, or in my case, did delete it. We had to manually (twice now - once for initial install, and once for reinstall after I reimported the product) set up the vbspell table.

[davidw]

LOL, reading through, someone else has already noticed this as well. :P

[tspore]

So how do I get this to work on my server? I tried to delete code, I tried everything listed on all 9 pages. Anyone have any clues that they could give me?

[Parker Clack]

Christian:

Thanks. That fixed it.

Just remove

// Remove Old vB Spell Table
$db->query_write("DROP TABLE IF EXISTS " . TABLE_PREFIX . "vbspell");

from the product install file and it loads just fine.

[davidw]

Originally Posted by tspore

So how do I get this to work on my server? I tried to delete code, I tried everything listed on all 9 pages. Anyone have any clues that they could give me?

What is it [not] doing?

[ShackMaster]

I installed it as normal... got db error when spell checking. I removed the
// Remove Old vB Spell Table
$db->query_write("DROP TABLE IF EXISTS " . TABLE_PREFIX . "vbspell");
from the .xml install file, imported it again with overwrite enabled.... now clicking on the spell check does nothing.

[jw00dy]

If I remember correctly, I had to delete mine, and actually go to the table in phpmyadmin and smoke the vbspell table as well, then it worked.

[ShackMaster]

lol... it's working now... maybe I wasn't holding my mouth right.

[user02934123123]

Dear all,

I just can't get this to install at all on 3.6.1. When I first tried a normal install with the dictionary file, I got the same problems many others have had: the install script took too long to run, and the server killed it. I then uninstalled the scraps of the mod that had wound their way into the system, and tried the alternative method (as above in this thread); but now always receive the following error during the import run:

PHP Code:

Database error in vBulletin 3.6.1:

Invalid SQL:

                INSERT INTO setting
                    (varname, grouptitle, value, defaultvalue, datatype, optioncode, displayorder, advanced, volatile, validationcode, blacklist, product)
                VALUES
                    (
                    'vbspell_allow_all',
                    'vbspell',
                    '1',
                    '1',
                    'free',
                    'yesno',
                    2,
                    0,
                    1,
                    '',
                    0,
                    'spellvb'
    ),
    (
                    'vbspell_use_groups',
                    'vbspell',
                    '2,5,6,9,19',
                    '5,6',
                    'free',
                    '',
                    3,
                    0,
                    1,
                    '',
                    0,
                    'spellvb'
    ),
    (
                    'vbspell_levenshtein_distance',
                    'vbspell',
                    '3',
                    '3',
                    'free',
                    '',
                    4,
                    0,
                    1,
                    '',
                    0,
                    'spellvb'
    );

MySQL Error  : Duplicate entry 'vbspell_allow_all' for key 1
Error Number : 1062
Date         : Saturday, September 23rd 2006 @ 03:41:45 AM
Script       : http://www.(...)/forum/admincp/plugin.php?do=productimport
Referrer     : http://www.(...)/forum/admincp/plugin.php?do=productadd
IP Address   : 000.000.000.000
Username     : username
Classname    : vb_database 


I've tried modifying the installscript as per comments above, but to no success.

I would deeply appreciate some assistance from anyone who's managed to get the script to work -- right now it simply doesn't function on 3.6.1, as it won't install.