MTJ
MTJ

Reputation: 1097

CKEditor custom build from source incl. certain ticket fix

I need to have new feature that was completed in http://dev.ckeditor.com/ticket/10931 (Allow nesting widgets) in the build.

I know that it allows various ACF bugs to appear since ACF doesn't currently filter widgets within widgets, but I think we can live with it while waiting for 4.5 to arrive.

Should it work by checking out Major branch from https://github.com/ckeditor/ckeditor-dev and doing a build on it?

Upvotes: 0

Views: 45

Answers (1)

oleq
oleq

Reputation: 15895

The branch you mentioned is unstable and not recommended for production (see the REDAME).

This repository contains the following branches:

  • master: development of the upcoming minor release.
  • major: development of the upcoming major release.
  • stable: latest stable release tag point (non-beta). *latest: latest release tag point (including betas).
  • release/A.B.x (e.g. 4.0.x, 4.1.x): release freeze, tests and tagging. Hotfixing.

Even though some features have already been merged into master or major, they're not production-ready until released. This is because of unpredicted interactions between plugins and possible bugs (regressions), which are detected during comprehensive testing phase, once the code is frozen.

There's always a risk that the feature is broken or the API will change, making migration to stable version of CKEditor complicated in the future. Of course, you can build CKEditor package out of unstable branch, i.e. with ckeditor-presets tool, but I don't recommend using it in production environment.

Also note that building a package based on major means including other features an fixes awaiting final testing in upcoming release, which may broke your application even more. Since http://dev.ckeditor.com/ticket/10931 is quite complex, extracting related commits only may be quite tricky in your case.

Upvotes: 1

Related Questions