* NEVER MIND (I forgot that I created a new folder on the test server, so I hadn't copied over the templates, etc... don't I feel like a genius!)
We have a test installation identical to the production install. It's on the same server in a different folder.
I'd like to import a blog into my test space, but it doesn't seem to work.
Since they use separate databases I can't see what's blocking me. Can someone advise me, or lead me to some info on this?
Thanks
Full Version: Importing Blog To To New Server
QUOTE (lyonardo @ Feb 28 2008, 01:11 PM) 
We have a test installation identical to the production install. It's on the same server in a different folder.
I'd like to import a blog into my test space, but it doesn't seem to work.
Since they use separate databases I can't see what's blocking me. Can someone advise me, or lead me to some info on this?
Thanks
I'd like to import a blog into my test space, but it doesn't seem to work.
Since they use separate databases I can't see what's blocking me. Can someone advise me, or lead me to some info on this?
Thanks
would be easier to advise if you tell us what you did
Great, thanks.
We started off making a complete copy of the MT installation from (for example) /blogfolder to /testfolder. Also, a separate (PostgreSQL) database.
The directory structure is replicated, so I thought it'd be easy to just import the entries. Nothing.
I thought maybe I'd create a new blog with the same name and settings, then just import the old entries into that. I can make new entries, and the import says it was succesful, but they don't display.
Next I did a backup of the production blog, then tried restoring over the top of my test blog of the same name. Nope.
It's possible now I've mucked up the database for this test blog. No big deal.
How SHOULD I have handled this?
Thanks,
Leo
would be easier to advise if you tell us what you did
We started off making a complete copy of the MT installation from (for example) /blogfolder to /testfolder. Also, a separate (PostgreSQL) database.
The directory structure is replicated, so I thought it'd be easy to just import the entries. Nothing.
I thought maybe I'd create a new blog with the same name and settings, then just import the old entries into that. I can make new entries, and the import says it was succesful, but they don't display.
Next I did a backup of the production blog, then tried restoring over the top of my test blog of the same name. Nope.
It's possible now I've mucked up the database for this test blog. No big deal.
How SHOULD I have handled this?
Thanks,
Leo
QUOTE (imabug @ Feb 28 2008, 10:29 AM)
QUOTE (lyonardo @ Feb 28 2008, 01:11 PM)
We have a test installation identical to the production install. It's on the same server in a different folder.
I'd like to import a blog into my test space, but it doesn't seem to work.
Since they use separate databases I can't see what's blocking me. Can someone advise me, or lead me to some info on this?
Thanks
I'd like to import a blog into my test space, but it doesn't seem to work.
Since they use separate databases I can't see what's blocking me. Can someone advise me, or lead me to some info on this?
Thanks
would be easier to advise if you tell us what you did
QUOTE (lyonardo @ Feb 28 2008, 01:48 PM)
Great, thanks.
We started off making a complete copy of the MT installation from (for example) /blogfolder to /testfolder. Also, a separate (PostgreSQL) database.
The directory structure is replicated, so I thought it'd be easy to just import the entries. Nothing.
I thought maybe I'd create a new blog with the same name and settings, then just import the old entries into that. I can make new entries, and the import says it was succesful, but they don't display.
Next I did a backup of the production blog, then tried restoring over the top of my test blog of the same name. Nope.
It's possible now I've mucked up the database for this test blog. No big deal.
How SHOULD I have handled this?
We started off making a complete copy of the MT installation from (for example) /blogfolder to /testfolder. Also, a separate (PostgreSQL) database.
The directory structure is replicated, so I thought it'd be easy to just import the entries. Nothing.
I thought maybe I'd create a new blog with the same name and settings, then just import the old entries into that. I can make new entries, and the import says it was succesful, but they don't display.
Next I did a backup of the production blog, then tried restoring over the top of my test blog of the same name. Nope.
It's possible now I've mucked up the database for this test blog. No big deal.
How SHOULD I have handled this?
What are you trying to import?
There are a couple of ways of doing this.
Method 1 involves creating an SQL dump of your production blog database and importing it into your test DB. Make sure your test MT installation is configured to point to your test DB. You'll need to change a few things like the publishing paths for your blog, but this should get you an otherwise identical copy of your production blog.
Method 2 involves using MT's import/export (System Overview/Tools) on your production blog to create a file that you will import (via MT import/export) into your test blog.
QUOTE (imabug @ Feb 29 2008, 10:31 AM)
QUOTE (lyonardo @ Feb 28 2008, 01:48 PM)
Great, thanks.
We started off making a complete copy of the MT installation from (for example) /blogfolder to /testfolder. Also, a separate (PostgreSQL) database.
The directory structure is replicated, so I thought it'd be easy to just import the entries. Nothing.
I thought maybe I'd create a new blog with the same name and settings, then just import the old entries into that. I can make new entries, and the import says it was succesful, but they don't display.
Next I did a backup of the production blog, then tried restoring over the top of my test blog of the same name. Nope.
It's possible now I've mucked up the database for this test blog. No big deal.
How SHOULD I have handled this?
We started off making a complete copy of the MT installation from (for example) /blogfolder to /testfolder. Also, a separate (PostgreSQL) database.
The directory structure is replicated, so I thought it'd be easy to just import the entries. Nothing.
I thought maybe I'd create a new blog with the same name and settings, then just import the old entries into that. I can make new entries, and the import says it was succesful, but they don't display.
Next I did a backup of the production blog, then tried restoring over the top of my test blog of the same name. Nope.
It's possible now I've mucked up the database for this test blog. No big deal.
How SHOULD I have handled this?
What are you trying to import?
There are a couple of ways of doing this.
Method 1 involves creating an SQL dump of your production blog database and importing it into your test DB. Make sure your test MT installation is configured to point to your test DB. You'll need to change a few things like the publishing paths for your blog, but this should get you an otherwise identical copy of your production blog.
Method 2 involves using MT's import/export (System Overview/Tools) on your production blog to create a file that you will import (via MT import/export) into your test blog.
Thanks for method 1
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.