I must be confused. I thought the idea with moving the config files (e.g. wb_ckconfig.js) to my template folder was so I can make changes there INSTEAD of the source module files, since the module files will be overwritten if you update/upgrade.
"problem" is the order in the ckeditor-include-file.
take a look into this file to understand - nearly in the top of this file you found some basic settings like (only 3 for example)
- $ckeditor->config['skin'] = 'moonocolor';
- $ckeditor->config['format_tags'] = 'p;div;h1;h2;h3;h4;h5;h6;pre;address';
- $ckeditor->config['resize_dir'] = 'vertical';
after this basic settings comes the path to the config files.
if WB calls the editor, it starts to load the settings in the top of the include, after that, it looks into the custom config files, but it is too late, to load the settings for this values again
there are only two ways to change the config from this point
way 1: load the custom config files before set standard values (like older ckeditor versions)
way 2: load custom values in the function call, but then you have to change the function (same problem with overwrite in upgrade)
i'll show way 1 for you and i'll talk with marmot - maybe its possible to change the order in the include-file
solution is testet and works - after that, you can set your custom settings in your individual config-files like wb_ckconfig.js in template folder
look at the begin from the ckeditor / include.php for the standard settings like this
* A list of semi colon separated style names (by default tags) representing
* the style definition for each entry to be displayed in the Format combo in
* the toolbar. Each entry must have its relative definition configuration in a
* setting named "format_(tagName)". For example, the "p" entry has its
* definition taken from config.format_p.
* @type String
* @default 'p;h1;h2;h3;h4;h5;h6;pre;address;div'
$ckeditor->config['format_tags'] = 'p;div;h1;h2;h3;h4;h5;h6;pre;address';
//$ckeditor->textareaAttributes = array( "rows" => 8, "cols" => 80 );
* If you also want to look for the template-specific css, you can simple add the files like below.
* Just uncomment one or both of the following two lines ;-) by removing the double-slashes ...
// $files['contentsCss']= '/template.css';
// $files['contentsCss']= '/css/template.css';
* The skin to load. It may be the name of the skin folder inside the editor installation path,
* or the name and the path separated by a comma.
* Available skins: moono, moonocolor
$ckeditor->config['skin'] = 'moonocolor';
// $ckeditor->config['contentsLangDirection'] = 'rtl';
* Setup the CKE language
$ckeditor->config['language'] = strtolower(LANGUAGE);
// The language to be used if config.language is empty and it's not possible to localize the editor to the user language.
// $ckeditor->config['defaultLanguage'] = strtolower(DEFAULT_LANGUAGE);
$ckeditor->config['defaultLanguage'] = 'en';
$ckeditor->config['resize_dir'] = 'vertical';
cut off this lines and paste it nearly to the end, but before this lines
must stay at the last lines in the include.php
echo $ckeditor->to_HTML( $name, $content, $ckeditor->config);