[xwiki-users] Determining Optimal Migration Path
We want to go from version 2.0.2 of XWiki Enterprise to the latest version. We found going straight from 2.0.2 to 2.7.1 messed up our formatting very badly. We see that we probably need to go through a migration step-by-step, version-by-version. But, do we need to go through every single point/maintenance release (e.g., 2.0.3, 2.0.4, etc.) which is 20-something releases, or just each minor (e.g., 2.1, 2.1, 2.3, etc.) release? Is there even a shorter migration path with fewer interim versions, hitting just the ones that make major changes (e.g., database schema and data changes, etc.)? And is there a way for me to determine that optimal migration path for myself as I get behind in versions? We love the product, but we want to just use it, not care and feed it too often, and keep it updated it when we find time to upgrade. Thanks, Jack Piccininni University of Illinois at Chicago
Try http://extensions.xwiki.org/xwiki/bin/view/Extension/Large+Wiki+Export Large Wiki Export and http://extensions.xwiki.org/xwiki/bin/view/Extension/Large+XAR+Import Large XAR Import But Test it before you go over to the new system. Volker -- View this message in context: http://xwiki.475771.n2.nabble.com/Determining-Optimal-Migration-Path-tp62081... Sent from the XWiki- Users mailing list archive at Nabble.com.
In XE 3.0 M1 we upgraded to Velocity 1.7 and this may cause some problems. Read http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterprise... Thanks, Caty On Fri, Mar 25, 2011 at 17:42, Jack Piccininni <[email protected]> wrote:
We want to go from version 2.0.2 of XWiki Enterprise to the latest version. We found going straight from 2.0.2 to 2.7.1 messed up our formatting very badly. We see that we probably need to go through a migration step-by-step, version-by-version. But, do we need to go through every single point/maintenance release (e.g., 2.0.3, 2.0.4, etc.) which is 20-something releases, or just each minor (e.g., 2.1, 2.1, 2.3, etc.) release?
Is there even a shorter migration path with fewer interim versions, hitting just the ones that make major changes (e.g., database schema and data changes, etc.)? And is there a way for me to determine that optimal migration path for myself as I get behind in versions?
We love the product, but we want to just use it, not care and feed it too often, and keep it updated it when we find time to upgrade.
Thanks,
Jack Piccininni University of Illinois at Chicago _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Volker, Thanks for this advice. It worked for the main content import, but we got a bad side-effect (the one that we found so far): the search page results are polluted with HTML markup, and without clickable links, making search unusable. Any ideas on what we should try to do? Is it generally advised that we upgrade to new versions? It seems pretty hard to do with the methods we've tried so far. Maybe some upgrade/migration paths are not workable(?). It's a shame because we have invested a lot of time using this product, populating it with massive content, but we may have to live with it in version 2.0.2 for as long as we use it. This is a bit frustrating. It would really be nice if there were resources to find the shortest workable migration path from version A to version B that will successfully migrate the database schema and its data without scrambling the content or rendering some functional aspect unusable. Thanks, Jack -- View this message in context: http://xwiki.475771.n2.nabble.com/Determining-Optimal-Migration-Path-tp62081... Sent from the XWiki- Users mailing list archive at Nabble.com.
I am doing the same job right now. So far: In the old wiki: Large Wiki Export by space export: only spaces with your content. Pages with umlauts in page URL "ÖÄÜöäüØÆÅ" or interpunctation ".;:'*=?" are getting messy. Some of the pages are in right "%C3%C8" format these pages are ok. I don't know why this problem is getting to my system. On new Wiki: Install a plain new Wiki! Large XAR Import with parameter "do not overwrite" (first point): You will get a new plain wiki and with your content. On the new system Backup with MySqlDumper. It works with 500mb files on my minimal Windows Xp. My development system: On a Ubuntu laptop with VirtualBox: Win XP without anything to simulate the environment on my work. on C: (it will not work a network disk!!!!) Mowesportable http://www.chsoftware.net/de/mowes/mowesportable/mowes.htm with apache2 php5 mysql and MySqlDumper. (MySqlDumper extra instalation) java xwiki Yes 2 server! Xwiki on port 8888 and apache2 for Mysql and MySqldumper on 8080 Volker -- View this message in context: http://xwiki.475771.n2.nabble.com/Determining-Optimal-Migration-Path-tp62081... Sent from the XWiki- Users mailing list archive at Nabble.com.
participants (4)
-
applejacko -
Ecaterina Moraru (Valica) -
Jack Piccininni
-
Legeinfo