CKeditor 5 plugincollection Error in console

Created on 7 February 2024, about 1 year ago

I am facing issue while upgrading CKeditor 4 to CKeditor 5.

I have upgraded the drupal 9 to 10, after that I have created the new Text format and choose the 'CKeditor 5' option to that format. Now I am trying to create a new content, the CKeditor Tools(styles, link, source) or features not working. Only the textarea is shown while selecting the Text format.

Please Support to fix this issue.

🐛 Bug report
Status

Active

Version

1.0

Component

User interface

Created by

🇮🇳India KalaiyarasiThangavel

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @KalaiyarasiThangavel
  • 🇺🇸United States bnjmnm Ann Arbor, MI

    Nothing mentioned in the issue indicates this is specific to the ckeditor5_dev module. Does this issue only happen if the ckeditor5_dev is enabled?

  • 🇮🇳India KalaiyarasiThangavel

    Hi,

    I think its core CKeditor 5 module installed in website. Sorry for mentioning the wrong version. Now i have attached the screenshots to understand the issue.
    For that, we have created the 'Test HTML' for using the CKeditor 5 module. Once it is selected in Text format in content, showing console error.

    Drupal version : 10.2.2

    Thanks.

  • 🇨🇦Canada awasson

    I have also been struggling with this issue on my Full HMTM editing profile. My Basic HTML is fine.

    It happened after upgrading to CKEditor 5 in Drupal 10 from CKEditor 4 in Drupal 9.

    For me, this involved upgrading the Anchor Link module from CKEditor 4 to a CKEditor 5 version.

    I found that the library for Anchor link was not loading and throwing an error that basically crashed the JS interpreter and stopped all of the other JS from running. I would check to make sure that any additional plugins that your using on the text editing profile that is causing issues are not having conflicts.

    Cheers,
    Andrew

  • 🇺🇸United States adriancotter

    Thanks @awasson I had this same issue -- and indeed, I had also not installed the library. Once I got that in it started working again.

Production build 0.71.5 2024