Drupalwoo blog

Have you ever created a webform in Drupal and wished you could pass some info into it?  Perhaps you want to capture something about the user who's filling out the form or where they're coming from or other similar information that may be able to be passed in automatically.

Fear not!  It's quite easy to pass information into Drupal's webforms through URLs.  Just grab the variables from the URL, set them as defaults into your necessary webform fields, and even make these fields editable by the user, disabled (but visible) or hidden altogether.  That should fit just about any need you have.


About Boostrap components

What I really love about Drupal's Bootstrap theme is the fact that you get to use all of Bootstrap's CSS, icons and other fun components.

Once you've implemented a Bootstrap sub-theme, using one of the many icons, buttons, drop-downs and other components is a breeze if you just follow the examples in the Bootstrap components guide.

I will highlight just a few of the many components you will have at your disposal if you subtheme Boostrap in your Drupal (or any) site.


After re-designing my site header to be small, fixed and semi-transparent, I wanted to make sure it is also fully responsive and looks good when viewed in any environment: large, wide desktop displays; medium tablet displays; as well as the narrow (and really rather limiting) mobile displays.

In the following tutorial, I discuss my design decisions, as well as provide implementations hints and details.


I recently re-designed my blog's top header (which includes the main menu, logo and search box).  I wanted to make it fixed (so it stays in place and is always accessible even as you scroll down to read my blog posts) and slightly transparent, so you visually notice that it's following you around as you scroll.  This post is about how to implement a similar header bar.


Solving the problem of systems talking to other systems has so many applications in our world of endless information.  For our tutorial, though, let's imagine that we have a small form, either on an app or external site, which users can use to create profiles.  We want that user submitted data to be saved on our separate Drupal site in a content type called 'bio', which has very similar (though not identical) fields.  Let's get it all setup!


In this tutorial, we'll create an HTML list, which can visually and dynamically self-filter and self-sort.  We'll start by creating an unordered list whose child <li> elements have some extra attributes, effectively creating multiple sets of sub-lists in the overall list.  Once we have that HTML setup, we can use a very clever jQuery library called Quicksand which can make the overall list organize itself into its sub-lists dynamically (and attractively).  Let's get started implementing this via a Drupal 7 theme!


You can all seen the numerous examples of beautifully styled dates on blog posts which look like little calendars or attractive, interesting blocks.  In this tutorial, I'll walk you through pulling the parts of your post Drupal post dates to be displayed separately, with their own class, so you can style your date in as detailed as a way as you want!



I recently had a project, which required the search results returned by the Solr search engine used on our Drupal site to be ordered by a custom field.  The custom field was not even directly on the given node, but could be calculated through some relationships to the node.  The default sort options of ordering by title, relevancy, type, author or date just wouldn't do here.

In this blog post I will show you how I added a custom field to the Solr index and ordered our search results based on that custom field. 


Drupal Commerce was made to work for selling and buying products that have a regular set price.  There are many add-on contrib modules you can use to set a discount and other ways of modifying the price, but again, the expectation is that you're selling a product that does have some sort of regular base price.

Well, what if that's not the case?  What if you want to use Drupal Commerce to allow users to pay the invoices they owe you, for example?  In that case, you'd have a product called 'Invoice', whose price is completely unknown.  One user may need to pay a $10.00 invoice, while another may owe you $230.50.  Drupal Commerce can still accommodate such scenarios, but you will need to create some custom rules to make it work.

Follow along with this tutorial for one possible setup to accomplish invoice payments through Drupal Commerce.


Learn how to create a Paypal 'Donate' button that can be put in a block and placed anywhere on your Drupal site.

You should have a current Paypal account for this.