If you are like me you probably hate wysiwyg edtors. The name What-You-See-Is-What-You-Get implies that when you are editing content you can add styles and that is how it will look once you hit save. But have you ever notice that it almost always doesn't work like that. Not only does it make a mess of your html/css, you end up with something that doesn't look like you created.

According to the usage stats on http://drupal.org the module uc_recurring is now installed on over 1,000 sites (as of the 28th September 2010).

1,125 to be exact!

Git (http://git-scm.com/) is a distributed version control system, replacing other tools like cvs or svn to manage your code history.

The great thing about git is that you don't need a central server to store your repositories you can carry around your repositories on your laptop.

There is a practice I have seen on a few different Drupal sites that causes me some concern. Its using cck field to store logic information.

Examples are:
* select fields for displaying the content somewhere on the site.
* weights for ordering content

What are the issues with this practice:
There are a couple of problems I see with doing this. The first is just the confusing between what is actual content (your data in the fields) and what should be programming logic in your application.

Univate has recently been involved in a video project. We were impressed with the Kaltura (www.kaltura.org) tools for managing, hosting and streaming video content and were also keen to use it has it had an existing drupal module ready to go. Being that it promotes itself as an open source project that is always a plus.

Unfortunately what it came time to develop the features for the specific site the drupal module did not live up to its promises and required a massive cleanup.

As a development company, we are often asked to extends existing systems by adding features or interact with remote systems. In both of these cases the first thing we look for is a API (Application Programmable Interface), this is a set of functions or interfaces that allow developers to talk to the existing system and add new features or just get data in and out of a remote system.

At Univate we have been involved in a number of membership/subscription projects. To achieve we use Ubercart Recurring Payments and Subscriptions (uc_recurring), which is a module that adds recurring payments support to the ubercart ecommerce modules for Drupal. Univate has been involved in actively development of the latest 2.x branch of this module.