This guide outlines the main steps that you need to follow for initializing WProofreader in 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.
Choose one of the options below how to enable spelling and grammar checking functionality of WProofreader in CKEditor 4.
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. Follow the steps described in the Get Started with WProofreader Cloud (autoSearch) or below.
<script> window.WEBSPELLCHECKER_CONFIG = { autoSearch: true, lang: 'auto', // enable language auto-detection option theme: 'gray', // adjust color theme of WProofreader to look more native to CKEditor 4 enableAutoSearchIn: ['.cke_wysiwyg_frame'], // limit WProofreader work only to CKEditor 4. They hide the original element and create an iframe element with cke_wysiwyg_frame class. serviceId: 'your-service-ID' // the activation key for the Cloud-based version }; </script> <script type="text/javascript" src="https://svc.webspellchecker.net/spellcheck31/wscbundle/wscbundle.js"></script> |
Option B. Using the init method
When using this method, WProofreader will be started on the CKEditor 4 load.
After you have initialized WProofreader in CKEditor 4, 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.