Error codes

Thrown when there is an attempt to make changes to the view tree when it is in incorrect state. This may cause some unexpected behaviour and inconsistency between the DOM and the view. This may be caused by:

calling change or forceRender during rendering process,
calling change or forceRender inside of post-fixer function.

`ckeditor-duplicated-modules`

This error is thrown when due to a mistake in how CKEditor 5 was installed or initialized, some of its modules were duplicated (evaluated and executed twice). Module duplication leads to inevitable runtime errors.

There are many situations in which some modules can be loaded twice. In the worst case scenario, you may need to check your project for each of these issues and fix them all.

Trying to add a plugin to an existing build

If you import an existing CKEditor 5 build and a plugin like this:

import ClassicEditor from '@ckeditor/ckeditor5-build-classic';
import Highlight from '@ckeditor/ckeditor5-highlight/src/highlight';

Then your project loads some CKEditor 5 packages twice. How does it happen?

The build package contains a file which is already compiled with webpack. This means that it contains all the necessary code from e.g. @ckeditor/ckeditor5-engine and @ckeditor/ckeditor5-utils.

However, the Highlight plugin imports some of the modules from these packages, too. If you ask webpack to build such a project, you will end up with the modules being included (and run) twice — first, because they are included inside the build package, and second, because they are required by the Highlight plugin.

Therefore, you must never add plugins to an existing build unless your plugin has no dependencies.

Adding plugins to a build is done by taking the source version of this build (so, before it was built with webpack) and adding plugins there. In this situation, webpack will know that it only needs to load each plugin once.

Read more in the "Installing plugins" guide.

Confused an editor build with an editor implementation

This scenario is very similar to the previous one, but has a different origin.

Let's assume that you wanted to use CKEditor 5 from source, as explained in the "Building from source" section or in the "Quick start" guide of CKEditor 5 Framework.

The correct way to do so is to import an editor and plugins and run them together like this:

import ClassicEditor from '@ckeditor/ckeditor5-editor-classic/src/classiceditor';
import Essentials from '@ckeditor/ckeditor5-essentials/src/essentials';
import Paragraph from '@ckeditor/ckeditor5-paragraph/src/paragraph';
import Bold from '@ckeditor/ckeditor5-basic-styles/src/bold';
import Italic from '@ckeditor/ckeditor5-basic-styles/src/italic';

ClassicEditor
    .create( document.querySelector( '#editor' ), {
        plugins: [ Essentials, Paragraph, Bold, Italic ],
        toolbar: [ 'bold', 'italic' ]
    } )
    .then( editor => {
        console.log( 'Editor was initialized', editor );
    } )
    .catch( error => {
        console.error( error.stack );
    } );

However, you might have mistakenly imported a build instead of the source ClassicEditor. In this case your imports will look like this:

import ClassicEditor from '@ckeditor/ckeditor5-build-classic';
import Essentials from '@ckeditor/ckeditor5-essentials/src/essentials';
import Paragraph from '@ckeditor/ckeditor5-paragraph/src/paragraph';
import Bold from '@ckeditor/ckeditor5-basic-styles/src/bold';
import Italic from '@ckeditor/ckeditor5-basic-styles/src/italic';

This creates the same situation as in the previous section because you use a build together with source plugins.

Remember: @ckeditor/ckeditor5-build-* packages contain editor builds and @ckeditor/ckeditor5-editor-* contain source editors.

Loading two or more builds on one page

If you use CKEditor 5 builds, you might have loaded two (or more) ckeditor.js files on one web page. Check your web page for duplicated <script> elements or make sure your page builder/bundler includes CKEditor only once.

If you want to use two different types of editors at once, see the "Using two different editors" section.

Using outdated packages

Building CKEditor 5 from source requires using multiple npm packages. These packages have their dependencies to other packages. If you use the latest version of, for example, @ckeditor/ckeditor5-editor-classic with an outdated version of @ckeditor/ckeditor5-image, npm or yarn will need to install two different versions of @ckeditor/ckeditor5-core because @ckeditor/ckeditor5-editor-classic and @ckeditor/ckeditor5-image may require different versions of the core package.

The solution to this issue is to update all packages to their latest version. We recommend using tools like node-check-updates which simplify this process.

Conflicting version of dependencies

This is a special case of the previous scenario. If you use CKEditor 5 with some third-party plugins, it may happen that even if you use the latest versions of the official packages and the latest version of these third-party packages, there will be a conflict between some of their dependencies.

Such a problem can be resolved by either downgrading CKEditor 5 packages (which we do not recommend) or asking the author of the third-party package to upgrade its depdendencies (or forking their project and doing this yourself).

