Fri, 07/31/2015 - 10:47 by Chris Burge

Sometimes it is necessary to remove one or more items from a Webform select list. For example, a client has a registration form for an event that will travel to a number of cities. After the event has passed for a particular city, the client desires the option to register for that city to be removed.

If the client simply removes the key|value pair for a city from the 'Options' list, then the key will remain stored in the database as the 'data' value for each submission in the 'webform_submitted_data' table; however, the value will be removed because the value is stored in the 'webform_component' table. As a result, when running reports or exporting data, only the key will be available (e.g. 'boston' but not 'Boston, MA').

The solution is to modify the Webform Select List component to allow for options to be 1) removed from the select list rendered for end users AND 2) maintained for data processing purposes.

Mon, 06/29/2015 - 10:39 by Chris Burge
In this blog post, we'll move a field into an existing fieldset in Drupal 7. There is a 'Path Override' field that we want to move into the 'path' fieldset, which is created by the Pathauto module. This change must be accomplished through code, using the hook_form_alter and hook_node_update functions, because it's not possible through the UI.
Mon, 03/16/2015 - 09:30 by Chris Burge
The Image Replace module finally allows for true art direction in Drupal when paired with the Picture module. Instead of being limited to a single source image for a responsive image, multiple source images can be used.
Tue, 11/25/2014 - 07:34 by Chris Burge

Find a DNS record's TTL value by querying one of its authoritative name servers.

With the 'dig' (domain information groper) command, it is possible to look up the TTL (time-to-live) value of a DNS record. For example, you may want to lookup the 'A' record for

Thu, 11/20/2014 - 16:17 by Chris Burge

The website migration described in this post provides a real-world example of how a reverse proxy server can facilitate a website migration and eliminate the lag caused by DNS propagation.


The client's situation is summarized below:

  1. Client has a WordPress site that continuously receives user-generated content in the form of comments
  2. Client is switching marketing agencies
  3. Client's old marketing agency is also his current webhost
  4. Client's DNS is hosted by his internet service provider (ISP)
    1. To update DNS records, the client must submit a ticket to the ISP
    2. It can take up to 24 hours for the ticket to be processed and completed.

Due to user-generated content, the client can't keep the website live on both the old web server and the new web server during propagation. A user post to the old web server would be lost.


Subscribe to Blog