Skip directly to content

When Running Mamp, Drupal, and Drush

on Mon, 11/03/2014 - 11:46pm

This is mostly just a reminder to myself :)

I know everyone runs into this one from time to time. I have before and reinstall MAMP infrequently enough that I forget. I always have to go throug hand remember when I get the following annoying message:

Command pm-enable needs a higher bootstrap level to run - you will need to invoke drush from a more functional Drupal environment to run this command.

So, for us who need a reminder:

  1. Make sure that export PATH=/Applications/MAMP/Library/bin/:$PATH is in  ~/.bash_profile.
  2. In settings.php, make sure that localhost is changed to
  3. Also in

Fitvids and Running Multiple Versions of jQuery

on Tue, 04/08/2014 - 10:29pm

The problem

I ran into a situation today that I finally tackled after avoiding with minor tweaks over the past year. We embed Vimeo videos throughout our site (both within the wysiwyg and using fields). Our site is responsive so I initally just used a max-width: 100%; and height: auto; rule to tame the iframes. This worked for the longest time with no issue until a recent Vimeo update that threw the videos out of wack. After fussing with it for a bit, I decided that I was going to actually take care of it the right way.


Fitvids is a great jQuery solution that adds responsive

Upgrading Drupal from 4.6 to 7? It can be done.

on Thu, 08/08/2013 - 10:29pm

Recently, I was challenged with upgrading a Drupal site from 4.6 to 7. If you're not too familiar with Drupal, you might not realize that Drupal must be upgraded one major release at a time. For those of you who are counting, that's four major version upgrades (4.6 -> 4.7 -> 5 -> 6 -> 7). This might not seem like a big deal, but depending on the site, this can be a tricky process. When you consider that with each new version, there are Drupal API changes to consider, contributed modules that may or may not be available (not to mention custom modules), and depending on how far back you go, PHP

Solr Part Two: Multicore Installations

on Wed, 07/24/2013 - 3:17pm

Always learning

Not too long ago, I wrote a post on installing Apache Solr on a CentOS. I'm in no way a Linux or Solr pro so I have figured out a couple of things over the past couple of weeks. One cool thing that I figured out was how to configure Apache Solr to run in a multicore setup. This is exactly what I needed as my organization has went from one site to three sites within the past six months. It also allows me to setup development sites that still have functional Solr searches. So, I will walk you through the solution that I came up with. 

Just so you know

Before I go into

Protecting your site with the Shield module

on Thu, 07/18/2013 - 12:05am

The shield module

Shield is a simple module that allows you to setup a domain access password for your site. I use on for development sites to prevent Google from crawling the site and to prevent accidental or sneaky visitors to the domain. What I like about the module is that it has a simple UI and just works out of the box. It's especially useful if you don't want to modify the .htaccess file and have to worry about tracking changes in git.

Don't use a module for every little thing

While I'm not a fan of using modules for every little bit of functionality when a line of code, an added