phpwiki-talk

[Phpwiki-talk] Restoring a ZipDump backup

[Frank S. <fra...@rn...>]

Hi all,

I currently use gdbm as my phpwiki backend, but for various reasons I want
to change that to a mySQL backend. So what I thought of doing was taking a
ZipDump of the entire wiki, changing the backend (setting up the database
schema, changing the entry script, blah blah) and use the loadfile action on
the new (empty) wiki to restore the wiki to its original state.

Currently this just doesn't work. Well, not as I expected, at any rate. The
first revision is saved as version one, and subsequent revisions have to be
merged by hand.

What I want is for the wiki to be restored in such a way that the users (who
are intimately familiar with details like what the current revision of
ArbitraryPage is, and what its major and minor edits are, etc) never even
notice the difference.

I can't see anywhere in phpwiki to do this. Is there? Failing that, if I
wanted to hack this up, where would I start?

My first thought was that, since I'm moving the pages to mySQL, I should
just write something that processes each (RFC822 encoded) page and applies
the appropriate SQL to the database. But this doesn't solve the general
problem of how to move one's backend to something arbitrary - what if one
wanted to move from a mySQL backend to a CVS backend, for instance? Or
flatfile to PostgreSQL?

frank

[Phpwiki-talk] Restoring a ZipDump backup

[Leiss, Klaus-G. 3. S-IS-RD-E. <Kla...@he...>]

Hello Frank,
I saved your message to the list, here are the parts
that you wrote.


> From: Frank Shearar [mailto:fra...@rn...]
> Sent: Wednesday, July 09, 2003 5:36 PM
> To: php...@li...
> Subject: RE: [Phpwiki-talk] Restoring a ZipDump backup

<snip>

=20
> Well, I hacked something together by chopping in lib/loadsave.php and
> lib/WikIDB.php.
>=20
> In summary, I commented out most of SavePage (all the bits=20
> with checking to
> see if we want to merge or overwrite pages) and just save the=20
> revisions as
> they come out the RFC822 files. Then in WikiWD.php I cut out=20
> the sanity
> checking of revision numbers and overwrite existing=20
> revisions. This is, of
> course, directly counter to the philosophy that old revisions=20
> are read only,
> but this was a temporary hack and I wanted to exactly restore a wiki.
>=20
> In detail, here are the diffs: (foo.restore is my special=20
> hacked version of
> foo.php, of course)
>=20
> -bash-2.05b$ diff loadsave.php loadsave.php.restore
> 376a377,380
> >     echo $pageinfo['pagename'] . ', ' . $pageinfo['version'];
> >     $page =3D $dbi->getPage($pagename);
> >     $page->save($content, $pageinfo['version'], $versiondata);
> > /*
> 483a488
> > */
>=20
> -bash-2.05b$ diff WikiDB.php WikiDB.php.restore
> 21a22
> > define('WIKIDB_RESTORE', 1);
> 615,621c616,628
> <         $latestversion =3D $backend->get_latest_version($pagename);
> <         $newversion =3D $latestversion + 1;
> <         assert($newversion >=3D 1);
> <
> <         if ($version !=3D WIKIDB_FORCE_CREATE && $version !=3D =
$newversion) {
> <             $backend->unlock();
> <             return false;
> ---
> >       if (WIKIDB_RESTORE) {
> >             $latestversion =3D 0;
> >             $newversion =3D $version;
> >         } else {
> >
> >             $latestversion =3D =
$backend->get_latest_version($pagename);
> >             $newversion =3D $latestversion + 1;
> >             assert($newversion >=3D 1);
> >
> >             if ($version !=3D WIKIDB_FORCE_CREATE && $version !=3D =
$newversion) {
> >                 $backend->unlock();
> >                 return false;
> >             }
>=20
> Then for each wiki I first created an IdontExist page, made=20
> its content
> "<?plugin WikiForm action=3Dloadfile?>", logged in as admin &=20
> hit the button.
>=20
> It seemed to work OK, although I'm still checking out the=20
> nitty gritties &
> corners of my wikis.
>=20
> frank