[MGNLUI-8013] CKEditor 5 Created: 27/Apr/23  Updated: 08/Feb/24

Status: In Progress
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0

Type: Epic Priority: Neutral
Reporter: Roman Kovařík Assignee: Dominik Maslanka
Resolution: Unresolved Votes: 1
Labels: security
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Relates
dependency
is depended upon by MGNLUI-8431 RTF Configuration from multiple files... Accepted
is depended upon by MGNLDAM-1218 Introduce imageUrl into chooseAsset A... Closed
Template:
Epic Name: CKEditor 5
Acceptance criteria:
Empty
Date of First Response:
Team: Nucleus
Work Started:

 Description   

Problem

https://ckeditor.com/blog/ckeditor-4-end-of-life/

Expected results

Customers can safely use a supported rich text editor.

Actual results

CKEditor 4 reaches its End of Life (EOL) in June 2023. From then onwards, it’ll no longer be updated, have security patches and bug fixes, or new features.

Workaround

https://ckeditor.com/blog/ckeditor-4-end-of-life/#2-extended-support-model

Possible solutions

  • Purchase the Extended Support Model (link in the Workaround section)
  • Implement (all these will most likely introduce major incompatibilities and need major effort)

Result of the spike:



 Comments   
Comment by Roman Kovařík [ 27/Apr/23 ]

Suggested steps:

  1. MGNLUI-8014 Replace the richTextField implementation with a simple HTML editor (Magnolia 6.3)
    • if cloud customers don't use more complex features like asset or page links
  2. MGNLVA-31 Remove CKEditor sources (Magnolia 6.3)
  3. MGNLUI-8019 Provide an alternative implementation of richTextField (Magnolia 6.2)

Although Upgrade to CKEditor5 is included in this epic, it can be declined.

Generated at Mon Feb 12 09:51:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.