Documentation for Confluence 5.4.
Documentation for Confluence OnDemand and earlier versions of Confluence is available too.

Skip to end of metadata
Go to start of metadata

Confluence 5.4 has now been released – see the Confluence 5.4 Release Notes.

19 September 2011

With great pleasure, Atlassian presents Confluence 4.0. This is one of the most significant updates to Confluence since its initial release in 2004. With a brand new WYSIWYG editor and wide-ranging user interface improvements, we're confident that Confluence 4.0 is the most productive and user-friendly version to date.

 

Highlights of Confluence 4.0:

More:

Video of What's New:


Thank you for your feedback:

More than 215 requests implemented
Over 1050 votes fulfilled

 

Icon

Note: The Wiki Markup editor has been removed in Confluence 4.x and replaced with a new XHTML-based editor. Please see Why We Removed the Wiki Markup Editor in Confluence 4.0 for full details

Highlights of Confluence 4.0

 

Brand New Editor

We've rebuilt the Confluence editor from the ground up, bringing you an editing experience that's simpler, faster and richer.

The new Confluence editor delivers many advantages:

  • Just one editor!
  • New, streamlined user interface.
  • Redesigned toolbar with enhanced text formatting (indent paragraphs) and alignment controls.

 

Simplified Editing Experience

Editing in Confluence 4.0 is more visual and more contextual, putting more power at your fingertips.

Table Editing

We've made table operations better in Confluence 4.0 with the following features:

  • Drag to Insert Tables
    Inserting tables is now easier and truly "WYSIWYG" with this new feature. Just click on the new Table dropdown and drag your mouse to choose the number of rows and columns you'd like in your new table. Oh, and don't worry if you like inserting tables with your keyboard, you can still use autoformatting or CTRL+SHIFT+I to insert a table.
  • New In-Context Table Toolbar
    The new table toolbar removes the need for a context menu and only appears when you add a table to the page.
  • Merge and Split Table Cells.
  • Highlight cells, rows or columns.
  • Cut, copy and paste table rows.

Improved Image Handling

  • Paste Images From Clipboard (Firefox and Chrome only)
    Just copy any image to your clipboard and hit CTRL+V in the editor. The image will get attached and embedded directly into your page. There's nothing to install on your desktop, it just works!
  • Turn Images Into Links
    Now you can turn images into links. This is especially handy for turning images into a button.
  • Custom Image Sizes
    If you don't like the preset image sizes, you can now specify an exact image width.
  • Search Images
    You can now embed images from other pages using the new Search tab in the image browser.

Simplified Macro Editing

Confluence 4.0 introduces macro placeholders, a visual representation of your macros while editing. Create rich content with new and existing macros, without the tools getting in the way. Makes macros easier to manage while editing.

  • A More Visual Experience
    Making it easier to visualise what the page will look like when you save it.
  • Macro Properties Panel
    Every macro has a properties panel. The property panels for particular macros, such as the Status and View PowerPoint macros have additional functionality, as shown in the screenshot below. 
  • Quick Access to Macro Editing
    Double-click the macro to open the Macro Browser for parameter editing. The contents of some macros can be modified directly from the editor.

 

New Macros

We've bundled more macros with Confluence, and made some of the existing macros better, to help you easily include and present relevant content:

  • Status Macro
    The Status macro is an easy way to show your status in reports (i.e. red, yellow or green) as a coloured lozenge. You can use the properties panel to quickly change the status.
  • Expand Macro
    The Expand macro allows you to add a dynamically expandable section of text to your page.

     
  • Profile Picture Macro
    The Profile Picture macro displays a users profile picture on a page. Useful for creating Team Pages.

 

Faster Editing Experience

Write Wiki Markup ... Fast!

Many of Confluence's biggest fans are avid wiki markup users. For you aficionados, we wanted to give you the fastest editing experience possible, while preserving the speed and efficiency of your existing wiki markup skills. So, we present you with Autoformatting!

Video of Autoformatting in Action:
What is Autoformatting?

Autoformatting lets you type wiki markup into the editor. This new feature will "auto-format" your text on the fly. To learn more, click on the  help button in the editor and select the Editor Autoformatting tab.

Try these and see what you think:

  • Font Formatting
    Bold, underline, strikethough, italic, superscript, subscript – just type the markup, such as *Bold*, and watch it convert to Bold on the fly!
  • Basic Tables
    Try typing |||||| , or || Heading 1 || Heading 2 || , then hit enter to to instantly see this:

    Heading 1

    Heading 2

  • Emoticons
    All of our emoticons convert on the fly. Try typing :-) into the editor to instantly see this: (smile). It even works for (/), showing this: (tick) .
  • Lists
    For numbered lists, type # and a space at the start of each line.
    For bulleted lists, type * and a space at the start of each line.
  • Headings
    Type h4. then some heading text to see a level 4 heading.

Quickly insert a link to create a page with Autocomplete for links. Simply type '[' in the editor and as you type, Confluence will display a Create Page link if a page with that title does not already exist in your current space.

