The fate of wiki in confluence

[andrey dmitriev]

Is wiki dead?

We attempted to upgrade our confluence from 3.5.16 to 4.x and the majority of our customizations broke to the point that we abandoned the upgrade and hoped Atlassian would come to its senses.

We rely heavility on Run, Aql, CustomWare plugins (Reporting, Scaffolding), "create page from a template", "edit-include" to display dynamic content from multiple datasources (in confluence and outside), and edit that code in wiki mode, and the disappearance of editing wiki directly was a big surprise (too bad Atlassian ignored my plea in their survey to not taking ability to remain being power users).

So while my question may read like a rant, it remains a question. Has atlassian made it any easier to work with power plugins?

Thanks,

[Daniel Borcherding · Accepted solution]

Hello,

We have the following blog post that details Atlassian's choice to move from wiki markup to xhtml based storage.

http://blogs.atlassian.com/2011/11/why-we-removed-wiki-markup-editor-in-confluence-4/

You can still insert wikimarkup from the Insert >Wikimarkup menu in the new Rich Text Editor. We understand that this change is less than favorable among companies that use wiki markup extensively. As the blog points out it was a business decision to make out product easier to use to a wide range of customers.

We did introduce the Source Editor plugin for users that need a high degree of control over their content.

All of the plugins you mention have a 4.x cognate available in our marketplace. I am not quite sure what the AQL plugin is but there are a number of plugins available there that may fill you need.

Please let us know if this covers you need. I am happy to try to work though any issues you may have with this process.

[Bob Swift]

Your power users can always continue to use wiki markup in places where it is important using the Wiki Plugin for Confluence