Note: All official CKEditor 5 packages (excluding integrations and ckeditor5-dev-* packages) are released in the same major version. This is — in the x.y.z, the x is the same for all packages. This is the simplest way to check whether you use packages coming from the same CKEditor 5 version. You can read more about versioning in the Versioning policy guide.

Packages were duplicated in `node_modules`

In some situations, especially when calling npm install multiple times, it may happen that npm will not correctly "deduplicate" packages.

Normally, npm deduplicates all packages so, for example, @ckeditor/ckeditor5-core is installed only once in node_modules/. However, it is known to fail to do so from time to time.

We recommend checking if any of the steps listed below help:

rm -rf node_modules && npm install to make sure you have a clean node_modules/ directory. This step is known to help in most cases.
If you use yarn.lock or package-lock.json, remove it before npm install.
Check whether all CKEditor 5 packages are up to date and reinstall them if you changed anything (rm -rf node_modules && npm install).

If all packages are correct and compatible with each other, the steps above are known to help. If not, you may try to check with npm ls how many times packages like @ckeditor/ckeditor5-core, @ckeditor/ckeditor5-engine and @ckeditor/ckeditor5-utils are installed. If more than once, verify which package causes that.

`cloud-services-internal-error`

An internal Cloud Services error occurred.

`cloudservices-reconnection-error`

Reconnection error.

`collaboration-missing-channelId`

Unique collaboration.channelId configuration is required for defining name for data stores. Note that application instances with the same channelId will share data each other.

`collection-add-invalid-id`

This item's id should be a string.

`collection-add-item-already-exists`

This item already exists in the collection.

`collection-add-item-bad-index`

The index number has invalid value.

`collection-bind-to-rebind`

The collection cannot be bound more than once.

`collection-get-invalid-arg`

Index or id must be given.

`collection-remove-404`

Item not found.

`commandcollection-command-not-found`

Command does not exist.

Parameters

commandName : String: Name of the command.

`commentsrepository-active-missing-comment-thread`

Cannot set not existing comment thread as an active. Check if comment thread of the given id is added to the repository.

`commentsrepository-active-not-attached`

Cannot set not attached comment thread as an active. Comment thread has to be attached to the target element to set it as active.

`commentsrepository-adapter-already-set`

Cannot set adapter more than once.

`commentsrepository-add-comment-internal-error`

Adding comment threw an error.

`commentsrepository-add-comment-to-missing-comment-thread`

Cannot add Comment to not existing CommentThread.

`commentsrepository-add-comment-user-not-exists`

Comment author is not defined in Users plugin.

`commentsrepository-attach-invalid-target`

Target is neither:

* a DOM element * {module:utils/dom/rect~Rect a rect instance} * a callback that returns one fo above

`commentsrepository-attach-missing-comment-thread`

Cannot attach not existing comment thread.

`commentsrepository-duplicated-comment-thread-id`

CommentThread with a given id is already added to the repository.

`commentsrepository-fetchcommentthread`

Fetching a comment thread failed.

`commentsrepository-get-comment-invalid-id`

Comment id has to be a string.

`commentsrepository-invalid-comment-authorId`

Comment author id has to be a string.

`commentsrepository-invalid-comment-content`

Comment content has to be a string.

`commentsrepository-invalid-comment-thread-id`

CommentThread id has to be a string.

`commentsrepository-invalid-commentId`

Comment id has to be a string.

`commentsrepository-missing-target`

Target is required to open new comment thread.

`commentsrepository-missing-thread-and-adapter`

Comment thread with given id is not added to the editor nor adapter is defined. See https://ckeditor.com/docs/ckeditor5/latest/features/collaboration/comments/integrate-comments-with-application.html.

`commentsrepository-missing-thread-and-adapter-method`

Comment thread with given id is not added to the editor nor adapter.getCommentThread() is defined. See https://ckeditor.com/docs/ckeditor5/latest/features/collaboration/comments/integrate-comments-with-application.html.

`commentsrepository-remove-comment-internal-error`

Removing comment resulted in an error.

`commentsrepository-remove-comment-missing-comment-thread`

Cannot remove comment from not existing CommentThread.

`commentsrepository-remove-missing-comment`

Cannot remove not existing Comment.

`commentsrepository-remove-missing-comment-thread`

Cannot remove not existing comment thread.

`commentsrepository-update-comment-invalid-content`

Comment content has to be a string.

`commentsrepository-update-comment-missing-comment-thread`

Cannot update comment of not existing CommentThread.

`commentsrepository-update-missing-comment`

Cannot update not existing Comment.

