To continue the thoughts presented in the previous post related to the error
on importing from xwiki 2.7. I forgot to mention that the file size78 MB. I
was wondering if it's too big. As a side note, I should mention that I
imported a small xwiki2.7 site, and I did not get any errors.
So I was looking for other ways that I could import the big file into a
brand new db. I’ll present the steps and let's see what do you think about
it.
1. Export xwiki2.7 from
http://localhost/phppgadmin/ into a file called
dump.sql. So this is like the backup for the xwiki2.7.
2. On the same site
http://localhost/phppgadmin/ I created a new db, totally
blank.
3. The site for the xwiki3.0 is totally empty. So the next step is Import
xwiki-3.0.xar (the download of 3.0 from their site). Note: you can import
even if you don’t have a login.
4. Logged in as admin and got fully functional xwiki 3.0 environment. So far
so good.
5. Then, now is the time to import the xwiki2.7. Since the import
functionality does not work from the xwiki, I tried to do it from the
command line.
6. So at the command line, navigate to the folder where dump.sql is, and
execute the command psql -d database -U user < dump.sql. What this does, it
imports everything from the xwiki2.7 to the new db. Checked the xwiki3.0 and
all the pages are there.
So the problem I have is that a database import is not the same thing as
exporting and importing from the wiki environment, because you simply
recreate the 2.7 database. This is no different than making a copy of the
database. The sql backup just creates sql commands to create the exact same
database…. Is this right?
Also, need to mention that even if I imported the dump.sql, it did not
change the version number. And it shouldn’t have happened right, because the
xwiki environment doesn’t change, right? Only the database is changed.
Suggestions? Anyone? :)
Thanks a bunch.
Alina.
--
View this message in context:
http://xwiki.475771.n2.nabble.com/Import-pages-from-xwiki-2-7-to-3-0-tp6316…
Sent from the XWiki- Users mailing list archive at
Nabble.com.