CKEditor 4 Documentation

Reporting Issues

If you feel you found an issue in CKEditor, we will be grateful for letting us know. Before you create a bug report, however, please read our guidelines on how to do it properly and most efficiently.

Reproduce on Demo Page

To eliminate the chance that the issue might be caused by some third-party software or your customizations, try to reproduce the issue on CKEditor samples in CKEditor SDK first.

CKEditor SDK samples are always running the latest editor version. Please note that if the problem was fixed in one of the releases that succeeded the version you are using, you will need to upgrade your CKEditor installation as we do not backport fixes.

Most of the issues are reproducible on samples. If you have a different case though, no problem. Go ahead with the next steps.

Avoid Duplicates

Before you file a new issue, make sure your issue has not been reported yet. Use the search page to check it. If the issue has already been reported, just add a 👍 (+1) reaction to it. During our GitHub transition period you can also check CKEditor's former bug tracker. If the issue is there but not on GitHub, put a reference link to the original Trac issue.

CKEditor is in active development, so there is a chance that we have already fixed your issue in the current code base. You should thus also test it on the last Nightly Build: http://nightly.ckeditor.com/

Reporting Issues

Once you are sure that you have a valid issue to report, it is time to learn more about our Issues Tracker Site.