Skip to main content

Really Getting into Drupal 7 .. upgrade from Drupal 5

Drupal 7 came out in January of this year, but I've only been dipping my toes before now. I ordered the new version of Pro Drupal Development and scanned for the interesting bits, and have created four new relatively simple D7 sites so far, even including some quick themeing.

But as of yesterday, I've finally started to climb the D7 learning curve, with a long delayed project to upgrade The Big Guide to Living and Working Overseas.

Working Overseas is my longest running project - I started it with a custom CMS while working at a previous employer. After leaving to work on my own (that's another story) and turning entirely to Drupal, Jean-Marc found me and I've been working with him ever since. Early on, I insisted he let me convert the site to Drupal and though he wasn't convinced at the time, he's been continually delighted ever since. He appreciates all of Drupal's many fine qualities and particularly its flexibility for all the custom stuff he wants, but even more - using Drupal is a sales bonus for him since he sells to universities and they all use Drupal.

So his site has now been ticking along since October 2007 in Drupal 5, undergoing a new theme in 2009, and continual new features implemented with a grab-bag of contributed and custom modules. In other words, a perfect nightmare for an upgrade.

But being optimistic and hopeful like Jack Layton, I brashly suggested we skip D6 and upgrade straight to D7. My thinking was that about half the process of an upgrade is the fiddly bits that you have to chase down manually, so it would only be 50% more work to upgrade to D7 than D6, roughly. Ha ha, you're thinking....

But there's more -- I also put him in contact with Thomas Cheng who I'd worked with as a designer, and he was convinced to simplify a bunch of his site and features, and even to do a redesign. So the D7 upgrade is a good idea because it provides all kinds of front end goodness like useability and accessibility bits and HTML5 support and better themeing tools. And since I don't have to upgrade all the customizations, it's not so bad, I'm thinking.

So, how does the story end? Stay tuned.

Popular posts from this blog

drupal, engagement, mailing lists, email

I lived, worked and studied in Costa Rica from 1984 to 1989. Ostensibly, I was there to study Mathematics at the University, and indeed I graduated with an MSc. in Mathematics supervised by Ricardo Estrada (check that page, he even advertises me as one of his past students). And yes, I do have a nine page thesis that I wrote and defended in Spanish somewhere in my files, on a proof and extension of one of Ramanujan's theories. But mathematics is a pretty lonely endeavour, and what drew me back to Central America (after the first visit, which was more of an accident), was the life and politics. The time I lived there was extremely interesting (for me as an outsider, though also painful and tragic for it's inhabitants) because of the various wars that were largely fuelled by US regional hegemonic interests (of the usual corporate suspects and individuals) and neglect (of the politicians and public) - the Contra war in Nicaragua, the full-scale guerrilla wars in El Salvador and...

IATS and CiviCRM

Update, Nov 2009: I've just discovered and fixed a bug I introduced in the 2.2 branch for the IATS plugin. The bug was introduced when i updated the API files from IATS and failed to notice that the legacy method for C$ one-time donations was no longer supported. If you're using a version greater than or equal to 2.2.7, and are using IATS for C$, non-recurring donations, then you're affected . To fix it edit the file : CRM/Core/Payment/IATS.php, and remove the line that looks like this: $canDollar = ($params['currencyID'] == 'CAD'); //define currency type The full fix removes a conditional branch based on that value a little further on, but by removing this line, it'll never actually use that branch. Drop me a line if you have any questions. Update, May 2009: This post is still getting quite a bit of traffic, which is great. Here are a few important things to note: The IATS plugin code is in CiviCRM, you don't need to add any code. Y...

CentOS4 and CiviCRM 2.1

With the new year, a new resolution to upgrade some sites to the new CiviCRM 2.1. CiviCRM 2.1 is particularly special because it requires Drupal 6 and it's the first version that supports Drupal 6. So upgrades of existing Drupal 5 sites are difficult, particularly if any custom modules or themes involved. As it turned out, my procrastination was justified. I asked my friend Rob Ellis to help with Maquila Solidarity Network , who I've been working with for a few months , and who decided that the new features in 2.1 were too good to postpone any longer. Rob did the upgrade and discovered two issues on my CentOS 4 server: The CiviCRM installer insists on PHP 5.2.x CiviCRM requires a version of PCRE with unicode None of this sounds very interesting, and I wouldn't post about it, except that I would have thought it wouldn't be as hard to fix as it was. So here's what I did, in case there's someone else out there with CentOS4 (or RHEL4) trying to run CiviCRM 2.1...