WProofreader is multilingual proofreading tool for web applications. It enables grammar and spell check combining spelling and grammar suggestions while you type or work with your text in a dedicated dialog. 

Its auto-searching feature enables detecting new editable fields on the page and proofreading the text they contain automatically on hover selection. No additional actions or plugins are required for enabling WProofreader in a specific WYSIWYG editor or HTML editable control. A single configuration applies to almost all editors and controls. Here is the list of WProofreader supported integrations

This guide outlines the main steps to integrate and configure WProofreader with auto-searching functionality (autoSearch option). All the steps described are provided for the Server version of WProofreader that is hosted and deployed on your server.

1. Initialize WProofreader

There are two approaches for initializing WProofreader with the autoSearch feature in your web app: using the config variable or inline data attributes. Their descriptions follow.

Option A. Initializing using config variable

1. Add config with options

Define the required options in WEBSPELLCHECKER_CONFIG. It can be added to any location on a web page before or after the wscbundle.js script. However, if you add wscbundle.js asynchronously, this CONFIG must be added before the script.

  • Enable autoSearch functionality using the autoSearch parameter.
  • Specify serviceProtocolserviceHostservicePort and servicePath to access the service.

In case of the direct connection to WebSpellChecker AppServer (AppServer is an entry point), you need to configure the SSL connection. Follow the steps described on the Enabling SSL connection with AppServer page (if you missed that step during the installation).

		autoSearch: true,
		enableGrammar: true,
        serviceProtocol: 'https',
        serviceHost: 'your_host_name',
        servicePort: '2880', //2880 is the default port that AppServer listens to. This is the entry point for the service. 
        servicePath: '/'

If you are not able to use a custom port (e.g. 2880) to access the service and deployed the Server to use the FastCGI protocol (via the SSRV.CGI component), you need to use the different values to access the service properly. Now the entry point for the service requests will be the SSRV.CGI component.

		autoSearch: true,
		enableGrammar: true,
        serviceProtocol: 'http(s)',
        serviceHost: 'your_host_name',
        servicePort: '443', // this is the port of your web server or Java application server
        servicePath: ''virtual_directory/script/ssrv.cgi''

You also have an option to load your CONFIG option on your web page from the file. Just create a *.js file (e.g. wscbundle_config.js) with CONFIG. This is an example of the wscbundle_config.js file.

	autoSearch: true,

Here is an example of the script that you need to add on your web page with the path to wscbundle_config.js.

<script type="text/javascript" src="[path_to_config]/wscbundle_config.js"></script>

2. Add WProofreader script

Add the wscbundle.js script on your web page.

<script type="text/javascript" src="http(s)://your_host_name/wscservice/wscbundle/wscbundle.js"></script>

Option B. Initializing using inline data attributes

In general, initialization of WProofreader using inline attributes is a good option if you want to have a single script with the base options. To define an additional option as an inline data attribute, use 'date-wsc-option_name', e.g. 'data-wsc-lang'. You can find the full list of options  here.


Consider the following limitation when using inline data attributes for the WProofreader options: as for now, only options which have boolean or string types can be used as data attributes. The options with array or number type are not supported (e.g. actionItems, suggestionsCount, moreSuggestionsCount).

2. Adjust default settings

You can customize the default options using WProofreader API.

You can check the demos of WProofreader integrations with various rich-text editors on our website.