Skip to Content
Skip to Navigation

2011-04-05 Update

Updated on April 6th, 2011 at 3:15 pm

Updates

  1. The deploy script (deploy.sh) was changed so that Production deployments would pull from a new URL. Originally, the deploy script pulled from a publically-accessible location. However, some svn updates would fail due to how publically accessible folders work in SVN. The script now pulls from a location that is accessible to any NetID.
  2. Deploying Drupal.docx was changed to reflect the above update.
  3. The sonsite module was updated to reflect improvements and bugfixes to two rules, Update PathAuto and Node updated by content creator.
    • Update PathAuto was updated to make generating node aliases more efficient when Folder terms are updated—rather than simply updating every node in Drupal, it now only updates the nodes that were actually affected by the term change.
    • Node updated by content creator was changed so that updates performed by the Link Checker module wouldn’t cause the node to go into revision moderation and require approval. That is, changes made by Link Checker no longer need to be approved by a section/site editor.
  4. The image_reference module was updated. It now provides an extra field to views, Image path, which is the path to any images attached to an Image node.
  5. A number of additional modules were added into SVN.

Upgrade Path

Getting the new rules and modules

  1. SSH into your server and change to the Drupal directory (~/public_html/drupal).
  2. Run:
    svn update
  3. Flush your Drupal caches.
  4. If you’ve modified the two rules that were updated, you will need to merge the changes.

Updating your working copy’s URL (related to update 1 above)

The previous URL for the production Drupal code still works, so if you don’t want to change it, you don’t have to. However, we were encountering issues where if certain types of changes were made (e.g., svn copy, svn mv), running svn update on a working copy that was checked out at the publicly available URL would fail and foobar the working copy. So, it is recommended to switch to the new URL.

  1. Put your site into maintenance mode.
  2. SSH into your server and change to the Drupal directory (~/public_html/drupal).
  3. Run:
    svn status
    to see what files have been added or modified since your last checkout
  4. Copy any added or modified files to somewhere outside of the ~/public_html/drupal folder. Be sure to copy your sites/default/settings.php file and sites/default/files directory.
  5. Make the sites/default folder and sites/default/settings.php file writeable. You can do this by running the following:
    chmod +w ~/public_html/drupal/sites/default
    chmod +w ~/public_html/drupal/sites/default/settings.php
  6. Erase your ~/public_html/drupal folder. You can do this by running:
    rm -rf ~/public_html/drupal
    If you get any errors about not being able to remove any files or folders, make sure they’re writeable and try erasing again.
  7. Checkout the Drupal code from the new SVN location. Run:
    svn co https://svn.cac.washington.edu/son/sontier/public/drupal/current/drupal/ ~/public_html/drupal
    You may be asked for a username and/or password. Any NetID username/password combination will work, including a supplemental NetID. You may also be asked if you want to store the NetID password unencrypted; it’s up to you if you want SVN to remember your credentials or not.
  8. Move the files you copied in step 2 above back to their original location. If you had to modify any file or folder permissions in order to copy them in the first place, make sure to change them back. sites/default should be set to 0x0555 (readable and executable by all, but not writeable by anyone). sites/default/settings.php should be set to 0x0444 (readable by all, but not executable or writeable by anyone).
    You can change the permissions from the command line by once again using the chmod command:
    chmod 555 ~/public_html/drupal/sites/default
    chmod 444 ~/public_html/drupal/sites/default/settings.php
  9. Flush your Drupal caches.
  10. Take your site out of maintenance mode.