(info) Introduced in a previous release of Confluence (see details in this blog post), adding links, media and macros can still be quickly added by typing [, ! or { in the editor to add various kinds of content to your page.

 

Introducing @mentions

Confluence 4.0 includes the new @mentions feature. This allows you to easily bring collaborators into a conversation: if you are mentioned in any Confluence content (a page, blog post or comment) you will be notified by email.

To mention someone, type @ and their name, when editing. Mentions will instantly suggest people you are following in your network, so you can quickly find and involve your friends.

 

Improved Page Comparison Functionality

We've got a better way to view changed content in Confluence.

Improved Page Diffs

We've simplified page diffs to make them easier to read. Now, page differences appear exactly as they do in Confluence. Images, text and tables are displayed as rendered. Additionally, page diffs now show changes to both formatting and macros.

Diffs in Email

Where possible, email notifications are now rendered in your email view with the correct diff colour coding.

 

Email Notification Improvements

New Email Design

All email notifications in Confluence now have a new design. This works in major email clients as well as on the iPhone.

Follow Notifications

Confluence now sends email when someone follows you.


 

New Confluence Installer and Guided Upgrades

Much to the delight of any sysadmins that are looking after Confluence, the Windows and Linux guided installers are now available.

Guided Upgrades

The new Linux and Windows Installers include an option that allows you to upgrade an existing Confluence 3.5.x (or later) installation. This upgrade automates the following tasks for you:

  1. Backs up the Installation and Home Directories of the existing Confluence installation.
  2. Installs Confluence 4.0.x whilst migrating the following from your existing Confluence installation: 
    • TCP port values in your existing Confluence installation's server.xml file,
    • The upgrade feature detects and notifies you of any other files in the Confluence subdirectory of your existing Confluence Installation Directory, which have been deleted, added or modified from the default. This informs you of any customisations you will need to manually migrate across to your upgraded Confluence installation directory.

Simplified Installation Process 

  • Guided installer: The guided install wizard has been implemented for Confluence 4.0 on both Windows and Linux operating systems. Installing a new instance is a breeze.
  •   Easy JIRA Integration: Hook Confluence up with JIRA, right within the Confluence setup wizard.

 

 

New Editor Plugin Points for Developers

We've added more editor plugin points for developers. Notable improvements include:

Editor Plugin Points

  • Extend the Macro Property Panel
    Plugin developers can add buttons to the Macro Property Panel in the editor.
    For example, insert a Gliffy diagram or see the tutorial on how to do this.
  • Render an Image in the Macro Placeholder
    A plugin developer can now render an image instead of a placeholder for bodyless macros. For more information, check out the tutorial on how to do this.
  • Custom Parameter Rendering in Placeholders
    You can choose to display any parameter in the macro placeholder in the editor, instead of having the placeholder automatically show the first few parameters.
  • New Pluggable More Menu
    Plugin developers can add items to the editor's More menu. See this tutorial for details.

Developer Resources

  • View Storage Format
    To assist with plugin developers and help with developer issues, developers running in Dev mode and Confluence administrators can view the page storage format from the Tools menu in Confluence.
  • New API Changes
    We have disabled the getPage() and getBlogEntry() read methods in the XML-RPC/SOAP API. If you have a script that primarily reads or appends to existing pages, it will break. Creating pages and overwriting existing pages will still work.
  • Plugin Developer Documentation
    We have created a landing page for Confluence 4.0 planning. This includes resources for plugin developers to help you create new plugins, and make use of the new plugin points, as well as upgrade your existing plugins.

Infrastructure Changes

This release includes a number of improvements in the APIs and under the covers as well.

  • Anti-XSS Mode
    This is now enabled by default for plugins.
  • Alignment and Border Parameters
    The alignment and border properties in the macro definition template have been removed.
  • Thumbnail Settings
    The Thumbnail maximum height and Thumbnail maximum width settings have been removed from the General Configuration page.
  • Link Browser
    The Link browser is no longer built in GWT and is now built in core JavaScript.
  • Integration Platform 2.12.0
  • Upgrade to AUI 3.5.0
 

Other Improvements

As always, we have made various small improvements to Confluence screens, functionality and supported platforms.

  • Chrome and Internet Explorer 9 Support
    See the upgrade notes for more information about browser support.
  • Administrator's task list in the Admin Console
    This new task list in the Admin Console helps administrators get started after a new install.
  • New keyboard shortcut:
    CTRL+SHIFT+E
    to preview when you are in the editor; hit 'E' to get back to the editor.
  • Administration UI
    Help tips have been added to the field descriptions.
  • Quicknav Improvements
    Quicknav now indicates the space the page is coming from. This helps you find a page that might have the same title across multiple spaces, as well as selecting the first search result by default, making it quicker to open the link.
  • Advanced Linking
    We've updated the Link dialog to cater for these link types: shortcut links, anchor Links, and undefined links (which you can do using Autocomplete).


 

Helping You Transition to Confluence 4.0

We've created a set of resources to help you manage the transition away from wiki markup. We know your people have become experts with using wiki markup in Confluence, but we think you'll really appreciate the new editor, and we want to make it as easy as possible for you to make the change. The change management resources are listed under the current documentation.

Release Notices

Upgrading from a previous version of Confluence

(warning) You can only upgrade to Confluence 4.0 from Confluence 3.5. From version 3.5 , you'll be able to use our now automated upgrader to move to 4.0. See the Confluence 4.0 Upgrade Notes.

Follow the normal upgrade instructions to upgrade your test instance to this release. We strongly recommend that you back up your Confluence Home directory and your database before upgrading.

When upgrading from a previous version of Confluence, if you have customised your cache settings (as documented in Cache Performance Tuning) then you may run into memory problems during the wiki to XHTML migration. We are working to fix this in a later release, but in the meantime you can revert your ehcache.xml to the default version.

  • If you still experience problems, try reducing the 'maxElementsInMemory' attribute on each cache to a very small value such as 50.
  • Note that any cache changes you make to work around migration problems should only be considered temporary. You should restore caching to its original settings again after migration has been successful.

Removed Functionality

Features removed from Confluence
  • The Edit Page in Word functionality
    This is being removed in Confluence 4.0. Note: This is a different feature to "Edit attachment in Word".
  • Mail Page Plugin
    The Mail Page plugin is no longer bundled in Confluence. With the introduction of the "Share Page" feature in 3.5 this is no longer needed.
  • Social Bookmarking Plugin
    The Social Bookmarking plugin is no longer bundled in Confluence but is still supported.
  • The SnipSnap importer has been removed from the admin console.
  • Please be aware that Confluence Clustered is not available for version 4.0 yet. It will be forthcoming in a minor release, following the launch of version 4.0.
Settings removed from Confluence

These settings were removed due to low recorded usage and the ongoing goal of simplifying Confluence.

  • The CamelCase Links setting, from general configuration.
  • The Number of Ancestors to Show in Breadcrumbs setting. 


A big thank you to everyone who helps us ensure that Confluence keeps getting better and better!

The Confluence 4.0 Team

Development

Ryan "Lawson" Ackley
Nabeelah "Stitch" Ali
Richard "Karaoke King" Atkins
Niraj "Max Connections" Bhawnani
Joseph "C# forever!" Clark
Paul "Caravan of Courage" Curren
Lachlan "Dilly" Dally
Chris "Daz" Darroch
Anna "A18Z" Dominguez
Matthew "Sony" Erickson
Steven "Lefty" Haffenden
Sam "@Mentions" Haldane
Chris "Killer" Kiehl
Daniel "Threads" Kjellin
Steve "CMD+V" Lancashire
David "Long" Loeng
Brian "The Intern" Nguyen
Craig "Patient Zero" Petchell
Agnes "GWT-free" Ro
Matt "Kermit" Ryall
Stefan "Git FTW" Saasen
Sam "Design School" Tardif
David "Animal" Taylor
Ryan "Bieber" Thomas
Wesley "Weasles" Walser
Don "Not Fun" Willis
Jared "Goonbag" Wyles

Architecture
Charles "Egregious" Miller

Build and Release Engineering
Adrián "Elastic" Deccico

Plugin Updates
David "Calendars" Chui
Philip "The Mac" Cher
Kai Fung "KFC" Chong

Management

Product Management
Bill "Keynote" Arconati
Sherif "Corners" Mansour

Product Marketing Management
Ryan "Phish" Anderson
Terrence "Yet Another CMC Guy" Caldwell
Matthew "Hollywood" Hodges

Development Manager
Jonathan "The Running Man" Gilbert

Cross Team

Technical Writing 
Edwin "Rambo" Dawson
Paul "TOC That Rocks" Watson
Sarah "Mad Docs" Maddox

Quality Assurance 
Joey "Good Morrow" Corea
Mark "Triple Word Score" Hrynczak
Federico "Boy Scout" Silva Armas

Front-end Development
Ben "Owie" Buchanan

Design
Stephen "Pixels" Russell

Support

Sydney Support
Renan Battaglin
Vincent Choy
Roy Hartono
Partha Kamal
Donna McGahan
Michael Seager

Amsterdam Support
Tony Atkins
Sherali Karimov
Dennis Kromhout van der Meer

Brazil Support
Rodrigo Adami
Tiago Kolling Comasseto
Guilherme Heck
Alyson Reis

Kuala Lumpur Support
Husein Alatas
Janet Albion
Septa Cahyadiputra
Kah Loun Foong
Sim Foo Guan
Heng Hwa Loi
Joachim Ooi
Hanis Suhailah

San Francisco Support
Rick Bal
David Chan
Robert Chang
Ty Davis
Marian Finch
Adam Laskowski
Brad Mallow
Wayne Tombo
Timothy Wong

Integration Management
Melanie Carasso
Ted Tencza

Integration Development
Sam Le Berrigaud
Don Brown
Trevor Campbell
Dave O'Flynn
Shihab Hamid
Adrian Hempel
Justin Koke
Peggy Kuo
Mark Lassau
Olli Nevalainen
Tim Pettersen
Felix Schmitz
Piyawoot Songsiritat
Joseph Walton
James Wong

Release Babies
Thomas Dawson
Max "The Giant" Kiehl
Evie Kjellin
Mathilda Saasen

 
  

  • No labels

51 Comments

  1. Anonymous

    I wish this editor could be available for Atlassian JIRA for the next release. (smile) 

  2. Anonymous

    When is Confluence 4 coming to Jira Studio?

    1. We're looking at late-Oct / early-Nov at the moment.

      1. Anonymous

  3. Anonymous

    Any chances the new editor will have an option to see the wiki markup "source" of a document? I've ran into some bugs with formatting when copying and pasting text from web pages into the editor where it would have been nice to be able to switch to "source" mode to tweak the format.

    1. No but if you file a bug at jira.atlassian.com and provide us with the content you were trying to paste and the problem you encountered then we can try and fix in order to prevent others from encountering the problem in the future.

      1. Anonymous

        I would like this as well, we use JIRA and Confluence at work and I have created tools that creates JIRA friendly "markup source".. this doesnt work anymore.

  4. Anonymous

    the code macro in my experimenting displays tabs as 4 spaces in the viewer, but in the editor, displays them as 8 spaces. This needs to be configurable, both in the view (as a system preference, and maybe a code block option), and in the editor (as a personal preference)

  5. Anonymous

    Just playing with it at the moment, guys. Wow! Huge improvement! And actually easy to install - that's gotta be a first (wink)

    However, search functionality could do with a little tweaking - in particular, given that Confluence is so perfectly suited to hosting very large documents, I'm very surprised there isn't a search hit highlighting feature yet? (Just to irritate you, I'd point out that Mindtouch has had this feature for some time - sorry! sorry!)

    Even better, of course, would be a couple of buttons allowing you to skip from one hit to the next/previous hit.

    But it's a huge step forwards, in any case. We're now looking seriously at Confluence as an intranet/extranet option.

  6. You took away the "Wiki Markup Editor".  It allowed me to display a page as wiki markup text, take the text with me, work on it offline in a text editor, bring it back, and paste it in.  I just spent a day doing just this and the company upgraded to 4.0 over the weekend.  Now I will lose all my work and waste another day trying to determine exactly what was changed and then trying to use the RTF editor to adjust all the items I had adjusted through wiki markup.

    Do not take away major functionality, even if in your opinion what you have done is better.  There are those of us who prefer certain ways of doing things!

    1. I'm not sure what I think about this one.  There are really several issues here.

      First, the move away from the wiki markup text was the major focus of this release.  It was clearly documented in Atlassian's release notes, and should have been properly reviewed and communicated by your organization before following-through with the upgrade to 4.0 to prevent issues such as the one you observed.

      Second, the new Confluence editor supports the import of wiki text.  Use Insert / Wiki Markup.

      Third, I do think that Atlassian needs to do something better with the View/Source option.  Wiki markup is now "deprecated", so I agree that this option should no longer be provided.  (It contributed to a significant number of "round-trip" issues, anyway.)  I would encourage a "View XHTML Source" option to be provided here instead - since XHTML is, in effect, the replacement for the Wiki markup - and is how the pages are stored within the database.  Eventually, users should also be given the option to import XHTML (as with wiki markup in the past) - providing users and systems an option to interface with the wiki pages, without needing to worry about any of the previous round-trip formatting issues.

      1. Thank you for the heads up on the "Insert / Wiki Markup" (I did not think to look for Import under Insert) function.

        I entered an Improvement request (CONF-23315).  I agree that there must be a way to directly edit XHTML; it can solve so many problems and issues as well as allow those of us who can write XHTML faster than we can use an RTF editor to exploit our skills and get the speed we want.  Just make sure the XHTML supports "<div>".  We have used a HTML-based RTF editor JIRA plugin for our JIRA system and it has an "HTML" button that pops up the source HTML in a simple web-based text field that you can edit and submit back into JIRA.  Works very well, except it does not support <div> and so it is difficult to get the appearance one may desire (mainly spacing between paragraphs and other elements).

        1. I agree that there must be a way to directly edit XHTML

          You could connect to Confluence via WebDAV.

    2. Anonymous

      Well they took away the only editor I actually used. Ever since we moved from Word to Confluence for documentation, I have been happy that I no longer had to deal with a "buggy-rich-text-editor"... And if they think they will be able to make their editor "bug-free", well i guess the naive is happier than the rest of us, because they won't, there is no such thing as bug free, and the more complex things become the more bugs they have, that is a fact of software (Something I as a developer just have to admit about my own software as well)...

      Having the ability to revert back to the raw text could often solve problems... I understand that some people are more comfortable in a "WYSIWYG" editor, but this won't go for all of us... But here is for hoping that there is enough people out there thinking like me to put some pressure on the team to bring back our beloved "Wiki Markup Editor"...

      Other than that, I HOPE!... that using the SOAP/XML-RPC API you will still get presented with the Wiki markup?... At least that enables me to circumvent this choice... beginning to edit in Raw XHTML?... unless it has full XHTML support, I can just see the editor fall completely apart... 

      1. I have been happy that I no longer had to deal with a "buggy-rich-text-editor"... And if they think they will be able to make their editor "bug-free", well i guess the naive is happier than the rest of us

        Have you tried the new editor yet? I think you'll be pleasantly surprised at how reliable it is.

        Of course there will be bugs and we will do our best to fix them. If you encounter any bugs please let us know what they are by raising an issue on our public issue tracker.

        1. Anonymous

          {quote}

          Have you tried the new editor yet? I think you'll be pleasantly surprised at how reliable it is. 

          Of course there will be bugs and we will do our best to fix them. If you encounter any bugs please let us know what they are by raising an issue on our public issue tracker.

          {quote}

          Well I posted here didn't I? (tongue)... But yes I have used it as I tested it out for my home setup and we will be using if in the company soon, but have not used it for long enough to run into bugs, but as a developer I know that bugs are inevitable and as mentioned the more complex the solution, the more bugs...

          As for Rich text editors, i have not worked with one single editor of that kind yet that did not cause pain sooner or later, and my best bet is that ones we go into special cases here this will be the same, the thing is that yes, for the most common case the editor will properly behave, but ones people go into cases that you might have not thought anyone would, that's where the test coverage is often (always?) low, and where the bugs or annoyances will properly occur.

          Tables Like

          Can't Be

          Edited, Adding New

          Rows

          Will

          Result in

          Only TwoColumns, and I wanted 4

          I did discover that using the "merge cells" can also produce strange behavior which I would classify as a bug, but since that wasn't possible before then I won't bash to much on that, it just goes to prove a point about what happens when you dive into higher complexity.

          I wanted to give this example by creating a section with 10 columns and then a step in each, copy a 3x3 table into each column and then do one step in first column, 2 in second etc... But I simply gave up in the end because doing that had become far to annoying as Copy/Paste never works as expected... So ill just give an example of one result Copy/Paste of an empty table yielded...  

          Try copying an empty table:

          Original: 

             
             
             

          One Result (I have seen multiple).

            
             
             

          When we will get 4.0 in the company, I won't mind posting bugs as I see them, but I will never support the choice of not having the option to revert to something more simple, something more manageable, and the trouble I wen't through doing this little simple post just supports my standpoint....

           

           

           

          1. When we will get 4.0 in the company, I won't mind posting bugs as I see them

            Thank you. We would greatly appreciate that (smile)

            I can reproduce the table copy and paste issue. It seems you did not select all the table cells to copy. See here.

            and the trouble I wen't through doing this little simple post just supports my standpoint....

            The bug you produced came from a feature that was not possible in wiki markup– merge cells. Did you have any issues with with entering the rest of your comment as you would have in the old wiki markup editor?

            How did you produce the first table in which you actually wanted 4 columns? Would be great to know what caused it so we can fix in it an future release.

            1. Anonymous

              It is true that it is a new feature, but the point was more to give examples of what troubles it can give...

              Such a table is extremely simple to produce... in... wiki markup...

              I did select the entire table, I even tried using the keyboard for selecting as that is more reliant... I had huge issues copying a column within a section as well, it kept copying the section + column...

              You never answered the question for the API, using the SOAP/XML-RPC API, till it return wiki markup or XHTML now?...

              In any case, these was just a few cases to demonstrate...

               

              1. You never answered the question for the API, using the SOAP/XML-RPC API, till it return wiki markup or XHTML now?...

                This question is answered at Confluence 4.0 Editor FAQ. It will return XHTML, but will accept both.

            2. Anonymous

              I can add a few more minor oddities, but of you wonder why those annoy me, then ask the person next to you to pull his chair over to your desk and for the entire day poke you lightly with his finger in 10 second intervals for the entire day, when you get really sour and agitated, you know why the smallest bug annoys me.

              Anywho.

              • Copying text into the code macro strips away line breaks and spaces, so now I have to format my code example all over again. 
              • Blocks like columns, the code macro etc seems to add spaces here and there, some of them disappear on save but are hugely annoying.
              • We can't link to the same stuff anymore, we frequently linked to documents under source control which was mirrored out to a share in the company.
                This only worked with IE 8 / IE 9 before it seems, now it doesn't work at all, I even ended up in the next bullet by trying multiple things.
              • I Managed to break "Un-linking" so that I could not get rid of a link I had created, this I could have fixed en either a Wiki or Source Editor, but the RTE was just stuck, even when I deleted the entire thing and re-wrote the text, it had keept some of the formatting so I had to color it which moves me to my next one.
              • I Can't seem to get rid of that superfluous tag now, ones you have chosen to color something you will have a "<span>" tag, but how would you ever remove that again, some times I can others I can't? This can over time lead to (I wen't crazy here to demonstrate a worst case scenario):

              Procedure is that you choose a color for something, but ups you marked a little to much so now you choose the little piece you marked to much and color that back, repeat over time. And not only did it Bloat the XHTML, which for many users wouldn't matter because they didn't know that, but it also slightly broke the editor as to set colors I had to click the color button multiple times.

              Some of these is already created as bugs (I did that), some aren't yet (specifically the last one and the added spaces)

              The worst thing about all these bugs is that if not all, then at least some of them will be hard to reproduce, e.g. the link one, how did I manage to get my self in that situation using the editor?... well I don't know. All of them could have been corrected using a Source Editor. (Direct XHTML editing or WIKI wouldn't matter in this case)
               

              1. Anonymous

                Ohh and another one. This comes in faster than you can say "Bug"...

                Apparently 4 dashes (which should produce a horizontal line) does not some times.

                Specifically I was placed in between 2 section macro blocks when noticing this.

            3. Anonymous

              Also ran into issues with the Dynamic task macro.

               - https://jira.atlassian.com/browse/CONF-23580

            4. Anonymous

              Also submitted:

               - https://jira.atlassian.com/browse/CONF-23581

              Because editing the properties of a macro with the new editor has become an absolute pain, and it defeats any sort of productivity you could imagine.

              Imagine a page with 10 code examples where you wanted to add line numbers... You would have to select and edit each of the at a time... A 2 minute task just became a 15 minute pain-full experience... 

            5. Anonymous

              You are also unable to select templates if you create a new page by creating the link first.

              Often we would go ahead and create the links to new pages, then create the new page after that following the link, you would then be offered to create it using a template, this has been removed with the new editor.

              https://jira.atlassian.com/browse/CONF-23884

            6. Anonymous

              The new way of linking is also freaking me out...

              Before I would type [New Link] and i would have a link, NOW i have to type [New Link <Arrow Down><Arrow Down><Arrow Down><Arrow Down><Enter>]

              And arrow down X number of times depending on existing pages... Now this certainly doesn't mimic the behavior working with the Wiki syntax before, so could you please add an option for personal preferences here, I would RARELY, if ever use "[]" for anything but links. And even then I would be use to escaping the characters...

              https://jira.atlassian.com/browse/CONF-23934

              1. Before I would type [New Link] and i would have a link, NOW i have to type [New Link <Arrow Down><Arrow Down><Arrow Down><Arrow Down><Enter>]

                Instead of pressing the down arrow, just press the up arrow once (smile)

                1. Anonymous

                  Which means you misunderstood the main point, the amount of "arrow" presses is irrelevant, it breaks the old pattern and is annoying because of that.

                  I suggested it to be a "personal setting" because some might actually need normal text surrounded by [], but if that is a minor part of the people using it, then maybe it would just be better to make it default behavior that ] was a shortcut to "Insert Link to Create Page"

                  1. it breaks the old pattern and is annoying because of that

                    We understand that change can be hard. In this case you've actually got a better solution for one extra keystroke – the up arrow. Confluence is checking to see that there no pages in the current Space with your desired title, avoiding the scenario that you create an undefined link to a page that already exists.

                    but if that is a minor part of the people using it

                    I'm glad you agree that this is a minority use case. If we provided a personal setting for every one of these, the number of settings would get of control (smile)

                    because some might actually need normal text surrounded by []

                    [it's still possible to do this] – just press ESC after pressing [ – that will disable Autocomplete. Hope that helps.

                    1. Anonymous

                      ...In this case you've actually got a better solution for one extra keystroke – the up arrow. Confluence is checking to see that there no pages in the current Space with your desired title, avoiding the scenario that you create an undefined link to a page that already exists.

                      The scenario you say I avoid, could not be achieved before, so to that there is no real change to the integrity, back to the case where it really just adds extra Key strokes.

                      And a inline search for existing pages, which is arguable not really any help in this scenario at all, but is when you need to add link to already know pages you didn't know you where going to add a link to in the first place... Wait what???...

                      What you maybe could do before was creating a link to an existing page and not discover that until after save, but if that was the case, you should really begin to think about naming conventions, because it is apparent to me that you just realized you had a problem naming things so they have unique meaning within the confinement of your project which hopefully maps to a space... But that is a whole other discussion.

                      I'm glad you agree that this is a minority use case.

                      Please read that I expect it to be the minority of people that actually uses the [] to NOT create links, and the most of us do only use those when we in fact do create links, and that is where I say that if that in fact is true, "]" should instead add the link, either to an existing one or to a new one.

                      (It should really not be that hard to implement). If there is one page match "]" = "Enter", if there is no page matches "]" = "Arrow Up + Enter"...

                      Now if it is really the case that everyone is running around typing [Hello] [This] [Is] [Not] [A] [Link] in there documents, then I will do this: o.O... And say fair enough.

                      [it's still possible to do this] – just press ESC after pressing [ – that will disable Autocomplete. Hope that helps.

                      Wait what?...

                      I had properly no written as much had I read to the end first, took your sections one at a time, but now I feel a kind of anger and fatigue since this indicates that you did not at all understand, maybe you didn't even read my comments all the way though?...

                      Sorry,but it feels like it with that statement... Even though [it's still possible to do this], which I already knew, as my complaints is exactly about that being the result of... typing... exactly... that... even... without... um... pressing... ESC...

                      Key PressesResultMy Wish
                      ​"[","ESC", "N", "O", "L", "I", "N", "K", "]"[NOLINK]​[NOLINK]
                      ​"[", "N", "O", "L", "I", "N", "K", "]" [NOLINK]NOLINK
                      ​"[","ESC", "T", "e", "s", "t", "]" [Test][Test]
                      ​"[", "T", "e", "s", "t", "]" [Test]Test
                      1. Anonymous

                        And my last paragraph vanished (one I had bellow the table).

                        I think I managed to CRASH the editor, meaning it didn't respond to anything at all, I could click save however and the text remained, and as I didn't fill in the "CAPTCHA" I could get out of that situation.

          2. I have to agree with anonymous's skepticism completely.  I almost always use the wiki markup mode, and frequently use it to fix bad RTF-mode formatting.  

            RTF editors for the web, not just Atlassian's, are always full of bugs in my experience.  Using Confluence 3.5, my encounter with RTF bugs is nearly 100% for any day that I use it – which is precisely why I avoid it and use wiki markup.  Who wants to have annoying formatting problems even 50% of the time they edit something?  I am not exaggerating here.

             

             

        2. Anonymous

          Row highlighting seems to not be preserved on copy.

          https://jira.atlassian.com/browse/CONF-23918

        3. Anonymous

          Another thing (yes yet another sigh)

          One of my co-workers have experienced that the editor will "discard" bullets sometimes in a multilevel bullet list on save. Causing Loss of data...

          He experienced this after some other buggy behavior with bullets where he created a sub level, and then the last of those he wanted to push a level up, thes caused the bullet in the sub-level just above to "merge" with the top bullet.

          Step one
          • Level 1 (Node 1)
            • Level 2 (Node 2)
          • Level 1 (Node 3)

          Add a level 2 node, this node was meant to be a level one (Node 4)

          Step two
          • Level 1 (Node 1)
            • Level 2 (Node 2)
            • Level 2 (Node 4)
          • Level 1 (Node 3)

          Un-indent that node (Node 4), caused a behavior that gave the following result.

          Step three
          • Level 1 (Node 1)Level 2 (Node 2)
          • Level 2 (Node 4)
          • Level 1 (Node 3)

          (That is what happened) I could not reproduce. But knowing how many oddities I have seen by now already, I trust him...

          Next thing was that some of the nodes vanished on save.

          I have not created a bug on this as I could not reproduce, if others can it would be great to know how and a link to the bug with detailed steps...

          He used the latest version of IE (I use Chrome)

    3. Anonymous

      This is my main concern with the removal of the Wiki Markup Editor as well.  I author long technical documents that usually take me a day or two to write.  I write the entire thing in a text editor offline, then copy-and-paste into the Wiki Markup Editor to finalize the formatting.  In the version we are testing internally (4.1.10) this has been replaced with the "Open in source editor" button in the editor window.  This works for me!

      -- Trevor

  7. Anonymous

    I must agree with Mr. Chris Johnson above. The RTF editor (v. 3.1 ->) is completely full of bugs. Once a developer has entered the Wiki Markup (which I strongly prefer), the RTF editor makes changes (adding "/" in places it does not belong) and changes the formatting once saved. I am very disappointed that Atlassian has decided to deprecate the Wiki Markup. This will force my companies developers to investigate alternative software packages or be stuck at v3.5. I can understand that the everyday user may not want to invest the necessary time to learn the Wiki Markup; however, the developers should not have to pay that price.

    I am very disappointed and very unhappy about this senseless decision. Please rethink this. We are LOSING capability, not gaining.

  8. Having used the new RTF editor now, I can unequivocally say that it is full of bugs.  I became so frustrated with its unpredictable behavior and reformatting of things I had not selected or deleted, especially trying to use "section" and "column", that I went back to the tried and true method of deleting everything in the RTF editor and then inserting Wiki Markup that I edit in a separate text editor (Notepad++).  This gives me what I want to see, how I want to see it, and gives me a text-based backup on my computer should the server ever lose everything.

    This RTF editor attempt was much better than before, but is still woefully inadequate and buggy, so much so that I am not going to use it except for very simple things.

    1. Gary – can I ask what browser (inc. version) you are using? We'd really appreciate it if you could file any bugs you find at jira.atlassian.com so we can fix them.

      especially trying to use "section" and "column"

      We're currently working on a page layout solution that we plan to ship in Confluence 4.1.

      1. Anonymous

        Unfortunetly there are so many small bugs (which is merely extremely annoying) that reporting them all seems to exhausting to care, especially when the bugs seems to get no attention at all.

        The new editor makes me tired, to tired to even try and help improving it by caring to rapport all those small things. Sorry...

        1. especially when the bugs seems to get no attention at all

          It's a shame you think this is the case. We've already pushed out four bug-fix releases for Confluence 4.0 and our next major release, scheduled for later this year – 4.1 – will include many fixes to editor reliability issues. We are listening and we are committed to fixing bugs that have been reported.

          1. What bugs? You can still use wiki markup using the markup macro. I understand their reasoning for this. Users were corrupting content by switching between user markup edits and the rich text editor. It's also a ton simpler to store in XML and not have that conversion take place for markup every request. 

  9. Is the UWC (Universal Wiki Converter) still available for Confluence 4.0?

  10. Just an additional note here. My JNDI configuation didn't work after the install. I had to copy the activation and mail jars from the webinf/lib directory to the tomcat/lib directory. Can you make the install do this automatically?

    1. Hi Jason,

      Thanks for the feedback, it is definitely a good idea to distribute those files already in the right place. We will track this improvement under https://jira.atlassian.com/browse/CONF-23640 .

  11. Anonymous

    A new RTF editor is great idea, but I don't see why you felt it necessary to remove the wiki markup editor.

    Please, please put it back, even if it's alongside the new editor.  For now, unfortunately, we're going to have to stick with 3.5.  For the most part users here will produce their documents using a WYSIWYG editor to handle the heavy lifting, and then drop to the wiki markup to fix various formatting issues.  Whilst you're acknowledging there are bugs in the new editor, being without a way to do stuff in wiki markup means we're left with no way to at least correct pages we're having problems with without waiting for you to release a patch to the editors behaviour.

  12. I can't believe Atlassian #&%$! removed the Link Icon setting and capability and did not mention it in the release notes.  Instead, it was just quietly removed from the documentation pages by the hapless documentation team.

    And by the way, it was a useful and important feature.  (thumbs down)

  13. Anonymous

    Removal of the wiki markup editor is really a big bummer. I have been using it for years and can not imagine to ever fully switch to a WYSIWYG editor (same reasons as everybody else mentioned). This is to me a blocker bug for upgrading to 4.x!

    Working with Atlassian tools has been a breeze in the last years, and I like pretty much everything what you guys do. But this really turns it around 180 degrees.

    Please consider bringing back wiki markup!

     

    Lutz Birkhahn

    1. Two things Atlassian has done that have mostly alleviated my concerns about the RTF editor, although it is still a pain to use when using bulleted or numbered lists.

      1. You can insert wiki markup by selecting "Wiki Markup" from the "Insert" drop-down list, although I find I almost never do this anymore due to the next item.
      2. You can now directly edit the HTML markup from the wiki page you are editing in the RTF editor by clicking on the "<>" button in the upper-right corner.  Since I know HTML, I can create information (sometimes) faster with (nearly always) less markup than the RTF editor creates and, an added bonus, I can fix the screwups the RTF editor causes to bulleted or numbered lists by modifying the incorrect HTML markup, applying it to the page, and then resuming my editing using the RTF editor.  And I can copy-and-paste the HTML markup and save it in a file as an independent secondary backup separate from what my IT group performs.
  14. Anonymous

    Is it possible to bring back the Wiki Markup Editor?

    I am aware of Insert | Wiki Markup option, and other workarounds for other issues, such as using shift-enter to get br tag (old default) rather than p tag (new default). I strongly prefer to use the Wiki Markup Editor.

    Thank you!

    Timur Shtatland

    Life Technologies

    1. Hallo Timur

      Thank you for your feedback. The Confluence product managers are holding an ongoing conversation about the new editor and the old wiki markup editor, on this page: Confluence 4 Editor - Customer Feedback. They've collated and responded to many of the reasons why people are missing wiki markup. There's also a message from the Atlassian founders, explaining why wiki markup isn't coming back.

      If you'd like to add a comment to the customer feedback page, the product managers will see it and respond. I hope this answers your question. (smile)

      Cheers, Sarah

       

  15. Anonymous

    So our IT just upgraded our Confluence to 4.0. Overnight, our knowledge sharing went from usable, flexible, reliable and fast to easy to use, simplistic, new-user-friendly, slow, unpredictable and cumbersome. Overnight, I went from loving Confluence to hating its guts - especially as I know how very, very powerful it used to be.

    Power users are not happy, but I do suppose it makes sense to improve the system for 80% of the users, even if it means a dramatic efficiency loss for the 20%.

  16. Anonymous

    Confluence 4 and beyond is not usable without the Wiki Markup Editor.

    Probably the biggest mistake your team ever made was removing the wme!