This guide outlines the main steps that you need to follow for initializing WProofreader in CKEditor 4.
1. Initialize CKEditor 4
Before integrating and configuring WProofreader, make sure CKEditor 4 is properly configured in your web application. To initialize CKEditor 4, follow the steps described in CKEditor 4 Quick Start Guide.
2. Initialize WProofreader
Choose one of the options below how to enable spelling and grammar checking functionality of WProofreader in CKEditor 4.
Option A. Using autoSearch
When using this method, you need a CONFIG and a wscbundle.js script. After setting up the autoSearch, WProofreader will be enabled as soon as the editable container with CKEditor is in focus. Check a sample below or follow the steps described in the Get started with WProofreader Server (autoSearch).
Option B. Using the init method
When using this method, WProofreader will be started on the editor load.
Initializing WProofreader using init() in CKEditor 4
3. Specify additional server parameters
Make sure you have specified the following server-specific options in CONFIG, which are instructing where spelling and grammar checking requests will be processed:
4. Remove old plugins
Remove SCAYT and WSC Dialog plugins for CKEditor 4 which are integrated by default to avoid any possible issues. It can be done by adding the removePlugins parameter to CKEditor config.js file:
5. Further actions
After completion of the initialization steps, you can customize WProofreader options, its user interface, and behavior using WProofreader customization options. More options and methods for advanced customization are available in API docs.
You can see the demo of CKEditor 4 integration on our website.