The autoSearch 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. HTML editable controls: <input> disabled by default <textarea> Elements with contenteditable attribute set to ‘true’: <div> <iframe> WProofreader also has a plugin for WordPress 4.x and WordPress 5.x. For more details, check the official repository of WProofreader plugin for WordPress.
HTML integration WYSIWYG editors
HTML editable controls:
<input> disabled by default
Elements with contenteditable attribute set to ‘true’:
WProofreader also has a plugin for WordPress 4.x and WordPress 5.x. For more details, check the official repository of WProofreader plugin for WordPress.
1. Obtain activation key
Sign up for the trial version to get started with WProofreader Cloud. Once you have subscribed, you will receive an email with your service ID, an activation key, required for the WProofreader service activation. If you already have one, you can skip this step.
If you already have one, you can skip this step.
2. Initialize WProofreader
Choose one of the options below to enable the spelling and grammar checking functionality of WProofreader in your rich text editor.
Option A. Using autoSearch
The fastest and easiest approach for WProofreader initialization in a rich text editor.
When using this method, you need a config variable 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).
Option В. Using the init method
When using this method, WProofreader will be started on the editor load. For details, refer to one of the guides explaining how to use the init() method with the most popular rich text editors:
- Initializing WProofreader in CKEditor 4
- Initializing WProofreader in CKEditor 5 v12.0+
- Initializing WProofreader in Froala Editor 3
- Initializing WProofreader in TinyMCE 5
- Migrating from SCAYT and WSC Dialog Plugins for CKEditor 4 to WProofreader
- Disabling WProofreader in source mode of WYSIWYG editors
- Configuring WProofreader Cloud for CKEditor 5 up to v11.2.0
- Getting started with WProofreader plugin for CKEditor 5
- Initializing WProofreader in TinyMCE 3
- Integrating WProofreader into Angular, React, Vue.js-based apps
3. WProofreader in action
Wonder how it works? Check public demos to see how WProofreader works with some WYSIWYG editors.