• Trial Hosted SpellChecker Hosted SpellChecker Licensed SpellChecker Upgrade
  Sign Up
• About Us
• Resellers Partners
  Partners
• Customers
• My Account
• Hosted Licensed Application Support Old Support Section

  Support

• SpellChecker - Hosted SpellChecker - Licensed For Search Engines For 3rd Party Applications Novell Netmail Communigate Pro SunOne Messaging Server Domino Custom Dictionaries
  Pricing
• Overview Hosted SpellChecker Licensed SpellChecker For Search Engines For 3rd Party Applications Novell Netmail Communigate Pro SunOne Messaging Server Domino Bulletin Board Systems Custom Dictionaries Custom UI
  Products
• Home

Support - Hosted Version - Migrating to new version

Why is it better?

The new SpellChecker version contains the WebSpellChecker and SpellCheckAsYouType solutions embedded. Please find the instructions to start using this product in your WYSIWYG editor.

The new version supports the latest browsers and Web sites. It is the only product that's going to be updated when new 3rd party products appear in the Internet.

Please follow our step-by-step instructions to migrate to the new WebSpellChecker version:

1. Migrating to new sproxy
2. Migrating to new scripts
   1. spch.js file
   2. fmch.js file
3. Migrating to new API
   • Text box solution (doSpell())
   • Multiple text box solution (FCH_CheckFormTextControls())

1. Migrating to a new sproxy

a. Download the latest version of the sproxy script;
b. Remove all content of the sproxy directory. Unpack downloaded archive to this directory;
c. Login from "My Account" tab to the page with your account information and download sproxy.ini file by clicking the "Download configuration file" link;
d. Place your sproxy.ini file to the sproxy directory.

2. Migrating to new scripts

a. spch.js file

The new version does not require the spch.js script file, but it requires a script derivable by means of sproxy. Just replace the include script as follows:

before migration:
<script type="text/javascript" src="http://example.net/sproxy/spch.js"></script>

after migration:
<script type="text/javascript" src="http://example.net/sproxy/sproxy.ext?cmd=script&doc=wsc"></script>

where: ext is the extension of the sproxy script. To find out the correct extension to use, check the sproxy archive you have downloaded from the SpellChecker.net site.

b. fmch.js file

The new version does not require the fmch.js script file include. Just remove it.

3. Migrating to a new API

a. Text box solution (doSpell())

From now on, the doSpell() function accepts only one parameter: the object with your specific data. Replace all doSpell() function parameter sets as follows:

before migration:
doSpell(lang, element, "http://example.net/sproxy/sproxy.ext", true);
where: lang {String} is the spell check language name; element {Element}is the control element instance.

after migration:
doSpell({ctrl: elementId, lang: lang});
where: elementId {String} is the control element identifier; lang {String} is the spell check language name.

b. Multiple text box solution (FCH_CheckFormTextControls())

The old version required to invoke the specific FCH_CheckFormTextControls() function to check multiple text boxes. Now this job is performed by the doSpell() function.

before migration:
FCH_CheckFormTextControls(elementsList,lang, "http://web-site/sproxy/sproxy.ext");
where: elementsList {String} is the comma-separated control elements list; lang {String} is the spell check language name.

after migration:
doSpell({ctrl: elementsId, lang: lang});
where: elementsId {Array} is an array of control elements identifiers; lang {String} is the spell check language name.

Here is a list of the most common cases to embed WebSpellChecker into your web site. Please contact our tech support if you have not found a solution for you here.