[Phpwiki-talk] migrating my old phpwiki and dealing with php-53 brokenness

[Philip J. H. <ph...@po...>]

I'm trying to migrate my old phpwiki off a hosted provider to my own
vps.  My problem is that my hosting provider foced an upgrade to php-53
and I'm running something like 1.3.14.  I hacked on my wiki a bit
(www.hollenback.net) to get it basically working.  However, I can't do
some key things like dump the wiki through the Administration interface
- it creates a dump but the dump is full of php warnings and errors so
it's not usable.

I did manage to dump out my old mysql database and I've been playing
with using that as the basis for my new wiki (neckbeard.us, running the
1.4.0 svn trunk).  I hacked on my mysql dump until I got it to load into
the new database on the new server.  I'm probably running one of the
oldest phpwikis in existence at this point so my database is filled with
tons of crufty and spam - thus I tried to edit a lot of that out
manually.

I was able to get the database set up, and run and action=upgrade on the
new phpwiki.  Now it appears to be mostly intact.

Unfortunately, I clearly have data inconsistencies.  For example, the
page

http://neckbeard.us/phpwiki/index.php/DenyHostsWentBad

exists if you go to it directly, but you can't edit it - phpwiki thinks
the page doesn't exist.  I think this is because the page exists in the
revision table and the page table, but a reference somewhere else is
incorrect.

Can anyone give me some guidance on how to fix all this?  I suppose I
could try an upgrade to 1.4.0trunk on my old hosting provider and see if
I can get a clean page dump.  Then I could just load that into the new
phpwiki.  However, I'm hesitant to muck with this host as I only have
cpanel access to it so dealing with a major phpwiki upgrade is annoying.
 Plus, I want to get off that provider as soon as possible anyway.

Is there a simple way I can repair my new database so that phpwiki finds
all the pages?  Or, is upgrading to 1.4.0trunk on the old host and
getting a clean page dump my best bet?  

Thanks,
P.
--  
Philip J. Hollenback
www.hollenback.net
@philiph


--  
Philip J. Hollenback
www.hollenback.net
@philiph


--  
Philip J. Hollenback
www.hollenback.net
@philiph