Blog

Ah yes... WYSIWYG editors (or as I prefer to more accurately call them, "rich text editors"). As you can see, I'm not their biggest fan. There are lots of reasons why they're troublesome, but I'll save that for another post. I wanted to quickly share a problem we came up against yesterday with a site we're about to launch, and its solution.

Building a membership site in Drupal isn't so hard, really. The challenge is to have memberships that include recurring fees. That is, a membership that automatically renews, and the member pays automatically. There are several reasons why this is hard. Some reasons include the payment processor - not all payment processors support recurring fees. But mostly, it's the tools we have available that are limiting in their options. But it is possible, though difficult, and fraught with peril.

When I first heard the news that there was a Drupal fork, I was pretty surprised and doubtful. Then I heard who started the fork (Nate Haug and Jen Lampton, really respected Drupalers), and I got a lot more interested, really fast. I've been playing with Backdrop now for a couple of weeks, and have even contributed some pull requests. It's helped me understand better the rationale behind the fork, and helped me think about what might happen moving forward.

We haven't posted in way too long because we've been busy building some cool new sites, including this responsive beauty: http://jewishsocialjustice.org. And then Michelle and I went to DrupalCon Portland.

If you haven't heard, Twitter RSS is officially dead on March 5, 2013 (here it is in Twitter-corporate-speak; Mashable translation). If you're using Aggregator to pull a Twitter RSS feed into your Drupal site for pretty stylin', then you have to act now.