`componentfactory-item-exists`

The item already exists in the component factory.

Parameters

name : String: The name of the component.

`componentfactory-item-missing`

The required component is not registered in the component factory. Please make sure the provided name is correct and the component has been correctly added to the factory.

Parameters

name : String: The name of the missing component.

`context-addEditor-private-context`

Cannot add multiple editors to the context which is created by the editor.

`context-initplugins-constructor-only`

Only a constructor function is allowed as a context plugin.

`context-initplugins-invalid-plugin`

Only a plugin marked as a context plugin is allowed to be used with a context.

`contextualballoon-add-view-exist`

Trying to add configuration of the same view more than once.

`contextualballoon-remove-view-not-exist`

Trying to remove the configuration of the view not defined in the stack.

`contextualballoon-showstack-stack-not-exist`

Trying to show a stack that does not exist.

`conversion-add-alias-dispatcher-not-registered`

Trying to register and alias for a dispatcher that nas not been registered.

`conversion-attribute-to-attribute-on-text`

This error occurs when a text node's attribute is to be downcasted by Attribute to Attribute converter. In most cases it is caused by converters misconfiguration when only "generic" converter is defined:

editor.conversion.for( 'downcast' ).attributeToAttribute( {
    model: 'attribute-name',
    view: 'attribute-name'
} ) );

and given attribute is used on text node, for example:

model.change( writer => {
    writer.insertText( 'Foo', { 'attribute-name': 'bar' }, parent, 0 );
} );

In such cases, to convert the same attribute for both Element and Text nodes, text specific Attribute to Element converter with higher priority must also be defined:

editor.conversion.for( 'downcast' ).attributeToElement( {
    model: {
        key: 'attribute-name',
        name: '$text'
    },
    view: ( value, writer ) => {
        return writer.createAttributeElement( 'span', { 'attribute-name': value } );
    },
    converterPriority: 'high'
} ) );

`conversion-for-unknown-group`

Trying to add a converter to an unknown dispatchers group.

`conversion-group-exists`

Trying to register a group name that has already been registered.

`datacontroller-get-non-existent-root`

Cannot get data from a non-existing root. This error is thrown when DataController#get() method is called with non-existent root name. For example, if there is an editor instance with only main root, calling get like:

data.get( { rootName: 'root2' } );

will throw this error.

`datacontroller-init-document-not-empty`

Cannot set initial data to not empty Document. Initial data should be set once, during Editor initialization, when the version is equal 0.

`datacontroller-init-non-existent-root`

Cannot init data on a non-existing root. This error is thrown when DataController#init() method is called with non-existent root name. For example, if there is an editor instance with only main root, calling init like:

data.init( { main: '<p>Foo</p>', root2: '<p>Bar</p>' } );

will throw this error.

`datacontroller-set-non-existent-root`

Cannot set data on a non-existing root. This error is thrown when DataController#set() method is called with non-existent root name. For example, if there is an editor instance with only main root, calling set like:

data.set( { main: '<p>Foo</p>', root2: '<p>Bar</p>' } );

will throw this error.

`detach-operation-on-document-node`

Cannot detach document node.

`document-applyOperation-wrong-version`

Only operations with matching versions can be applied.

Parameters

operation : Operation

`document-selection-gravity-wrong-restore`

Restoring gravity for an unknown UID is not possible. Make sure you are using a correct UID obtained from the overrideSelectionGravity to restore.

Parameters

uid : String: The unique identifier returned by _overrideGravity.

`document-selection-wrong-position`

Range from document selection starts or ends at incorrect position.

Parameters

range : Range

`editor-create-initial-data`

The config.initialData option cannot be used together with initial data passed as the first parameter of Editor.create().

`editor-missing-sourceelement`

Cannot update the source element of a detached editor.

The updateSourceElement() method cannot be called if you did not pass an element to Editor.create().

`editor-source-element-already-used`

A DOM element used to create the editor (e.g. InlineEditor.create()) has already been used to create another editor instance. Make sure each editor is created with an unique DOM element.

Parameters

element : HTMLElement: DOM element that caused the collision.

`editor-ui-deprecated-editable-elements`

The EditorUI#\_editableElements property has been deprecated and will be removed in the near future. Please use setEditableElement() and getEditableElement() methods instead.

Parameters

editorUI : EditorUI: Editor UI instance the deprecated property belongs to.

`editor-wrong-element`

This error is thrown when trying to pass a <textarea> element to a create() function of an editor class.

The only editor type which can be initialized on <textarea> elements is classic editor. This editor hides the passed element and inserts its own UI next to it. Other types of editors reuse the passed element as their root editable element and therefore <textarea> is not appropriate for them. Use a <div> or another text container instead:

