CKEditor WYSIWYG Editor for MODX Revolution - Support Thread

10 Posts

mvk Reply #61, 10 years, 7 months ago

I've just tried to customize the toolbar via the corresponding system setting. However, there was a syntax error and I wasn't able to reset the setting with the backend, as only the top menu and the left tree division was shown on every page. So here's my tip for anyone that has the same problem: If you have access to the Modx database you can easily reset the toolbar setting by deleting the ckeditor.toolbar record in the modx_system_settings table. If you are using a query based DB client just excute the following query:

UPDATE modx_system_settings SET value = '' WHERE modx_system_settings.key = 'ckeditor.toolbar';

After that, you have to empty the Modx cache. Now the backend should work properly again.

57 Posts

ntech Reply #62, 10 years, 3 months ago

Hi,

Not sure where to go to submit a bugfix, the plugin was not loading on IE8 browsers (i know, but the client uses IE8...) we determined this was due to a forEach loop in the plugin:

core/components/ckeditor/elements/plugins/ckeditor.plugin.php

Specifically in the Ext.onReady JavaScript call

I made the following change which fixes the bug:

Ext.onReady(function() {
    var textAreas = Ext.query('$selector');
    Ext.each(textAreas, function(textArea){
        var htmlEditor = MODx.load({
            xtype: 'modx-htmleditor',
            width: 'auto',
            height: parseInt(textArea.style.height) || 200,
            name: textArea.name,
            value: textArea.value || '<p></p>'
        });

        textArea.name = '';
        textArea.style.display = 'none';

        htmlEditor.render(textArea.parentNode);
        htmlEditor.editor.on('key', function(e){ MODx.fireResourceFormChange() });
    });
});

Thought I'd post it here so it can be updated in a future release.

Thanks for a great plugin btw!

149 Posts

danya_postfactum Reply #63, 10 years, 3 months ago

Thanks ntech. I will add this fix to the next release (unfortunately, I have no idea when), although I usually does not care about IE8 support.

76 Posts

johnnyp Reply #64, 10 years, 2 months ago

When I add settings to config.js they don't apply. Am I missing something?

76 Posts

johnnyp Reply #65, 10 years, 2 months ago

Any chance of someone giving me some help – config.js doesn't seem to do anything.

I need to configure ignoreEmptyParagraph to true, otherwise the empty editors dump paragraph tags into my pages. Especially annoying when you have a basic optional TV that can never be empty.

94 Posts

William A Reply #66, 10 years, 1 month ago

Is it possible to set your own style classes as you do in Tiny?

--------------------------------------
www.williamastrom.se

17 Posts

fk_abs Reply #67, 10 years, 1 month ago

Quote from: DesignByWilliam at Apr 11, 2014, 10:18 AM

Is it possible to set your own style classes as you do in Tiny?

For sure, you need an stylesheet, which defines your style.
Then set your custom-classes in the settings section and add the styles to the styles.js of the editor.

You can even define which element for which style you want to use easily.
See my attachements, I just "screenshoted" the steps together for you ,-)

EDIT:
you can also define the styles itself in the styles.js instead of using a stylesheet and classes (note the predefined "style-blocks" in the style.js), but I recommend you using classes because it makes the source much more readable and this will definitely come in handy in e.g. debugging browser-related style-issues [ed. note: fk_abs last edited this post 10 years, 1 month ago.]

94 Posts

William A Reply #68, 10 years, 1 month ago

Thanks alot! Will make it easier on my clients:)

--------------------------------------
www.williamastrom.se

98 Posts

dennisleahy Reply #69, 10 years ago

I thought this thread was getting a bit long, so I started a couple of other threads about this extremely important MODX Extra (for which I want to thank dayna_postfactum!)

I was frustrated by not being able to control the CSS that the WYSIWYG (text area) uses, and the answer may be simple to you, but it wasn't my first thought. Or my second...

So, I'll put it in this thread so more people find it:
It is quite likely that you will NOT be able to simply point at your site's CSS file and get the WYSIWYG to display the way you want. The default behavior is to use the CSS body descriptor, not whatever CSS you have for your page's content DIV.

So, make a copy of your site's CSS file that describes the HTML body, and Save As a new CSS filename. In that new CSS file, copy the code from your content DIV to the body descriptor. That new filename's full URL is what you should then specify in MODX as the CSS file for the CKEditor.

Hope this helps someone.

Dennis

10 Posts

mvk Reply #70, 10 years ago

I've just freshly installed MODx Revo 2.2.14 and haven't done anything besides creating a simple template and installing Wayfinder and Breadcrumbs via the Package Manager. Unfortunately, after I installed CKEditor 1.1.1, there was only the top menu and the left division with the resources/elements/file-trees on virtually every page in the Manager. In order to be able to use the Manager again I had to disable the plugin via the database. I completely removed CKEditor and installed it again, but it had no effect. Is there any solution yet?