Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By BridgeBurner-1 on
Hi, all.
I recently migrated my webhosting and I'm in the process of migrating the sites I have hosted to the new one. I download everything involved with a particular domain (html file, sql database, tec.) to my local hard drive. Now, I was hoping just to move the db to the new host and install Drupal 6 RC3. I moved the database successfully, but noticed that installing Drupal 6 cleaned out the story content on the db. While I'm sure there's a way to do this so that story content stays intact, it strikes me that I really would like to start with a fresh db since I'll be redesigning my site and using different modules. So, rather than have a fairly bloated db I was wondering if there's an easy way to migrate just the story content and its relevant fields to the fresh db.
I think I know what record I want (dr_content_type_story?) but I need to know what else I might need to bring along for the ride or how to properly go about it. I'm really looking for minimal information here. I don't care about comments or nodewords or any of that junk--just the actual content. As I said, I was going to totally revamp my site anyway, so I would more than likely end up redoing all that stuff anyway.
Thanks for any help you can provide.
Comments
One other piece of info you
One other piece of info you might need is that I have access to phpMyAdmin to look at the db and change it if needed. I'm sure that makes things much easier for me and I'd prefer to use that to make the necessary changes.
One bump for the Superbowl
One bump for the Superbowl hangover crew.
If there isn't a good solution, then I'm just going to brute-force it. I've saved the html code from the source of the google cached pages for each individual story, so I guess I can just remake those stories and change the authorship date.
I'm pretty sure in
I'm pretty sure in phpmyadmin that you can go to the export tab, select only the tables that you want to export, export those tables as a single file and then on your new web host, import the backup and that should restore on your story content while leaving everything else in your DB fresh.
_______________________________________________________________________________
http://www.hagrin.com - Just my little slice of the Interweb
It can get pretty involved
It can get pretty involved according to what other modules you have enables, such as CCK.
You have to keep in mind all the taxonomy relation tables.
100% agreed and that's why
100% agreed and that's why trying to start with a partially fresh DB is probably a bad idea. I would suggest doing a full DB restore and then managing the modules the right way instead. :)
_______________________________________________________________________________
http://www.hagrin.com - Just my little slice of the Interweb
Ehh...go easy on me, my
Ehh...go easy on me, my previous Drupal install was the first. If it such an awful idea I'll just brute force it, which sounds a lot more elegant than what I'd probably have to do to update the db with my story content. I suspected a convoluted interconnectedness, which is why I posted this thread.
Apologize Bridge - didn't
Apologize Bridge - didn't mean to come off rude.
Good luck with the migration. You might want to try setting up a test site with your existing data and executing your migration steps and seeing how it turns out with any approach you take.
_______________________________________________________________________________
http://www.hagrin.com - Just my little slice of the Interweb
No hard feelings, thanks. I
No hard feelings, thanks. I do take your point that a careful selection of modules is key. Right now, to be honest, I'm finding it perfectly easy to simply copy-paste my old content. When/if my site becomes more trafficked and I need to update or migrate again (god forbid) I'll probably thank my lucky stars that I kept things in order.