Last updated Jul 8, 2024

Preparing for Confluence 4.0

Who should read this?

This documentation is intended for Confluence plugin developers. This documentation will walk through:

What's changing in Confluence 4.0?

Both the content storage format and the user experience for adding macros will change in Confluence 4.0. This release will introduce a new WYSIWYG editor with a completely different architecture based on XHTML. Also, the end user experience will change as follows:

We provide a set of tools to help you test your macro:

Frequently Asked Developer Questions

What does the new XHTML storage format look like?

See Confluence Storage Format.

Can we get access to the Confluence 4.0 source code?

If you are a plugin developer, an existing customer or partner you have access to the Confluence 4.0 release including the source from the usual locations.

For customers concerned about getting "locked in," will there be a way to export the content in a usable format?

Confluence will continue to support exporting content to Word, PDF and HTML. Additional to this, space and site administrators can export content to XML. Finally, the Universal Wiki Converter is a plugin that allows customers to move from one wiki to another.

Are nested macros supported in the new macro editor?

Yes, they are. Macros will be placed within other macros using "Macro Placeholders". Macro Placeholders are a visual representation of a macro on a page. Below is an example of what two would look like in the new editor:

What is happening to user macros?

This question can be answered in two parts:

  1. Upgrading user macros from 3.x:
    All user macros will continue to work when upgrading to 4.0. However, in order for end users to insert user macros Administrators will need to enable their user macros in the Macro Browser if they hadn't already done so in Confluence 3.4 or 3.5. This can be done via the User Macro Admin Console. Administrators have the option of only showing user macros to other administrators. It is strongly advised that you recreate your user macros in 4.0 format.
  2. Creating new user macros:
    User macros no longer have an output type of wiki markup. Instead of wiki markup, they accept XHTML in the macro template. User macros can still embed other macros using the new XHTML syntax. See the documentation.

Will it be possible to have pre/post hooks during the storage->view conversion process?

We acknowledge that would be very useful for things like security plugins, deciding if the end user can have the plugin rendered (even if they can view the page). However, we don't have this yet and are unsure if this will make it into the initial version of 4.0. We are focused on improving the editing experience rather than including more plugin points to the rendering subsystem (at this point). Your feedback for this would be appreciated.

Will we have access to edit the source code?

Please see the editor FAQ page for this.

How come you can not support old remote API for content import/export? Can it go through the to/from XHTML converter?

One of the main reasons to switch to an XHTML based storage format is that we can't convert from HTML to wiki markup in a reliable way. The remote API will offer an additional method that allows for one way conversion of wiki markup to the XHTML based storage format.

What other resources do we provide?

Rate this page: