Editor Does Not Work Properly
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
The problem can occur in either the page editor or comment editor. The editor does not work as expected. For example:
Bottom bar of the page editor disappears
Page editor does not show the content
Drafts are not saved
Comment editor shows an error: "Error loading the comment editor. Timeout while waiting for the editor resources to load"
The symptoms can vary. These are just some of the examples that you may encounter.
Cause
Problems with the editor can be due to one of the following reasons:
Interference from a third-party plugin
Confluence JIRA Plugin is disabled
Customisations
Resolution
In order to fix this issue, please try to apply one of the following resolutions:
Enable plugin safe mode to temporarily disable third-party plugins, and check the editor. If the problems with the editor go away, this points to interference from a third-party plugin. You can then enable your plugins one-by-one to see which one is the culprit.
Ensure that the Confluence JIRA Plugin is enabled, because it is needed in order for the editor to work properly. The Confluence JIRA Plugin may be disabled during start up due to timeout.
Ensure that the Atlassian TinyMCE Plugin is enabled, as explained in this KB
Ensure that the Atlassian Editor Plugin is enabled. This pluginmay also be disabled during start up due to timeout, and this plugin must also be enabled in order for the editor to work properly. Increase plugin timeout value to prevent this from happening again. See Plugins are disabled at startup and various timeout errors appear in the logs after startup for more information.
Was this helpful?