FINAL DRAFT TAGGER ERROR PARSING XML CODE

FINAL DRAFT TAGGER ERROR PARSING XML CODE

16:17:55,953 ERROR convertServiceException No status code found for exception, converting to internal server error :

It's possible to edit a page source via an app, if such an app is installed, the editing can break the content.įor Confluence 6.x or later, please check the atlassian-confluence.log file for entries similar to the following:.

Content imported from an old version of Confluence.

An example can be seen in the screenshot below:.A page was imported from an instance has had a third-party app that supplied a macro that isn't available in the destination server.The current Confluence server doesn't have the third-party app installed or has the app disabled.It was noticed that the problem may happen when: Identifying what's broken requires a deeper analysis of the problem. This error is usually due to broken HTML content. In recent versions of Confluence ( Confluence 6 onward), the error shown in the UI is a generic error message due to the introduction of Collaborative Editing:Ĭonfluence Server and Datacenter Diagnosis In Confluence 5.10.x or earlier versions, the following error will be seen in the page editor when you attempt to save the page: In this example, a page containing Unknown macros can't be saved. Depending on the version, a different error in the UI is displayed.

Ī page can't be saved after editing or not its content. This article only applies to Atlassian products on the server and data center platforms. Platform Notice: Server and Data Center Only.

Final draft tagger error parsing xml