<div id="editor">
    <p>Initial content.</p>
</div>

`filerepository-no-upload-adapter`

You need to enable an upload adapter in order to be able to upload files.

This warning shows up when FileRepository is being used without definining an upload adapter.

If you see this warning when using one of the CKEditor 5 Builds it means that you did not configure any of the upload adapters available by default in those builds.

See the comprehensive "Image upload overview" to learn which upload adapters are available in the builds and how to configure them.

If you see this warning when using a custom build there is a chance that you enabled a feature like ImageUpload, or ImageUploadUI but you did not enable any upload adapter. You can choose one of the existing upload adapters listed in the "Image upload overview".

You can also implement your own image upload adapter.

`fileuploader-decoding-image-data-error`

Problem with decoding Base64 image data.

`fileuploader-missing-api-address`

Api address must be provided as the third argument.

`fileuploader-missing-file`

File must be provided as the first argument.

`fileuploader-missing-token`

Token must be provided as the second argument.

`fileuploader-uploading-data-failed`

Uploading file failed.

`finish-invalid-action`

The config.finishEditing.action must be a function.

`font-size-invalid-definition`

Provided value as an option for FontSize seems to invalid.

See valid examples described in the plugin configuration.

`font-size-invalid-use-of-named-presets`

If config.fontSize.supportAllValues is true, you need to use numerical values as font size options.

See valid examples described in the plugin configuration.

Parameters

presets : Array.<String>: Invalid values.

`inlineannotations-attach-already-attached`

Cannot attach the same annotation twice.

`inlineannotations-detach-not-attached`

Cannot detach a UI if it is not attached.

`inlineannotations-not-allowed-with-context`

Cannot switch Annotations UI to InlineAnnotations when using Context.

`insert-operation-position-invalid`

Insertion position is invalid.

`insertcontent-invalid-insertion-position`

An internal error occured during merging insertion content with siblings. The insertion position should equal to the merge position.

`insertcontent-wrong-position`

Given node cannot be inserted on the given position.

Parameters

node : Node: Node to insert.
position : Position: Position to insert the node at.

`invalid-date-time-format`

Date format must be a function.

`letters-invalid-element`

Letters should be bootstrapped on an HTMLElement element.

const element = document.createElement( 'div' );
letters.bootstrap( element );

or:

const element = document.createElement( 'div' );
Letters.create( element, config )
    .then( letters => {} );

`letters-ui-already-created.`

LettersUI is already created.

`license-key-invalid`

Invalid license key. Please contact our customer support at https://ckeditor.com/contact/.

`liveposition-root-not-rootelement`

LivePosition's root has to be an instance of RootElement.

`locale-deprecated-language-property`

The Locale#language property was deprecated and will be removed in the near future. Please use the uiLanguage and contentLanguage properties instead.

`marker-destroyed`

Cannot use a destroyed marker instance.

`mention-feed-callback-error`

The callback used for obtaining mention autocomplete feed thrown and error and the mention UI was hidden or not displayed at all.

`mentioncommand-incorrect-id`

The feed item ID must start with the marker character.

Correct mention feed setting:

mentions: [
    {
        marker: '@',
        feed: [ '@Ann', '@Barney', ... ]
    }
]

Incorrect mention feed setting:

mentions: [
    {
        marker: '@',
        feed: [ 'Ann', 'Barney', ... ]
    }
]

See MentionConfig.

`mentioncommand-incorrect-marker`

The marker must be a single character.

Correct markers: '@', '#'.

Incorrect markers: '$', '[@'.

See MentionConfig.

`mentionconfig-incorrect-marker`

The marker must be a single character.

Correct markers: '@', '#'.

Incorrect markers: '$', '[@'.

See MentionConfig.

`merge-operation-how-many-invalid`

Merge operation specifies wrong number of nodes to move.

`merge-operation-source-position-invalid`

Merge source position is invalid. The element to be merged must have a parent node.

`merge-operation-target-position-invalid`

Merge target position is invalid. The element to be merged must have a parent node.

`model-createPositionAt-offset-required`

Model#createPositionAt() requires the offset to be specified when the first parameter is a model item.

`model-document-createRoot-name-exists`

A root with the specified name already exists.

Parameters

doc : Document
name : String

`model-nodelist-offset-out-of-bounds`

Given offset cannot be found in the node list.

Parameters

offset : Number
nodeList : NodeList: Stringified node list.

`model-position-after-root`

You can not make a position after a root element.

Parameters

root : Item

`model-position-before-root`

