CKEditor - How to enable spell check

dbs

It was not a list of possible steps.
All steps are needed.
Therefore
QuoteYou see, it is not so easy.
[url="https://onkel-franky.de"]https://onkel-franky.de[/url]

Nicky

Way too complicated for me to fix. I did try this though -

QuoteNext is, edit the ckeditor/include.php. Add wsv or scayt to the allowed plugins in line 166 ($ckeditor->config['extraPlugins']).

but all my pages' WYSIWYG & source markup disappeared (which returned after I restored the original include.php).

So, I'll stick with using a browser spell checker I guess...

But thanks for looking at this.

Luisehahne

Quote from: dbs on February 06, 2020, 07:34:24 AM

I think the spellcheck ist not implemented for reasons.
To use it you need also the right plugin in ckeditor/ckeditor/plugins/
Maybe wsv or scayt are the right ones, but do they work with this ckeditor version?
Next is, edit the ckeditor/include.php. Add wsv or scayt to the allowed plugins in line 166 ($ckeditor->config['extraPlugins']).
Next is, contains your toolbar the right placeholder for the plugin?


The reason to remove some plugins was to limit the package zip size  to max 2MB

Dietmar
Note: Once the code has been generated, it is easy to debug. It's not a bug, it's a feature!

dbs

Hello, in PHP<?php
this
/*
    config.scayt_autoSt artup = true;
*/

this
/*
// config.scayt_autoSt artup = true;
*/

and this
// config.scayt_autoSt artup = true;
do all the same. It comments out the code, make it unusable.
(the space in Startup is a forum bug)

I think the spellcheck ist not implemented for reasons.
To use it you need also the right plugin in ckeditor/ckeditor/plugins/
Maybe wsv or scayt are the right ones, but do they work with this ckeditor version?
Next is, edit the ckeditor/include.php. Add wsv or scayt to the allowed plugins in line 166 ($ckeditor->config['extraPlugins']).
Next is, contains your toolbar the right placeholder for the plugin?

You see, it is not so easy.
[url="https://onkel-franky.de"]https://onkel-franky.de[/url]

Nicky

Thanks, I did try this,

  config.browserContextMenuOnCtrl = true;

    config.basicEntities = true;

    config.entities = false;
/*
// config.scayt_autoStartup = true;
*/

and did the same with the wb version on the same line as in my original post. No change. Tried Chrome, FF, Opera, and Edge.


johnbroeckaert

try //   instead of /* in front of the line
so
// config.scayt_autoSt artup = true;

Nicky

Hello Bakers,

CKEditor help - how to enable spell checking.


I changed this from false to true in these two lines shown below in bold, logged-out and restarted WB (v2.12.2 r379)



wb_ckconfig.js

config.browserContextMenuOnCtrl = true;

    config.basicEntities = true;

    config.entities = false;
/*
    config.scayt_autoStartup = true;
*/



settings_config.js

config.browserContextMenuOnCtrl = true;

    config.basicEntities = true;

    config.entities = false;
/*
    config.scayt_autoStartup = true;
*/


Other than spell checking, CKEditor works fine for me. But there is no spell check icon, button or toolbar.

I seem to remember spell check was enabled by default in early WB versions.

What else do I need to do to get spellcheck working? Could it be a server issue ?

Nicky