ckEditor upgrade?

[Scott Mitchell]

Hi all,

One of our users discovered an issue with the RichText editor. He wanted to turn an image into a link to a DAM object, so he highlighted the image and clicked the DAM object link button. But when he selected the object from the DAM, the editor converted the image into text and removed the image. I looked into the ckEditor. It looks like the version we have in our Magnolia 6.2 instance is version 4.3.2, and it is around 6 years old.

So, I would like to upgrade the ckEditor in Magnolia. The latest ckEditor 4 is v4.21. Has anyone done this? Can I just replace the ckeditor folder with a newer version of ckEditor, or is there more involved? 

I'm also concerned about the impending end-of-life for ckEditor 4 at the end of this month. https://ckeditor.com/ckeditor-4/ So, perhaps ckEditor 5 could be an upgrade target after 4.21.

Also, does anyone know how to check the version of ckEditor in a Magnolia 5.6.8 instance? In this version, it looks like it is part of Vaadin, and not the full ckEditor install like it is in 6.2. 

Thanks,
Scott

[Mykola Soldatenkov]

Might be a hack, but...

If you open devtools before loading dialog for the first time you'll see, that Magnolia makes request to
/magnoliaAuthor/VAADIN/widgetsets/info.magnolia.widgetset.MagnoliaProWidgetSet/ckeditor/ckeditor.js.

Officially there is no proof for that nor this is a preferred solution, but it is possible to generate custom ckeditor bundle with the help of the builder (https://ckeditor.com/cke4/builder) and place it in:
a) /tomcat/VAADIN/widgetsets/info.magnolia.widgetset.MagnoliaProWidgetSet/ folder (for DX Core)
b) /tomcat/VAADIN/widgetsets/info.magnolia.widgetset.MagnoliaWidgetSet/ folder (for CE)
Keep in mind, that it is outside of webapps folder and might require custom CI/CD configuration

You can replace only minor releases that way, because ckeditor 5 works differently - it relies on es6 modules and it requires refactoring of the server side code of the RichTextField and also newer implementation of the Page link plugin and Asset link plugin

--
You received this message because you are subscribed to the Google Groups "Magnolia User Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to user-list+...@magnolia-cms.com.
To view this discussion on the web, visit https://groups.google.com/a/magnolia-cms.com/d/msgid/user-list/CA%2B5HZ%3DyDQ-Os6N56mzGar4b%3DEzmQiOzwxdmFdR2%2Bhy0-K7oTBA%40mail.gmail.com.

--

-- 

Powyższa wiadomość wraz z ewentualnymi załącznikami jest przeznaczona wyłącznie do wiadomości osób lub podmiotów, do których jest w sposób zamierzony zaadresowana. W przypadku otrzymania powyższej wiadomości w wyniku pomyłki, prosimy o pilne powiadomienie o tym fakcie nadawcy oraz o usunięcie wiadomości z systemu, a także o nie rozpowszechnianie treści w niej zawartych. Otrzymanie powyższej wiadomości nie może stanowić podstawy do jakichkolwiek zobowiązań nadawcy tej wiadomości wobec osób nie będących jej zamierzonymi adresatami. 

This e-mail message and any attachments is intended solely for the use of the persons or entities to whom it is intentionally addressed. If you have received this message in error, please notify the sender about this fact immediately and delete it completely from your computer system. Please do not disseminate this message unless you are the intended recipient of it. This e-mail message shall not create any legal obligation on the part of the sender to persons who are not intended recipients of it.

[Roman Kovařík]

Hi Scott,

You should be able to configure a redirect for the CKeditor files. https://docs.magnolia-cms.com/product-docs/6.2/Administration/URI-mapping/Virtual-URI-mapping.html#_via_yaml.

You can see all the files the CKEditor requests in the browser, as Mykola pointed out.

I'm not sure if the described issue is caused by the really old version of CKEditor (I don't even remember such old version Magnolia 6.2) or an old version of Magnolia itself.

There was a lot of fixes lately.

Hope that helps 

Roman