You can not make a position before a root element.

Parameters

root : Item

`model-position-fromjson-no-root`

Cannot create position for document. Root with specified name does not exist.

Parameters

rootName : String

`model-position-parent-incorrect`

Position parent have to be a model element or model document fragment.

`model-position-path-incorrect-format`

Position path must be an array with at least one item.

Parameters

path

`model-position-root-invalid`

Position root is invalid.

Positions can only be anchored in elements or document fragments.

`model-selection-range-intersects`

Trying to add a range that intersects with another range in the selection.

Parameters

addedRange : Range: Range that was added to the selection.
intersectingRange : Range: Range in the selection that intersects with addedRange.

`model-selection-set-ranges-not-range`

Selection range set to an object that is not an instance of Range.

Only Range instances can be used to set a selection. Common mistakes leading to this error are:

using DOM Range object,
incorrect CKEditor 5 installation with multiple ckeditor5-engine packages having different versions.

`model-selection-setFocus-no-ranges`

Cannot set selection focus if there are no ranges in selection.

`model-selection-setTo-not-selectable`

Cannot set the selection to the given place.

Invalid parameters were specified when setting the selection. Common issues:

A TextProxy instance was passed instead of a real Text.
View nodes were passed instead of model nodes.
null/undefined was passed.

`model-selection-setTo-required-second-parameter`

selection.setTo requires the second parameter when the first parameter is a node.

`model-textproxy-wrong-length`

Given length value is incorrect.

`model-textproxy-wrong-offsetintext`

Given offsetInText value is incorrect.

`model-tree-walker-no-start-position`

Neither boundaries nor starting position of a TreeWalker have been defined.

`model-writer-insert-forbidden-move`

Cannot move a node from a document to a different tree. It is forbidden to move a node that was already in a document outside of it.

`move-operation-node-into-itself`

Trying to move a range of nodes into one of nodes from that range.

`move-operation-nodes-do-not-exist`

The nodes which should be moved do not exist.

`move-operation-range-into-itself`

Trying to move a range of nodes into the middle of that range.

`narrowsidebar-attach-already-attached`

Cannot attach narrow sidebar twice.

`narrowsidebar-detach-not-attached`

Cannot detach not attached sidebar.

`nodelist-index-out-of-bounds`

Given index cannot be found in the node list.

`nodelist-insertNodes-not-node`

Trying to insert an object which is not a Node instance.

`notificationcenter-missing-container-element`

Missing container element.

`observable-bind-duplicate-properties`

Properties must be unique.

`observable-bind-no-callback`

Binding multiple observables only possible with callback.

`observable-bind-rebind`

Cannot bind the same property more than once.

`observable-bind-to-extra-callback`

Cannot bind multiple properties and use a callback in one binding.

`observable-bind-to-many-not-one-binding`

Binding one attribute to many observables only possible with one attribute.

`observable-bind-to-parse-error`

Invalid argument syntax in to().

`observable-bind-to-properties-length`

The number of properties must match.

`observable-bind-wrong-properties`

All properties must be strings.

`observable-set-cannot-override`

Cannot override an existing property.

This error is thrown when trying to set an property with a name of an already existing property. For example:

let observable = new Model();
observable.property = 1;
observable.set( 'property', 2 );            // throws

observable.set( 'property', 1 );
observable.set( 'property', 2 );            // ok, because this is an existing property.

`observable-unbind-wrong-properties`

Properties must be strings.

`observablemixin-cannot-decorate-undefined`

Cannot decorate an undefined method.

Parameters

object : Object: The object which method should be decorated.
methodName : String: Name of the method which does not exist.

`operation-utils-move-range-not-flat`

Trying to move a range which starts and ends in different element.

`operation-utils-remove-range-not-flat`

Trying to remove a range which starts and ends in different element.

`pendingactions-add-invalid-message`

The message must be a string.

`plugincollection-context-required`

If a plugin is a context plugin, all plugins it requires should also be context plugins instead of plugins. In other words, if one plugin can be used in the context, all its requirements should also be ready to be used in the context. Note that the context provides only a part of the API provided by the editor. If one plugin needs a full editor API, all plugins which require it are considered as plugins that need a full editor API.

Parameters

plugin : String: The name of the required plugin.
requiredBy : String: The name of the parent plugin.

`plugincollection-load`

It was not possible to load the plugin.

This is a generic error logged to the console when a JavaSript error is thrown during the initialization of one of the plugins.

If you correctly handled the promise returned by the editor's create() method (like shown below), you will find the original error logged to the console, too:

