Drupal 7

I'm new to Organic Groups (OG). If you are too, then it's a way to relate group content together, e.g. you could have a set of campaigns, and each campaign may have a number of petitions, blog posts, users etc.

Goal: I would like my campaign (i.e. group) pages to list the petitions that are part of that campaign (i.e. group content) in a Block, using Views.

Migrating CiviCRM between servers is quite a PITA. But it's important to have a separate developmnet site, right?

I've created a script that I use to do it. The script, once configured, must be run from the development server end.

Basically, here's what it does

Note: A comment below says that this procedure does not work for upgrading from 3.4 to 4.2. (Thanks Paul!)

The path I took was

1. Migrate my site to a test server
2. Upgrade CiviCRM from 3.4 to 4.1 on the existing Drupal 6 site.
3. Upgrade Drupal from 6 to 7 while simultaneously updating the CiviCRM codebase for Drupal 7

I found lots of pages on CiviCRM's wiki about various upgrades, but apparently one's not been written for the upgrade of D6 to D7. So thought it would be worth sharing this.

Drupal is very themable. There's so many ways to theme content that it can be very confusing to remember/figure out what's responsible for what. And then if the stock theming capabilities aren't enough, once you've installed Omega (and possibly Delta and Context) and Display Suite, they haystack's size increases exponentially.

I keep finding that things that are supposed to make things simpler or easier, actually don't.

I needed to be able to add a new activity record to every contact in my search results.

Here's how I used a CiviCRM hook to add a function to the list of tasks you can perform on a set of search results.

I was really glad to be working to create Easy Green Print with a friendly local company who are the leading light in environmental printing. It ticked a lot of boxes for me:

I have a server with several Drupal websites on it. I want a separate codebase for each so that I can tweak, play on one without affecting the others. I like using Git. This page documents (for my reference as much as for your delight!) my workflow.

Advantages:

In looking for an answer to this question, most posts say something like: Drupal is almost entirely modular, and driven by lots of "hooks" and what code is actually executed when is deep Drupal Voodo. Or they say RTFM. I think the F stands for Fantastic, but it could also be Fragmented. This is my attempt to understand what hooks get called when in the delivery of a simple page (like this one).

Drupal 7 has an amazingly granular templating system that means each bit of the hierarchically structured page data can have its own template. After spending a long time understanding this I set to work on my first task.

I wanted a pull-out quote on some pages that integrates with the main layout - I don't just want it stuck in the main page content area block. This means that when it's used, I want it to interrupt the sidebar's content, to demand the attention that I have decided it deserves.