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

Me and varnish win against a DDOS attack.

This past month one of my servers experienced her first DDOS - a distributed denial of service attack. A denial of service attack (or DOS) just means an attempt to shut down an internet-based service by overwhelming it with requests. A simple DOS attack is usually relatively easy to deal with using the standard linux firewall called iptables.  The way iptables works is by filtering the traffic based on the incoming request source (i.e., the IP of the attacking machine). The attacking machine's IP can be added into your custom ip tables 'blacklist' to block all traffic from it, and it's quite scalable so the only thing that can be overwhelmed is your actual internet connection, which is hard to do.

The reason a distributed DOS is harder is because the attack is distributed from multiple machines. I first noticed an increase in my traffic about a day after it had started - it wasn't slowing down my machine, but it did show up as a spike in traffic. I quickly saw that…

Upgrading to Drupal 8 with Varnish, Time to Upgrade your Mental Model as well

I've been using Varnish with my Drupal sites for quite a long while (as a replacement to the Drupal anonymous page cache). I've just started using Drupal 8 and naturally want to use Varnish for those sites as well. If you've been using Varnish with Drupal in the past, you've already wrapped your head around the complexities of front-end anonymous page caching, presumably, and you know that the varnish module was responsible for translating/passing the Drupal page cache-clear requests to Varnish - explicitly from the performance page, but also as a side effect of editing nodes, etc.

But if you've been paying attention to Drupal 8, you'll know that it's much smarter about cache clearing. Rather than relying on explicit calls to clear specific or all cached pages, it uses 'cache tags' which require another layer of abstraction in your brain to understand.

Specifically, the previous mechanism in Drupal 7 and earlier was by design 'conservative' …

Confused by online payment processing? You're not alone.

In the old days during "polite" conversation, it was considered rude to talk about sex, politics, religion and money. You might think we're done with taboos, we're not (and I'll leave Steven Pinker to make the general argument about that, as he does so well in The Better Angels of Our Nature).

The taboo I'm wrestling with is about money - not how much you make, but about online payment processing, how it works, and what it costs. In this case, I think the taboo exists mainly because of the stakes at hand (i.e. lots of money) and the fact that most of those who are involved don't get much out of explaining how it really works - i.e. the more nuanced communications are overwhelmed by sales-driven messaging, and the nuanced stuff is either proprietary secrets or likely to get slapped down by the sales department.

In other words, if you want to really understand about online payment processing because you want to decide between one system and another, you'…