FAQ | This is a LIVE service | Changelog

Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • renovate/configure
  • 2.8
  • 2.7
  • 2.6
  • 2.5
  • 2.4
  • 2.3
  • 1.8.2
  • 2.1
  • 2.2
  • 2.0
  • 1.9
  • 1.8
  • 1.7.5
  • 1.7.4
  • 1.7.3
  • 1.7.2
  • 1.7.1
  • 1.7
  • 2.10.7
  • 2.10.6
  • 2.10.5
  • 2.10.4
  • 2.10.3
  • 2.10.2
  • 2.10.1
  • 2.10
  • 2.9.3
  • 2.9.1
  • 2.9
  • 2.8
  • 2.7
  • 2.5
  • 2.4
  • 7.x-2.3
  • 7.x-1.8.2-full
  • 7.x-1.8.2-lite
  • 7.x-2.1
  • 2.0
40 results
Compare
Name Last commit Last update
..
doc
CHANGELOG.md
README.md
cambridge_lite.info
cambridge_lite.install
cambridge_lite.make
cambridge_lite.profile
README.md

University of Cambridge lite install profile

This install profile contains the basics required for a University of Cambridge Drupal site (such as the University's house style and Raven authentication). It also provide a handful of the most common modules (such as Views); important patches are also applied to some modules where there hasn't been a new stable release.

Installing a new Drupal site

In a fresh copy of Drupal extract the contents of this profile to /profiles/cambridge_lite/, then follow the normal Drupal installation process. On the first screen you will see the option to use the Cambridge install profile:

Select profile

(If you have an existing site, presumably using one of Drupal's bundled install profiles, and would like to switch to this install profile, you can Google how to do it. It won't configure the site, but can be useful if you would like to use the modules provided by the profile.)

Updating the profile

New versions of the profile will be released every couple of months (sooner if there are security fixes), containing updates to modules (including patches), as well as new modules/functionality.

When updating the profile, replace the whole contents of the /profiles/cambridge_lite/ folder then run Drupal's update process.

You shouldn't normally make changes to the /profiles/cambridge_lite/ folder (including trying to updates profile-provided modules through Drupal's update manager), as you may run into problems trying to update the profile in the future.

If you do need a different version of a module to what the profile provides, however, you can override it by placing your version in your site's folder (so one of /sites/all/modules/, /sites/default/modules/ or /sites/www.mysite.cam.ac.uk/modules/). When the profile is updated to include the new version you should then remove your override and let Drupal revert back to using the profile's version.