Last updatedMay 15, 2019

Browse menu and Space Tools changes in Confluence 5.0

Some plugin developers maybe impacted with some changes introduced in Confluence 5.0. These changes were introduced after the BETA2 release of Confluence 5. A brief overview:

  • You current version of plugin will still work with confluence 5.0 even if you don't update your plugin.
  • You might want to adjust your plugin to suit the new space admin layout.
  • The latest changes only affect the Space Admin/Tools area.

Bellow is the list of changes with the examples:

No more Browse menu in the default theme

This change was in the Confluence 5 BETA and EAP releases. The Default theme no longer has the Browse menu. Note: the Documentation theme still has this.

The items that used to be in the browse menu moved to either

  • the top level items ( section="system.header/left" )
  • the help menu ( section="")

Additionally, there is a new administration menu (section="system.admin/pages") which is only visible to system administrators and not visible to other users.

There is still a user menu ( section="system.user").

If your plugin used to add a link to the Browse menu under system.browse section it will appear under Help menu. We recommend changing the plugin for Confluence 5.0 and move the menu item into the appropriate place. You can use one of the sections described above but first, please, consider the newly added sections:

There is a tutorial about the space main links section and we will describe the Space Tools section.

Space Tools Sections

We have re-organised space admin/operations screens. We simplified them and made them more intuitive for confluence's users.

The list of sections:


Currently items defined by plugins will appear under "Add-ons" section unless they specify one of the section listed above. If plugin defines its own section with several items then the section will appear on the top.

Documentation theme still has that menu

One thing to keep in mind pace that is configured to use Documentation Theme will still have Browse menu and old layout of Space Details. Going forward we plan to remove documentation theme but for Confluence 5.0 the web items/sections should cater for both themes.

In quite a few places we define the same item/section twice and display one of the items would have a condition that will only evaluate to true when inside the default theme. Bellow is the example of such item

<!-web item only shown for spaces with sidebar see the SpaceSidebarCondition ->
<web-item key="watch-space" name="Watching" section="system.content.collector.pages" weight="1">
    <label key="" />
    <link linkId="space-watching">/spaces/addspacenotification.action?key=$generalUtil.urlEncode($helper.spaceKey)&#url_xsrfToken()</link>
    <condition class="com.atlassian.confluence.plugin.descriptor.web.conditions.user.UserLoggedInCondition"/>
    <condition class="com.atlassian.confluence.plugin.descriptor.web.conditions.user.UserWatchingSpaceCondition" invert="true"/>
    <condition class="com.atlassian.confluence.plugin.descriptor.web.conditions.SpaceSidebarCondition"/> <!- Show the web fragment if the space sidebar is available. ->

<!-web item only shown for spaces with sidebar see the inverted SpaceSidebarCondition ->   
<web-item key="startwatching" name="Watching" section="" weight="20">
    <label key="" />
    <link linkId="space-watching">/spaces/addspacenotification.action?key=$generalUtil.urlEncode($helper.spaceKey)&#url_xsrfToken()</link>
    <icon height="16" width="16">
    <condition class="com.atlassian.confluence.plugin.descriptor.web.conditions.user.UserLoggedInCondition"/>
    <condition class="com.atlassian.confluence.plugin.descriptor.web.conditions.user.UserWatchingSpaceCondition" invert="true"/>
    <condition class="com.atlassian.confluence.plugin.descriptor.web.conditions.user.UserWatchingSpaceForContentTypeCondition" invert="true">
        <param name="type">blogpost</param>
    <condition class="com.atlassian.confluence.plugin.descriptor.web.conditions.SpaceSidebarCondition" invert="true"/>

Any questions? Feel free to comment on the page to let us know.