There's a lot wrong with that...
What you should do is restore the database, point a clean 5.1.7 at it, export the space(s) you need to xml and then import them in your 5.1.5 separately.
Thanks for the answer.. I was afraid that was the case
A database restore is out of the question though, so I am a little stuck. Any pointers and/or hacks just to get the data to a point where I can copy-and-paste or export would be appreciated though.
Could I create a clean DB from that SQL and then just reconfigure a Confluence 5.1.x to use it? In theory I could then XML export the content I want and import it into my new Confluence.
That's what a mysqldump file is for - recreating a database.
I'd install a clean Confluence 5.1 hooked up to an empty database to start with, just so that you know it works without data, and you don't have to manually deal with any config. Then stop it, and edit the dbconfig.xml file in the confluence-home directory so that it points to the restored database, and restart it. It would be a good idea to re-index it straight away.
IF it looks healthy at this point, that's a good time to get the xml out of it!
Ok, update on my adventures in Confluence land.
Twiddled the mysql dump to use latin1 in stead of utf-8.
Imported that into a fresh MySQL database instance.
Pointed a new Confluence 5.9.7 at that (yes, I was wrong on the version number initially)
Did a backup with Confluence's own backup tools.
Restored that in a fresh Confluence 5.9.7.
So far so good
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs