Comments for scurker.com http://scurker.com Blog & Portfolio of Jason Wilson Fri, 14 May 2010 04:40:34 +0000 http://wordpress.org/?v=2.9.1 hourly 1 Comment on Migration from Drupal 6.x to Wordpress 2.9x by Celsius1414 http://scurker.com/blog/2010/02/migration-from-drupal-6-x-to-wordpress-2-9x/#comment-73 Celsius1414 Fri, 14 May 2010 04:40:34 +0000 http://scurker.com/?p=50#comment-73 Experimenting on transferring a Drupal 6 site into Wordpress 2.9, I ran into some Internal Server 500 Errors after performing the above steps. After a metric crapload of troubleshooting, I finally figured it out -- if any post_date times are out of order, it will cause an error to happen. For example: ID post_date 2 2006-03-16 12:07:27 3 2006-03-16 17:11:07 4 2005-06-22 22:31:31 5 2006-03-16 18:12:09 A 500 error happens in this case because post #4 is out of chronological order with the rest of the posts. You can confirm/fix this by either deleting #4 or changing its post_date to fit into that slot. Since I have nearly 2,000 posts in my database, I am going to have to figure out an automated way to fix the problem. My guess is that I'll just need to sort the table by post_date, then auto-replace the IDs in the new order. (This probably would not work for maintaining the URLs of Drupal sites with the node numbers attached -- not without some fancy Apache footwork -- but I have custom URLs so that's not an issue for me.) Anyhow, an esoteric issue, but I thought I'd post it here just in case somebody else ran into it. :) Experimenting on transferring a Drupal 6 site into Wordpress 2.9, I ran into some Internal Server 500 Errors after performing the above steps.

After a metric crapload of troubleshooting, I finally figured it out — if any post_date times are out of order, it will cause an error to happen.

For example:

ID post_date
2 2006-03-16 12:07:27
3 2006-03-16 17:11:07
4 2005-06-22 22:31:31
5 2006-03-16 18:12:09

A 500 error happens in this case because post #4 is out of chronological order with the rest of the posts. You can confirm/fix this by either deleting #4 or changing its post_date to fit into that slot.

Since I have nearly 2,000 posts in my database, I am going to have to figure out an automated way to fix the problem. My guess is that I’ll just need to sort the table by post_date, then auto-replace the IDs in the new order.

(This probably would not work for maintaining the URLs of Drupal sites with the node numbers attached — not without some fancy Apache footwork — but I have custom URLs so that’s not an issue for me.)

Anyhow, an esoteric issue, but I thought I’d post it here just in case somebody else ran into it. :)

]]> Comment on Migration from Drupal 6.x to Wordpress 2.9x by Sarah http://scurker.com/blog/2010/02/migration-from-drupal-6-x-to-wordpress-2-9x/#comment-27 Sarah Tue, 13 Apr 2010 01:41:54 +0000 http://scurker.com/?p=50#comment-27 You have absolutely saved my life. I'm working on migrating a client's local news blog from Drupal to WordPress, and was having no luck until I tried your method. I was beginning to think I was going to have to re-post his more than 2,000 articles one by one. You have absolutely saved my life. I’m working on migrating a client’s local news blog from Drupal to WordPress, and was having no luck until I tried your method. I was beginning to think I was going to have to re-post his more than 2,000 articles one by one.

]]> Comment on Migration from Drupal 6.x to Wordpress 2.9x by Nick http://scurker.com/blog/2010/02/migration-from-drupal-6-x-to-wordpress-2-9x/#comment-17 Nick Mon, 29 Mar 2010 22:36:10 +0000 http://scurker.com/?p=50#comment-17 This was so helpful, thank you very much. This was so helpful, thank you very much.

]]>