# Error codes
CKEditor 5 Framework logs errors and warnings to the console. The following list contains more detailed descriptions of those issues.
### `accessibility-unknown-keystroke-info-category`
Cannot add keystrokes in an unknown category. Use [`addKeystrokeInfoCategory`](../api/module_core_accessibility-Accessibility.md#function-addKeystrokeInfoCategory) to add a new category or make sure the specified category exists.
#### Parameters
* `categoryId: string`
The id of the unknown keystroke category.
* `keystrokes: AddKeystrokeInfosData#keystrokes`
Keystroke definitions about to be added.
### `accessibility-unknown-keystroke-info-group`
Cannot add keystrokes to an unknown group.
Use [`addKeystrokeInfoGroup`](../api/module_core_accessibility-Accessibility.md#function-addKeystrokeInfoGroup) to add a new group or make sure the specified group exists.
#### Parameters
* `groupId: string`
The id of the unknown keystroke group.
* `categoryId: string`
The id of category the unknown group should belong to.
* `keystrokes: AddKeystrokeInfosData#keystrokes`
Keystroke definitions about to be added.
### `addcommentthreadcommand-incorrect-ranges`
Cannot add comment thread. Selection is empty and no valid ranges provided.
### `addcommentthreadcommand-user-not-found`
Cannot add comment thread. User is not defined.
### `ai-applying-suggestion-failed`
An error thrown when applying an AI-generated suggestion to the document fails (e.g. an engine invariant violation while replaying operations).
### `ai-aws-adapter-not-supported`
The `AWSTextAdapter` is no longer supported. The Amazon Bedrock adapter has been removed. Please contact CKEditor support at https\://support.ckeditor.com for more information about available AI adapters.
### `ai-chat-content-too-large`
The content is too large to be used as chat context.
### `ai-chat-context-file-too-large`
The file is too large to be used as chat context.
### `ai-chat-context-file-too-many-pages`
The file has too many pages to be used as chat context.
### `ai-chat-context-form-data-size-limits-exceeded`
The form data size limits have been exceeded for chat context.
### `ai-chat-context-invalid-data`
An error thrown when a URL resource has invalid data type (not a string).
#### Parameters
* `resourceId: string`
The ID of the resource.
* `sourceId: string`
The ID of the source provider.
* `expectedType: string`
The expected data type.
* `actualType: string`
The actual data type.
### `ai-chat-context-unsupported-file-type`
The file type is not supported for chat context.
### `ai-chat-context-unsupported-type`
An error thrown when an unsupported resource type is used. Only URL and FILE types are supported.
#### Parameters
* `resourceId: string`
The ID of the resource.
* `sourceId: string`
The ID of the source provider.
* `resourceType: string`
The unsupported resource type.
### `ai-chat-controller-no-active-conversation`
User message was sent before the conversation was started.
### `ai-chat-conversation-already-started`
An error thrown when trying to start a conversation that is already started.
### `ai-chat-conversation-init-failed`
An error thrown when the conversation fails to initialize (e.g. due to a network error).
### `ai-chat-conversation-init-from-id-failed`
An error thrown when the conversation fails to initialize from ID (e.g. due to a network error).
### `ai-chat-conversation-not-found`
An error thrown when the conversation conversation with given ID was not found.
### `ai-chat-conversation-set-model-not-available`
An error thrown when trying to set model that is not available.
### `ai-chat-conversation-set-model-null`
An error thrown when trying to set model to null.
### `ai-chat-conversation-start-failed`
An error thrown when the conversation fails to start (e.g. due to a network error).
### `ai-chat-conversation-start-no-model-selected`
An error thrown when trying to start a conversation but no model is selected.
### `ai-chat-default-model-id-unrecognized`
Model with given ID configured via `ai.models.defaultModelId` is not available. Falling back to the first available model.
#### Parameters
* `defaultModelId: string`
The ID of the model configured via `ai.models.defaultModelId` that was not found.
* `fallBackModelId: string`
The ID of the fall back model
### `ai-chat-document-upload-failed`
An error thrown when the documents fail to upload as AI chat context (e.g. due to a network error).
### `ai-chat-document-upload-reply-mismatch`
The document upload endpoint returned a reply that does not match the uploaded documents (different length or a missing `id`). This indicates a backend contract violation.
### `ai-chat-documents-missing-description`
When a chat conversation uploads more than one document in a single message (multi-root or multi-editor), each root should declare a `description` in its [root configuration](../api/module_core_editor_editorconfig-RootConfig.md). Routing AI replies back to the source root works without it (it uses `channelId` and `rootName`), but the AI chat service uses descriptions to semantically distinguish roots — so when a user scopes a request to a specific area ("edit the title", "summarize the introduction"), the model can route the change to the intended root. Without descriptions, such area-scoped requests may target the wrong root.
### `ai-chat-feed-view-item-not-a-reply-item`
Item with the given ID cannot be updated because it is not a reply item.
### `ai-chat-feed-view-item-not-a-suggestion-item`
Item with the given ID cannot be updated because it is not a suggestion item.
### `ai-chat-feed-view-item-not-a-suggestion-or-reply-item`
Item with the given ID cannot be updated because it is not a suggestion or reply item.
### `ai-chat-feed-view-item-not-found`
Item with the given ID does not exist.
### `ai-chat-feed-view-scroll-to-suggestion-invalid-item`
Item with the given ID cannot be scrolled to because it is not a suggestion item.
### `ai-chat-feed-view-scroll-to-suggestion-part-view-not-found`
Part view with the given index does not exist.
### `ai-chat-file-upload-failed`
An error thrown when the file fails to upload as AI chat context (e.g. due to a network error).
### `ai-chat-handle-user-conversation-not-initialized`
An error thrown when trying to handle user message but conversation is not initialized.
### `ai-chat-handle-user-interaction-already-in-progress`
An error thrown when trying to handle user message but interaction is already in progress.
### `ai-chat-interaction-error`
An error thrown when error is received from the AI endpoint.
### `ai-chat-invalid-request`
The chat request data is invalid.
### `ai-chat-model-already-set`
The model has already been set and cannot be changed.
### `ai-chat-model-id-unrecognized`
Model with given ID is not available. Falling back to the default model.
#### Parameters
* `modelId: string`
The ID of the model that was not found.
* `fallBackModelId: string`
The ID of the fall back model.
### `ai-chat-model-not-found`
The requested model was not found.
### `ai-chat-models-unable-to-retrieve`
An error thrown when the list of available AI models cannot be retrieved while resolving the conversation's selected model (e.g. due to a network error).
### `ai-chat-resource-load-failed`
An error thrown when a resource fails to load data (e.g. due to a network error).
#### Parameters
* `resourceId: string`
The ID of the resource that failed to load.
* `sourceId: string`
The ID of the source provider.
### `ai-chat-resource-no-data`
An error thrown when a resource has no data available.
#### Parameters
* `resourceId: string`
The ID of the resource.
* `sourceId: string`
The ID of the source provider.
### `ai-chat-shortcuts-ai-tabs-not-found`
The [AI Chat Shortcuts](../api/module_ai_aichatshortcuts_aichatshortcuts-AIChatShortcuts.md) feature was unable to switch the user interface because the [AI Tabs](../api/module_ai_aitabs_aitabs-AITabs.md) plugin was not found.
Please make sure the AI Tabs feature is enabled before running shortcuts that interact with it.
### `ai-chat-shortcuts-invalid-config`
The [AI Chat Shortcuts](../api/module_ai_aichatshortcuts_aichatshortcuts-AIChatShortcuts.md) configuration is invalid. Please make sure the shortcut has all necessary properties.
See [`AIChatShortcutChatDefinition`](../api/module_ai_aichatshortcuts_aichatshortcuts-AIChatShortcutChatDefinition.md) to learn more about configuring chat shortcuts.
#### Parameters
* `shortcut: object`
The chat shortcut configuration that is invalid.
### `ai-chat-shortcuts-review-mode-not-found`
The [AI Chat Shortcuts](../api/module_ai_aichatshortcuts_aichatshortcuts-AIChatShortcuts.md) feature was unable to run the shortcut because the [AI Review Mode](../api/module_ai_aireviewmode_aireviewmode-AIReviewMode.md) feature was not found.
Please make sure the AI Review mode feature is enabled before running shortcuts that interact with it.
### `ai-chat-shortcuts-translate-not-found`
The [AI Chat Shortcuts](../api/module_ai_aichatshortcuts_aichatshortcuts-AIChatShortcuts.md) feature was unable to run the shortcut because the [AI Translate](../api/module_ai_aitranslate_aitranslate-AITranslate.md) feature was not found.
Please make sure the AI Translate feature is enabled before running shortcuts that interact with it.
### `ai-chat-source-not-found`
An error thrown when a source provider is not found.
#### Parameters
* `sourceId: string`
The ID of the source provider.
### `ai-chat-source-resources-load-failed`
An error thrown when resources fail to load from a source provider.
#### Parameters
* `sourceId: string`
The ID of the source provider.
### `ai-chat-unsafe-content-detected`
Unsafe content was detected in the chat request.
### `ai-chat-unsupported-content-type`
The content type is not supported for chat operations.
### `ai-chat-url-upload-failed`
An error thrown when the URL fails to upload (e.g. due to a network error).
#### Parameters
* `url: string`
The URL that failed to upload.
### `ai-commands-config-order-collision`
The same `order` value has been set for two (or more) definitions in the AI Assistant feature configuration.
Learn more about [command definitions](../api/module_ai_aiassistant_aiassistant-AICommandDefinition.md) and [group definitions](../api/module_ai_aiassistant_aiassistant-AIGroupDefinition.md) used in the [feature configuration](../api/module_ai_aiassistant_aiassistant-AIAssistantConfig.md#member-commands)
#### Parameters
* `conflictingDefinitions: Array`
Definitions that have the same `order` value.
### `ai-document-root-missing-title`
Each editor root should declare a `title` (or, for backward compatibility, a `label`) in its [root configuration](../api/module_core_editor_editorconfig-RootConfig.md) (or in the options passed to [`MultiRootEditor#addRoot()`](../api/module_editor-multi-root_multirooteditor-MultiRootEditor.md#function-addRoot:ROOT_CONFIG)). Routing AI replies back to the source root works without it (it uses `channelId` and `rootName`), but the AI chat service uses these names to semantically distinguish roots — so when a user scopes a request to a specific area ("edit the title", "summarize the introduction"), the model can route the change to the intended root. Without a name, such area-scoped requests may target the wrong root.
### `ai-documentposition-createfrompath-path-cannot-be-empty`
The path cannot be empty when creating document position from path.
### `ai-documentposition-index-out-of-bounds`
The index is out of bounds for the document position.
### `ai-documentprocessinggateway-empty-reply`
The AI service's reply contained no documents at all. See `ai-documentprocessinggateway-empty-root-content` for the case where the reply has an entry for every processed root but one of them came back with empty content.
### `ai-documentprocessinggateway-empty-root-content`
The AI service's reply included an entry with empty content for one of the processed roots. Verify that the AI service is configured correctly for the model and prompt used.
#### Parameters
* `channelId: string`
The channel ID of the root whose reply content was empty.
* `rootName: string`
The name of the root whose reply content was empty.
### `ai-documentprocessinggateway-empty-roots`
`AIDocumentProcessingGateway.processDocument()` was called with `roots: []`. Pass at least one `{ channelId, rootName }` entry, or omit the `roots` option entirely to process every root across every editor in the context.
### `ai-documentprocessinggateway-missing-document`
Thrown when `AIDocumentProcessingGateway.processDocument()` encounters no document.
Empty string (`''`) is accepted.
### `ai-documentprocessinggateway-missing-prompt`
Thrown when `AIDocumentProcessingGateway.processDocument()` is called without a prompt.
### `ai-documentprocessinggateway-reply-count-mismatch`
The AI service's reply contained a different number of documents than the number of document content parts sent in the request. Each request document part should produce exactly one reply entry, in the same order — a mismatch means the reply cannot be reliably mapped back to the roots that were processed.
#### Parameters
* `expected: number`
The number of document content parts sent in the request.
* `received: number`
The number of documents returned in the reply.
### `ai-documentprocessinggateway-root-not-found`
`AIDocumentProcessingGateway.processDocument()` was called with a `roots` entry that does not match any root in the current context. Verify that its `channelId` matches the `collaboration.channelId` of one of the editor instances and that its `rootName` matches an existing, non-`$graveyard` root within that editor.
#### Parameters
* `channelId: string`
The channel ID that was provided.
* `rootName: string`
The root name that was provided.
### `ai-documentprocessinggateway-run-failed`
Thrown when `AIDocumentProcessingGateway.processDocument()` fails on the underlying request.
When the AI service rejected the request, the backend's structured response is exposed under `error.data.backendData` (for example, an `issues` list describing which fields failed validation).
#### Parameters
* `error: Error`
The error that was thrown during the run.
* `backendData: object`
The structured `data` returned by the AI service backend. Present only when
### `ai-gateway-apply-empty-roots`
Thrown when `AIGateway.apply()` is called with an explicitly empty `options.roots` array.
### `ai-gateway-apply-invalid-status`
Thrown when `AIGateway.apply()` is called with an `AIRunSingleRootResult` whose `status` is not `'completed'`. Inspect `result.status` (and `result.error`) before applying.
#### Parameters
* `status: string`
The current status of the run result.
### `ai-gateway-apply-root-not-found`
Thrown when an entry in `AIGateway.apply()`'s `options.roots` filter does not match any per-root sub-result in `result.results`.
#### Parameters
* `channelId: string`
The `channelId` of the unmatched filter entry.
* `rootName: string`
The `rootName` of the unmatched filter entry.
### `ai-gateway-merge-failed`
Thrown when [`mergeChangesIntoContent`](../api/module_ai_aicore_aigateway-AIGateway.md#function-mergeChangesIntoContent) fails to merge AI-produced changes into the document snapshot.
#### Parameters
* `id: string`
The id of the change that failed to merge.
* `content: string`
The content of the change that failed to merge.
* `error: Error`
The error that was thrown during the merge.
### `ai-get-editor-from-context-no-editor`
No editor found in the context.
### `ai-interaction-invalid-event-type`
There was a problem processing the response chunk. The event type is invalid.
#### Parameters
* `chunk: object`
The chunk that was received from the AI endpoint.
* `event: string`
The event type that was received from the AI endpoint.
### `ai-invalid-content-type`
The content type provided is invalid.
### `ai-invalid-license-key`
Invalid license key. Please contact our customer support at https\://ckeditor.com/contact/.
### `ai-missing-channel-id`
The collaboration `channelId` configuration is required to use AI features.
### `ai-missing-token`
The authentication [`config.cloudServices.tokenUrl`](../api/module_cloud-services_cloudservicesconfig-CloudServicesConfig.md#member-tokenUrl) configuration is required for handling AI connection.
### `ai-models-unable-to-retrieve`
The editor was unable to retrieve the list of available AI models. This can happen due to a network error.
### `ai-no-track-changes`
Tried to insert AI-proposed changes as suggestions but track changes plugin is not loaded on the target editor.
#### Parameters
* `channelId: string`
`collaboration.channelId` of the editor missing the `TrackChanges` plugin.
* `rootName: string`
Name of the root the run entry targeted on that editor.
### `ai-quick-actions-models-unable-to-retrieve`
The editor was unable to retrieve the list of available AI models. This can happen due to a network error. Some quick actions may be unavailable or work improperly.
### `ai-quick-actions-plugin-not-found`
Thrown when trying to execute an AI Quick Action but the required plugin is not available. This error indicates that the required plugin is not installed or not loaded.
### `ai-quick-actions-unavailable-model`
A quick action is using an outdated or unavailable model in its configuration. The quick action has been disabled. Please update the model to a supported version.
#### Parameters
* `actionId: string`
The ID of the quick action with the outdated model.
* `modelId: string`
The outdated model identifier.
### `ai-rate-limits-exceeded`
Rate limits for the AI service have been exceeded.
### `ai-reply-get-content-parts-group-not-found`
The change group with the given index does not exist.
### `ai-request-aborted`
Request to the AI API was aborted.
### `ai-request-failed`
Failed to fetch response from the AI API.
### `ai-response-parser-unable-to-set-up-parser`
The Markdown to HTML converter was unable to set up the parser.
### `ai-review-mode-check-run-chunk-error`
An error specific to one chunk occurred during the AI review mode check run.
### `ai-review-mode-check-run-failed`
The current check run has failed.
### `ai-review-mode-check-run-general-error`
A general error occurred during the AI review mode check run.
### `ai-review-mode-command-unavailable-due-to-missing-model`
A review command is unavailable because the required AI model is not available.
This can happen, for example, due to a network error that prevents fetching the list of available models or if the model is no longer available. The command will not be visible in the UI and cannot be executed.
See [`AIModelsConfig`](../api/module_ai_aicore_model_aimodels-AIModelsConfig.md) documentation for more details on AI models configuration.
### `ai-review-mode-models-unable-to-retrieve`
The editor was unable to retrieve the list of available AI models for review mode for a custom command. This can happen, for example, due to a network error.
If this error occurs, review custom command will not be available.
### `ai-review-mode-no-current-check-run`
The current check run was not started or has been removed.
### `ai-review-mode-non-existent-commands-used`
Non-existent command IDs were used to configure AI Review commands list.
See [`availableCommands`](../api/module_ai_aireviewmode_aireviewmode-AIReviewModeConfig.md#member-availableCommands) documentation.
### `ai-review-mode-source-check-not-found`
The source check with the given ID was not loaded or has been removed.
### `ai-reviewcoreediting-check-run-failed`
Thrown when a review-core check run (started via `AIReviewCoreEditing.runCheck()`) fails at runtime. This wraps transport, parsing, and merge failures that happen after the request has been dispatched. Callers can inspect `error.data.apiId` and `error.data.args` to identify which check was running.
When the AI service rejected the request, the backend's structured response is exposed under `error.data.backendData` (for example, an `issues` list describing which fields failed validation).
#### Parameters
* `apiId: string`
The `apiId` of the check that failed (e.g. `translate`).
* `args: object`
The `args` that were passed to the check run.
* `error: Error`
The error that was thrown during the run.
* `backendData: object`
The structured `data` returned by the AI service backend. Present only when
### `ai-reviewcoreediting-empty-roots`
Thrown when `AIReviewCoreEditing.runCheck()` is called with `roots: []`. Pass at least one `{ channelId, rootName }` entry, or omit the `roots` option entirely to run against every root across every editor in the context.
### `ai-reviewcoreediting-root-not-found`
Thrown when `AIReviewCoreEditing.runCheck()` is called with a `roots` option that contains an entry that does not match any root in the current context. Verify that each entry's `channelId` matches the `collaboration.channelId` of one of the editor instances and that its `rootName` matches an existing, non-`$graveyard` root within that editor.
#### Parameters
* `channelId: string`
The channel ID that was provided.
* `rootName: string`
The root name that was provided.
### `ai-reviewgateway-missing-custom-command-model`
Thrown when `AIReviewGateway.runCustomReview()` is called and no model can be resolved — neither `options.model` nor the command's default model is available.
#### Parameters
* `checkId: string`
The command ID that was passed.
### `ai-reviewgateway-missing-custom-command-prompt`
Thrown when `AIReviewGateway.runCustomReview()` is called without a prompt.
#### Parameters
* `checkId: string`
The command ID that was passed.
### `ai-reviewgateway-not-a-custom-command`
Thrown when `AIReviewGateway.runCustomReview()` resolves the built-in `custom` command and finds that the resolved command is not the built-in `custom` command. Extras configured via `ai.review.extraCommands` are not custom and must be invoked through `AIReviewGateway.runReview()`.
#### Parameters
* `checkId: string`
The command ID that was resolved.
### `ai-reviewgateway-not-a-system-command`
Thrown when `AIReviewGateway.runReview()` is called with a `commandId` that points at the built-in `custom` command. Use `AIReviewGateway.runCustomReview()` for it instead.
#### Parameters
* `checkId: string`
The command ID that was passed.
### `ai-reviewgateway-review-command-run-failed`
Thrown in older versions when `AIReviewGateway` failed on running a review command. As of v48.4.0 runtime failures surface via `AIRunResult#error` with the shared `ai-reviewcoreediting-check-run-failed` code instead. Kept here so the console-log link from older editors still resolves against `latest` docs.
#### Parameters
* `checkId: string`
The command ID for which the command run failed.
* `error: Error`
The error that was thrown during the command run.
### `ai-reviewgateway-unknown-command`
Thrown when `AIReviewGateway.runReview()` is called with a `commandId` that is not registered in the current editor configuration.
#### Parameters
* `checkId: string`
The unknown command ID that was passed.
### `ai-reviewmode-missing-custom-command-model`
Thrown when `AIReviewMode.startCustomReview()` is called and no model can be resolved — neither `options.model` nor the built-in `custom` command's default model is available.
### `ai-reviewmode-missing-custom-command-prompt`
Thrown when `AIReviewMode.startCustomReview()` is called without a prompt.
### `ai-reviewmode-not-a-system-command`
Thrown when `AIReviewMode.startReview()` is called with a `commandId` that points at the built-in `custom` command. Use `AIReviewMode.startCustomReview()` for it instead.
#### Parameters
* `commandId: string`
The command ID that was passed.
### `ai-reviewmode-review-already-running`
Thrown when `AIReviewMode.startReview()` or `AIReviewMode.startCustomReview()` is called while another review check run is already in progress. Wait for the current run to finish (or abort it) before starting a new one.
### `ai-reviewmode-review-tab-not-active`
Thrown when `AIReviewMode.startReview()` is called while the review tab is not the active tab in `AITabs`. The integrator must activate the `'reviewMode'` tab (e.g. via `editor.plugins.get( 'AITabs' ).view.activateTab( 'reviewMode' )`) before calling `startReview()`.
### `ai-reviewmode-review-vetoed`
Thrown when `AIReviewMode.startReview()` or `AIReviewMode.startCustomReview()` is called and activating the review tab is vetoed by a listener (for example another AI tab has an unresolved run and the user declines the confirmation dialog asking to leave it).
### `ai-reviewmode-unknown-command`
Thrown when `AIReviewMode.startReview()` is called with a `commandId` that is not registered in the current editor configuration.
#### Parameters
* `commandId: string`
The unknown command ID that was passed.
### `ai-service-url-invalid-version`
The configured [`config.ai.serviceUrl`](../api/module_ai_aiconfig-AIConfig.md#member-serviceUrl) must end with `/v1` version.
#### Parameters
* `serviceUrl: string`
The configured service URL that failed validation.
### `ai-tabs-configuration-not-found`
Configuration for the AI tabs container was not found.
Please make sure that `config.ai.container` is set.
### `ai-tabs-unsupported-ui-side`
Target side is not supported.
### `ai-tabs-unsupported-ui-type`
Target UI type is not supported.
### `ai-translate-translation-already-running`
Thrown when `AITranslate.startTranslate()` is called while another translation run is already in progress. Wait for the current run to finish before starting a new one.
### `ai-translate-translation-vetoed`
Thrown when `AITranslate.startTranslate()` is called and activating the translate tab is vetoed by a listener (for example another AI tab has an unresolved run and the user declines the confirmation dialog asking to leave it).
### `ai-translate-unknown-language`
Thrown when `AITranslate.startTranslate()` is called with a `languageId` that is not present in the list of available languages. Use `AITranslate.getAvailableLanguages()` for valid language ids.
#### Parameters
* `languageId: string`
The unknown language ID that was passed.
### `ai-trial-license-key-reached-limit-changes`
You have exhausted the trial usage limit (reason: reached document changes limit). Restart the editor.
Please contact our customer support to get full access at https\://ckeditor.com/contact/.
### `ai-usage-limits-exceeded`
Usage limits for the AI service have been exceeded.
### `aiadapter-text-adapter-not-set`
AI text adapter plugin has not been added to the editor. Use one of the provided adapter plugins (e.g. `OpenAITextAdapter` if you connect to OpenAI or Azure OpenAI service) or create a custom adapter.
### `aitextadapter-send-request-failed`
Sending a request to the AI service API failed.
### `alignment-config-classname-already-defined`
The same `className` in one of the `alignment.options` was already declared.
#### Parameters
* `option: object`
First option that declares given `className`.
* `configuredOptions: object`
* Contents of `alignment.options`.
### `alignment-config-classnames-are-missing`
The `className` property has to be defined for all options once at least one option declares `className`.
#### Parameters
* `configuredOptions: object`
Contents of `alignment.options`.
### `alignment-config-name-already-defined`
The same `name` in one of the `alignment.options` was already declared. Each `name` representing one alignment option can be set exactly once.
#### Parameters
* `option: object`
First option that declares given `name`.
* `configuredOptions: object`
Contents of `alignment.options`.
### `alignment-config-name-not-recognized`
The `name` in one of the `alignment.options` is not recognized. The available options are: `'left'`, `'right'`, `'center'` and `'justify'`.
#### Parameters
* `option: object`
Options with unknown value of the `name` property.
### `annotation-invalid-target`
An error thrown when the target type is invalid.
The target should be either:
* a DOM element or an array of DOM elements,
* or [a rect instance](../api/module_utils_dom_rect-Rect.md),
* or `null`,
* or a callback that returns one of the above.
### `annotationcollection-duplicated-item`
The annotation already exists in the collection. It cannot be added more than once.
### `annotationcollection-not-existing-item`
The annotation does not exist in the collection and cannot be removed.
### `annotationsuis-annotation-mismatch`
An annotation should always belong only to one annotations UI instance. Check filters that were passed to [`activate` methods](../api/module_comments_annotations_annotationsuis-AnnotationsUIs.md#function-activate).
### `annotationsuis-missing-ui`
UI with a given name has been not registered.
### `annotationsuis-missing-ui`
UI with a given name has been not registered.
### `annotationsuis-missing-ui`
UI with a given name has been not registered.
### `annotationsuis-register-already-registered`
UI with a given name already registered.
### `annotationsuis-register-invalid-interface`
The annotations UI plugin should implement `AnnotationsUI` interface.
### `attachtoform-missing-elementapi-interface`
The editor passed to `attachToForm()` must implement the [`ElementApi`](../api/module_core_editor_utils_elementapimixin-ElementApi.md) interface.
### `attribute-element-get-elements-with-same-id-no-id`
Cannot get elements with the same id for an attribute element without id.
### `attribute-operation-attribute-exists`
The attribute with given key already exists for the given node.
#### Parameters
* `root: ModelItem`
The item element.
* `key: string`
The key of the attribute.
### `attribute-operation-range-not-flat`
The range to change is not flat.
### `attribute-operation-wrong-old-value`
Changed node has different attribute value than operation's old attribute value.
#### Parameters
* `root: ModelItem`
The item element.
* `key: string`
The key of the attribute.
* `value: never`
The value.
### `batch-constructor-deprecated-string-type`
The string value for a `type` property of the `Batch` constructor has been deprecated and will be removed in the near future. Please refer to the [`Batch` constructor API documentation](../api/module_engine_model_batch-Batch.md#function-constructor) for more information.
### `batch-type-deprecated`
The `Batch#type` property has been deprecated and will be removed in the near future. Use `Batch#isLocal`, `Batch#isUndoable`, `Batch#isUndo` and `Batch#isTyping` instead.
### `cannot-change-view-tree`
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`](../api/module_engine_view_view-EditingView.md#function-change) or [`forceRender`](../api/module_engine_view_view-EditingView.md#function-forceRender) during rendering process,
* calling [`change`](../api/module_engine_view_view-EditingView.md#function-change) or [`forceRender`](../api/module_engine_view_view-EditingView.md#function-forceRender) inside of [post-fixer function](../api/module_engine_view_document-ViewDocument.md#function-registerPostFixer).
### `case-change-invalid-license-key`
Invalid license key. Please contact our customer support at https\://ckeditor.com/contact/.
### `case-change-trial-license-key-reached-limit-changes`
You have exhausted the trial usage limit (reason: reached document changes limit). Restart the editor.
Please contact our customer support to get full access at https\://ckeditor.com/contact/.
### `ckbox-access-default-workspace-error`
The user is not authorized to access the workspace defined in the`ckbox.defaultUploadWorkspaceId` configuration.
### `ckbox-fetch-category-http-error`
Fetching a list of available categories with which an uploaded file can be associated failed.
### `ckbox-image-edit-unavailable-with-trusted-types`
The CKBox image editor is not available, because the application enforces Trusted Types with the `require-trusted-types-for 'script'` CSP directive. The image editor writes HTML in a way that this directive rejects, and the editor cannot change how it does that. Choosing assets in CKBox still works.
The editor disables its own **Edit image** button. The **Edit** button in the CKBox dialog is part of CKBox, so it stays available, but the image editor that it opens cannot load the image either.
For a detailed overview, check the [Content Security Policy](../getting-started/setup/csp.md#known-limitations) guide.
### `ckbox-image-not-processed`
Image has not been processed yet.
### `ckbox-image-processing-failed`
The image processing failed.
### `ckbox-plugin-image-feature-missing`
The CKBox feature requires one of the following plugins to be loaded to work correctly:
* [`ImageBlock`](../api/module_image_imageblock-ImageBlock.md),
* [`ImageInline`](../api/module_image_imageinline-ImageInline.md),
* [`Image`](../api/module_image_image-Image.md) (loads both `ImageBlock` and `ImageInline`)
Please make sure your editor configuration is correct.
#### Parameters
* `editor: Editor`
The editor instance.
### `ckbox-plugin-missing-token-url`
The [`config.ckbox.tokenUrl`](../api/module_ckbox_ckboxconfig-CKBoxConfig.md#member-tokenUrl) or the [`config.cloudServices.tokenUrl`](../api/module_cloud-services_cloudservicesconfig-CloudServicesConfig.md#member-tokenUrl) configuration is required for the CKBox plugin.
```typescript
ClassicEditor.create( {
attachTo: document.createElement( 'div' ),
ckbox: {
tokenUrl: "YOUR_TOKEN_URL"
// ...
}
// ...
} );
```
### `ckeditor-duplicated-modules`
This error is thrown when, due to a mistake in the way CKEditor 5 was installed, imported, or initialized, some of its modules were evaluated and executed twice. Duplicate modules inevitably lead to runtime errors and increased bundle size.
#### Check dependency versions
First, make sure that you use the latest version of all CKEditor 5 dependencies. Depending on the installation method, you should check the versions of the `ckeditor5`, `ckeditor5-premium-features`, or `@ckeditor/ckeditor5-` packages. If you cannot update to the latest version, ensure that all the CKEditor 5 packages are in the same version.
If you use third-party plugins, make sure to update them, too. If they are incompatible with the version of CKEditor 5 you use, you may need to downgrade the CKEditor 5 packages (which we do not recommend). Ask the plugin's author to upgrade the dependencies, or fork their project and update it yourself.
#### Check imports
The next step is to look at how you import CKEditor 5 into your project.
**The [new installation methods](../updating/nim-migration/migration-to-new-installation-methods.md) are designed to prevent module duplication, so if you are not using them yet, you should consider updating your project**. However, several legacy installation methods are still supported for backward compatibility, and mixing them may result in module duplication.
These are the most common import methods of the CKEditor 5 packages.
* **New installation methods (NIM)** – Imports from the `ckeditor5` and `ckeditor5-premium-features` packages.
* **Optimized build** for the new installation methods – Imports from the `@ckeditor/ckeditor5-/dist/index.js`.
* **Predefined builds** (no longer supported) – Imports from the `@ckeditor/ckeditor5-build-` packages.
* **Default imports** (legacy) – Imports from the `@ckeditor/ckeditor5-` packages (default export).
* **`src`** (legacy) – Imports from the `@ckeditor/ckeditor5-/src/*`.
* **DLL builds** (legacy) – Imports from the `ckeditor5/build/` and `@ckeditor/ckeditor5-/build/*`.
The best way to avoid duplicate modules is to avoid mixing these installation methods. For example, if you use imports specific to the optimized build, you should use them for all CKEditor 5 packages. In addition, since the DLL builds already include the core of the editor, they cannot be used with other types of imports.
Here is a matrix showing which installation methods are compatible with each other:
| | NIM | Optimized build | Predefined builds | Default imports | `src` | DLL builds |
| ---------------- | --- | --------------- | ----------------- | --------------- | ----- | ---------- |
| NIM | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ |
| Optimized builds | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ |
| Predefined build | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ |
| Default imports | ❌ | ❌ | ❌ | ✅ | ✅ | ❌ |
| `src` | ❌ | ❌ | ❌ | ✅ | ✅ | ❌ |
| DLL builds | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ |
If you use any third-party plugins, make sure the way you import them is compatible with the way you import CKEditor 5.
New installation methods and optimized builds
If you use the [new installation methods](../updating/nim-migration/migration-to-new-installation-methods.md), you should only import { code } from the `ckeditor5` and `ckeditor5-premium-features` packages. Do not import { code } from the `@ckeditor/ckeditor5-` packages unless you follow the [Optimizing build size](../getting-started/setup/optimizing-build-size.md) guide and the imports from the `@ckeditor/ckeditor5-` packages end with `/dist/index.js`.
If you use a CDN, ensure that some files are not included twice in your project.
Examples of valid and invalid import paths:
```js
import { ClassicEditor, Highlight } from 'ckeditor5'; // ✅
import { Highlight } from '@ckeditor/ckeditor5-highlight/dist/index.js'; // ✅
import { Highlight } from '@ckeditor/ckeditor5-highlight/src/highlight.js'; // ❌
import { Highlight } from '@ckeditor/ckeditor5-highlight'; // ❌
import '@ckeditor/ckeditor5-highlight/build/highlight.js'; // ❌
```
(Deprecated) Predefined builds
**As of April, 2025 predefined build are no longer supported. Please refer to the [Quick Start](../getting-started/index.md) guide to choose one of the modern installation and integration methods available**.
If you use the predefined builds, you cannot import any additional plugins. These builds already include the editor's core and selected plugins and importing additional ones will cause some modules to be bundled and loaded twice.
Examples of valid and invalid import paths:
```js
import { ClassicEditor } from '@ckeditor/ckeditor5-build-classic'; // ✅
import { Highlight } from 'ckeditor5'; // ❌
import { Highlight } from '@ckeditor/ckeditor5-highlight/dist/index.js'; // ❌
import { Highlight } from '@ckeditor/ckeditor5-highlight'; // ❌
import { Highlight } from '@ckeditor/ckeditor5-highlight/src/highlight'; // ❌
import '@ckeditor/ckeditor5-highlight/build/highlight'; // ❌
```
If you are missing some features from the list of plugins, you should switch to the [new installation methods](../updating/nim-migration/migration-to-new-installation-methods.md) which do not have this limitation.
(Legacy) Default imports and \`src\` imports
If you use the legacy customized installation method, you should only import code from the `@ckeditor/ckeditor5-` packages. While you can import code from the `@ckeditor/ckeditor5-/src/*` files, it is not recommended as it can make migration to the new installation methods more difficult.
If you use this installation method, you should not import { code } from the `ckeditor5` or `ckeditor5-premium-features` packages.
Examples of valid and invalid import paths:
```js
import { ClassicEditor } from '@ckeditor/ckeditor5-editor-classic'; // ✅
import { Highlight } from '@ckeditor/ckeditor5-highlight'; // ✅
import { Highlight } from '@ckeditor/ckeditor5-highlight/src/highlight.js'; // ✅ (not recommended)
import { Highlight } from 'ckeditor5'; // ❌
import { Highlight } from '@ckeditor/ckeditor5-highlight/dist/index.js'; // ❌
import '@ckeditor/ckeditor5-highlight/build/highlight'; // ❌
```
(Legacy) DLL builds
If you are using the [legacy DLL builds](../updating/nim-migration/dll-builds.md), you should not import any non-DLL modules.
Examples of valid and invalid import paths:
```js
import 'ckeditor5/build/ckeditor5-dll.js';// ✅
import '@ckeditor/ckeditor5-editor-classic/build/editor-classic.js';// ✅
import '@ckeditor/ckeditor5-highlight/build/highlight.js';// ✅
import { Highlight } from 'ckeditor5'; // ❌
import { Highlight } from '@ckeditor/ckeditor5-highlight/dist/index.js'; // ❌
import { Highlight } from '@ckeditor/ckeditor5-highlight'; // ❌
import { Highlight } from '@ckeditor/ckeditor5-highlight/src/highlight.js'; // ❌
```
#### Reinstall `node_modules`
Usually, npm and other package managers deduplicate all packages - for example, `ckeditor5` is only installed once in `node_modules/`. However, it is known to fail to do so occasionally.
To rule out this possibility, you can try the following:
1. Remove the `node_modules` directory.
2. Remove the `package-lock.json`, `yarn.lock`, or `pnpm-lock.yaml` files (depending on the package manager used).
3. Run `npm install` to reinstall all packages.
4. Run `npm ls` to check how many times packages like `@ckeditor/ckeditor5-core` are installed. If they are installed more than once, verify which package causes that.
### `ckfinder-missing-image-plugin`
CKFinder requires at least one plugin providing support for images loaded in the editor. Please make sure either:
* [`Image`](../api/module_image_image-Image.md) (which loads both types of images),
* or [`ImageBlock`](../api/module_image_imageblock-ImageBlock.md),
* or [`ImageInline`](../api/module_image_imageinline-ImageInline.md).
is loaded in your editor configuration.
### `ckfinder-unknown-openermethod`
The `ckfinder.openerMethod` must be one of: "popup" or "modal".
### `cloudservices-init`
An internal `WebSocketGateway` error.
This error might occur because of the incorrectly configured [`webSocketUrl`](../api/module_cloud-services_cloudservicesconfig-CloudServicesConfig.md#member-webSocketUrl) \* `config.cloudServices.webSocketUrl`} or because of the service handling the WebSocket connections being unavailable.
The original error is passed in the `error.data.originalError` property.
### `cloudservices-reconnection-error`
An internal reconnection error.
### `cloudservices-token-not-registered`
The provided `tokenUrl` was not registered by [`registerTokenUrl`](../api/module_cloud-services_cloudservices-CloudServices.md#function-registerTokenUrl).
### `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-invalid-index`
The `index` passed to [`Collection#addMany()`](../api/module_utils_collection-Collection.md#function-addMany) is invalid. It must be a number between 0 and the collection's length.
### `collection-bind-to-rebind`
The collection cannot be bound more than once.
### `collection-get-invalid-arg`
An index or ID must be given.
### `collection-remove-404`
Item not found.
### `color-picker-unavailable-with-trusted-types`
The color picker is not available, because the application enforces Trusted Types with the `require-trusted-types-for 'script'` CSP directive. The color picker cannot be rendered under that directive, so the editor turns it off.
The color palettes and the document colors are not affected. To turn the color picker off yourself, and stop this warning, set the `colorPicker` option of the feature to `false`.
For a detailed overview, check the [Content Security Policy](../getting-started/setup/csp.md#known-limitations) guide.
### `commandcollection-command-not-found`
Command does not exist.
#### Parameters
* `commandName: string`
Name of the command.
### `commentsrepository-missing-thread-and-adapter-method`
Comment thread with a given id is not added to the editor nor `adapter.getCommentThread()` is defined. See the [Comments integration](../features/collaboration/comments/comments-integration.md) guide.
### `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](../api/module_ui_componentfactory-ComponentFactory.md#function-add) 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](../api/module_core_contextplugin-ContextPlugin.md).
### `context-initplugins-invalid-plugin`
Only a plugin marked as a [context plugin](../api/module_core_contextplugin-ContextPlugin.md#static-member-isContextPlugin) 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 an alias for a dispatcher that nas not been registered.
### `conversion-attribute-to-attribute-on-text`
This error occurs when a [text node's](../api/module_engine_model_textproxy-ModelTextProxy.md) attribute is to be downcasted by an [`Attribute to Attribute converter`](../api/module_engine_conversion_conversion-Conversion.md#function-attributeToAttribute). In most cases it is caused by converters misconfiguration when only "generic" converter is defined:
```typescript
editor.conversion.for( 'downcast' ).attributeToAttribute( {
model: 'attribute-name',
view: 'attribute-name'
} ) );
```
and given attribute is used on text node, for example:
```typescript
model.change( writer => {
writer.insertText( 'Foo', { 'attribute-name': 'bar' }, parent, 0 );
} );
```
In such cases, to convert the same attribute for both [`ModelElement`](../api/module_engine_model_element-ModelElement.md) and [`Text`](../api/module_engine_model_textproxy-ModelTextProxy.md) nodes, text specific [`Attribute to Element converter`](../api/module_engine_conversion_conversion-Conversion.md#function-attributeToElement) with higher [priority](../api/module_utils_priorities-PriorityString.md) must also be defined:
```typescript
editor.conversion.for( 'downcast' ).attributeToElement( {
model: {
key: 'attribute-name',
name: '$text'
},
view: ( value, { writer } ) => {
return writer.createAttributeElement( 'span', { 'attribute-name': value } );
},
converterPriority: 'high'
} ) );
```
#### Parameters
* `data: object`
The conversion data.
### `conversion-element-to-structure-disallowed-text`
This error occurs when a [model element](../api/module_engine_model_element-ModelElement.md) is downcasted via [`elementToStructure`](../api/module_engine_conversion_downcasthelpers-DowncastHelpers.md#function-elementToStructure) helper but the element was allowed to host `$text` by the [model schema](../api/module_engine_model_schema-ModelSchema.md).
For instance, this may be the result of `myElement` allowing the content of [`$block`](../framework/deep-dive/schema.md#generic-items) in its schema definition:
```typescript
// Element definition in schema.
schema.register( 'myElement', {
allowContentOf: '$block',
// ...
} );
// ...
// Conversion of myElement with the use of elementToStructure().
editor.conversion.for( 'downcast' ).elementToStructure( {
model: 'myElement',
view: ( modelElement, { writer } ) => {
// ...
}
} );
```
In such case, [`elementToElement()`](../api/module_engine_conversion_downcasthelpers-DowncastHelpers.md#function-elementToElement) helper can be used instead to get around this problem:
```typescript
editor.conversion.for( 'downcast' ).elementToElement( {
model: 'myElement',
view: ( modelElement, { writer } ) => {
// ...
}
} );
```
#### Parameters
* `elementName: string`
The name of the element the structure is to be created for.
### `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.
### `conversion-model-consumable-not-consumed`
Some of the [model items](../api/module_engine_model_item-ModelItem.md) were not consumed while downcasting the model to view.
This might be the effect of:
* A missing converter for some model elements. Make sure that you registered downcast converters for all model elements.
* A custom converter that does not consume converted items. Make sure that you [consumed](../api/module_engine_conversion_modelconsumable-ModelConsumable.md#function-consume) all model elements that you converted from the model to the view.
* A custom converter that called `event.stop()`. When providing a custom converter, keep in mind that you should not stop the event. If you stop it then the default converter at the `lowest` priority will not trigger the conversion of this node's attributes and child nodes.
#### Parameters
* `items: Array`
Items that were not consumed.
### `conversion-slot-filter-incomplete`
Filters provided to `writer.createSlot()` are incomplete and exclude at least one children element (one of the children elements would not be assigned to any of the slots).
#### Parameters
* `element: ModelElement`
The element of which children would not be properly
### `conversion-slot-filter-overlap`
Filters provided to `writer.createSlot()` overlap (at least two filters accept the same child element).
#### Parameters
* `element: ModelElement`
The element of which children would not be properly
### `conversion-slot-mode-unknown`
Unknown slot mode was provided to `writer.createSlot()` in the downcast converter.
#### Parameters
* `modeOrFilter: never`
The specified mode or filter.
### `css-full-page-provide-sanitize-function`
When using the Full page with the `config.htmlSupport.fullPage.allowRenderStylesFromHead` set to `true`, it is strongly recommended to define a sanitize function that will clean up the CSS which is present in the `` in editors content in order to avoid XSS vulnerability.
For a detailed overview, check the [Full page HTML feature](../features/html/full-page-html.md) documentation.
### `data-filter-invalid-definition`
The definition cannot be handled by the data filter.
Make sure that the registered definition is correct.
### `datacontroller-get-detached-root`
Retrieving document data for a detached root.
This usually indicates an error as a detached root should be considered "removed" and should not be included in the document data.
### `datacontroller-get-non-existent-root`
Cannot get data from a non-existing root. This error is thrown when [`DataController#get()` method](../api/module_engine_controller_datacontroller-DataController.md#function-get) is called with a non-existent root name. For example, if there is an editor instance with only `main` root, calling [`get`](../api/module_engine_controller_datacontroller-DataController.md#function-get) like:
```typescript
data.get( { rootName: 'root2' } );
```
will throw this error.
### `datacontroller-init-document-not-empty`
Cannot set initial data to a non-empty [`ModelDocument`](../api/module_engine_model_document-ModelDocument.md). Initial data should be set once, during the [`Editor`](../api/module_core_editor_editor-Editor.md) initialization, when the [`version`](../api/module_engine_model_document-ModelDocument.md#member-version) is equal 0.
### `datacontroller-init-non-existent-root`
Cannot init data on a non-existent root. This error is thrown when [DataController#init() method](../api/module_engine_controller_datacontroller-DataController.md#function-init) is called with non-existent root name. For example, if there is an editor instance with only `main` root, calling [`init`](../api/module_engine_controller_datacontroller-DataController.md#function-init) like:
```typescript
data.init( { main: 'Foo
', root2: 'Bar
' } );
```
will throw this error.
### `datacontroller-set-non-existent-root`
Cannot set data on a non-existent root. This error is thrown when the [DataController#set() method](../api/module_engine_controller_datacontroller-DataController.md#function-set) is called with non-existent root name. For example, if there is an editor instance with only the default `main` root, calling [`set`](../api/module_engine_controller_datacontroller-DataController.md#function-set) like:
```typescript
data.set( { main: 'Foo
', root2: 'Bar
' } );
```
will throw this error.
### `decompress-compressor-not-found`
The compressor could not decompress the data as the compressor for one of entries in the `types` array has not been found.
### `detach-operation-on-document-node`
Cannot detach document node.
### `document-outline-container-not-provided`
A DOM element to inject the document outline is not provided. Please set the [`config.documentOutline.container`](../api/module_document-outline_documentoutline-DocumentOutlineConfig.md#member-container) configuration option.
#### Parameters
* `editor: Editor`
Editor instance related to error.
### `document-outline-invalid-license-key`
Invalid license key. Please contact our customer support at https\://ckeditor.com/contact/.
### `document-outline-trial-license-key-reached-limit-changes`
You have exhausted the trial usage limit (reason: reached document changes limit). Restart the editor.
Please contact our customer support to get a full access at https\://ckeditor.com/contact/.
### `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`](../api/module_engine_model_writer-ModelWriter.md#function-overrideSelectionGravity) to restore.
#### Parameters
* `uid: string`
The unique identifier returned by
### `document-selection-wrong-position`
Range from [document selection](../api/module_engine_model_documentselection-ModelDocumentSelection.md) starts or ends at incorrect position.
#### Parameters
* `range: ModelRange`
The invalid range.
### `documentcompare-apply-failed`
Applying the patch operations to the document failed. The patch might be applied partially and the document may be in a broken state.
### `documentcompare-apply-session-mismatch`
The patch is applied for a different document or editing session than the one it was captured in. The snapshot it was produced from is stale (for example the collaboration session was flushed, or the editor was re-initialized), so the patch changes cannot be merged with the current document.
### `documentcompare-applypatch-invalid-patch`
The patch failed validation and cannot be applied. The patch operations were trial-applied to a copy of the current document which failed. The patch operations are incorrect and structurally invalid against the current document. The patch cannot be applied on the document.
### `documentcompare-applypatch-unsupported-operation`
The patch contains a root operation, which is not produced and is not supported by `DocumentCompare`.
### `documentcompare-no-track-changes`
Track changes feature is required to apply operations as suggestions.
### `domconverter-invalid-attribute-detected`
Invalid attribute name was ignored during rendering.
### `domconverter-transparent-rendering-unsupported-in-editing-pipeline`
The `dataPipeline:transparentRendering` flag is supported only in the data pipeline.
### `domconverter-unsafe-attribute-detected`
The [`ViewDomConverter`](../api/module_engine_view_domconverter-ViewDomConverter.md) detected an interactive attribute in the [editing pipeline](../framework/architecture/editing-engine.md#editing-pipeline). For the best editing experience, the attribute was renamed to `data-ck-unsafe-attribute-[original attribute name]`.
If you are the author of the plugin that generated this attribute and you want it to be preserved in the editing pipeline, you can configure this when creating the element using [`ViewDowncastWriter`](../api/module_engine_view_downcastwriter-ViewDowncastWriter.md) during the [model–view conversion](../framework/architecture/editing-engine.md#conversion). Methods such as [`createContainerElement`](../api/module_engine_view_downcastwriter-ViewDowncastWriter.md#function-createContainerElement:WITHOUT_CHILDREN), [`createAttributeElement`](../api/module_engine_view_downcastwriter-ViewDowncastWriter.md#function-createAttributeElement), or [`createEmptyElement`](../api/module_engine_view_downcastwriter-ViewDowncastWriter.md#function-createEmptyElement) accept an option that will disable filtering of specific attributes:
```typescript
const paragraph = writer.createContainerElement( 'p',
{
class: 'clickable-paragraph',
onclick: 'alert( "Paragraph clicked!" )'
},
{
// Make sure the "onclick" attribute will pass through.
renderUnsafeAttributes: [ 'onclick' ]
}
);
```
#### Parameters
* `domElement: HTMLElement`
The DOM element the attribute was set on.
* `key: string`
The original name of the attribute
* `value: string`
The value of the original attribute
### `domconverter-unsafe-script-element-detected`
While rendering the editor content, the [`ViewDomConverter`](../api/module_engine_view_domconverter-ViewDomConverter.md) detected a `