There’s been a lot said and written about the most recent drama in the Drupal community, quite a few people have asked me why I care. This is hard to answer without sounding flippant in 140 characters, so I’ve taken the time to write another blog post about the topic. This one a little less angry and more reasoned than the first.
I have had many differences with the Drupal Association in the past, starting with the many clashes we had with their erstwhile leadership when we were organising DrupalCon Copenhagen 2010, so I’ll admit I wasn’t their biggest fan before the latest events.
One of the things the Drupal community prides itself on, is how open the community is. And that is generally true, but there's one exception.
And that is the Kafkaesque horror-show we subject any newcomers that would like to publish their code on Drupal.org to. It goes by the name of “Project Applications“.
Do you need to tell your visitors when you are open for business? Your office hours, when the service desk is open?
Then Opening Hours might be the module for you. In this post, I'm going demonstrate how the module can be used, as well as some of the API capabilities for extending it.
One of the more annoying things about theming Drupal sites is having
to wade through the staggering amounts of wrapping
<div> elements and
containers. Some of these are are fairly easy to get rid of. Others
require you to override core templates.
I recently found a clean way to get rid of a couple of those. These two were introduced in Drupal 7, and you will probably find them on almost all Drupal 7 sites – they look like this:
If you use a good database system, foreign keys is an actual concept on the server that is used to enforce data integrity.
With database-level foreign keys, it becomes impossible to break your data by deleting data referenced by other data, without also dealing with the referenced data.
As you may know, Yahoo! is in trouble, and has decided to jettison the social bookmarking service del.icio.us (Delicious).
I am not a big delicious user anymore (actually, I deleted my account when Microsoft was trying to purchase Yahoo!), but this recent closing made me wonder if the Drupal community couldn’t do better...
One of the great strengths of Drupal is self-hosting, and a bookmarking service is not a complicated thing.
More than a year ago, I was agitating for a move to Drupal 7 for all the blogging developers. As is rather obvious now, Drupal 7 was not in a state then for public websites. There was outstanding security issues, no upgrade path, lots of API changes to be made, etc.
However, since that has all been resolved now, I figured it was about time I moved my blog over. I have obviously been preparing for this for some time, as I will get back to in later blog posts.