I'm trying to add a new configuration option pastedHtmlSanitizer to the existing core plugin wysiwygarea. My problem is that this new configuration option is ignored in any custom config.js files I use.
So... I've added the following to _source/plugins/wsyiwygarea/plugin.js.
And this works fine - the option is set and picked up.
Then I've added the following to my config.js for the app I'm writing:
The result is that the other config options (eg. 'bodyClass') are being picked up by the editor instance, but my pastedHtmlSanitizer option is being ignored and is being set to the default specified in the plugin code.
I should also note that the option is passed through correctly if specified when instanciating the editor instance. Eg.
The above works fine.
I've read through as much of the source code as I can possibly imagine causing a different behavior between different options, but I can't find what's causing this option to be ignored.
Anyone had this issue? Anyone know what I'm doing wrong?
So... I've added the following to _source/plugins/wsyiwygarea/plugin.js.
/** * A function for sanitizing pasted HTML before inserting into the wysiwyg window * @type Function * @default <code>null</code> * @example * config.pastedHtmlSanitizer = function(html) { return html.replace('foo', 'bar'); } */ CKEDITOR.config.pastedHtmlSanitizer = null;
And this works fine - the option is set and picked up.
Then I've added the following to my config.js for the app I'm writing:
CKEDITOR.editorConfig = function( config ) { ... ... config.bodyClass = 'rich_text ck_rich_text'; config.pastedHtmlSanitizer };
The result is that the other config options (eg. 'bodyClass') are being picked up by the editor instance, but my pastedHtmlSanitizer option is being ignored and is being set to the default specified in the plugin code.
I should also note that the option is passed through correctly if specified when instanciating the editor instance. Eg.
CKEDITOR.replace('#some_text_area', { pastedHtmlSanitizer: function(html) {return html.replace('foo', 'bar'); } });
The above works fine.
I've read through as much of the source code as I can possibly imagine causing a different behavior between different options, but I can't find what's causing this option to be ignored.
Anyone had this issue? Anyone know what I'm doing wrong?
Re: Adding new configuration options
Re: Adding new configuration options