If you spend a lot of your day at the command line (as I do), you're constantly on the lookout for new tools and tricks to increase your productivity and efficiency. Today we're going to take a look at the pushd suite of commands that exist in most shells (e.g., bash, tcsh and so forth).
In this post, I'll walk through how to enable and configure the module, use it to shout, "Hello, World!", and then go into some more advanced configuration.
To use the module, you must enable it. This module has recently been installed on Stanford Sites and does not get enabled by default.
As a follow-up to my post on configuring your Drupal site for improved performance, in this post I will detail how to go a little further using the XML Sitemap module to create a sitemap, and then using the ITS Scheduling Service to set up a cron job to "prime" the page cache for all pages in the sitemap.
The modern Web is a dynamic place. However, sometimes it's necessary (or desirable) to remove the dynamic functionality of a website, while preserving its static content.
Inspired in part by Karen Stevenson's excellent blog post, "Sending a Drupal Site into Retirement," I wanted to outline a few other techniques for accomplishing this.
Reasons you may want to create a static copy of a site:
Sometimes, however, in developing a custom module, you want to provide a suggestion for an HTML framework, and not rely on the theme's default implementation of a given block of HTML.
You may ask yourself:
Can I use .tpl.php files in a Drupal module?
(And you may ask yourself, "How do I work this?", and you may ask yourself, "Where is that large automobile?")
In August, 2013, the Administration Views module was updated from 7.x-1.0-alpha1 to 7.x-1.0 on Stanford Sites. This update has the potential to cause several issues, manifesting in one or several of the following ways: