Even though it is highly recommended to always use the latest version of WProofreader package (wscbundle.js), there might be exceptions to this rule. 

Rarely we can introduce drastic changes to the user interface or overall user experience. Thus, it might require extra time for existing customers to adapt to changes.

1. In the initialization of WProofreader, you are required to specify the path to wscbundle.js script. Its default and recommended path is below.

Path to the latest version:

<script type="text/javascript" src="https://svc.webspellchecker.net/spellcheck31/wscbundle/wscbundle.js"></script>

An example of a specific version of wscbunle.js using jsDelivr CDN.

<script src='https://cdn.jsdelivr.net/gh/WebSpellChecker/[email protected]/wscbundle/wscbundle.js'></script>

Select the required release tag from the open WProofreader repository. The scope of changes in each release will be available on the public changelog.

2. Make sure you have the additional service endpoint (serviceProtocol, serviceHost, servicePort, servicePath) parameters explicitly specified in the configuration script as shown below.

serviceProtocol: 'http',
serviceHost: 'svc.webspellchecker.net',
servicePort: '443',
servicePath: 'spellcheck31/api'

Otherwise, you might receive an error like this:

“CORS response parsing error: SyntaxError: Unexpected token 'M', "Method Not Allowed" is not valid JSON”.