Skip to Content
Skip to Navigation

2011-12-29 Update

Updated on December 29th, 2011 at 8:56 pm

Updates

This update contains a number of (related) changes. A new role has been added, expert users, which is similar to the advanced users role. The primary difference is that expert users, by default, have the ability to create Web Parts and use the "promote to front page" checkbox. This can be useful if you want to, for instance, allow a section editor the ability to create Web Parts in their section.

To make use of this role, you will need to create a new group in the UW Groups Service similar to what is necessary with the advanced users role. It should be named [stem]_expert-users, where [stem] is your UW Groups Service stem (e.g. uw_nursing_web).

As with the advanced users role, expert users apply across all of your domains. That is, an expert user on one of your Drupal sites will be an expert user on another, assuming they share the same UW Groups Service stem.

In addition, a new module, promote_sans_admin, has been added. This adds a new permission, promote nodes, which can be given to roles who don't otherwise have the ability to use the "promote to front page" checkbox (in standard Drupal, only roles with the administer nodes privilege can use this checkbox). This is used in conjunction with the new role described above to allow expert users to select this checkbox, as it is oftentimes used when creating Web Parts.

As always, you can change the permissions of any role to suit your specific site's needs. The above permissions are just the default.

Lastly, and more technically, the way LDAP groups are being filtered has changed. In the past, LDAP groups have been filtered and mapped to Drupal roles using a field in the ldap_groups module (which you can get to by going to Site configuration / LDAP / Groups in your administration menu). All of that logic has been moved to the son_business_rules module instead, to ease in the creation of new roles.

All new sites that you deploy will henceforth reflect these changes. Because making all of these changes to existing sites by hand would be difficult and error-prone, to update existing sites, you will need to run an update script which will make all of the above changes for you.

Upgrade Path

  1. SSH into your server.
  2. Get the new update script:
    Run svn update helperfiles/
  3. Make the update script executable:
     Run chmod +x helperfiles/update-scripts/update\ 2011-12-27\ 001.sh
  4. Execute the update script:
    Run ./helperfiles/update-scripts/update\ 2011-12-27\ 001.sh
  5. The helper script will ask you a few questions. If you have configuration settings stored (in the ~/.drupal_config.sh file), it will attempt to use those for the default answers. 

    The questions are similar to those asked when you first deploy Drupal. Please refer to the Technical Documentation for a detailed explanation of each question.
  6. The update script will then ask if it can create the new expert users role for you. If you opt not to, you will need to create a new role called 'expert users' (without quotes) and set the permissions to what is suitable for your site by hand.
  7. Lastly, update the site and flush caches:
    Run drush updatedb