How to greatly increase the odds your patch will be accepted in two simple steps.

Armed with a few simple tools you, too, can be a superhero.

Got this error this morning. A quick burn through drupal.org didn't turn up an explanation of what, exactly, this error message means so I did a little digging. Long story short, if you're getting this error it means you've screwed something up in your module's .info file.

I recently had a client complain to me about the wording of one of their site's error pages. If a user went to user/<user id>/fbconnect and their account wasn't linked to a facebook account then they get an error message. Problem is the original wording of the message (while perfectly clear to me) was confusing the hell of of this guy's userbase. (Note: this message was removed from later versions of the module.)

Configuring virtual hosts for your local dev environment sucks, here's what to do about it.

There are several modules available that provide IP to location lookup, but sometimes you just have to write your own.

I swear I don't remember deleting the "story" and "page" content types. Maybe the Aegir installation profile did something creative. Maybe I did it and have since forgotten. Anyway I need both of those content types back on my dev server for testing. What now?

OR adventures in unintentionally case sensitive autocomplete fields

Getting it done with file_exists(), fopen() and form_set_error().

I was hanging out in #drupal-support this afternoon when an interesting question was asked: how do I redirect users to something other than /user when they log in? Having no prior experience with this I decided to dive in and find out for myself.

There's a module for that