By Erik, 29 May, 2011

(No drush!?!? #inconceivable)

With all of the fancy ways to upgrade Drupal core floating around: drush, git, diff, patching. What if you only have FTP?

As always, the first steps are to a) plan, b) backup, and c) be flexible.

It always helps to have a plan. Write it down, think it through, practice on something other than your production site.

By Erik, 26 May, 2011

When new security releases come out for Drupal, updating is definitely something that you want to do sooner rather than later. My philosophy has generally been to update my local setup immediately, let all of our developers/users know that I am going to update the shared dev server within two days, then schedule a time to update production based on any issues we find with the dev server. Since we run most of our sites as a rather large multisite, it means updating everybody at once, but hey, that's what dev's for, right? Well, we'll leave that for another discussion.

By Erik, 23 May, 2011

Recently, we have been moving away from using sites/all to store modules and themes because we heavily use multisite setups and need to keep the sites contained and independent.

To change a site away from using sites/all, I djinn'ed up a drush command that looks to see what's being invoked from sites/all.

By Erik, 11 November, 2010

So I have set up my localhost with MAMP and I don't want to muck about with Dynamic DNS or constantly editing my /etc/hosts file to be able to bring down Drupal sites from multisite installations on our company servers.

At work, we run a bunch of Drupal sites out of a single Drupal code-base (aka multisites). There are lots of domains, subdomains, etc. There's no problem at work for this, we've got it under control, but when I want to pull one of those sites down to my Macbook to do some playing, I have to do things a little differently.

By Erik, 3 November, 2010

Typically, upon login, users are directed to the page from which they logged in. If that is "/user" then you are brought back to the user profile page. If you would like people to be sent to specific pages after logging in, there are a couple of modules that can help. LoginToboggan (http://drupal.org/project/logintoboggan) is one of the most common login tools, and as the project page shows, it does many different things from allowing users to login with their email address, giving you a small horizontal login block.

By Erik, 27 September, 2009

I had a question posed to me about how to change the "Request new password" text on the User Login block, so I did a little investigation and came across a great article by Addison Berry of Lullabot that did basically what I wanted, but only to a different form.

By Erik, 8 September, 2008

I remembered in the morning that my father had at least one if not all of the Pirates of the Caribbean movies on DVD. So off to my parents house to raid the movie Library. While there, I got the second and third Pirates movies, the second Matrix movie (just in case there was something about the Oracle from the Matrix) and just for good measure, a new Dilbert book.

I watched the third Pirates movie first because it was "At the End of the World" and about half way through got to this dialog:

By Erik, 7 September, 2008

So on my actual birthday, I thought briefly of going on my quest before work, leaving at 5:30am or so. But fate, tiredness, and kids who needed to get ready for the first day of school put a damper on those plans. So I remained patient and waited until my important meetings were over at work and decided that on my birthday, I could leave a little early. At 3pm, I left for Ipswich. It was a beautiful day to be on the road with the windows down and the country music playing.

By Erik, 5 September, 2008

I got one of the coolest presents this year. My brother gave me:

  • two photographs
  • a hand-scrawled piece of paper
  • and a locked box without a key

A Treasure Hunt!

By Erik, 27 March, 2008

I have two Elements that I have in $RT_HOME/local/html/Elements

  1. QuickSearch
  2. OwnerSummary

which serve to expand the Quick Search sidebar to include ticket owners and the number of tickets in their queues. The list of Queues is editable and it seems to work well to keep a fairly quick view of the status of tickets that are owned.

These Elements work for me, but I haven't done any testing to see if they are really bullet proof for everyone. Feel free to use and adapt as you will.