The project I'm currently working on requires different registration paths and logic for users with different roles. The heavy lifting of having different paths for the registration page, different form elements to collect profile data, and also the final role assignment is done with the Profile2 Registration Path module. But one piece was missing.

Recently I came across something that feels like a bug in the jQuery Update module. The current version allows to specify a modern jQuery version to use for a site, which is awesome when you want to include modern user interface functionality using jQuery UI. Additionally the module allows to override the jQuery version that should be used, but only for admin pages (introduced after a rather long issue discussion).

Sometimes I just want to display specific pieces of information in, say, a node view. For styling reasons it is often preferable to have the same kind of basic wrapper markup as for fields. This would be particularly useful for pseudo fields that can be declared using hook_extra_fields. Those pseudo fields act almost like real fields in the Fields UI, meaning I can position them just like real fields, put them into groups, etc.

I just wanted to migrate a database from my dev server to my local environment (after having updated from OS X 10.6.8 to 10.9 the other day) and was surprised that the restore on my local machine silently failed. No error message, nothing. First I guessed that this had something to do with permissions in the file system. I checked and everything was fine. So where to look next?

Modules like Better Exposed Filters can help you create great user experiences for accessing all the content you want to be found on your website using views filters. Something that I have often missed though, is the ability to have multiple exposed filter blocks, e.g. one in the sidebar, with a subset of filters, and then another one directly above the search results that provides additional filters and / or options that control the display of the search results. All that good stuff that is already built into views can only be displayed in one block. I know I'm not the only one missing this so I decided to give it a try and solve this problem in way of a module.

During development I often need to know what a fully build views query looks like. There are several ways to accomplish this, but unfortunately none of these really worked for me, so I build my own.

Ok, so I read this blog post.
And although I find the argumentation in parts a little exaggerated, I can still see the point. So I have set up this blog (thanks to the author of the other blog post for the theme). Let's see if I can integrate writing posts into my daily work flow.