Go to the Stanford University web site
Log In
(To add something to the Commons.)


Drupal is a free software package that allows an individual or a community of users to easily publish, manage and organize a wide variety of content on a website. Many people in the Stanford community have created web site using Drupal and IT Services' MySQL service. In addition to the documentation maintained on this site, you can learn about Drupal at Stanford by subscribing to the drupallers mailing list. [Subscribe to Drupallers].There is also a "sandbox" instance of Drupal called Drupal in Practice where you can experiment with new modules and familiarize yourself with Drupal administration. The site is maintained by Zach Chandler.

Drupal.Stanford.edu: Stanford Drupal Resources

Stanford has a very active and engaged Drupal community[1]. These are some of the Stanford specific resources for Drupal:

Redirect from AFS to sites.stanford.edu and exclude one directory

We have recently moved a website from /afs/ir/group/name-of-group/ to sites.stanford.edu platform with url http://new-name.stanford.edu and we wanted to redirect everything from old site to new site, except forms that are built using Form Builder.

I wanted to share our code for those who are following the same trail...

RewriteEngine On

RewriteCond %{REQUEST_URI} !/group/name-of-group/forms [NC]
RewriteCond %{HTTP_HOST} !new-name.stanford.edu$ [NC]
RewriteRule ^(.*)$ http://new-name.stanford.edu/$1 [L,R=301]

drush and PHP errors on the corns

The latest version of PHP on the corn servers (PHP 5.5.3 as of June, 2014) generates PHP strict error warnings when trying to use drush with Drupal.

To get around that issue, add the following line of code at the top of your settings.php file (right after the <?php opening statement):

ini_set('error_reporting', '0');

Features Prefix Registry

One of our major goals as a Drupal community is to facilitate the re-use of exportables, like Features (using the Drupal Features module).

There is more extensive documentation of our best practices in publicly shared google doc: https://docs.google.com/document/d/1YJykryqu2wY8K-o85dE3ev0H1rWHYHvSpqMcqwVY5yY/edit?usp=sharing

Prime Your Cache with a Cron Job

Properly configuring caching on a Drupal site is one of the most important things that a site administrator can do to improve performance. Caching represents a tradeoff between speed and "freshness" of content, however. There are some tools, such as the Boost crawler, that can prime your cache.

(See also: Load Page Cache after Cron Runs.)

Stanford Sites - Backup and Migrate Files in dev

Hi all,

For a personal stanford sites site (i.e. people.stanford.edu/mstoaks) Is it correct that the module "Backup and Migrate Files" is only available in production and not in dev (people-dev.stanford.edu/mstoaks)?


Drupal 6 to Drupal 7 Migration Worksheet

This document is a work in progress. For a formatted version of this worksheet that you can print and fill out, download the PDF.

Rationale for This Document

An upgrade of a Drupal 6 website is a complex proposition. As a general rule of thumb, many professional Drupal development teams approach a major Drupal version upgrade as a new site development project, and estimate anywhere from 60-80% of the original development resources (time, money) for the upgrade.

drush sqlq formatting

How To

Ever get frustrated about the output from 'drush sqlq'?

Add '--extra="-t"' to your 'drush sqlq' command, and get a nicely-formatted table. ("--extra" allows you to include any options you would pass to 'mysql').

(Run 'man mysql' to see more options to pass to '--extra'.)

Drupal 6 Installation Instructions

There are two ways you can run Drupal 6.x at Stanford.

Stanford Sites

Request your Drupal 6.x site on the Stanford Sites service. This is open to everyone, including individuals. Installation is easy and code updates and maintenance are handled by IT Services. You can't install your own modules or themes, but installations come with plenty of pre-installed modules chosen by the community. Read more at sites.stanford.edu.

Drupal and Virtual Host Proxies on the WWW Servers

In fall 2011, the web infrastructure team in IT Services made some changes to how virtual host (vhost) proxies are handled. Previously, all proxies were on a dedicated pool of proxy servers (proxy1.stanford.edu, proxy2.stanford.edu, proxy3.stanford.edu). This configuration required the use of the Reverse Proxy module. The infrastructure team is in the process of moving all existing proxies onto the www servers themselves.