-
Notifications
You must be signed in to change notification settings - Fork 40
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
Keep CKEditor and plugins up to date. #3355
Comments
...we are currently using version 4.7.3 (backdrop/backdrop#2134), which was a security update. |
PR up for review: backdrop/backdrop#2347 Note that the build has automatically added |
New PR to update to 4.11.0: backdrop/backdrop#2361 Notable changes since 4.10.1:
|
I tested image embedding, linking to existing content and file embedding in backdrop/backdrop#2361. All works well for me. |
Thanks @herbdool 👍 ...ideally, I would like us to have a way to get this update out to people that wish to help with testing, and in fact get such changes (CKEditor, jQuery, jQuery UI etc.) out as early as possible to give them enough time to be beta-tested. I realise that people using git as part of their deployments can checkout the branch, but it would help to have a packaged dev version, or even RCs. A subject for the next meeting to be discussed I guess. |
PR updated to upgrade to 4.11.1 ...plus also updated the |
I've merged backdrop/backdrop#2361 into 1.x for 1.12.0. The 3 week lead time before the Jan 15 is less than we wanted, and that's my fault for dallying the merge of this PR. Please keep an eye out for any problems with the CKEditor update so we can correct them before the 1.12 release. Thanks @klonos and @herbdool! I'm not sure if I should close this issue or keep it open to bump to the next version. Thoughts? |
Thanks @quicksketch 👍 ...as also mentioned during the dev meeting, we should encourage all people that have open PRs to close and reopen them, so that the sandboxes get rebuilt with the updated version of CKEditor. We should do that at the very least for any CKEditor-related issues, because it would "grab" a bigger set of testers, and thus help catch any possible breakages sooner. (I'll cross-post this on Gitter 😉) I think leave this ticket open and bump to 1.13. |
RTBC 👍 |
Great, merged backdrop/backdrop#2881. We're now up to 4.12.1. 😄 |
My RTBC here is for this pr: backdrop/backdrop#3103 which brings CKE up to 4.14.0 |
We're now on the current version, CKEditor 4.14.0. |
Well, necessity causes things to get done 😅 ...after the recent 1.19.1 security update, we're now in the most recent v4.16.1: |
backdrop/backdrop#3684 updates us to 4.16.2. |
This is a sibling to #2493
Keeping the editor up to date regularly should minimise troubleshooting issues introduced along the way (because we'll be "jumping" less versions up).
List of things to test each time we update:
PR by @klonos (4.7.3 to 4.11.1): backdrop/backdrop#2361Merged into 1.12.0PR by @quicksketch (4.11.1 to 4.12.1) backdrop/backdrop#2881PR by @quicksketch (4.12.1 to 4.14.0) backdrop/backdrop#3103The text was updated successfully, but these errors were encountered: