[xwiki-users] V7, wikis creation, descriptors and wizard issues.
Hi all, In XWiki prior to V6, when creating a new wiki using the Wiki Manager, we had the choice to provision the wiki or not by choosing "Later" from the wizard. That 'Later' trick was very useful because it was allowing the wiki descriptor to be created (but not only it, see below) without adding content to the wiki. Then, if you wanted to import a wiki (or subwiki) from another xwiki instance to the new instance using a database dump, you just had to drop and recreate the just-created database and import the dump. This is more or less what is explained here http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Backup. Less because there is no notion of sub-wiki in this doc, but we will cover this in another thread. The current one being how to bring a solution to my current issue. So the wizard trick was useful. Now in V7 any new wiki is automatically provisioned, no choice on this. Today we need to import an existing wiki in a older xwiki to a fresh xwiki v7 farm. We could export the older wiki as XAR but for some reason, the admin tool's large export tool (http://extensions.xwiki.org/xwiki/bin/view/Extension/Large+Export+By+Space+A...) locks after writing 1.7GB (vmassol, is this the other one you suggested to use http://extensions.xwiki.org/xwiki/bin/view/Extension/Large+Wiki+Export ? ) Anyway we get used to db level export so we are working through this thread. We spend the whole day to turn around the problem in V7 until we got bored to hell :) 1) if you try to create the descriptor by hand, there is something that prevent it to be listed in the wikimanager. 2) to turn around 1), we've created a 'dummy' wiki using the UI as the usual manner, then exported a XAR of the 'dummy' wiki descriptor document. 3) Restore the XAR with option "as backup" turned on (the last is very important). 4) So now we got a descriptor for our wiki. There is still no corresponding database at this point so we create the database and import the content. 5) now restart xwiki so the database upgrade occurs. Well. 6) Now we indeed run the imported wiki but next we have to upgrade all the documents package but no wizard is triggered ? Why : the issue at this point is there is no folder in the PermDir/jobs/status/distribution/wiki/<wikiname> which sounds logical because we created the descriptor "by hand" throught a XAR import which doesn't include the process of writing initial status.xml files in PermDir/jobs/status/distribution/wiki/<wikiname>/status.xml So indeed we're stuck. How do we run the Document Wizard Upgrade at this point ? Regards, -- Martin
Le 21/04/2015 17:10, [email protected] a écrit :
Why : the issue at this point is there is no folder in the PermDir/jobs/status/distribution/wiki/<wikiname> which sounds logical because we created the descriptor "by hand" throught a XAR import which doesn't include the process of writing initial status.xml files in PermDir/jobs/status/distribution/wiki/<wikiname>/status.xml
So indeed we're stuck. How do we run the Document Wizard Upgrade at this point ?
The other issue was the imported wiki skin definition was overriding the DW URL. Since then we have moved to XWiki 6.4.4 as it is the version supported by XWiki SAS. We did the wizard trick and poped up the DW by typing the URL by hand in the broswer, so it bypass the skin. Anyway, there is still some migration/move/upgrade use cases scenarios to elaborate. I'll start this when I got time. But anyone can start over, maybe you, Denis ? -- Martin
On Thu, Apr 23, 2015 at 1:49 PM, [email protected] <[email protected]> wrote:
Le 21/04/2015 17:10, [email protected] a écrit :
Why : the issue at this point is there is no folder in the PermDir/jobs/status/distribution/wiki/<wikiname> which sounds logical because we created the descriptor "by hand" throught a XAR import which doesn't include the process of writing initial status.xml files in PermDir/jobs/status/distribution/wiki/<wikiname>/status.xml
So indeed we're stuck. How do we run the Document Wizard Upgrade at this point ?
The other issue was the imported wiki skin definition was overriding the DW URL.
Since then we have moved to XWiki 6.4.4 as it is the version supported by XWiki SAS. We did the wizard trick and poped up the DW by typing the URL by hand in the broswer, so it bypass the skin.
I recommend switching temporarily to the default skin before doing an upgrade.
Anyway, there is still some migration/move/upgrade use cases scenarios to elaborate. I'll start this when I got time. But anyone can start over, maybe you, Denis ?
-- Martin _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi Marius/Thomas/Denis/All, I agree that Martin’s use case is valid (we discussed it on IRC a few days ago and Denis confirmed the need that he’s seen). Here’s the need: - You have farm 1 on XWiki version N with several users/customers on it each with a subwiki - You want to upgrade some of them to a more recent version of XWiki - You install farm 2 with XWiki version P (where P > N) - Thus the need is: how to move subwiki S from farm 1 to farm 2 I think we need to recommend some solution for this typical use case and document it at http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Upgrade. This page currently doesn’t mention anything about a farm/subwikis. Do we have some official recommendation on this (best practice)? Do we know how to support this use case? If not, is there something we can do make this use case simpler to achieve? Thanks -Vincent On 24 Apr 2015 at 07:48:33, Marius Dumitru Florea ([email protected](mailto:[email protected])) wrote:
On Thu, Apr 23, 2015 at 1:49 PM, [email protected] wrote:
Le 21/04/2015 17:10, [email protected] a écrit :
Why : the issue at this point is there is no folder in the PermDir/jobs/status/distribution/wiki/ which sounds logical because we created the descriptor "by hand" throught a XAR import which doesn't include the process of writing initial status.xml files in PermDir/jobs/status/distribution/wiki//status.xml
So indeed we're stuck. How do we run the Document Wizard Upgrade at this point ?
The other issue was the imported wiki skin definition was overriding the DW URL.
Since then we have moved to XWiki 6.4.4 as it is the version supported by XWiki SAS. We did the wizard trick and poped up the DW by typing the URL by hand in the broswer, so it bypass the skin.
I recommend switching temporarily to the default skin before doing an upgrade.
Anyway, there is still some migration/move/upgrade use cases scenarios to elaborate. I'll start this when I got time. But anyone can start over, maybe you, Denis ?
-- Martin
participants (3)
-
Marius Dumitru Florea -
mh＠ow2.org -
vincent＠massol.net