ClassicEditor.create( document.getElementById( 'editor' ) )
    .then( editor => {
        // ...
    } )
    .catch( error => {
        console.error( error );
    } );

Parameters

plugin : String: The name of the plugin that could not be loaded.

`plugincollection-plugin-name-conflict`

Two plugins with the same pluginName were loaded. This will lead to runtime conflicts between these plugins.

In practice, this warning usually means that new plugins were added to an existing CKEditor 5 build. Plugins should always be added to a source version of the editor (@ckeditor/ckeditor5-editor-*), not to an editor imported from one of the @ckeditor/ckeditor5-build-* packages.

Check your import paths and the list of plugins passed to Editor.create() or specified in Editor.builtinPlugins.

The second option is that your node_modules/ directory contains duplicated versions of the same CKEditor 5 packages. Normally, on clean installations, npm deduplicates packages in node_modules/, so it may be enough to call rm -rf node_modules && npm i. However, if you installed conflicting versions of packages, their dependencies may need to be installed in more than one version which may lead to this warning.

Technically speaking, this error occurs because after adding a plugin to an existing editor build dependencies of this plugin are being duplicated. They are already built into that editor build and now get added for the second time as dependencies of the plugin you are installing.

Parameters

pluginName : String: The duplicated plugin name.
plugin1 : function: The first plugin constructor.
plugin2 : function: The second plugin constructor.

`plugincollection-plugin-not-found`

Some plugins are not available and could not be loaded.

Plugin classes (constructors) need to be provided to the editor before they can be loaded by name. This is usually done in CKEditor 5 builds by setting the builtinPlugins property.

If you see this warning when using one of the CKEditor 5 Builds, it means that you try to enable a plugin which was not included in that build. This may be due to a typo in the plugin name or simply because that plugin is not a part of this build. In the latter scenario, read more about custom builds.

If you see this warning when using one of the editor creators directly (not a build), then it means that you tried loading plugins by name. However, unlike CKEditor 4, CKEditor 5 does not implement a "plugin loader". This means that CKEditor 5 does not know where to load the plugin modules from. Therefore, you need to provide each plugin through reference (as a constructor function). Check out the examples in "Building from source".

Parameters

plugins : Array.<String>: The name of the plugins which could not be loaded.

`plugincollection-plugin-not-loaded`

The plugin is not loaded and could not be obtained.

Plugin classes (constructors) need to be provided to the editor and must be loaded before they can be obtained from the plugin collection. This is usually done in CKEditor 5 builds by setting the builtinPlugins property.

Note: You can use editor.plugins.has() to check if plugin was loaded.

Parameters

plugin : String: The name of the plugin which is not loaded.

`plugincollection-required`

Cannot load a plugin because one of its dependencies is listed in the removePlugins option.

Parameters

plugin : String: The name of the required plugin.
requiredBy : String: The name of the parent plugin.

`position-incorrect-path`

The position's path is incorrect. This means that a position does not point to a correct place in the tree and hence, some of its methods and getters cannot work correctly.

Note: Unlike DOM and view positions, in the model, the position's parent is always an element or a document fragment. The last offset in the position's path is the point in this element where this position points.

Read more about model positions and offsets in the Editing engine architecture guide.

Parameters

position : Position: The incorrect position.

`protobuffactory-cannot-get-descriptor-before-build`

Cannot get descriptor before build.

`range-create-from-ranges-empty-array`

At least one range has to be passed to Range.\_createFromRanges().

`realtimecollaborationclient-editor-setdata-and-editor-data-set-are-forbidden-in-real-time-collaboration`

Trying to use editor.setData() or editor.data.set() in real-time collaboration. Re-setting data in real-time collaboration usually means a mistake (incorrect integration or plugin). Using it may overwrite local (not yet synchronized) changes on remote clients. If you tried to set editor initial data, use initialData configuration option instead. If you tried to set editor data in a plugin, consider applying the changes through the Writer in a model.change() block. If you understand effects of using editor.data.set() in real-time collaboration and want to suppress this error, set suppressErrorInCollaboration flag to true in the second parameter of editor.data.set() call: editor.data.set( '<p>Your data</p>', { suppressErrorInCollaboration: true } ).

`realtimecollaborationclient-handleserverresponse`

Server response error.

`realtimecollaborationclient-init-connection-failed`

Connecting with the server resulted in error.

`realtimecollaborationclient-init-document-already-initialized`

Trying to set initial data to initialized document.

`realtimecollaborationclient-init-non-existent-root`

Attempting to init data on a non-existing root.

`realtimecollaborationclient-init-session-connection-error`

Connecting to the session resulted in an error.

`realtimecollaborationclient-initservice-incorrect-server-operation`

