Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade CKeditor to latest version #8151

Closed
nino-filigran opened this issue Aug 23, 2024 · 1 comment · Fixed by #8577
Closed

Upgrade CKeditor to latest version #8151

nino-filigran opened this issue Aug 23, 2024 · 1 comment · Fixed by #8577
Assignees
Labels
feature use for describing a new feature to develop security use to identify issue related to security solved use to identify issue that has been solved (must be linked to the solving PR) technical improvement Technical refactor or improvement is needed
Milestone

Comments

@nino-filigran
Copy link

Use case

Currently using the 6.2 version while 9.00 is available.

@nino-filigran nino-filigran added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team labels Aug 23, 2024
@nino-filigran nino-filigran modified the milestone: Release 6.2.15 Aug 23, 2024
@nino-filigran nino-filigran added technical improvement Technical refactor or improvement is needed and removed needs triage use to identify issue needing triage from Filigran Product team labels Aug 23, 2024
@lndrtrbn lndrtrbn self-assigned this Aug 23, 2024
@lndrtrbn
Copy link
Member

CKEditor needs particular attention when migrating as we are building it manually. Required step to be able to customize it, at least for version 6.

Could be nice to check if version 9 allows customization without rebuild

@Archidoit Archidoit self-assigned this Sep 30, 2024
@Archidoit Archidoit linked a pull request Oct 2, 2024 that will close this issue
@Archidoit Archidoit added this to the Release 6.4.0 milestone Oct 2, 2024
Archidoit added a commit that referenced this issue Oct 17, 2024
Co-authored-by: Landry Trebon <landry.trebon@filigran.io>
@Archidoit Archidoit added the solved use to identify issue that has been solved (must be linked to the solving PR) label Oct 17, 2024
labo-flg pushed a commit that referenced this issue Oct 25, 2024
Co-authored-by: Landry Trebon <landry.trebon@filigran.io>
labo-flg added a commit that referenced this issue Oct 25, 2024
Co-authored-by: Archidoit <75783086+archidoit@users.noreply.github.com>
Co-authored-by: Landry Trebon <landry.trebon@filigran.io>
@labo-flg labo-flg added the security use to identify issue related to security label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop security use to identify issue related to security solved use to identify issue that has been solved (must be linked to the solving PR) technical improvement Technical refactor or improvement is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants