Does UWC work with Confluence 4?
Asked by Todd Palmer:

Trying to import a MoinMoin wiki into Confluence 4 and it looks like it hasn't been updated to support Confluence 4? I get the following exception. Importing an existing wiki is a critical feature to evaluation and adoption, so any help would be appreciated.

```
org.apache.xmlrpc.XmlRpcException: java.lang.Exception: com.atlassian.confluence.rpc.RemoteException: Unsupported operation: Wiki formatted content can no longer be retrieved from this API. Please use the version 2 API. The version 2 WSDL is available at: http://localhost:9090/rpc/soap-axis/confluenceservice-v2?wsdl. XML-RPC requests should prefixed with "confluence2.". Please use getPageSummary() to get page data without its content.        at org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:104)        at org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:71)        at org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)        at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)        at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)        at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)        at biz.artemis.confluence.xmlrpcwrapper.RemoteWikiBroker.populatePageXmlRpcData(RemoteWikiBroker.java:208)        at biz.artemis.confluence.xmlrpcwrapper.RemoteWikiBroker.storeNewOrUpdatePage(RemoteWikiBroker.java:260)        at com.atlassian.uwc.ui.ConverterEngine.sendPage(ConverterEngine.java:1742)        at com.atlassian.uwc.ui.ConverterEngine.sendPage(ConverterEngine.java:1859)        at com.atlassian.uwc.ui.ConverterEngine.sendPage(ConverterEngine.java:1621)        at com.atlassian.uwc.ui.ConverterEngine.writeHierarchy(ConverterEngine.java:1537)        at com.atlassian.uwc.ui.ConverterEngine.writeHierarchy(ConverterEngine.java:1485)        at com.atlassian.uwc.ui.ConverterEngine.convert(ConverterEngine.java:412)        at com.atlassian.uwc.ui.ConverterEngine.convert(ConverterEngine.java:210)        at com.atlassian.uwc.ui.UWCGuiModel.convert(UWCGuiModel.java:180)        at com.atlassian.uwc.ui.listeners.ConvertListener$Worker.construct(ConvertListener.java:277)        at com.atlassian.uwc.ui.SwingWorker$2.run(SwingWorker.java:110)        at java.lang.Thread.run(Unknown Source)
```


Answers:
author: Laura Kolker
body: Yes and no.

Short story: Some of the work needed to get the UWC working with Confluence 4 has been completed, but not released, so if you're willing to [build from source](https://studio.plugins.atlassian.com/wiki/display/UWC/UWC+Developer+Documentation#UWCDeveloperDocumentation-BuildInstructions), then you can get those changes right now. (Works more or less, except the comments get munged.)

Otherwise, you'll have to wait til the [next release](https://studio.plugins.atlassian.com/wiki/display/UWC/UWC+Updates) of the UWC. (Or do your migration to a staging Conf 3, and use Confluence's upgrade processes to upgrade the data to Conf 4)

comments: author: Todd Palmer
body: OK got the development build, but unfortunately now I get a different problem. I've exported the old wiki, but when I got to import it all I get are a bunch of errors that say:

011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: FrontPage/SalesAndMarketing/1 - SKIPPING  
011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: FrontPage/1 - SKIPPING  
011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: FrontPage/SalesAndMarketing/Sending/null/1 - SKIPPING  
011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: FrontPage/SalesAndMarketing/Sending/1 - SKIPPING  
011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: FrontPage/SalesAndMarketing/1 - SKIPPING  
011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: FrontPage/1 - SKIPPING  
011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: FrontPage/SalesAndMarketing/null/1 - SKIPPING  
011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: FrontPage/SalesAndMarketing/1 - SKIPPING  
011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: FrontPage/1 - SKIPPING  
011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: FrontPage/null/1 - SKIPPING  
011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: FrontPage/1 - SKIPPING  
011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: GuestGroup/null/1 - SKIPPING  
011-09-27 14:26:20,386 ERROR \[Thread-10\] - .... unexpected name: GuestGroup/1 - SKIPPING  
011-09-27 14:26:20,386 INFO \[Thread-10\] - Uploading Pages to Confluence...  
011-09-27 14:26:20,386 INFO \[Thread-10\] - Page 'Home' does not exist. Creating it now.  
011-09-27 14:26:20,824 INFO \[Thread-10\] - Conversion Complete  
And it skips all the pages . It looks like the revision number is in the page. If I look in the converted pages for one t outputs as skipped (FrontPage/1).

The page FrontPage.txt exists with {orig-title:FrontPage}.

I've tried with content-hierarchy-setname.property true or false with similar results.Any ideas?


author: Laura Kolker
body: Hrm. What happens if you switch off the [page history](https://studio.plugins.atlassian.com/wiki/display/UWC/UWC+Moinmoin+Notes#UWCMoinMoinNotes-history)?


author: Todd Palmer
body: If I turn off history in the exporter and converter I get the same result.

```
2011-09-28 07:00:16,986 ERROR [Thread-12] - .... unexpected name: FrontPage/1 - SKIPPING2011-09-28 07:00:16,986 ERROR [Thread-12] - .... unexpected name: FrontPage/SalesAndMarketing/Images/null/1 - SKIPPING2011-09-28 07:00:16,986 ERROR [Thread-12] - .... unexpected name: FrontPage/SalesAndMarketing/Images/1 - SKIPPING2011-09-28 07:00:16,986 ERROR [Thread-12] - .... unexpected name: FrontPage/SalesAndMarketing/1 - SKIPPING2011-09-28 07:00:16,986 ERROR [Thread-12] - .... unexpected name: FrontPage/1 - SKIPPING2011-09-28 07:00:16,986 ERROR [Thread-12] - .... unexpected name: FrontPage/SalesAndMarketing/Sending/null/1 - SKIPPING2011-09-28 07:00:16,986 ERROR [Thread-12] - .... unexpected name: FrontPage/SalesAndMarketing/Sending/1 - SKIPPING2011-09-28 07:00:16,986 ERROR [Thread-12] - .... unexpected name: FrontPage/SalesAndMarketing/1 - SKIPPING2011-09-28 07:00:16,986 ERROR [Thread-12] - .... unexpected name: FrontPage/1 - SKIPPING2011-09-28 07:00:16,986 ERROR [Thread-12] - .... unexpected name: FrontPage/SalesAndMarketing/null/1 - SKIPPING2011-09-28 07:00:17,002 ERROR [Thread-12] - .... unexpected name: FrontPage/SalesAndMarketing/1 - SKIPPING2011-09-28 07:00:17,002 ERROR [Thread-12] - .... unexpected name: FrontPage/1 - SKIPPING2011-09-28 07:00:17,002 ERROR [Thread-12] - .... unexpected name: FrontPage/null/1 - SKIPPING2011-09-28 07:00:17,002 ERROR [Thread-12] - .... unexpected name: FrontPage/1 - SKIPPING2011-09-28 07:00:17,002 ERROR [Thread-12] - .... unexpected name: GuestGroup/null/1 - SKIPPING2011-09-28 07:00:17,002 ERROR [Thread-12] - .... unexpected name: GuestGroup/1 - SKIPPING2011-09-28 07:00:17,002 INFO  [Thread-12] - Uploading Pages to Confluence...2011-09-28 07:00:17,002 INFO  [Thread-12] - Page 'Home' does not exist. Creating it now.2011-09-28 07:00:17,486 INFO  [Thread-12] - Conversion Complete
```


author: Laura Kolker
body: So the moinmoin converter was user submitted (which simply means it worked great for that user and their organization). Over the years, we've added a few bits and pieces to try to make it cover a few more cases, like hierarchy, but without real data to work off, sometimes these features just don't work. You're probably going to need to get a developer team together to expand on what's there. It's a place to start, but it's clearly not going to handle your dataset as is.

One other thought: If you don't need it, you could try turning off the hierarchy. Just comment out the hierarchy related properties by putting a hash symbol (#) infront of the property defining the hierarchy class.


author: Todd Palmer
body: The documentation really should do a better job of explaining the converters up front. "Supported" should mean just that IMHO.


author: Ellen Feaheny [AppFusions]
body: You do not have to wait for the UWC to be compatible with Conf 4 - you can migrate using the UWC 3.5.x versions - then upgrade. 3.5.X \> 4.X Confluence upgrades are pretty straight-forward.

At least that is today's answer, and definitely to evolve.

Regardless, the UWC is not a silver bullet - it helps you along, but [this checklist](https://www.appfusions.com/display/Dashboard/Wiki+Migration+Checklist)gives an idea of the many content and other areas to think through - for starts. With the help of the UWC, you are already 2 wks ahead on your effort, before you even started!

Beyond, happy to chat with you to understand your project/needs, and explain your options and you can decide from there.

Best,

Ellen  
info@appfusions.com


author: Ellen Feaheny [AppFusions]
body: The UWC update for Confluence 4.2.X is now officially underway ...

Couple dev days into it \>\> Magic eight ball says: prognosis looks positive, for release in Sept.

Will update when released.. in mid/late Sept 2012.


author: David Skreiner
body: a) The above link is outdated. Good documentation for UWC is available here:  
[](https://migrations.atlassian.net/wiki/display/UWC/UWC+Developer+Documentation)<https://migrations.atlassian.net/wiki/display/UWC/UWC+Developer+Documentation>  

b) Appfusion don't seem to reply to emails. Anyone know details, like do they still work on UWC?

c) I found this thread by looking for "unexpected name ... SKIPPING". In our case, the problem was in the (optional) page hierarchy: It tried to link many pages like ABC/DEF, ABC/DEG and ABC/DEH to the ABC page, which did not exist. The workaround was to just create an ABC page so the hierarchy information / node links would work.


author: Ellen Feaheny [AppFusions]
body: |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Updates are posted - have at it! <https://twitter.com/appfusions/status/253905889482903552> Thanks [Laura@appfusions.com](mailto:Laura@appfusions.com) and recent client for their support on this effort! |


author: Laura Kolker
body: [Go to the p.a.c. page](https://plugins.atlassian.com/plugin/details/14575) and expand the Compatibility with Confluence subsection


author: Nuno Dias
body: Hello, is there a compatibility matrix for UWC / Confluence?

I have read various pages of documentation and did not find which version of UWC is compatible with Confluence 4 (version 4.1 to be precise).

Seemed kinda strange since is very commom on plugin pages.


Tags: universal-wiki-converter