Autocomplete

Does the autocomplete functionality work in the wiki editor?

No. Autocomplete will only work in the Rich Text Editor.

Is Autocomplete limited to a space or all the pages that I have access to?

Autocomplete works across all spaces. It also respects permissions that are already set. Just like search you won't see pages you don't have the permission to view.

How do you know which attachment you're selecting if they have the same name?

If you hover your mouse cursor over the Attachment in the Autocomplete drop down you will get a tool tip telling you which space that attachment is located in.

How do you insert a regular bracket into the page? (If you don't want to do a link?)

You can just enter the bracket and press ESC to exit Automcomplete.

Keyboard Shortcuts

Where will all of the info on the shortcuts live?

You can find the complete list of keyboard shortcuts here - Keyboard shortcuts

Will the new shortcuts work in the wiki editor also?

The shortcuts only work in the Rich Text Editor.

Templates

Can you show some of the examples of the templates?

You can check them out yourself here: https://plugins.atlassian.com/search/category/20177

Themes

How do existing users migrate their left navigation theme to a new supported theme?

They can still use the Left Navigation Theme but they can change the theme of their space via Browse > Space Admin > Themes. Just like the Left-Navigation theme, the Documentation theme does support custom wiki markup in the side-bar. To migrate the sidebar content, they will have to manually copy and paste the markup from the side-bar page in the Left-Navigation theme to the Navigation section in the Documentation theme. See Configure the Documentation Theme for details. 

Is the documentation theme in 3.2 the same as the one in the plugin exchange now? any enhancements?

The bundled Documentation theme is the same as the one on in the plugin exchange.

Custom headers and footers: are they to be defined space-wide, or on a parent-children basis?

You can define a header and footer at both the space and site level. See Configure the Documentation Theme and this blog post.

Is the documentation theme compatible with Internet Explorer 6?

No. IE6 is a supported browser for Confluence 3.2 but not all the features of the documentation theme will work in IE6.

Hardware Requirements

Are the hardware requirements for Confluence 3.2 different when compared to previous releases?

The hardware requirements have not changed. Please see this page for details - Server Hardware Requirements

Sandbox

What is the URL for the sandbox?

You can find the Confluence sandbox at http://sandbox.onconfluence.com/

Supported platforms

Have you made any changes to supported platforms? appservers, DBMS, browsers. Thanks

We've added support for Firefox 3.6 and deprecated support for Jboss. See the list of supported platforms for details - Supported Platforms

Rich Text Editing in Chrome is not supported in 3.1

That's correct, Chrome is not officially supported but we enabled rich text editing for Chrome in 3.1.

Which browser do you recommend? Is Firefox ok?

We support Internet Explorer 6, 7, 8; Firefox 3, 3.5, 3.6; Safari 3, 3.1, 4. (On 13 July 2010, in line with Microsoft's Support Lifecycle policy, support for IE6 will end.) Chrome should work with the Rich Text Editor but is not officially supported.

Is Jboss and MS IE 6.0 no longer supported with 3.2?

IE6 is still supported in this release. JBoss is not. (On 13 July 2010, in line with Microsoft's Support Lifecycle policy, support for IE6 will end.) Please refer to: Supported Platforms

Do you allow rich text editing in Chrome now?

We have enabled Rich Text Editing for Chrome but it is not officially supported in Confluence 3.2. See Supported Platforms for details.

Upgrade

Will all plugins that worked with Confluence 3.1 work on 3.2?

It depends on which plugins you are running. Before upgrading, you should check with the plugin devloper or check http://plugins.atlassian.com to see whether it's compatible with Confluence 3.2.

What upgrade path is supported for 3.2? We're running a very old version of Confluence. Can we upgrade directly?

Upgrading to Confluence 3.2 should be fairly straightforward. Please refer to the Confluence 3.2 upgrade notes for further essential information about plugins and other factors affecting your upgrade - Confluence 3.2 Upgrade Notes

I'm running 3.1. what's the easiest way to upgrade to 3.2?

Upgrading to Confluence 3.2 should be fairly straightforward. Please refer to the Confluence 3.2 upgrade notes for further essential information about plugins and other factors affecting your upgrade - Confluence 3.2 Upgrade Notes

  • No labels