Uploading 3.x markup using CLI to 4.x

We're still running Confluence 3.x and are looking into the issues involved in upgrading to 4.x.

We have several pages where other programs create files in wiki-markup on our fileservers. Then, as a scheduled task, CLI will StorePage to update them in the wiki.

Now, I know that 4.x has the new editor, but it supposedly can still read markup.

So what will happen with these pages? Will the formatting be translated so they continue to work, or will we have to revise the formatting in these reports?

Anybody else have experience with this kind of automation? How was your upgrade?

1 answer

1 accepted

Good question! Confluence Command Line Interface defaults to wiki markup for any content that is provided whether it is targeting 3.x or 4.x. When targeting 4.x, it uses Confluence service to automatically convert the wiki markup to native 4.x format. noConvert is a new option that also allows 4.x storage format to be used in the CLI. So, your automation should continue to work provided it is producing valid wiki markup with all macros defined - undefined macros can cause the converter to flag errors preventing a page update.

Thank you. That's WONDERFUL news and will save some work when we upgrade..

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Thursday in Agile

How Scrum works? It starts with training and education

To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?”  That question applies to both implementation and improvements on the Scrum framew...

184 views 3 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you