An incorrect operation came from the server.

`realtimecollaborationclient-initservice-internal-error`

Internal CollaborativeEditingService error.

`realtimecollaborationclient-sendbufferedoperations`

Sending update to the server threw an error.

`rename-operation-wrong-name`

Element to change has different name than operation's old name.

`rename-operation-wrong-position`

Given position is invalid or node after it is not instance of Element.

`renderer-unknown-type`

Unknown type passed to Renderer.markToSync.

`rootattribute-operation-attribute-exists`

The attribute with given key already exists for the given node.

Parameters

root : RootElement
key : String

`rootattribute-operation-not-a-root`

The element to change is not a root element.

Parameters

root : RootElement
key : String
value : *

`rootattribute-operation-wrong-old-value`

The attribute which should be removed does not exists for the given node.

Parameters

root : RootElement
key : String
value : *

`rootattributeoperation-fromjson-no-root`

Cannot create RootAttributeOperation for document. Root with specified name does not exist.

Parameters

rootName : String

`schema-cannot-extend-missing-item`

Cannot extend an item which was not registered yet.

This error happens when a plugin tries to extend the schema definition of an item which was not registered yet.

Parameters

itemName: The name of the model element which is being extended.

`schema-cannot-register-item-twice`

A single item cannot be registered twice in the schema.

This situation may happen when:

Two or more plugins called register() with the same name. This will usually mean that there is a collision between plugins which try to use the same element in the model. Unfortunately, the only way to solve this is by modifying one of these plugins to use a unique model element name.
A single plugin was loaded twice. This happens when it is installed by npm/yarn in two versions and usually means one or more of the following issues:
- a version mismatch (two of your dependencies require two different versions of this plugin),
- incorrect imports (this plugin is somehow imported twice in a way which confuses webpack),
- mess in node_modules/ (rm -rf node_modules/ may help).

Note: Check the logged itemName to better understand which plugin was duplicated/conflicting.

Parameters

itemName: The name of the model element that is being registered twice.

`schema-check-merge-no-element-after`

The node after the merge position must be an element.

`schema-check-merge-no-element-before`

The node before the merge position must be an element.

Missing container element.

Missing positioned container for the editor with a sidebar.

Container element is not a HTMLElement.

`simple-upload-adapter-missing-uploadUrl`

The config.simpleUpload.uploadUrl configuration required by the SimpleUploadAdapter is missing. Make sure the correct URL is specified for the image upload to work properly.

`special-character-invalid-group-name`

The name "All" for a special category group cannot be used because it is a special category that displays all available special characters.

`split-operation-graveyard-position-invalid`

Graveyard position invalid.

`split-operation-how-many-invalid`

Split operation specifies wrong number of nodes to move.

`split-operation-position-invalid`

Split position is invalid.

`split-operation-split-in-root`

Cannot split root element.

`template-extend-render`

Extending a template after rendering may not work as expected. To make sure the extending works for an element, make sure it happens before render is called.

`token-cannot-download-new-token`

Cannot download new token from the provided url.

`token-missing-token-url`

A tokenUrl must be provided as the first constructor argument.

`toolbarview-item-unavailable`

There was a problem processing the configuration of the toolbar. The item with the given name does not exist so it was omitted when rendering the toolbar.

This warning usually shows up when the Plugin which is supposed to provide a toolbar item has not been loaded or there is a typo in the configuration.

Make sure the plugin responsible for this toolbar item is loaded and the toolbar configuration is correct, e.g. Bold is loaded for the 'bold' toolbar item.

You can use the following snippet to retrieve all available toolbar items:

Array.from( editor.ui.componentFactory.names() );

Parameters

name : String: The name of the component.

`track-changes-accept-suggestion-not-found`

Suggestion to accept does not exist.

`track-changes-adapter-already-set`

Cannot set an adapter more than once.

`track-changes-adapter-missing-getsuggestion`

Adapter not set or is missing getSuggestion() method.

`track-changes-command-not-found`

Trying to enable command that does not exist.

`track-changes-discard-suggestion-not-found`

Suggestion to discard does not exist.

`track-changes-suggestion-data-mismatch`

Suggestion marker data does not match loaded suggestion data.

`track-changes-suggestion-not-found`

Suggestion with given id not found.

`track-changes-user-not-found`

User with given id not found.

`translation-service-quantity-not-a-number`

An incorrect value was passed to the translation function. This was probably caused by an incorrect message interpolation of a plural form. Note that for messages supporting plural forms the second argument of the t() function should always be a number or an array with a number as the first element.

`trial-license-key-reached-limit`

