nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

how much longer will atlassian support 3.x wiki markup

Michael Roff2

Bob Swift has provided a Wiki Markup Plugin which allows 3.x wiki markup to "exist" within a 4.x environement. - https://bobswift.atlassian.net/wiki/display/CWP/Confluence+Wiki+Plugin;jsessionid=DC0FBC42EFF57A72FEF891C1561A606F

In the limitations section of the plugin's documentation page, Bob notes:

Limitations

Only Confluence 3.x wiki style macro is supported. This means that only macros that support 3.x legacy mode can be used inside the wiki macro. At some point in the future Atlassian may withdraw 3.x legacy support.

I would like to use this wiki markup plugin to provide a quick way to migrate my 3.5 Confluance instance to 4.2, however, before I do this, I would like to know what Atlassian's plans are regarding the continued support of 3.x wiki markup.

From my perspective, if there was no further development work from Atlassian to support this, I would be voting for indefinite support (well maybe until the next major disruption in editing styles comes along) but certainly for the life of 4.x I would hope.

Comments Atlassian?

Accepted answers

Joe Clark

As far as I know, we have no plans to remove wiki markup as a programmatic input method for Confluence.

All comments

Michael Roff2

Seriously? No comment?

Even a comment saying ... we don't know would be good.

Joe Clark

As far as I know, we have no plans to remove wiki markup as a programmatic input method for Confluence.

Michael Roff2

Thanks Joseph.

Any chance this question could be posed to "those in the know" within Atlassian like @sherif mansour to see what the thoughts are?

Bob Swift

Discussions at Summit also indicated same as Joseph's comment!

Jobin Kuruvilla [Adaptavist]

Why do you think Joseph is not "those in the know" ? This is something echoed for a long time now. I am sure you will know it first here if something changes!

Graham Hannington

If you're interested in this question, you might also be interested in Wikifier RT (converts Confluence 4.x rich text editor content to wiki markup).

Michael Roff2

Thank you for your thoughts on this subject Graham, I think it adds some valuable questions which would benefit from a detailed response from Atlassian.

Thank you also for your links to the Wikifier RT tool - I haven't used it yet - but it looks like a handy option if you need an alternative to the new C4 editor.

John Graybeal

A hugely valuable conversation here, on top of the valuable plugin.

In a side discussion with Atlassian, I finally grokked the reason, or at least a reason, they have so avoided the wiki support. If there are dueling formats on a site, full interoperability requires everyone to be able to use both readily. If Atlassian can move everyone to rich-text editing using a single supported editor, it unifies the platform and precludes dissatisfaction with how one editor breaks another.

While I'm not sure they foresaw the fervor with which us technophiles will continue to dissect their editor, I'm sure the vision is a primary editor sufficiently elegant and bug-free to satisfy all users. At that point life gets simpler for Atlassian and (most of) their Confluence users.

From this background, the editor comments page, the above thread, and the existence of the plugin itself, I'm pretty confident they appreciate the value in supporting the wiki text as a legacy format, and we could expect the plugin to stay through v4. Just one view, but I'm willing to stake my team's upgrade on it. Now there's just the matter of those bugs in the RT editor....

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

migration