Confluence manual import method: “Filter Streams Converter” Output options

Help / Discuss
1

Continuing the tests on XWiki 15.10 in direction of a large Confluence migration, (using a Debian server) I want to refine the option choices used when hitting the Filter Streams Converter tool.
Maybe you’ll wonder “Why manual”, just saying, for the time being it is what has been working best so far in XWiki previous versions.

Here are the options about which I’d like insights:

06-12-23_11-24-04
06-12-23_11-24-041692×559 47.2 KB

Up to now I have been using the first you can see in the selected area of this screenshot, XWiki instance output stream (xwiki+instance). This what I found in the XWiki documentation related to import manually in a Debian server.

The questions wether or not the other options available which I have selected visually in the drop down menu for «Output type» might be a better choice? What does «Output type» really refer to?
Why is it “either / or” when it comes to “+document”/“+extensions”/“+users” ? Wouldn’t we want them all?
Thanks for enlightening me! :blush:

2

The “+” might be a bit misleading in the technical identifier, it’s actually kind of the opposite: the others are more specific output filters (for example only taking into account documents, or users/groups, or extensions) while the first one dynamically call all the registered instance output filters (any extension could inject support for custom metadata coming from an input filter which is currently ignored by the standard output filters).

3

@tmortagne Thank you for your answer.

(any extension could inject support for custom metadata coming from an input filter which is currently ignored by the standard output filters).

What is it you name the standard output filters? Is it XWiki instance output stream (xwiki+instance) or the first choice in the drop down menu maybe?

While I’m here, I noticed a typo at the end of the page :

 Preserve version Indicate if the versions related informations comming from the events should be kept boolean

I think there should be only one m in coming?

4

All the ones you listed are, I talked about standard output filters. The first one is simply the main one, dynamically gathering all the others (part of XWiki Standard, which provide 3, or coming from some extension).

Indeed, @rjakse might be interested in this since he is currently working on some refactoring related to this exact property :wink:

1 Like
5

I think there should be only one m in coming?

Actually, we fixed this last week :slight_smile: Misc: Fix typo comming -> coming by raphj · Pull Request #2670 · xwiki/xwiki-platform · GitHub

Thanks Thomas for the ping.

1 Like
6

@rjakse I just found one more in the Filter Streams Converter:

The list of base URLs leading to the Confluence instance. They are used to convert wrongly entered absoulte URLs into wiki links. The first URL in the list will be used to compute page URLs used in the conversion report if the the 'Store Confluence details' property is used

absoulte => absolute

Best regards,
Joyce

7

Good catch, this will be fixed in a later release :slight_smile:

See [Misc] Fix typos · xwiki-contrib/confluence@bdbff9a · GitHub

1 Like