I came in this morning to tackle the bug from hell.
Chris Charabaruk, AKA @coldacid, is leading the charge to replicate Dan Zarella's Tweetbacks for Wordpress in Drupal.
(This may well apply to Drupal 5.x as well, but I have not tested it so for now this post is only tagged 6.x.)
I had an issue the other day born out of a misconception about the way block and page caching works.
No more phantom XML-RPC failures caused by variable type!
You may or may not be aware web services are very strictly typed (well, XML is, period). That means if you send a web service a string, e.g. '233', when it wants an integer, e.g. 233 (note the very subtle difference) it will break!
Note, Actions and Triggers are core in Drupal 6.x so this only applies to Drupal 5.x if you are using the Actions module as a 5.x contributed module:http://drupal.org/project/actions
In our team I'm as guilty of this as anyone, but we're occasionally caught out by the creation an un-managed and un-documented dependency on a module, perhaps in a theme's template.php file or even in a module where someone forgot to list the dependency in the .info file or meant to remove the fu
How to solve problems with Apache 2 vhosts?
This is worth a blog post, as it took us a while to get to the root of the problem. We had a fresh installation of RedHat (RHEL 5, to be precise) which comes with Apache 2. I'm used to having a vhosts include for httpd.conf that looks something like this:
Don't get me wrong, the documentation relating to theming for module developers in Drupal 6.x is all there and complete. The trouble is, it's spread over several different places. The purpose of this blog entry is to do a step-by-step guide to theming something in a module for Drupal 6.
These days, now the Update Status module is core in Drupal 6, people find themselves updating their core, modules and themes far more regularly than before. This is, of course, a very good thing.
I had an interesting gotcha this afternoon. With Drupal 6.x came a new hook, hook_boot(). It supercedes the !$may_cache behaviour in Drupal 5.x by providing a hook that any code which *must* run on all pages, cached or otherwise, can be placed in.
The other day I expanded on someone else's blog about load testing Drupal with JMeter, by writing about how one can submit forms, and as such potentially handle deployments, with Drupal.
I've finally updated this site to Drupal 6.6. It's using a new theme, because my old one isn't ready yet. I may port it myself, as my girlfriend says she liked the green, but for now it's grey and claret. Hope you like the new colours!
Here's a really nasty little gotcha! You have a load of content, all of the same type. You give a role permissions to edit any nodes of this content type, but it gets all weird. Some of the content they *can* edit. Some they cannot. Node access!?! No. Much simpler than that.
What's worse than having a problem with your version control software?
There is nothing worse than having a problem with your version control software. Normally you can just nuke your checked out code and re-check it out, but sometimes (like in my case right now) that's not an option because you have loads of site-specific settings and folders in place.
Just a quick one to report the famous SourceForge has become a Drupal website, as reported by Dries in his blog. The list of high profile Drupal sites grows and grows. That's all for now.
If you type Drupal and JMeter in to Google, you'll probably turn up this useful blog post fairly quickly:
I've just started using the SOAP Client module in Drupal to handle SOAP requests. It's a great little tool.
Greg Harvey examines why Drupal is sometimes perceived as an expensive system.
I am in the process of setting up my own Drupal-based development business. I get a lot of contact through my website, LinkedIn, Drupal.org and many other places - more than I can actually field. Which is wonderful, but saying "no" all the time feels like a huge missed opportunity.
I'm currently working on a multi-site Drupal installation. There is one theming module shared by all instances which exposes some key blocks and views they all require. During development, this was built on the initial site, so occasionally you will find something like this in the module: