Features, a neat module to embed stuff in code. Keeping stuff in the database brings all sorts of ugly deployment and performance issues, so we avoid like the proverbial plague.
I'm an experienced Drupal developer. I've been embedding stuff in code for ages now. Views, Panel pages, ImageCache presets, even putting CCK content type exports in to hook_install() implementations just to try to keep stuff in code. Many of you are probably in the same boat.
We have just finished a migration job for a client of ours from an old .Net system in to Drupal, the last task of which was to write some Apache mod_rewrite conditions and rules to deal with the URLs of their old website.
So we've done all French sites before. And we've done all English sites before. But a recent project was our first real forray in to multilingual sites and it's an e-commerce/Ubercart job! Talk about gluttons for punishment!
Note: Apparently it works fine with Windows too! See comments. I'm pretty excited right now. I just tried drush make for the first time. Download it here:http://drupal.org/project/drush_make
Here's another one of my little Linux admin scripts for all you Drupal developers out there. It's a Linux shell script requiring Drush, MySQL and Subversion, but could be easily modified to work with other databases and repositories and should work fine on a Mac, I think.
Ups and downs again today. Some strong support from Europe again, but the US has yielded no strong continuation.
OpenID has been about for a while. But only when forced to really use it, did I start to understand
Important edit: Seems it doesn't work with Google Apps accounts - apologies to Zach in the comments, you were quite right. I'm revising this post. However, it does still work as described with all Google Mail domain accounts (e.g. personal Google accounts).
Update on the Helping Drupal Help Haiti campaign
Having finally sorted out our goals (use the Project EPIC Twitter syntax to get targetted information to people who can help, using Drupal as a tool for managing and organising that data), day 3 started with an ambitious set of tickets:
Update 2 on the Helping Drupal Help Haiti campaign
So we've started the second day of this project. Our mission is starting to become clearer.
You may have noticed a degree of Haiti noise on the Internet today.
Quick post today, no politics *whatsoever*. ;-) I just wrote another little batch script for deploying my Drupal sites from local to stage. Before I post the code, here's the workflow here in our office at CMS Professionals:
We often see people getting berrated for posting dupes, sometimes deservedly. Let me say from the get go that I do not, in any way, support the needless creation of noise in issue queues by people who are so lazy as to have made *NO EFFORT WHATSOEVER* to find a solution.
How to avoid duplicate content by making sure that any requests to no sub domain get permanently redirected to the correct sub domain
Quick non-Drupal, but very useful, post here. There are lots of people talking about things like this on the 'net, but I've never found my specific requirements in one place. So here they are, in one place. I'm sure other UK web developers will need them!
Quick post this evening, because I'm stopping for the day. Just a troubleshooting tip for web services. We use the excellent Drupal Services module quite a lot for integration work. Take a look, if you don't know it:
I've spent the last few days wrestling with an evil bug. I had a content type, called Card, which I could create fine when logged in as any authenticated user of any role. All cool. I should also be able to create this content as anonymous.
Edit: Please read this blog post, but also please jump in on this thread - the idea is already proposed but needs community support:http://drupal.org/node/484034
I happened across a wee bug in Views 2 today. I think I've noticed it before, and I'd be a monkey's uncle if it isn't already in the queue, but this is a synopsis:
Every time you build a new application in Drupal you *always* have to carefully govern the number of options available to normal site editors, or their heads will explode. (Literally. I've seen it.)
Tutorial on how to bring a Debian and Ubuntu server up to spec to run Drupal 6.
A few weeks ago I wrote a post about how to bring a stock CentOS 5 server up to spec to run Drupal 6. It seems only fair I do the same for Debian and Ubuntu, since it seems they too are not without their little issues when a stock install.
Yay! My first blog post with the 7.x tag! It's coming up fast, folks... Shame this one is a gripe.