CKEditor WYSIWYG Editor for MODX Revolution - Support Thread

1) Check CKEditor plugin is present and enabled.
2) Ensure your resource has `Use RTE` option set.
3) Check /manager/assets/components/ckeditor/ folder.
4) Open DevTools (F12) and check there are no javascript errors.

(it appears that everything I check has the same owner/group : 3065 3065)

core/components/ckeditor Permissions: 0755, Owner/Group 3065 3065

core/components/ckeditor/elements/plugins Permissions: 0755, Owner/Group 3065 3065

core/components/ckeditor/model/ckeditor Permissions: 0644, Owner/Group 3065 3065

---------------------------
core/packages/ has folders for both the old (ckeditor-1.1.1-pl) and new (ckeditor-1.3.0-pl)plug-in/Extras
permissions for the old ckeditor folder and files (which was working, prior to the MODX upgrade) seems to be the same as the new folder and files (and all have the same owner/group : 3065 3065)

I do not see any folder or filenames that include "www-data", in fact, nothing with "www" and nothing with "data" (though I have not opened and examined the underlying php files)

---------------------
[venting]Very, very frustrating. It just should not be this difficult to upgrade MODX Revolution. This is my first site I've tried to set-up with MODX, and if I had not already invested hundreds of hours in trying to learn Evo, then Revo, I would scrap MODX and find a different content management system.[/venting]

-Dennis

Quote from: Tom at Jan 21, 2015, 08:47 AM

These are not MODx settings, but ownership of various folders inside the installation directory. If you are hosting on a Lunix box, you might find them in /var/www/core/components

I guess this is my fault. Could you give me access to the manager panel?

@dennisleahy: www-data is usually the name for user and also usually the same name is used for group. The webserver operates as that user. You can Google for more info on that. Besides a name, each user & group have numbers. Your 3065 might very likely be the same as "www-data" e.g. the webserver user... but just to be sure

BTW: danya_postfactum is the guru here... not me for sure!

danya_postfactum is the guru here

If I were guru, people would not have troubles with CKEditor

Quote from: danya_postfactum at Jan 21, 2015, 09:07 AM

1) Check CKEditor plugin is present and enabled.
2) Ensure your resource has `Use RTE` option set.
3) Check /manager/assets/components/ckeditor/ folder.
4) Open DevTools (F12) and check there are no javascript errors.

Thanks for replying, Danya

1) Check CKEditor plugin is present and enabled.
Yes

2) Ensure your resource has `Use RTE` option set.
I don't see "Use RTE" anywhere. If I go to the resource, and click on the resource (the test webpage) then click on the "Settings" tab, I see a checkbox "Rich Text" and it is checked. Is this what you mean? I unchecked it and re-checked the checkbox.

3) Check /manager/assets/components/ckeditor/ folder.
What specifically am I looking for? The folder does exist and has numerous subfolders.

4) Open DevTools (F12) and check there are no javascript errors.
I don't fully know what I'm doing when in DevTools (usually just use it to inspect elements), but see no indication of errors. I hit 'Reload' on the Network tab, and now the CKEditor shows up.

I don't understand why that "Reload" would get the RTE working again - I would think that clearing cache and logging out and back in would have already do it...but, wherever the magic came from, it IS working.

Thanks, Danya!

-Dennis [ed. note: dennisleahy last edited this post 11 years, 8 months ago.]

OK, wow, it has been a journey, and now I'm back to about where I was before the Revo 2.3.2 upgrade and the CKEditor 1.3.0 upgrade. (Thanks to Danya)

CKEditor is extremely powerful and versatile. If I was the MODX developer, CKEditor would be a core component, not an Extra. (TinyMCE has always been good, but never better than CKEditor.)

I tried creating a couple of separate threads:

How to: make CKEditor display CSS properties correctly in dropdowns?
https://forums.modx.com/thread/89902/how-to-make-ckeditor-display-css-properties-correctly-in-dropdowns#dis-post-494105
----------------------

How to: make CKEditor display CSS properties correctly in WYSIWYG textarea?
https://forums.modx.com/thread/90280/how-to-make-ckeditor-display-css-properties-correctly-in-wysiwyg-textarea
----------------------

CKEditor suggestion: include URL to customization files, per template and TV.
https://forums.modx.com/thread/90484/ckeditor-suggestion-include-url-to-customization-files-per-template-and-tv#dis-post-496222
----------------------

to talk about CKEditor, because I hated to see this thread get filled-up with anything and everything CKEditor related, but perhaps Danya wants to keep all of this under one roof. So,...

I believe that once website developers get the CKEditor's WYSIWYG CSS and CKEditor's built-in "template" functionality working properly, it will be the way most website developers deliver MODX sites to the users (content creators.)

My thread (URL, above) "How to: make CKEditor display CSS properties correctly in WYSIWYG textarea?" shows how to get the WYSIWYG text input area to actually be WYSIWYG - if you are good enough with CSS to make a modified version of your site's CSS file to "fool" CKEditor. I'm almost good enough.

My final frontier for most of this site is to get CKEditor to display 3 columns (not 5), where the center column is liquid (or at least fills the available screen space on the content creator's monitor.
This is how close (or how far) I have come to getting it:


The problem is in the CSS used for the WYSIWYG - the page (with 3 columns) renders correctly:

Solved the issue of the CSS used by CKEditor providing a WYSIWYG layout for content creators. This thread is part of the solution, but you need to just keep tweaking the CSS that the CKEditor will see until it "fakes" the CSS that the rendered pages will use.

-Dennis

[ed. note: dennisleahy last edited this post 11 years, 8 months ago.]

Hello,

I'm stuck with something that seems pretty obvious but I don't know how to make it work.
I'm trying to add a custom template with the "templates" ckeditor plugin.

I created my template.js file, based on the default.js in manager/assets/components/ckeditor/plugins/templates/templates/, I added the line in manager/assets/components/ckeditor/config.js file, I cleared MODx cache but nothing.

I tried to modify the default list of templates by modifying the default.js file, just to check, and nothing is happening in my resource's ckeditor.

How can I make the changes I made, happen in my resource's ckeditor ?