You have exhausted the trial usage limit. You need to restart the editor now. Please contact our customer support to get a full access at https://ckeditor.com/contact/.

`ui-template-extend-children-mismatch`

The number of children in extended definition does not match.

`ui-template-revert-not-applied`

Attempting to revert a template which has not been applied yet.

`ui-template-wrong-syntax`

Node definition cannot have the "tag" and "text" properties at the same time. Node definition must have either "tag" or "text" when rendering a new Node.

`ui-view-render-rendered`

This View has already been rendered.

`ui-viewcollection-delegate-wrong-events`

All event names must be strings.

`unexpected-error`

An unexpected error occurred inside the CKEditor 5 codebase. This error will look like the original one to make the debugging easier.

This error is only useful when the editor is initialized using the Watchdog feature. In case of such error (or any CKEditorError error) the watchdog should restart the editor.

`updatecommentcommand-internal-error`

Updating comment resulted in an error.

`uploadgateway-missing-api-address`

Api address must be provided.

`uploadgateway-missing-token`

Token must be provided.

`users-add-duplicated-id`

User with a given id is already added.

`users-add-invalid-id`

The id must be a string.

`users-me-already-defined`

Cannot add a local user more than once.

`users-me-missing-user`

Cannot add an undefined user as a local user.

`view-conversion-dispatcher-incorrect-result`

Incorrect conversion result was dropped.

Model range should be a conversion result.

`view-createPositionAt-offset-required`

View#createPositionAt() requires the offset to be specified when the first parameter is a view item.

`view-emptyelement-cannot-add`

Cannot add children to EmptyElement.

`view-node-not-found-in-parent`

The node's parent does not contain this node. It means that the document tree is corrupted.

`view-position-after-root`

You can not make a position after a root.

Parameters

root : Node

`view-position-before-root`

You cannot make a position before a root.

Parameters

root : Node

`view-renderer-filler-was-lost`

The inline filler node was lost. Most likely, something overwrote the filler text node in the DOM.

`view-selection-add-range-not-range`

Selection range set to an object that is not an instance of Range.

`view-selection-range-intersects`

Trying to add a range that intersects with another range from selection.

Parameters

addedRange : Range: Range that was added to the selection.
intersectingRange : Range: Range from selection that intersects with addedRange.

`view-selection-setFocus-no-ranges`

Cannot set selection focus if there are no ranges in selection.

`view-selection-setTo-not-selectable`

Cannot set selection to given place.

`view-selection-setTo-required-second-parameter`

selection.setTo requires the second parameter when the first parameter is a node.

`view-textproxy-wrong-length`

Given length value is incorrect.

`view-textproxy-wrong-offsetintext`

Given offsetInText value is incorrect.

`view-tree-walker-no-start-position`

Neither boundaries nor starting position have been defined.

`view-uielement-cannot-add`

Cannot add children to UIElement.

`view-writer-break-non-container-element`

Trying to break an element which is not a container element.

`view-writer-break-root`

Trying to break root element.

`view-writer-cannot-break-empty-element`

Cannot break inside EmptyElement instance.

`view-writer-cannot-break-ui-element`

Cannot break inside UIElement instance.

`view-writer-insert-invalid-node`

Inserted nodes should be valid to insert. of AttributeElement, ContainerElement, EmptyElement, UIElement, Text.

`view-writer-invalid-position-container`

Position's parent container cannot be found.

`view-writer-invalid-range-container`

Range container is invalid. This can happen if range start and range end positions are not placed inside same container or parent container for these positions cannot be found.

`view-writer-merge-containers-invalid-position`

Element before and after given position cannot be merged.

`view-writer-unwrap-invalid-attribute`

Attribute element need to be instance of attribute element.

`view-writer-wrap-invalid-attribute`

Attribute element need to be instance of attribute element.

`viewconsumable-invalid-attribute`

Class and style attributes should be handled separately in ViewConsumable#add().

What you have done is trying to use:

consumables.add( { attributes: [ 'class', 'style' ] } );

While each class and style should be registered separately:

consumables.add( { classes: 'some-class', styles: 'font-weight' } );

ClassicEditor.create( document.createElement( 'div' ), {
    cloudServices: {
        webSocketUrl: "YOUR_WEBSOCKET_URL"
        // ...
    }
    // ...
} );

Parameters

toolbarId: Toolbar id.

Parameters

Parameters

Trying to add a plugin to an existing build

Confused an editor build with an editor implementation

Loading two or more builds on one page

Using outdated packages

Conflicting version of dependencies

Packages were duplicated in node_modules

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Packages were duplicated in `node_modules`