Home of the Stanford Web Services Blog
Posted by John Bickar on Friday, October 31, 2014 - 2:43pm
Drupal 7.32 was released on October 15th to fix a critical security vulnerability. All Drupal 7 sites on sites.stanford.edu and people.stanford.edu were upgraded that day. On October 29th, a further Public Service Announcement was released, detailing the severity of the vulnerability and steps to take if you believe that your Drupal 7 site may have been compromised.
In this article we are going to talk about what hard and soft configuration is and how to decide between the two when creating a distribution.
Web archives are a great way to reference or recover deprecated site content. You can help to ensure that old versions of your website will be faithfully preserved by designing for archivability.
A critical security update for Drupal 7.x was released today, October 15. University IT is conducting unscheduled maintenance for all websites hosted on the Stanford Sites Drupal hosting service to mitigate this vulnerability, and no further actions need to be taken by site owners at this time. More details on what was included in this critical update can be found at https://www.drupal.org/drupal-7.32.
When we launch a site at Stanford Web Services, we open the doors and roll out the red carpet for the search engines to index the site. However, before launch we like to keep the content under wraps and ask the search engines not to index the site. To do this, we use a module called Stanford MetaTag NoBots.
Pages