WordPress to Drupal: It's Alive (sort of)

It looks like the more involved access control consideration for a Drupal based web site only really arise for sites that will have multiple user roles. Since this site will, at least initially, be a blog, I don't see a need for roles beyond administrator (me), registered users and anonymous users. That is, my new site will be a blog that combines elements from my web site but doesn't attempt to be anything more than a multiple topic blog.

Given this, I decided to migrate the current state of my new Drupal based site to my web server. The Drupal site implementation is way short of what I'm looking for in a final site structure to say nothing of not having any real content. Assuming I don't run across something like a security flaw that impels me to remove this or any of the subsequent development snapshots, the original Drupal site will be accessible here. The most recent implementation will also be available as http://davenjudy.org/davesBlog/.

UPDATE 29 August 2008: What I had hoped to preserve between versions is actually in the database. That means that there isn't an easy way to keep old versions around since I only have one database. I'm keeping the database snapshots and will provide the snapshots if there is any interest at some point in the future.

Expect the "current" site to change from time to time as I add content and functionality. I'm a little less than half way through Building powerful and robust web sites with Drupal 6 so expect things to change as I learn more. The lesson learned this time was that turning off "Clean URLs" before migrating to another server really is a must. On the plus side, I found yet another way to get the browser to display a blank screen.

As always, questions, comments or suggestions are welcome.

Cheers,
Dave