ToddGee.commie

I'm finally getting around to upgrading sites from Drupal 6 to Drupal 7.  Drupal 8 is coming out soon and, when that happens, Drupal 6 will fall from support.  These are my own notes for how to get the job done, but maybe they'll help others. 

I generated these notes when updating this site.  (It has been reborn as a Drupal-7 site!)  This is not my first D-7 site, but it's the first that I've upgraded from D-6 to D-7...

See the post, written so long ago, on Upgrading Drupal 5 to Drupal 6.  Many of the concepts are the same.

This is the notes for the notes created for the "Introduction to Drupal CMS" class I did as part of the 2013 Learnapalooza event.  Learnapalooza recruits members of the community to teach 1-hour classes and arranges for venues in which those classes can be held. My class was held at the Elastic Arts Center from 2:30p - 3:30p on 9/22/2013 (World Carfree Day!)

When I started this blog post I was in the planning phases for a gallery in Drupal.  I currently have a gallery2 gallery that I've maintained for several years.  I've been thinking for some time that I would like to replace this software for many reasons (which I'll cover in some future post.)  One of my initial thoughts is that I would replace the gallery with some custom software written in Drupal.  Below is some of the brainstorming requirements I created.

Ok.  So I just finished rewriting my Drupal Script Library for the second time.

The first time was the rewrite to use a Git based install rather than using CVS.

This time, I got rid of the SCM checkout meme altogether and switched over to using 'drush dl' to deploy new modules.

I'm always having to look this up on drupal.org, so I thought I'd just put it here once and for all.

(FWIW, you can read about it here: http://drupal.org/node/764100 among other places.)

This post describes the work I have done to create "template sites".  Template sites are Drupal installations created and maintained with initial setup done to speed the creation of a new site.  The template sites can be duplicated onto a new domain and database loaded with a single simple script.

UPDATE: I just rewrote the script library to deploy modules with drush instead of Git.  See my post on the subject.

I am a Java developer and use Eclipse most every day.  However, as you can see on this blog, I do a fair amount of Drupal work and have dabbled in writing Drupal modules.

A few releases of Eclipse ago, I spent quite a bit of time installing the eclipse PDT project on top of my eclipse for Java installation. I remember it taking quite a bit of time to sort things out.

So today I finally got around to installing VirtualBox on my lappy.  I had been using VMWare for many years.  I had bought a license several years ago, upgraded a couple times, and had used VMWare Player after it was made free (as in beer).  Often, however, I found myself having to patch the source for the kernel modules to get them to compile on my Fedora install.

I had often heard good things about VirtualBox so I thought I'd give it a shot.